proxy_send_timeout

Syntax: proxy_send_timeout time; Default: proxy_send_timeout 60s; Context: http, server, location Sets a timeout for transmitting a request to the proxied server. The timeout is set only between two successive write operations, not for the transmission of the whole request. If the proxied server does not receive anything within this time, the connection is closed.

mp4_limit_rate_after

Syntax: mp4_limit_rate_after time; Default: mp4_limit_rate_after 60s; Context: http, server, location Sets the initial amount of media data (measured in playback time) after which the further transmission of the response to a client will be rate limited. This directive is available as part of our commercial subscription.

auth_http_timeout

Syntax: auth_http_timeout time; Default: auth_http_timeout 60s; Context: mail, server Sets the timeout for communication with the authentication server.

hls_forward_args

Syntax: hls_forward_args on | off; Default: hls_forward_args off; Context: http, server, location This directive appeared in version 1.5.12. Adds arguments from a playlist request to URIs of fragments. This may be useful for performing client authorization at the moment of requesting a fragment, or when protecting an HLS stream with the ngx_http_secure_link_module module. For example, if a client requests a playlist http://example.com/hls/test.mp4.m3u8?a=1&b=2, the arguments

uwsgi_cache_max_range_offset

Syntax: uwsgi_cache_max_range_offset number; Default: — Context: http, server, location This directive appeared in version 1.11.6. Sets an offset in bytes for byte-range requests. If the range is beyond the offset, the range request will be passed to the uwsgi server and the response will not be cached.

limit_conn_zone

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

limit_req_zone

Syntax: limit_req_zone key zone=name:size rate=rate; Default: — Context: http Sets parameters for a shared memory zone that will keep states for various keys. In particular, the state stores the current number of excessive requests. The key can contain text, variables, and their combination. Requests with an empty key value are not accounted. Prior to version 1.7.6, a key could contain exactly one variable. Usage example: limit_req_zone $binary_remote_addr zone=o

ssl_stapling_responder

Syntax: ssl_stapling_responder url; Default: — Context: http, server This directive appeared in version 1.3.7. Overrides the URL of the OCSP responder specified in the “Authority Information Access” certificate extension. Only “http://” OCSP responders are supported: ssl_stapling_responder http://ocsp.example.com/;

fastcgi_cache_methods

Syntax: fastcgi_cache_methods GET | HEAD | POST ...; Default: fastcgi_cache_methods GET HEAD; Context: http, server, location This directive appeared in version 0.7.59. If the client request method is listed in this directive then the response will be cached. “GET” and “HEAD” methods are always added to the list, though it is recommended to specify them explicitly. See also the fastcgi_no_cache directive.

status_zone

Syntax: status_zone zone; Default: — Context: server Enables collection of virtual http or stream (1.7.11) server status information in the specified zone. Several servers may share the same zone.