Syntax: dav_methods off | method ...; Default: dav_methods off; Context: http, server, location Allows the specified HTTP and WebDAV methods. The parameter off denies all methods processed by this module. The following methods are supported: PUT, DELETE, MKCOL, COPY, and MOVE. A file uploaded with the PUT method is first written to a temporary file, and then the file is renamed. Starting from version 0.8.9, temporary files and the persistent store can be put on different fil

Syntax: uwsgi_temp_path path [level1 [level2 [level3]]]; Default: uwsgi_temp_path uwsgi_temp; Context: http, server, location Defines a directory for storing temporary files with data received from uwsgi servers. Up to three-level subdirectory hierarchy can be used underneath the specified directory. For example, in the following configuration uwsgi_temp_path /spool/nginx/uwsgi_temp 1 2; a temporary file might look like this: /spool/nginx/uwsgi_temp/7/45/0000

Syntax: ssl_trusted_certificate file; Default: — Context: stream, server This directive appeared in version 1.11.8. Specifies a file with trusted CA certificates in the PEM format used to verify client certificates. In contrast to the certificate set by ssl_client_certificate, the list of these certificates will not be sent to clients.

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

Syntax: scgi_next_upstream_timeout time; Default: scgi_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: lingering_close off | on | always; Default: lingering_close on; Context: http, server, location This directive appeared in versions 1.1.0 and 1.0.6. Controls how nginx closes client connections. The default value “on” instructs nginx to wait for and process additional data from a client before fully closing a connection, but only if heuristics suggests that a client may be sending more data. The value “always” will cause nginx to unconditionally wait for

Syntax: proxy_ssl_ciphers ciphers; Default: proxy_ssl_ciphers DEFAULT; Context: http, server, location This directive appeared in version 1.5.6. Specifies the enabled ciphers for requests to a proxied HTTPS server. The ciphers are specified in the format understood by the OpenSSL library. The full list can be viewed using the “openssl ciphers” command.

Syntax: proxy_pass_request_body on | off; Default: proxy_pass_request_body on; Context: http, server, location Indicates whether the original request body is passed to the proxied server. location /x-accel-redirect-here/ { proxy_method GET; proxy_pass_request_body off; proxy_set_header Content-Length ""; proxy_pass ... } See also the proxy_set_header and proxy_pass_request_headers directives.

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: userid_mark letter | digit | = | off; Default: userid_mark off; Context: http, server, location If the parameter is not off, enables the cookie marking mechanism and sets the character used as a mark. This mechanism is used to add or change userid_p3p and/or a cookie expiration time while preserving the client identifier. A mark can be any letter of the English alphabet (case-sensitive), digit, or the “=” character. If the mark is set, it is compared with the