DownstreamCachePurgeLocationPrefix removes cache headers for .pagespeed. resources #652
Comments
oschaaf
added a commit
that referenced
this issue
Apr 1, 2014
- Make kPreserveOnlyCacheControl do what it says on the tin - Serve pagespeed resources with the response headers computed by PSOL regardless of whether downstream caching is configured. Fixes #652
oschaaf
added a commit
that referenced
this issue
Apr 2, 2014
- Make kPreserveOnlyCacheControl do what it says on the tin - Serve pagespeed resources with the response headers computed by PSOL regardless of whether downstream caching is configured. Fixes #652
oschaaf
added a commit
that referenced
this issue
Apr 10, 2014
- Make kPreserveOnlyCacheControl do what it says on the tin - Serve pagespeed resources with the response headers computed by PSOL regardless of whether downstream caching is configured. Fixes #652
oschaaf
added a commit
that referenced
this issue
Apr 10, 2014
- Make kPreserveOnlyCacheControl do what it says on the tin - Serve pagespeed resources with the response headers computed by PSOL regardless of whether downstream caching is configured. Fixes #652
|
Confirmed fixed per email |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As reported at ngx-pagespeed-discuss:
Adding this line to nginx.conf makes the cache headers disappear for .pagespeed. resources:
pagespeed DownstreamCachePurgeLocationPrefix http://localhost:80/;According to @anupamadutta:
"Regarding Expires header, I am wondering if https://github.com/pagespeed/ngx_pagespeed/pull/555/files could have anything to do with this. This was intended to be applied for HTML only, but I don't know if it happened to somehow get rid of Expires (and other headers) for other resources as well. Could you take a look?"
The text was updated successfully, but these errors were encountered: