Syntax: ssl_trusted_certificate file; Default: — Context: http, server This directive appeared in version 1.3.7. Specifies a file with trusted CA certificates in the PEM format used to verify client certificates and OCSP responses if ssl_stapling is enabled. In contrast to the certificate set by ssl_client_certificate, the list of these certificates will not be sent to clients.

Syntax: proxy_send_timeout time; Default: proxy_send_timeout 60s; Context: http, server, location Sets a timeout for transmitting a request to the proxied server. The timeout is set only between two successive write operations, not for the transmission of the whole request. If the proxied server does not receive anything within this time, the connection is closed.

Syntax: xclient on | off; Default: xclient on; Context: mail, server Enables or disables the passing of the XCLIENT command with client parameters when connecting to the SMTP backend. With XCLIENT, the MTA is able to write client information to the log and apply various limitations based on this data. If XCLIENT is enabled then nginx passes the following commands when connecting to the backend: EHLO with the server name XCLIENT EHLO or HELO, as passed by the client

Syntax: charset_types mime-type ...; Default: charset_types text/html text/xml text/plain text/vnd.wap.wml application/javascript application/rss+xml; Context: http, server, location This directive appeared in version 0.7.9. Enables module processing in responses with the specified MIME types in addition to “text/html”. The special value “*” matches any MIME type (0.8.29). Until version 1.5.4, “application/x-javascript” was used as the default MIME type instead of “application/j

Syntax: limit_zone name $variable size; Default: — Context: http This directive was made obsolete in version 1.1.8 and was removed in version 1.7.6. An equivalent limit_conn_zone directive with a changed syntax should be used instead: limit_conn_zone $variable zone=name:size;

Syntax: scgi_store_access users:permissions ...; Default: scgi_store_access user:rw; Context: http, server, location Sets access permissions for newly created files and directories, e.g.: scgi_store_access user:rw group:rw all:r; If any group or all access permissions are specified then user permissions may be omitted: scgi_store_access group:rw all:r;

Syntax: server_name_in_redirect on | off; Default: server_name_in_redirect off; Context: http, server, location Enables or disables the use of the primary server name, specified by the server_name directive, in absolute redirects issued by nginx. When the use of the primary server name is disabled, the name from the “Host” request header field is used. If this field is not present, the IP address of the server is used. The use of a port in redirects is controlled by the port_in_r

Syntax: client_body_in_file_only on | clean | off; Default: client_body_in_file_only off; Context: http, server, location Determines whether nginx should save the entire client request body into a file. This directive can be used during debugging, or when using the $request_body_file variable, or the $r->request_body_file method of the module ngx_http_perl_module. When set to the value on, temporary files are not removed after request processing. The value clean

Syntax: absolute_redirect on | off; Default: absolute_redirect on; Context: http, server, location This directive appeared in version 1.11.8. If disabled, redirects issued by nginx will be relative. See also server_name_in_redirect and port_in_redirect directives.

Syntax: mp4_limit_rate on | off | factor; Default: mp4_limit_rate off; Context: http, server, location Limits the rate of response transmission to a client. The rate is limited based on the average bitrate of the MP4 file served. To calculate the rate, the bitrate is multiplied by the specified factor. The special value “on” corresponds to the factor of 1.1. The special value “off” disables rate limiting. The limit is set per a request, and so if a client simultaneousl