Welcome! Log In Create A New Profile

Advanced

Re: RE: Proxying setup delivering wrong cache entry in some edge cases

December 03, 2018 11:55AM
Thanks for your answer and apologies for the long delay.

How would the $http_host ever be empty? If I make a request without it I receive a 400 Bad Request as the HTTP spec defines it. Does Nginx still forward the request to the upstream server and populate a cache entry?

Additionally, if I make requests to our backend without a proper X-Forwarded-For header I will always receive a 404 and not data for a wrong domain.

Unfortunately we're still not able to reproduce the problem on our end, but still receive complaints from users encountering the problem.

We removed all caching from the problematic endpoint, but the problem still seems to persist. Are there any known conditions, where Nginx would pass on a wrong host to the upstream server for any kind of reason?
Subject Author Posted

Proxying setup delivering wrong cache entry in some edge cases

benzimmer October 15, 2018 02:23PM

RE: Proxying setup delivering wrong cache entry in some edge cases

Reinis Rozitis October 16, 2018 06:04AM

Re: RE: Proxying setup delivering wrong cache entry in some edge cases

benzimmer December 03, 2018 11:55AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 287
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