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: limit_conn_log_level info | notice | warn | error; Default: limit_conn_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 limits the number of connections.

Syntax: limit_conn_log_level info | notice | warn | error; Default: limit_conn_log_level error; Context: stream, server Sets the desired logging level for cases when the server limits the number of connections.

Syntax: limit_conn_status code; Default: limit_conn_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_conn zone number; Default: — Context: stream, server Sets the shared memory zone and the maximum allowed number of connections for a given key value. When this limit is exceeded, the server will close the connection. For example, the directives limit_conn_zone $binary_remote_addr zone=addr:10m; server { ... limit_conn addr 1; } allow only one connection per an IP address at a time. When several limit_conn directives are specified, any configured limit w

Syntax: limit_conn zone number; Default: — Context: http, server, location Sets the shared memory zone and the maximum allowed number of connections for a given key value. When this limit is exceeded, the server will return the 503 (Service Temporarily Unavailable) error in reply to a request. For example, the directives limit_conn_zone $binary_remote_addr zone=addr:10m; server { location /download/ { limit_conn addr 1; } allow only one connection per an IP add

Syntax: least_time header | last_byte; Default: — Context: upstream This directive appeared in version 1.7.10. Specifies that a group should use a load balancing method where a request is passed to the server with the least average response time and least number of active connections, taking into account weights of servers. If there are several such servers, they are tried in turn using a weighted round-robin balancing method. If the header parameter is specified, time to receiv

Syntax: least_time connect | first_byte | last_byte; Default: — Context: upstream Specifies that a group should use a load balancing method where a connection is passed to the server with the least average time and least number of active connections, taking into account weights of servers. If there are several such servers, they are tried in turn using a weighted round-robin balancing method. If the connect parameter is specified, time to connect to the upstream server

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: least_conn; Default: — Context: upstream This directive appeared in versions 1.3.1 and 1.2.2. Specifies that a group should use a load balancing method where a request is passed to the server with the least number of active connections, taking into account weights of servers. If there are several such servers, they are tried in turn using a weighted round-robin balancing method.