Integrate Collabora online preview with our Dashboard view

Closes https://code.vereign.com/code/dashboard/issues/354

@igor.markin @viktor.popov Could you review?

added 1 commit

• 934e212e - Refactor collabora discovery

Compare with previous version

added reviewed label

resolved all discussions

added needs review label

added 1 deleted label

removed needs review label

added 12 commits

• 934e212e...04ce9979 - 8 commits from branch master
• 16721087 - Pass collabora host url to the VCL initialization
• b8efc5e9 - Added collaboraDiscovery method
• 0af9bb8f - Refactor collabora discovery
• b9e3ee93 - Fix the issue that browsers that still cache iframe and at the same time don't…

Compare with previous version

@alexey.lunin do you have any idea why browsers can have outdated cached iframe, but it's okay with client? When we checked it with Olgun, they both have headers Cache-Control: must-revalidate max-age 1.

@igor.markin I saw this behavior earlier. I had to reset request's cache with chrome dev utils in the network section. I remember I saw cache-control: public for the vcl/js/iframe and vcl/js/client (or may be for at least one of them).

So, I think browser still think that the above requests should be loaded from the disk.

<meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> May be adding it to the header will help

@alexey.lunin but no-cache cancels must-revalidate. Shouldn't we just leave must-revalidate here?

Yes, true. http-equiv not necessary in our case

assigned to @gospodin.bodurov

added ReadyForMergeInMaster label

merged

mentioned in commit 01e002d2