Hi!
> > > proxy_next_upstream error timeout invalid_header http_500 http_502
> > > http_503 http_504 http_404;
>
> What you describe looks very familiar - there was such a bug which
> manifested itself with backup servers and proxy_next_upstream
> http_404. It was fixed in 1.3.0/1.2.1 though:
>
Hello!
On Sat, May 11, 2013 at 04:13:38PM +1000, Daniel Black wrote:
[...]
> > A request for /img/file_doesnt_exist.jpg results in the backend server
> > (192.168.129.90) getting continuous requests for the same file (which
> > doesn't exist there either so 404 each time), while the original
> >
Just to prove I'm not making it up (even though I'm having a hard time
replicating it).
log_format extended '$remote_addr - $remote_user [$time_local] '
'"$request" $status $request_time $body_bytes_sent '
'$upstream_cache_status $upstream_addr $upstream_
A request for /img/file_doesnt_exist.jpg results in the backend server
(192.168.129.90) getting continuous requests for the same file (which doesn't
exist there either so 404 each time), while the original requester waits and
nginx keeps asking the backend the same.
I'm using the nginx-1.4.1 f
