Cache-control header


(Douglas (@finnatic at @waikato)) #1

We have caching turned on with the 'Browser Cache Expiry' set to 86400. With some pages however we're using the 'root node specific' option to customise the caching for those pages, and on one of those pages I've set the 'Browser Cache Expiry' to 60 instead.


Despite that, the response headers that I can view (using the Firefox Web Developer Extension) include:


[quote]Cache-Control: max-age=86400, public[/quote]



Is it the customisation and cache manager that control that? Or should I be looking somewhere else?


How do we control the cache headers of an asset?
(Douglas (@finnatic at @waikato)) #2

Referring to the manual again:


http://manuals.matrix.squiz.net/system-management/chapters/cache-manager


[quote]You can modify the following settings for each root node:



Browser Cache Expiry: set the length of time (in seconds) that the selected root node is cached in the browser. Once this time has lapsed, the page will be considered expired. The default settings is the value that is entered into the Browser Cache Expiry field on the Details screen. To revert back to this default setting, select Use Default and click Commit.[/quote]



I've reviewed the root node customisation we have and believe I've found the source of my problem. The asset we're trying to customise is the Index page for the site in question e.g. www.waikato.ac.nz/example/ - except that the actual page is www.waikato.ac.nz/example/home, and that's what the customisation is applied to.



Checking www.waikato.ac.nz/example/home separately, I can see the expected response header:


[quote]

…Cache-Control: max-age=60, public…[/quote]



I've created an additional customisation for the site, with no inclusion of assets, which seems to work as a solution.



It does leave me wondering however if it is safe to have the Index page for a site without a web path set for it?