uwsgi_ssl_server_name

Syntax: uwsgi_ssl_server_name on | off; Default: uwsgi_ssl_server_name off; Context: http, server, location This directive appeared in version 1.7.0. Enables or disables passing of the server name through TLS Server Name Indication extension (SNI, RFC 6066) when establishing a connection with the secured uwsgi server.

proxy_pass

Syntax: proxy_pass URL; Default: — Context: location, if in location, limit_except Sets the protocol and address of a proxied server and an optional URI to which a location should be mapped. As a protocol, “http” or “https” can be specified. The address can be specified as a domain name or IP address, and an optional port: proxy_pass http://localhost:8000/uri/; or as a UNIX-domain socket path specified after the word “unix” and enclosed in colons: proxy_pass http://unix:/tmp/

server_name

Syntax: server_name name; Default: server_name hostname; Context: mail, server Sets the server name that is used: in the initial POP3/SMTP server greeting; in the salt during the SASL CRAM-MD5 authentication; in the EHLO command when connecting to the SMTP backend, if the passing of the XCLIENT command is enabled. If the directive is not specified, the machine’s hostname is used.

uwsgi_cache_key

Syntax: uwsgi_cache_key string; Default: — Context: http, server, location Defines a key for caching, for example uwsgi_cache_key localhost:9000$request_uri;

try_files

Syntax: try_files file ... uri;try_files file ... =code; Default: — Context: server, location Checks the existence of files in the specified order and uses the first found file for request processing; the processing is performed in the current context. The path to a file is constructed from the file parameter according to the root and alias directives. It is possible to check directory’s existence by specifying a slash at the end of a name, e.g. “$uri/”. If none of the files were f

msie_padding

Syntax: msie_padding on | off; Default: msie_padding on; Context: http, server, location Enables or disables adding comments to responses for MSIE clients with status greater than 400 to increase the response size to 512 bytes.

uwsgi_param

Syntax: uwsgi_param parameter value [if_not_empty]; Default: — Context: http, server, location Sets a parameter that should be passed to the uwsgi server. The value can contain text, variables, and their combination. These directives are inherited from the previous level if and only if there are no uwsgi_param directives defined on the current level. Standard CGI environment variables should be provided as uwsgi headers, see the uwsgi_params file provided in the distribu

fastcgi_ignore_headers

Syntax: fastcgi_ignore_headers field ...; Default: — Context: http, server, location Disables processing of certain response header fields from the FastCGI 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

uwsgi_ssl_password_file

Syntax: uwsgi_ssl_password_file file; Default: — Context: http, server, location This directive appeared in version 1.7.8. Specifies a file with passphrases for secret keys where each passphrase is specified on a separate line. Passphrases are tried in turn when loading the key.

large_client_header_buffers

Syntax: large_client_header_buffers number size; Default: large_client_header_buffers 4 8k; Context: http, server Sets the maximum number and size of buffers used for reading large client request header. A request line cannot exceed the size of one buffer, or the 414 (Request-URI Too Large) error is returned to the client. A request header field cannot exceed the size of one buffer as well, or the 400 (Bad Request) error is returned to the client. Buffers are allocated only on dema