Syntax: proxy_cookie_path off;proxy_cookie_path path replacement; Default: proxy_cookie_path off; Context: http, server, location This directive appeared in version 1.1.15. Sets a text that should be changed in the path 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 “path=/two/some/uri/”. The directive proxy_cookie_path /two/ /; will rewrite this attribute to “path=/so

Syntax: limit_conn_zone key zone=name:size; Default: — Context: stream Sets parameters for a shared memory zone that will keep states for various keys. In particular, the state includes the current number of connections. The key can contain text, variables, and their combinations (1.11.2). Connections with an empty key value are not accounted. Usage example: limit_conn_zone $binary_remote_addr zone=addr:10m; Here, the key is a client IP address set by the $binary_remot

Syntax: http { ... } Default: — Context: main Provides the configuration file context in which the HTTP server directives are specified.

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.

Syntax: fastcgi_no_cache string ...; Default: — Context: http, server, location Defines conditions under which the response will not be saved to 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 saved: fastcgi_no_cache $cookie_nocache $arg_nocache$arg_comment; fastcgi_no_cache $http_pragma $http_authorization; Can be used along with the fastcgi_cache_bypass directive.

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

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.

Syntax: proxy_pass_request_headers on | off; Default: proxy_pass_request_headers on; Context: http, server, location Indicates whether the header fields of the original request are passed to the proxied server. location /x-accel-redirect-here/ { proxy_method GET; proxy_pass_request_headers off; proxy_pass_request_body off; proxy_pass ... } See also the proxy_set_header and proxy_pass_request_body directives.

Syntax: proxy_next_upstream_timeout time; Default: proxy_next_upstream_timeout 0; Context: http, server, location This directive appeared in version 1.7.5. Limits the time during which a request can be passed to the next server. The 0 value turns off this limitation.

Syntax: xslt_last_modified on | off; Default: xslt_last_modified off; Context: http, server, location This directive appeared in version 1.5.1. Allows preserving the “Last-Modified” header field from the original response during XSLT transformations to facilitate response caching. By default, the header field is removed as contents of the response are modified during transformations and may contain dynamically generated elements or parts that are changed independently of the ori