Syntax: stub_status; Default: — Context: server, location The basic status information will be accessible from the surrounding location. In versions prior to 1.7.5, the directive syntax required an arbitrary argument, for example, “stub_status on”.

Syntax: stream { ... } Default: — Context: main Provides the configuration file context in which the stream server directives are specified.

Syntax: sticky_cookie_insert name [expires=time] [domain=domain] [path=path]; Default: — Context: upstream This directive is obsolete since version 1.5.7. An equivalent sticky directive with a new syntax should be used instead: sticky cookie name [expires=time] [domain=domain] [path=path];

Syntax: status_zone zone; Default: — Context: server Enables collection of virtual http or stream (1.7.11) server status information in the specified zone. Several servers may share the same zone.

Syntax: sticky cookie name [expires=time] [domain=domain] [httponly] [secure] [path=path];sticky route $variable ...;sticky learn create=$variable lookup=$variable zone=name:size [timeout=time]; Default: — Context: upstream This directive appeared in version 1.5.7. Enables session affinity, which causes requests from the same client to be passed to the same server in a group of servers. Three methods are available: cookie When

Syntax: status; Default: — Context: location The status information will be accessible from the surrounding location. Access to this location should be limited.

Syntax: status_format json;status_format jsonp [callback]; Default: status_format json; Context: http, server, location By default, status information is output in the JSON format. Alternatively, data may be output as JSONP. The callback parameter specifies the name of a callback function. The value can contain variables. If parameter is omitted, or the computed value is an empty string, then “ngx_status_jsonp_callback” is used.

Syntax: state file; Default: — Context: upstream This directive appeared in version 1.9.7. Specifies a file that keeps the state of the dynamically configurable group. Examples: state /var/lib/nginx/state/servers.conf; # path for Linux state /var/db/nginx/state/servers.conf; # path for FreeBSD The state is currently limited to the list of servers with their parameters. The file is read when parsing the configuration and is updated each time the upstream configuration is cha

Syntax: state file; Default: — Context: upstream This directive appeared in version 1.9.7. Specifies a file that keeps the state of the dynamically configurable group. Examples: state /var/lib/nginx/state/servers.conf; # path for Linux state /var/db/nginx/state/servers.conf; # path for FreeBSD The state is currently limited to the list of servers with their parameters. The file is read when parsing the configuration and is updated each time the upstream configuration is cha

Syntax: ssl_verify_depth number; Default: ssl_verify_depth 1; Context: mail, server This directive appeared in version 1.7.11. Sets the verification depth in the client certificates chain.