To francis Thank you for your answer. > the thing that your upstream sends is not a thing that nginx recognizes as a strong etag. > The HTTP/1.1 RFC (https://tools.ietf.org/html/rfc7232#section-2.3) says that the etag header must be of the form Oh, I wasn't aware of the thing. > The best fix in your case is probably to change your upstream to send valid headers. I tried maby ohbarye - Nginx Mailing List - English
Hi, I'm using nginx as a reverse proxy and found a behavior that I wouldn't expect. According to some references below, I assume nginx would downgrade strong etags to weak ones when it modifies response content (e.g. gzip compression). But nginx removes strong etags on gzip compression instead of a downgrade. - http://nginx.org/en/CHANGES (See "Changes with nginx 1.7.3 08 Jul 2014"by ohbarye - Nginx Mailing List - English