Re: catching 408 response from upstream server

2015-02-11 Thread shmulik
Hi, Below is the debug_http log showing the same location handling upstream response of 409, and next of 408. You can see that the 408 response is handled differently: // 409 -- // 2015/02/11 22:07:03 [debug] 20611#0: *3 http upstream process header

Re: catching 408 response from upstream server

2015-02-11 Thread shmulik
Thank you. As i wrote in reply to B. R., i'm trying to catch an 408 response from an upstream server, and turn it into a 302 redirect. Since the upstream is the one answering with 408, i cannot control its logic by tweaking Nginx configuration. In my scenario, the client is "fast enough", as Nginx

Re: catching 408 response from upstream server

2015-02-11 Thread shmulik
Hi, Below is the debug_http log showing the same location handling upstream response of 409, and next of 408. You can see that the 408 response is handled differently: // 409 -- // 2015/02/11 22:07:03 [debug] 20611#0: *3 http upstream process header

Re: catching 408 response from upstream server

2015-02-10 Thread Frederik Nosi
Hi, On 02/10/2015 08:35 AM, shmulik wrote: Hi, I'm using nginx as reversed proxy, using the proxy module. Whenever i get a response code >= 400 from the upstream server, i'm redirecting the client to a different url. This is the configuration i use (simplified): location ~ "^/proxy/hos

Re: catching 408 response from upstream server

2015-02-10 Thread B.R.
I do not see anything in error_page documentation stating it would not send anything for 408. I suggest a problem on your side. Do you have HTTP Requests/Responses traces to show? Any sign of trouble (configuration, not applied,

catching 408 response from upstream server

2015-02-09 Thread shmulik
Hi, I'm using nginx as reversed proxy, using the proxy module. Whenever i get a response code >= 400 from the upstream server, i'm redirecting the client to a different url. This is the configuration i use (simplified): location ~ "^/proxy/host_(.*)/fallback_(.*)" { proxy_pas