• Resolved 34sfdsdsds

    (@34sfdsdsds)


    I’m using Hummingbird Page Caching and my http headers currently output:

    cache-control: max-age=3600, must-revalidate

    Does that mean that, every hour, WordPress & Hummingbird generate a fresh cached copy of a given page? If so, is there a way to increase that length of max-age? I see that option for RSS, but not for HTML Page Caching.

    Or is it actually that, every hour, a browser checks for a new fresh cached copy of the page, sees that there isn’t one, and instead just uses the copy that already exists?

    I tried to override that max-age by adding the below to my htaccess, but that only added a second cache-control header, and I think browsers simply defaulted to the lower hour-long cache value.

    <FilesMatch “\.(html|htm|php)$”>
    Header set Cache-Control “max-age=31536000”
    </FilesMatch>

    Thanks in advance for any help!

Viewing 4 replies - 1 through 4 (of 4 total)
  • @34sfdsdsds,

    You should be able to control that setting from the Browser caching module in Hummingbird.

    Best regards,
    Anton

    Thread Starter 34sfdsdsds

    (@34sfdsdsds)

    In Hummingbird -> Caching -> Browser Caching, the file types listed with expiry configuration options are: CSS, JavaScript, Media, Images, Cloudflare. All are currently set to 1 year. There is no Text/HTML file type listed and therefore no expiry option. Lower on the page is an Expiry Time drop down, but it says it is for “JavaScript, CSS, Media, Images,” not text/html. It is currently set to 1 year.

    In Hummingbird -> Caching -> Page Caching, I have caching turned on for different page types in WordPress, but there are no options on that page that I can see to modify the expiration/max-age time of those page types. Hummingbird -> Caching -> RSS Caching has an option, but Page Caching doesn’t have an option that I see.

    For “text/html” file types, how do I change Hummingbird’s max-age of “cache-control: max-age=3600, must-revalidate” (I think it is coming from one of Hummingbird’s class files, but obviously I don’t want to edit those) to something other than 3600?

    @34sfdsdsds,

    There’s no need to re-define an expiration value for Page Caching. Hummingbird auto tracks changes that are made to pages/posts/etc and will auto clear outdated caches.

    To answer your original question:

    Does that mean that, every hour, WordPress & Hummingbird generate a fresh cached copy of a given page?

    No, that does not mean that WordPress will generate a fresh copy for a given page at this interval. It means that a user’s browser will need to revalidate the cache after this time and either refresh the cache or extend it for another max-age period.

    Best regards,
    Anton

    Plugin Support Pawel – WPMU DEV Support

    (@wpmudev-support9)

    Hello @34sfdsdsds

    Hope you’re doing well!

    We’ve not heard from you in a while. I’ve marked this ticket as resolved for now, but if you need anything else at all, we’re here for you, please just reopen the ticket or create a new one.

    Kind regards,
    Nastia

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Help with cache-control’ is closed to new replies.