Mercurial > hg > nginx-site
changeset 2056:af6f326dee75
Fixed spelling of "invalid_response" in "memcached_next_upstream".
| author | Ruslan Ermilov <ru@nginx.com> |
|---|---|
| date | Wed, 11 Oct 2017 12:00:58 +0300 |
| parents | f37d90fcd415 |
| children | dd78dd9e2cb7 |
| files | xml/en/docs/http/ngx_http_memcached_module.xml |
| diffstat | 1 files changed, 1 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/xml/en/docs/http/ngx_http_memcached_module.xml +++ b/xml/en/docs/http/ngx_http_memcached_module.xml @@ -202,7 +202,7 @@ The directive also defines what is consi <link doc="ngx_http_upstream_module.xml" id="max_fails">unsuccessful attempt</link> of communication with a server. The cases of <literal>error</literal>, <literal>timeout</literal> and -<literal>invalid_header</literal> are always considered unsuccessful attempts, +<literal>invalid_response</literal> are always considered unsuccessful attempts, even if they are not specified in the directive. The case of <literal>not_found</literal> is never considered an unsuccessful attempt.