Skip to content
Snippets Groups Projects
Commit b9e3ee93 authored by Alexey Lunin's avatar Alexey Lunin
Browse files

Fix the issue that browsers that still cache iframe and at the same time don't... 

Fix the issue that browsers that still cache iframe and at the same time don't cache client raise an exception because collabora parameter is not defiled
parent 0af9bb8f
No related tags found
1 merge request!20Integrate Collabora online preview with our Dashboard view
Hide whitespace changes
Inline Side-by-side
  • Igor Markin @igor.markin ·
    Maintainer

    @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.

    Edited by Igor Markin
  • Alexey Lunin @alexey.lunin ·
    Developer

    @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.

  • Alexey Lunin @alexey.lunin ·
    Developer

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

  • Igor Markin @igor.markin ·
    Maintainer

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

  • Alexey Lunin @alexey.lunin ·
    Developer

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

0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment