Syntax: memcached_next_upstream error | timeout | invalid_response | not_found | off ...; Default: memcached_next_upstream error timeout; Context: http, server, location Specifies in which cases a request should be passed to the next server: error an error occurred while establishing a connection with the server, passing a request to it, or reading the response header; timeout a timeout has occurred while establishing a connection with the server, passing

Syntax: memcached_gzip_flag flag; Default: — Context: http, server, location This directive appeared in version 1.3.6. Enables the test for the flag presence in the memcached server response and sets the “Content-Encoding” response header field to “gzip” if the flag is set.

Syntax: memcached_force_ranges on | off; Default: memcached_force_ranges off; Context: http, server, location This directive appeared in version 1.7.7. Enables byte-range support for both cached and uncached responses from the memcached server regardless of the “Accept-Ranges” field in these responses.

Syntax: memcached_connect_timeout time; Default: memcached_connect_timeout 60s; Context: http, server, location Defines a timeout for establishing a connection with a memcached server. It should be noted that this timeout cannot usually exceed 75 seconds.

Syntax: memcached_buffer_size size; Default: memcached_buffer_size 4k|8k; Context: http, server, location Sets the size of the buffer used for reading the response received from the memcached server. The response is passed to the client synchronously, as soon as it is received.

Syntax: memcached_bind address [ transparent ] | off; Default: — Context: http, server, location This directive appeared in version 0.8.22. Makes outgoing connections to a memcached server originate from the specified local IP address with an optional port (1.11.2). Parameter value can contain variables (1.3.12). The special value off (1.3.12) cancels the effect of the memcached_bind directive inherited from the previous configuration level, which allows the system to

Syntax: max_ranges number; Default: — Context: http, server, location This directive appeared in version 1.1.2. Limits the maximum allowed number of ranges in byte-range requests. Requests that exceed the limit are processed as if there were no byte ranges specified. By default, the number of ranges is not limited. The zero value disables the byte-range support completely.

Syntax: match name { ... } Default: — Context: stream Defines the named test set used to verify server responses to health checks. The following parameters can be configured: send string; sends a string to the server; expect string | ~ regex; a literal string (1.9.12) or a regular expression that the data obtained from the server should match. The regular expression is specified with the preceding “~*” modifier (for case-insensitive matching), or the “~” modifier (for ca

Syntax: match name { ... } Default: — Context: http Defines the named test set used to verify responses to health check requests. The following items can be tested in a response: status 200; status is 200 status ! 500; status is not 500 status 200 204; status is 200 or 204 status ! 301 302; status is neither 301 nor 302 status 200-399; status is in the range from 200 to 399 status ! 400-599; status is not in the range from 400 to 599 status 301-303 307; status is either 301, 302

Syntax: master_process on | off; Default: master_process on; Context: main Determines whether worker processes are started. This directive is intended for nginx developers.