Welcome! Log In Create A New Profile

Advanced

Re: proxy_cache incorrectly returning 304 Not Modified

Jon Leighton
January 10, 2014 11:38AM
Hello!

On 10/01/14 16:06, Maxim Dounin wrote:
> Note though that nginx doesn't understand "Vary: Accept-Encoding",
> and will return cached response regardless of client's
> Accept-Encoding. To make sure gzipped responses aren't sent to
> clients without gzip support you should either disable caching of
> such responses, or switch off gzip of your backend (e.g., with
> "proxy_set_header Accept-Encoding '';"), or switch on gunzip in
> nginx (http://nginx.org/r/gunzip).

Thanks, this is the conclusion I came to also. Also I agree about
Pingdom probably just not making it clear that the response was all binary.

I am hopefully going to solve it by putting the compression method
(based on Accept-Encoding) in the cache key. Not sure if the 304 issue
will come back but it's a step in the right direction at least.

Thanks,
Jon

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

proxy_cache incorrectly returning 304 Not Modified

Jon Leighton January 08, 2014 09:58AM

Re: proxy_cache incorrectly returning 304 Not Modified

Maxim Dounin January 09, 2014 09:48AM

Re: proxy_cache incorrectly returning 304 Not Modified

Jon Leighton January 10, 2014 07:20AM

Re: proxy_cache incorrectly returning 304 Not Modified

Jon Leighton January 10, 2014 07:56AM

Re: proxy_cache incorrectly returning 304 Not Modified

Maxim Dounin January 10, 2014 11:08AM

Re: proxy_cache incorrectly returning 304 Not Modified

Jon Leighton January 10, 2014 11:38AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 303
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready