uwsgi_ignore_headers

Syntax: uwsgi_ignore_headers field ...; Default: — Context: http, server, location Disables processing of certain response header fields from the uwsgi server. The following fields can be ignored: “X-Accel-Redirect”, “X-Accel-Expires”, “X-Accel-Limit-Rate” (1.1.6), “X-Accel-Buffering” (1.1.6), “X-Accel-Charset” (1.1.6), “Expires”, “Cache-Control”, “Set-Cookie” (0.8.44), and “Vary” (1.7.7). If not disabled, processing of these header fields has the following effect: “X-Accel-Exp

xslt_stylesheet

Syntax: xslt_stylesheet stylesheet [parameter=value ...]; Default: — Context: location Defines the XSLT stylesheet and its optional parameters. A stylesheet is compiled at the configuration stage. Parameters can either be specified separately, or grouped in a single line using the “:” delimiter. If a parameter includes the “:” character, it should be escaped as “%3A”. Also, libxslt requires to enclose parameters that contain non-alphanumeric characters into single or dou

dav_methods

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

secure_link_secret

Syntax: secure_link_secret word; Default: — Context: location Defines a secret word used to check authenticity of requested links. The full URI of a requested link looks as follows: /prefix/hash/link where hash is a hexadecimal representation of the MD5 hash computed for the concatenation of the link and secret word, and prefix is an arbitrary string without slashes. If the requested link passes the authenticity check, the $secure_link variable is set to the link extracted

uwsgi_cache

Syntax: uwsgi_cache zone | off; Default: uwsgi_cache off; Context: http, server, location Defines a shared memory zone used for caching. The same zone can be used in several places. Parameter value can contain variables (1.7.9). The off parameter disables caching inherited from the previous configuration level.

types_hash_max_size

Syntax: types_hash_max_size size; Default: types_hash_max_size 1024; Context: http, server, location Sets the maximum size of the types hash tables. The details of setting up hash tables are provided in a separate document.

http2_max_field_size

Syntax: http2_max_field_size size; Default: http2_max_field_size 4k; Context: http, server Limits the maximum size of an HPACK-compressed request header field. The limit applies equally to both name and value. Note that if Huffman encoding is applied, the actual size of decompressed name and value strings may be larger. For most requests, the default limit should be enough.

uwsgi_request_buffering

Syntax: uwsgi_request_buffering on | off; Default: uwsgi_request_buffering on; Context: http, server, location This directive appeared in version 1.7.11. Enables or disables buffering of a client request body. When buffering is enabled, the entire request body is read from the client before sending the request to a uwsgi server. When buffering is disabled, the request body is sent to the uwsgi server immediately as it is received. In this case, the request cannot be passed to

uwsgi_cache_use_stale

Syntax: uwsgi_cache_use_stale error | timeout | invalid_header | updating | http_500 | http_503 | http_403 | http_404 | off ...; Default: uwsgi_cache_use_stale off; Context: http, server, location Determines in which cases a stale cached response can be used when an error occurs during communication with the uwsgi server. The directive’s parameters match the parameters of the uwsgi_next_upstream directive. The error parameter also permits

ssl_trusted_certificate

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.