What has started disallowing caching of pages and CSS?

Our QA is Matrix->Apache->squid.


Previously this has been configured so that squid caches everything and it was doing just that. Something has changed recently, post a 3.22.3->3.28.0 upgrade that has seen the cache related headers for just pages and CSS files changed to:



Cache-Control no-store, no-cache, must-revalidate, post-check=0, pre-check=0, must-revalidate

Pragma no-cache



Other file types have the expected cache headers.





Note, Matrix config is currently:



define('SQ_CONF_SEND_CACHEABLE_HEADER', '1');

define('SQ_CONF_SEND_LAST_MODIFIED_HEADER', '1');

define('SQ_CONF_SEND_NOT_MODIFIED_HEADER', '1');

define('SQ_CONF_SEND_NO_CACHE_HEADER', '0');



Also, there are no Root-Node specific directives and I have removed all Type-Code specific directives.



Where do I start looking?

[quote]
Our QA is Matrix->Apache->squid.



Where do I start looking?

[/quote]



The settings you posted are the same you used for the old version?



I presume you have checked the headers coming directly out of Matrix (before Squid)?



Did you upgrade Squid at the same time, by any chance?



You could look in the Apache config - I assume this was not changed, but you can override headers there.



When you say pages, do you mean standard page assets, or all HTML pages? If it is all HTML then that would suggest Apache or Squid settings.

@rhulse: Good tip about checking without squid in the chain. It appears that Matrix is not sending the correct headers.


Yes, it's only on "Standard Pages" and CSS files. Javascript files, images and flash files are all showing the correct caching headers. Weird. I'm going to put it down to squid but it's not reproducible and only occurs occasionally so I'm moving on.