Syntax: ssl_session_timeout time; Default: ssl_session_timeout 5m; Context: mail, server Specifies a time during which a client may reuse the session parameters.

Syntax: lock_file file; Default: lock_file logs/nginx.lock; Context: main nginx uses the locking mechanism to implement accept_mutex and serialize access to shared memory. On most systems the locks are implemented using atomic operations, and this directive is ignored. On other systems the “lock file” mechanism is used. This directive specifies a prefix for the names of lock files.

Syntax: ssl_session_ticket_key file; Default: — Context: http, server This directive appeared in version 1.5.7. Sets a file with the secret key used to encrypt and decrypt TLS session tickets. The directive is necessary if the same key has to be shared between multiple servers. By default, a randomly generated key is used. If several keys are specified, only the first key is used to encrypt TLS session tickets. This allows configuring key rotation, for example: ssl_session_tic

Syntax: uwsgi_bind address [transparent] | off; Default: — Context: http, server, location Makes outgoing connections to a uwsgi 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 uwsgi_bind directive inherited from the previous configuration level, which allows the system to auto-assign the local IP address and port. The transpar

Syntax: proxy_cache_lock on | off; Default: proxy_cache_lock off; Context: http, server, location This directive appeared in version 1.1.12. When enabled, only one request at a time will be allowed to populate a new cache element identified according to the proxy_cache_key directive by passing a request to a proxied server. Other requests of the same cache element will either wait for a response to appear in the cache or the cache lock for this element to be released, up to the ti

Syntax: proxy_ssl_certificate_key file; Default: — Context: http, server, location This directive appeared in version 1.7.8. Specifies a file with the secret key in the PEM format used for authentication to a proxied HTTPS server. The value engine:name:id can be specified instead of the file (1.7.9), which loads a secret key with a specified id from the OpenSSL engine name.

Syntax: scgi_pass_request_headers on | off; Default: scgi_pass_request_headers on; Context: http, server, location Indicates whether the header fields of the original request are passed to the SCGI server. See also the scgi_pass_request_body directive.

Syntax: limit_req_log_level info | notice | warn | error; Default: limit_req_log_level error; Context: http, server, location This directive appeared in version 0.8.18. Sets the desired logging level for cases when the server refuses to process requests due to rate exceeding, or delays request processing. Logging level for delays is one point less than for refusals; for example, if “limit_req_log_level notice” is specified, delays are logged with the info level.

Syntax: uwsgi_buffering on | off; Default: uwsgi_buffering on; Context: http, server, location Enables or disables buffering of responses from the uwsgi server. When buffering is enabled, nginx receives a response from the uwsgi server as soon as possible, saving it into the buffers set by the uwsgi_buffer_size and uwsgi_buffers directives. If the whole response does not fit into memory, a part of it can be saved to a temporary file on the disk. Writing to temporary files is cont

Syntax: timer_resolution interval; Default: — Context: main Reduces timer resolution in worker processes, thus reducing the number of gettimeofday() system calls made. By default, gettimeofday() is called each time a kernel event is received. With reduced resolution, gettimeofday() is only called once per specified interval. Example: timer_resolution 100ms; Internal implementation of the interval depends on the method used: the EVFILT_TIMER filter if kqueue is used; timer