Viewing 5 replies - 31 through 35 (of 35 total)
  • Thread Starter Aleksandar

    (@aivanov12)

    Please tell me the following.

    I currently have BrowserCache enabled in the plugin and set it to expire at 31557600 seconds. Where can I see in the browser console the number 31557600 seconds. Because I can’t find it anywhere… It’s set in the settings, but it’s not there.

    I have also set Cloudflare to “Respect Existing Headers”.

    No matter how I change the settings, I see the same numbers in the console.

    I note that at the server level I don’t have any custom headers set that would cause a conflict.

    @aivanov12

    You must read what @qtwrk writes.

    <FilesMatch “\.(ico|pdf|flv|jpg|jpeg|png|webp|gif|js|svg|mp4|css|swf)$”>
    Header set Cache-Control “max-age=31557400, public”
    </FilesMatch>

    The code above has only affect on static sources and only this is what is about. The first entry in the list of requested sources is the main document. This main document may not be cached by browser and that’s why the main document has its own setting for cache-control. Ignore this main document. It is only about static sources like CSS, Javascript, images and so on.

    If you want proof if the cache-control header is set, click on any static source like CSS and check the header for cache-control. This header is one of the first header in the list of all headers.

    Plugin Support qtwrk

    (@qtwrk)

    forget about the .htaccess directive

    if you are using OpenLiteSpeed, you need to follow this guide https://openlitespeed.org/kb/how-to-set-up-custom-headers/

    Thread Starter Aleksandar

    (@aivanov12)

    Thank you. I have applied the directions in this guide. But that didn’t change anything.

    Plugin Support qtwrk

    (@qtwrk)

    please screenshot me your context setting , and make sure you have modified the correct virtual host

Viewing 5 replies - 31 through 35 (of 35 total)
  • The topic ‘The browser cache timeout is not running’ is closed to new replies.