Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Combined CSS not cacheable (Cache-Control: max-age=300,private) #1080
CentOS 6.6 - mod_pagespeed 184.108.40.206-4448 - Apache 2.2.15
After enabling CoreFilters on a website, I noticed CSS are not cacheable whereas other resources managed by mod_pagespeed (images, scripts are). Here's our test URL: http://reunion.orange.fr/meteo/?PageSpeedFilters=rewrite_css,combine_css
Here's our architecture:
And our configuration:
Any clue what's happening?
I have a stylesheet which is cacheable: https://cdn.orange.re/assets/css/A.print.css,qts=1418037241.pagespeed.cf.GhUTE4B2Xp.css
FYI, the original IP and User-agent is exposed to the Apache server (using mod_rpaf for the original IP).
Hi -- a typical problem we've seen in the past resulting in PageSpeed
I can describe more in detail about how that happens if you are
We have seen this problem before with Cloudfront stripping
On Fri, May 15, 2015 at 1:04 AM, Julien Tessier firstname.lastname@example.org
Thanks for your feedback. User-Agent/Accept is forwarded all the way to the origin server but a couple of extra headers are added in between (prefixed by "X-") and Host is changed to "reunion.orange.fr" and HTTPS is converted to HTTP. Headers are lower-cased because we are using SPDY on the CDN.
I set up an example here: https://cdn.orange.re/tests/headers.php.
Please note the CDN caches files using their filename, so this may be an issue if the same filename is served to webp and jpeg browsers.
By default, PageSpeed puts webp-related CSS/images into different filenames
I am wondering whether the http/https switch might change the computed
On Fri, May 15, 2015 at 9:48 AM, Julien Tessier email@example.com
I'm experiencing the same issue. I got one server for the cdn and 3 webservers. All of them have pagespeed activated. The webservers are accessing to a cloudfront directly which origin is the CDN server. I get cc:private,max-age=300 only for webp assets. here is an example : https://cdn2.jrcigars.com/images/banner/1485963901632-1.jpeg/640/x400.pagespeed.ic.IpbcEckH0_.webp
Does that make sense? I found on one of your other reply that all instances should have exactly the same pagespeed config, can you explain that? My CDN doesn't have the same configuration as the 3 webservers. Is that the issue? To what extend should it be similiar?
We're having this issue right now! Please check:
what is causing that?