Syntax: location [ = | ~ | ~* | ^~ ] uri { ... }location @name { ... } Default: — Context: server, location Sets configuration depending on a request URI. The matching is performed against a normalized URI, after decoding the text encoded in the “%XX” form, resolving references to relative path components “.” and “..”, and possible compression of two or more adjacent slashes into a single slash. A location can either be defined by a prefix string, or by a re

Syntax: limit_except method ... { ... } Default: — Context: location Limits allowed HTTP methods inside a location. The method parameter can be one of the following: GET, HEAD, POST, PUT, DELETE, MKCOL, COPY, MOVE, OPTIONS, PROPFIND, PROPPATCH, LOCK, UNLOCK, or PATCH. Allowing the GET method makes the HEAD method also allowed. Access to other methods can be limited using the ngx_http_access_module and ngx_http_auth_basic_module modules directives: limit_except GET { allow 192

Syntax: modern_browser browser version;modern_browser unlisted; Default: — Context: http, server, location Specifies a version starting from which a browser is considered modern. A browser can be any one of the following: msie, gecko (browsers based on Mozilla), opera, safari, or konqueror. Versions can be specified in the following formats: X, X.X, X.X.X, or X.X.X.X. The maximum values for each of the format are 4000, 4000.99, 4000.99.99, and 4000.99.99.99, respectively. The s

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.

Syntax: uwsgi_buffer_size size; Default: uwsgi_buffer_size 4k|8k; Context: http, server, location Sets the size of the buffer used for reading the first part of the response received from the uwsgi server. This part usually contains a small response header. By default, the buffer size is equal to one memory page. This is either 4K or 8K, depending on a platform. It can be made smaller, however.

Syntax: memcached_pass address; Default: — Context: location, if in location Sets the memcached server address. The address can be specified as a domain name or IP address, and a port: memcached_pass localhost:11211; or as a UNIX-domain socket path: memcached_pass unix:/tmp/memcached.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.

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/

Syntax: scgi_cache_lock on | off; Default: scgi_cache_lock off; Context: http, server, location This directive appeared in version 1.1.12. When enabled, only one request at a time will be allowed to populate a new cache element identified according to the scgi_cache_key directive by passing a request to an SCGI server. Other requests of the same cache element will either wait for a response to appear in the cache or the cache lock for this element to be released, up to the time se

Syntax: ntlm; Default: — Context: upstream This directive appeared in version 1.9.2. Allows proxying requests with NTLM Authentication. The upstream connection is bound to the client connection once the client sends a request with the “Authorization” header field value starting with “Negotiate” or “NTLM”. Further client requests will be proxied through the same upstream connection, keeping the authentication context. In order for NTLM authentication to work, it is necessary to e

Syntax: proxy_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: proxy_cache_bypass $cookie_nocache $arg_nocache$arg_comment; proxy_cache_bypass $http_pragma $http_authorization; Can be used along with the proxy_no_cache directive.