Syntax: f4f; Default: — Context: location Turns on module processing in the surrounding location.

Syntax: timeout time; Default: timeout 60s; Context: mail, server Sets the timeout that is used before proxying to the backend starts.

Syntax: auth_jwt string [token=$variable] | off; Default: auth_jwt off; Context: http, server, location Enables validation of JSON Web Token. The specified string is used as a realm. Parameter value can contain variables. The optional token parameter specifies a variable that contains JSON Web Token. By default, JWT is passed in the “Authorization” header as a Bearer Token. JWT may be also passed as a cookie or a part of a query string: auth_jwt "closed site" token

Syntax: google_perftools_profiles file; Default: — Context: main Sets a file name that keeps profiling information of nginx worker process. The ID of the worker process is always a part of the file name and is appended to the end of the file name, after a dot.

Syntax: image_filter_interlace on | off; Default: image_filter_interlace off; Context: http, server, location This directive appeared in version 1.3.15. If enabled, final images will be interlaced. For JPEG, final images will be in “progressive JPEG” format.

Syntax: uwsgi_modifier1 number; Default: uwsgi_modifier1 0; Context: http, server, location Sets the value of the modifier1 field in the uwsgi packet header.

Syntax: flv; Default: — Context: location Turns on module processing in a surrounding location.

Syntax: js_include file; Default: — Context: http Specifies a file that implements location and variable handlers in nginScript.

Syntax: uwsgi_cache_lock_timeout time; Default: uwsgi_cache_lock_timeout 5s; Context: http, server, location This directive appeared in version 1.1.12. Sets a timeout for uwsgi_cache_lock. When the time expires, the request will be passed to the uwsgi server, however, the response will not be cached. Before 1.7.8, the response could be cached.

Syntax: max_ranges number; Default: — Context: http, server, location This directive appeared in version 1.1.2. Limits the maximum allowed number of ranges in byte-range requests. Requests that exceed the limit are processed as if there were no byte ranges specified. By default, the number of ranges is not limited. The zero value disables the byte-range support completely.