Syntax: client_max_body_size size; Default: client_max_body_size 1m; Context: http, server, location Sets the maximum allowed size of the client request body, specified in the “Content-Length” request header field. If the size in a request exceeds the configured value, the 413 (Request Entity Too Large) error is returned to the client. Please be aware that browsers cannot correctly display this error. Setting size to 0 disables checking of client request body size.

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: 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

Syntax: match name { ... } Default: — Context: http Defines the named test set used to verify responses to health check requests. The following items can be tested in a response: status 200; status is 200 status ! 500; status is not 500 status 200 204; status is 200 or 204 status ! 301 302; status is neither 301 nor 302 status 200-399; status is in the range from 200 to 399 status ! 400-599; status is not in the range from 400 to 599 status 301-303 307; status is either 301, 302

Syntax: uwsgi_max_temp_file_size size; Default: uwsgi_max_temp_file_size 1024m; Context: http, server, location When buffering of responses from the uwsgi server is enabled, and the whole response does not fit into the buffers set by the uwsgi_buffer_size and uwsgi_buffers directives, a part of the response can be saved to a temporary file. This directive sets the maximum size of the temporary file. The size of data written to the temporary file at a time is set by the uwsgi_temp_f

Syntax: proxy_cookie_domain off;proxy_cookie_domain domain replacement; Default: proxy_cookie_domain off; Context: http, server, location This directive appeared in version 1.1.15. Sets a text that should be changed in the domain 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 “domain=localhost”. The directive proxy_cookie_domain localhost example.org; will rewrite this

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

Syntax: xml_entities path; Default: — Context: http, server, location Specifies the DTD file that declares character entities. This file is compiled at the configuration stage. For technical reasons, the module is unable to use the external subset declared in the processed XML, so it is ignored and a specially defined file is used instead. This file should not describe the XML structure. It is enough to declare just the required character entities, for example: <!ENTITY nbsp "

Syntax: resolver address ... [valid=time];resolver off; Default: resolver off; Context: mail, server Configures name servers used to find the client’s hostname to pass it to the authentication server, and in the XCLIENT command when proxying SMTP. For example: resolver 127.0.0.1 [::1]:5353; An address can be specified as a domain name or IP address, and an optional port (1.3.1, 1.2.2). If port is not specified, the port 53 is used. Name servers are queried in a round-robin fas