Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache purge and vary header with new Nginx #36

Open
vedranf opened this issue Jun 9, 2015 · 2 comments
Open

Cache purge and vary header with new Nginx #36

vedranf opened this issue Jun 9, 2015 · 2 comments

Comments

@vedranf
Copy link

vedranf commented Jun 9, 2015

Hello,

Nginx will save response to different cache files when Vary: Accept-Encoding is set. That is, one will be uncompressed, other compressed. This module will delete only one version of the file, making it partially usable. This was added in nginx changeset 60fde1bc7236:

http://mailman.nginx.org/pipermail/nginx-devel/2014-October.txt

Changes with nginx 1.7.7 28 Oct 2014

*) Change: now nginx takes into account the "Vary" header line in a
   backend response while caching.
@kyledrake
Copy link

FWIW, I had a flavor of this issue with nginx 1.6.2. It would serve the gzipped version even if the client did not request it via Accept-Encoding.

I "fixed" it by turning off upstream compression, but it's obviously not ideal.

@senj
Copy link

senj commented Jul 8, 2016

Can I remove both versions with this plugin manually?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants