You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
"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:
- 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
- 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
- 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
- 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
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: