catching 408 response from upstream server

[B.R.]

I do not see anything in error_page
<http://nginx.org/en/docs/http/ngx_http_core_module.html#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, wrong location, empty
arguments, etc.)?
---
*B. R.*

On Tue, Feb 10, 2015 at 8:35 AM, shmulik <nginx-forum at nginx.us> 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/host_(.*)/fallback_(.*)" {
>
>             proxy_pass http://$1;
>
>             proxy_intercept_errors on;
>             error_page 404 408 500 http://$2;
>         }
>
> However, i've noticed that when the upstream server responds with 408
> response code, nginx does not send a redirect.
> Instead it terminates the connection to the client.
>
> Is this the intended behavior?
> Is there any way around it?
> I'd like to be able to intercept 408 responses as well and redirect them.
> Any alternative suggestions to implement it are very welcome.
>
> Thanks in advance,
> Shmulikb
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,256530,256530#msg-256530
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20150210/09f0922d/attachment-0001.html>