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 c
On 10/01/14 12:18, Jon Leighton wrote:
> Do you know of any reasons why the response might be blank? I copied the
> cache file so I could review it, and I checked that the X-Request-Id
> matches so it's definitely the same entry. The cache file *does* contain
> the response body
Hello Maxim,
Thanks for your reply.
>> Does this look like a bug? Or could it be a configuration issue? I can't
>> think of any reason why this should be the correct thing for the proxy
>> cache to do.
>
> This easily can be a result of a misconfiguration (e.g.,
> proxy_set_header used incorrect
Hi there,
I work on a site which has nginx in front of a Rails application, and we
use proxy_cache.
For the home page, our application returns a "max-age=600, public"
Cache-Control header, and we have nginx configured to cache the response
using proxy_cache.
This generally works fine, but last n
