Interestingly, this will teach me not to leave out "irrelevant" bits of my config files when posting them. My configs failed to include a few items like ModSecurity, because it didn't occur to me that they could have any impact on the problem I was describing. As it turns out, disabling ModSecurity solved the problem. I'm still not sure why ModSecurity is causing NGINX to serve bad data on reloads, but it's clearly a ModSecurity issue or a problem with the communication between ModSecurity and NGINX.

BH


-----Original Message-----
From: nginx-bounces@nginx.org [mailto:nginx-bounces@nginx.org] On Behalf Of Maxim Dounin
Sent: Wednesday, February 26, 2014 1:12 AM
To: nginx@nginx.org
Subject: Re: Odd issue with proxy_pass serving wrong cached data

Hello!

On Wed, Feb 26, 2014 at 02:32:25AM +0000, Brian Hill wrote:

> So now it doesn't look like it's a caching issue at all. I've
> completely gutted my config files and stripped it down, and I'm still
> seeing the same issue. I even shot a video of what I'm seeing and
> stuck it on YouTube as an example (http://youtu.be/lPR1453YBUw). As
> the video shows, the connections for the linked images don't load
> properly on reloads if I'm connecting through the NGINX server, but
> work fine if I connect directly to the backend origin server. Has
> anyone ever seen anything like this? Any ideas?

Looking into logs usually helps a lot.

Symptoms suggest most likely you've run out of local ports on nginx host due to sockets in TIME-WAIT state (and you have no tw_reuse/tw_recycle switched on), but it's hard to tell anything exact from the information you've provided.

--
Maxim Dounin
http://nginx.org/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx