Response Sent To Wrong User

[Yaoxing]

Yes I found it in the cache directory. Seems like a bug of proxy_cache. 
And I find a solution by changing the last lines to
location ~* (details\.dx)|(products\.dx)|(instantbuy\.ashx) {
proxy_cache www;
proxy_pass http://cluster;
}
location ~* \.(jpg|png|gif|css|js) {
proxy_cache www;
proxy_pass http://cluster;
}
location ~ . {
proxy_pass http://cluster;
}
So that I cache only the specified types and pass all the other requests 
to the server. Compare to previously, I pass specified types and cache 
all the other types. This ways it works no matter how heavy the stress 
is, according to my stress testing. So I put the 2 nginx gateways online 
last night. Seems to be alright until now, a lot of 504 though.
If your configuration is similar to mine, I think you'd better change it 
this way in case there's any problem. Let me know if you need the 
testing tool I use. It's written in several hours, shitty but works:)

Regards,
Yaoxing


于 2010/2/9 6:05, nginx-request at nginx.org 写道:
> ------------------------------
>
> Message: 5
> Date: Mon, 8 Feb 2010 08:37:59 -0600
> From: Ryan Malayter<malayter at gmail.com>
> To:nginx at nginx.org
> Subject: Re: nginx Digest, Vol 4, Issue 21
> Message-ID:
> 	<5d7f07421002080637l36a1639dh13b7c57e76393347 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Sat, Feb 6, 2010 at 12:08 AM, Yaoxing<yaoxing.zhang at gmail.com>  wrote:
>    
>> >  Sure. I also tried nginx 0.8.33, same problem.
>> >  I use output cache for some other pages but not for this problem page. Once
>> >  I should get Nginx work properly, I think I'll remove output cache from
>> >  those pages so that I can reduce stress of IIS.
>> >  Any way, here's the config file. And I'm keep testing. I'll let you know if
>> >  I find any solution.
>>      
> I can't see anything wrong with that configuration from my reading of
> the documentation. The only thing different from my own configuration
> would be proxy_cache_valid being unqualified and defined at 60m.
> Can you run a grep -r against all of  /www/cache to see if the page in
> question is being written to cache at all? If it is, then it seems
> like there is a bug in proxy_cache. If there isn't, then it seems like
> the bug must be in some other part of nginx (or even IIS).
>
> -- RPM