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
> If that is not doable, then possibly you could patch your nginx to accept
> this invalid header; or possibly you could try some other config-based
> manipulation to make things work the way that you want. I suspect that
> either of those is likely to be more work in the long run than fixing
> the
On Wed, Jan 01, 2020 at 07:19:48AM -0500, ohbarye wrote:
Hi there,
> Hi, I'm using nginx as a reverse proxy and found a behavior that I wouldn't
> expect.
> So my question is: Is it expected behavior that nginx removes strong etags
> on gzip compression?
No, but: the thing that your upstream se
On Tue, Dec 31, 2019 at 06:24:18AM -0500, hmahajan21 wrote:
Hi there,
> Yes my question is why ngnix override the header and append double host in
> host header
Thanks.
What is the nginx config that is used?
Your test request will be handled in one server{} block, and eventually
in one locatio
