proxy_ssl_session_reuse

Syntax: proxy_ssl_session_reuse on | off; Default: proxy_ssl_session_reuse on; Context: stream, server Determines whether SSL sessions can be reused when working with the proxied server. If the errors “SSL3_GET_FINISHED:digest check failed” appear in the logs, try disabling session reuse.

tcp_nopush

Syntax: tcp_nopush on | off; Default: tcp_nopush off; Context: http, server, location Enables or disables the use of the TCP_NOPUSH socket option on FreeBSD or the TCP_CORK socket option on Linux. The options are enabled only when sendfile is used. Enabling the option allows sending the response header and the beginning of a file in one packet, on Linux and FreeBSD 4.*; sending a file in full packets.

uwsgi_read_timeout

Syntax: uwsgi_read_timeout time; Default: uwsgi_read_timeout 60s; Context: http, server, location Defines a timeout for reading a response from the uwsgi server. The timeout is set only between two successive read operations, not for the transmission of the whole response. If the uwsgi server does not transmit anything within this time, the connection is closed.

uwsgi_pass

Syntax: uwsgi_pass [protocol://]address; Default: — Context: location, if in location Sets the protocol and address of a uwsgi server. As a protocol, “uwsgi” or “suwsgi” (secured uwsgi, uwsgi over SSL) can be specified. The address can be specified as a domain name or IP address, and a port: uwsgi_pass localhost:9000; uwsgi_pass uwsgi://localhost:9000; uwsgi_pass suwsgi://[2001:db8::1]:9090; or as a UNIX-domain socket path: uwsgi_pass unix:/tmp/uwsgi.socket; If a domain nam

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

if

Syntax: if (condition) { ... } Default: — Context: server, location The specified condition is evaluated. If true, this module directives specified inside the braces are executed, and the request is assigned the configuration inside the if directive. Configurations inside the if directives are inherited from the previous configuration level. A condition may be any of the following: a variable name; false if the value of a variable is an empty string or “0”; Before version 1.0.

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.

log_subrequest

Syntax: log_subrequest on | off; Default: log_subrequest off; Context: http, server, location Enables or disables logging of subrequests into access_log.

keepalive_requests

Syntax: keepalive_requests number; Default: keepalive_requests 100; Context: http, server, location This directive appeared in version 0.8.0. Sets the maximum number of requests that can be served through one keep-alive connection. After the maximum number of requests are made, the connection is closed.

fastcgi_cache_bypass

Syntax: fastcgi_cache_bypass string ...; Default: — Context: http, server, location Defines conditions under which the response will not be taken from a cache. If at least one value of the string parameters is not empty and is not equal to “0” then the response will not be taken from the cache: fastcgi_cache_bypass $cookie_nocache $arg_nocache$arg_comment; fastcgi_cache_bypass $http_pragma $http_authorization; Can be used along with the fastcgi_no_cache directive.