Mercurial > hg > nginx-site
comparison xml/en/docs/http/ngx_http_memcached_module.xml @ 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 | 6839c258c473 |
children | a9a9a052b5bd |
comparison
equal
deleted
inserted
replaced
2055:f37d90fcd415 | 2056:af6f326dee75 |
---|---|
200 <para> | 200 <para> |
201 The directive also defines what is considered an | 201 The directive also defines what is considered an |
202 <link doc="ngx_http_upstream_module.xml" id="max_fails">unsuccessful | 202 <link doc="ngx_http_upstream_module.xml" id="max_fails">unsuccessful |
203 attempt</link> of communication with a server. | 203 attempt</link> of communication with a server. |
204 The cases of <literal>error</literal>, <literal>timeout</literal> and | 204 The cases of <literal>error</literal>, <literal>timeout</literal> and |
205 <literal>invalid_header</literal> are always considered unsuccessful attempts, | 205 <literal>invalid_response</literal> are always considered unsuccessful attempts, |
206 even if they are not specified in the directive. | 206 even if they are not specified in the directive. |
207 The case of <literal>not_found</literal> | 207 The case of <literal>not_found</literal> |
208 is never considered an unsuccessful attempt. | 208 is never considered an unsuccessful attempt. |
209 </para> | 209 </para> |
210 | 210 |