Mercurial > hg > nginx-site
diff xml/en/docs/http/ngx_http_proxy_module.xml @ 942:ba3d6ade3513
Elaborate on upstream server failures.
Documented that {proxy,fastcgi,memcached}_next_upstream directives define
what is considered an unsuccessful attempt of communication with a server.
author | Ruslan Ermilov <ru@nginx.com> |
---|---|
date | Fri, 05 Jul 2013 10:40:38 +0400 |
parents | e26a18eb5ccd |
children | fbb4cc6f8c3d |
line wrap: on
line diff
--- a/xml/en/docs/http/ngx_http_proxy_module.xml Fri Jul 05 08:11:37 2013 +0400 +++ b/xml/en/docs/http/ngx_http_proxy_module.xml Fri Jul 05 10:40:38 2013 +0400 @@ -10,7 +10,7 @@ <module name="Module ngx_http_proxy_module" link="/en/docs/http/ngx_http_proxy_module.html" lang="en" - rev="11"> + rev="12"> <section id="summary"> @@ -883,6 +883,20 @@ transferring a response, fixing this is impossible. </para> +<para> +The directive also defines what is considered an unsuccessful attempt +of communication with a +<link doc="ngx_http_upstream_module.xml" id="server"/>. +The cases of <literal>error</literal>, <literal>timeout</literal> and +<literal>invalid_header</literal> are always considered unsuccessful attempts, +even if they are not specified in the directive. +The cases of <literal>http_500</literal>, <literal>http_502</literal>, +<literal>http_503</literal> and <literal>http_504</literal> are +considered unsuccessful attempts only if they are specified in the directive. +The cases of <literal>http_403</literal> and <literal>http_404</literal> +are never considered unsuccessful attempts. +</para> + </directive>