spdy_chunk_size

Syntax: spdy_chunk_size size; Default: spdy_chunk_size 8k; Context: http, server, location This directive appeared in version 1.5.9. Sets the maximum size of chunks into which the response body is sliced. A too low value results in higher overhead. A too high value impairs prioritization due to HOL blocking.

proxy_headers_hash_max_size

Syntax: proxy_headers_hash_max_size size; Default: proxy_headers_hash_max_size 512; Context: http, server, location Sets the maximum size of hash tables used by the proxy_hide_header and proxy_set_header directives. The details of setting up hash tables are provided in a separate document.

proxy_cookie_path

Syntax: proxy_cookie_path off;proxy_cookie_path path replacement; Default: proxy_cookie_path off; Context: http, server, location This directive appeared in version 1.1.15. Sets a text that should be changed in the path attribute of the “Set-Cookie” header fields of a proxied server response. Suppose a proxied server returned the “Set-Cookie” header field with the attribute “path=/two/some/uri/”. The directive proxy_cookie_path /two/ /; will rewrite this attribute to “path=/so

session_log_zone

Syntax: session_log_zone path zone=name:size [format=format] [timeout=time] [id=id] [md5=md5] ; Default: — Context: http Sets the path to a log file and configures the shared memory zone that is used to store currently active sessions. A session is considered active for as long as the time elapsed since the last request in the session does not exceed the specified timeout (by default, 30 seconds). Once a session is no longer active, it is written to the l

uwsgi_ssl_verify

Syntax: uwsgi_ssl_verify on | off; Default: uwsgi_ssl_verify off; Context: http, server, location This directive appeared in version 1.7.0. Enables or disables verification of the secured uwsgi server certificate.

fastcgi_cache_valid

Syntax: fastcgi_cache_valid [code ...] time; Default: — Context: http, server, location Sets caching time for different response codes. For example, the following directives fastcgi_cache_valid 200 302 10m; fastcgi_cache_valid 404 1m; set 10 minutes of caching for responses with codes 200 and 302 and 1 minute for responses with code 404. If only caching time is specified fastcgi_cache_valid 5m; then only 200, 301, and 302 responses are cached. In addition, the any

proxy_pass_error_message

Syntax: proxy_pass_error_message on | off; Default: proxy_pass_error_message off; Context: mail, server Indicates whether to pass the error message obtained during the authentication on the backend to the client. Usually, if the authentication in nginx is a success, the backend cannot return an error. If it nevertheless returns an error, it means some internal error has occurred. In such case the backend message can contain information that should not be shown to the client. Howe

ssl_certificate

Syntax: ssl_certificate file; Default: — Context: mail, server Specifies a file with the certificate in the PEM format for the given server. If intermediate certificates should be specified in addition to a primary certificate, they should be specified in the same file in the following order: the primary certificate comes first, then the intermediate certificates. A secret key in the PEM format may be placed in the same file. Since version 1.11.0, this directive can be specified

secure_link_md5

Syntax: secure_link_md5 expression; Default: — Context: http, server, location Defines an expression for which the MD5 hash value will be computed and compared with the value passed in a request. The expression should contain the secured part of a link (resource) and a secret ingredient. If the link has a limited lifetime, the expression should also contain $secure_link_expires. To prevent unauthorized access, the expression may contain some information about the client, such a

expires

Syntax: expires [modified] time;expires epoch | max | off; Default: expires off; Context: http, server, location, if in location Enables or disables adding or modifying the “Expires” and “Cache-Control” response header fields provided that the response code equals 200, 201, 204, 206, 301, 302, 303, 304, or 307. The parameter can be a positive or negative time. The time in the “Expires” field is computed as a sum of the current time and time specified in the directive