On 12 Sep 2013 14:06, "ochronus" wrote:
>
> Thank you again for your exhaustive answer.
> I think I won't drop HAProxy so soon ;)
As an aside, I'm pretty sure HAP doesn't do /anything/ meaningful with
etags as it doesn't examine response bodies' content, nor does it cache.
Very happy to be told o
Thank you again for your exhaustive answer.
I think I won't drop HAProxy so soon ;)
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,242807,242812#msg-242812
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Thu, Sep 12, 2013 at 08:07:00AM -0400, ochronus wrote:
> Thanks a lot for the quick response!
> Indeed, I had gzip turned on globally.
> This is still strange though, is there no way to pass the Etag header from
> the upstream in this case?
The ETag header used in it's strong from mean
Thanks a lot for the quick response!
Indeed, I had gzip turned on globally.
This is still strange though, is there no way to pass the Etag header from
the upstream in this case?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,242807,242810#msg-242810
Hello!
On Thu, Sep 12, 2013 at 07:07:29AM -0400, ochronus wrote:
[...]
> My problem is that nginx deletes the ETag header from the response even if I
> specify proxy_pass_header ETag.
> The upstream server does return the correct headers:
The ETag header is removed if nginx changes a response r
I have a simple config that proxies to/from a django app:
upstream django_app{
server 127.0.0.1:4567;
}
server {
listen 80;
server_name x;
location / {
proxy_pass_header Set-Cookie;
proxy_pass_header ETag;
proxy_pass http://django_app;
}
}
My
