Syntax: lingering_time time; Default: lingering_time 30s; Context: http, server, location When lingering_close is in effect, this directive specifies the maximum time during which nginx will process (read and ignore) additional data coming from a client. After that, the connection will be closed, even if there will be more data.

Syntax: limit_zone name $variable size; Default: — Context: http This directive was made obsolete in version 1.1.8 and was removed in version 1.7.6. An equivalent limit_conn_zone directive with a changed syntax should be used instead: limit_conn_zone $variable zone=name:size;

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

Syntax: limit_req_status code; Default: limit_req_status 503; Context: http, server, location This directive appeared in version 1.3.15. Sets the status code to return in response to rejected requests.

Syntax: limit_rate_after size; Default: limit_rate_after 0; Context: http, server, location, if in location This directive appeared in version 0.8.0. Sets the initial amount after which the further transmission of a response to a client will be rate limited. Example: location /flv/ { flv; limit_rate_after 500k; limit_rate 50k; }

Syntax: limit_req zone=name [burst=number] [nodelay]; Default: — Context: http, server, location Sets the shared memory zone and the maximum burst size of requests. If the requests rate exceeds the rate configured for a zone, their processing is delayed such that requests are processed at a defined rate. Excessive requests are delayed until their number exceeds the maximum burst size in which case the request is terminated with an error 503 (Service Temporarily Unavail

Syntax: limit_req_log_level info | notice | warn | error; Default: limit_req_log_level error; Context: http, server, location This directive appeared in version 0.8.18. Sets the desired logging level for cases when the server refuses to process requests due to rate exceeding, or delays request processing. Logging level for delays is one point less than for refusals; for example, if “limit_req_log_level notice” is specified, delays are logged with the info level.

Syntax: limit_rate rate; Default: limit_rate 0; Context: http, server, location, if in location Limits the rate of response transmission to a client. The rate is specified in bytes per second. The zero value disables rate limiting. The limit is set per a request, and so if a client simultaneously opens two connections, the overall rate will be twice as much as the specified limit. Rate limit can also be set in the $limit_rate variable. It may be useful in cases where rate should

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: 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