Syntax: ssl_client_certificate file; Default: — Context: http, server Specifies a file with trusted CA certificates in the PEM format used to verify client certificates and OCSP responses if ssl_stapling is enabled. The list of certificates will be sent to clients. If this is not desired, the ssl_trusted_certificate directive can be used.

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

Building nginx on the Win32 platform with Visual C Build steps See also

Syntax: ssl_stapling_file file; Default: — Context: http, server This directive appeared in version 1.3.7. When set, the stapled OCSP response will be taken from the specified file instead of querying the OCSP responder specified in the server certificate. The file should be in the DER format as produced by the “openssl ocsp” command.

Syntax: proxy_intercept_errors on | off; Default: proxy_intercept_errors off; Context: http, server, location Determines whether proxied responses with codes greater than or equal to 300 should be passed to a client or be intercepted and redirected to nginx for processing with the error_page directive.

Syntax: uwsgi_next_upstream_timeout time; Default: uwsgi_next_upstream_timeout 0; Context: http, server, location This directive appeared in version 1.7.5. Limits the time during which a request can be passed to the next server. The 0 value turns off this limitation.

Syntax: add_header name value [always]; Default: — Context: http, server, location, if in location Adds the specified field to a response header provided that the response code equals 200, 201, 204, 206, 301, 302, 303, 304, or 307. A value can contain variables. There could be several add_header directives. These directives are inherited from the previous level if and only if there are no add_header directives defined on the current level. If the always parameter is specified

Syntax: uwsgi_pass_request_body on | off; Default: uwsgi_pass_request_body on; Context: http, server, location Indicates whether the original request body is passed to the uwsgi server. See also the uwsgi_pass_request_headers directive.

Syntax: client_body_in_single_buffer on | off; Default: client_body_in_single_buffer off; Context: http, server, location Determines whether nginx should save the entire client request body in a single buffer. The directive is recommended when using the $request_body variable, to save the number of copy operations involved.

Syntax: hls_fragment time; Default: hls_fragment 5s; Context: http, server, location Defines the default fragment length for playlist URIs requested without the “len” argument.