nginx serving wrong proxy content, static assets not affected

Eduardo Kortright ekortright at ewtn.com
Fri Jan 6 20:50:17 UTC 2023


Hi Payam,

I’m not doing any caching.  It looks like it is indeed a DNS problem, as the Docker containers are occasionally changing their IP address as the containers are restarted, but as Ángel pointed out, nginx does not resolve the name at each request, but only when it loads the configuration initially.  Thank you for your help.


Sounds like you are either having hash collisions or incorrect dns resolution.

- Are you caching? Set a larger key size
- Have you looked at dns and host resolution for the impacted requests?

—
Payam

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20230106/d0889f6d/attachment-0001.htm>


More information about the nginx mailing list