state

Syntax: state file; Default: — Context: upstream This directive appeared in version 1.9.7. Specifies a file that keeps the state of the dynamically configurable group. Examples: state /var/lib/nginx/state/servers.conf; # path for Linux state /var/db/nginx/state/servers.conf; # path for FreeBSD The state is currently limited to the list of servers with their parameters. The file is read when parsing the configuration and is updated each time the upstream configuration is cha

charset

Syntax: charset charset | off; Default: charset off; Context: http, server, location, if in location Adds the specified charset to the “Content-Type” response header field. If this charset is different from the charset specified in the source_charset directive, a conversion is performed. The parameter off cancels the addition of charset to the “Content-Type” response header field. A charset can be defined with a variable: charset $charset; In such a case, all possible value

uwsgi_temp_file_write_size

Syntax: uwsgi_temp_file_write_size size; Default: uwsgi_temp_file_write_size 8k|16k; Context: http, server, location Limits the size of data written to a temporary file at a time, when buffering of responses from the uwsgi server to temporary files is enabled. By default, size is limited by two buffers set by the uwsgi_buffer_size and uwsgi_buffers directives. The maximum size of a temporary file is set by the uwsgi_max_temp_file_size directive.

scgi_pass

Syntax: scgi_pass address; Default: — Context: location, if in location Sets the address of an SCGI server. The address can be specified as a domain name or IP address, and a port: scgi_pass localhost:9000; or as a UNIX-domain socket path: scgi_pass unix:/tmp/scgi.socket; If a domain name resolves to several addresses, all of them will be used in a round-robin fashion. In addition, an address can be specified as a server group.

proxy_hide_header

Syntax: proxy_hide_header field; Default: — Context: http, server, location By default, nginx does not pass the header fields “Date”, “Server”, “X-Pad”, and “X-Accel-...” from the response of a proxied server to a client. The proxy_hide_header directive sets additional fields that will not be passed. If, on the contrary, the passing of fields needs to be permitted, the proxy_pass_header directive can be used.

ip_hash

Syntax: ip_hash; Default: — Context: upstream Specifies that a group should use a load balancing method where requests are distributed between servers based on client IP addresses. The first three octets of the client IPv4 address, or the entire IPv6 address, are used as a hashing key. The method ensures that requests from the same client will always be passed to the same server except when this server is unavailable. In the latter case client requests will be passed to another ser

uwsgi_ssl_protocols

Syntax: uwsgi_ssl_protocols [SSLv2] [SSLv3] [TLSv1] [TLSv1.1] [TLSv1.2]; Default: uwsgi_ssl_protocols TLSv1 TLSv1.1 TLSv1.2; Context: http, server, location This directive appeared in version 1.5.8. Enables the specified protocols for requests to a secured uwsgi server.

scgi_cache_purge

Syntax: scgi_cache_purge string ...; Default: — Context: http, server, location This directive appeared in version 1.5.7. Defines conditions under which the request will be considered a cache purge request. If at least one value of the string parameters is not empty and is not equal to “0” then the cache entry with a corresponding cache key is removed. The result of successful operation is indicated by returning the 204 (No Content) response. If the cache key of a purge request

http2_max_requests

Syntax: http2_max_requests number; Default: http2_max_requests 1000; Context: http, server, location This directive appeared in version 1.11.6. Sets the maximum number of requests that can be served through one HTTP/2 connection, after which the connection is closed and the client should use a new connection.

client_body_temp_path

Syntax: client_body_temp_path path [level1 [level2 [level3]]]; Default: client_body_temp_path client_body_temp; Context: http, server, location Defines a directory for storing temporary files holding client request bodies. Up to three-level subdirectory hierarchy can be used under the specified directory. For example, in the following configuration client_body_temp_path /spool/nginx/client_temp 1 2; a path to a temporary file might look like this: /spool/ngin