Syntax: health_check [parameters]; Default: — Context: server Enables periodic health checks of the servers in a group. The following optional parameters are supported: interval=time sets the interval between two consecutive health checks, by default, 5 seconds. jitter=time sets the time within which each health check will be randomly delayed, by default, there is no delay. fails=number sets the number of consecutive failed health checks of a particular server after w

Syntax: health_check [parameters]; Default: — Context: location Enables periodic health checks of the servers in a group referenced in the surrounding location. The following optional parameters are supported: interval=time sets the interval between two consecutive health checks, by default, 5 seconds. jitter=time sets the time within which each health check will be randomly delayed, by default, there is no delay. fails=number sets the number of consecutive failed hea

Syntax: hash key [consistent]; Default: — Context: upstream Specifies a load balancing method for a server group where client-server mapping is based on the hashed key value. The key can contain text, variables, and their combinations (1.11.2). Usage example: hash $remote_addr; Note that adding or removing a server from the group may result in remapping most of the keys to different servers. The method is compatible with the Cache::Memcached Perl library. If the consistent pa

Syntax: hash key [consistent]; Default: — Context: upstream This directive appeared in version 1.7.2. Specifies a load balancing method for a server group where the client-server mapping is based on the hashed key value. The key can contain text, variables, and their combinations. Note that adding or removing a server from the group may result in remapping most of the keys to different servers. The method is compatible with the Cache::Memcached Perl library. If the consistent pa

Syntax: gzip_vary on | off; Default: gzip_vary off; Context: http, server, location Enables or disables inserting the “Vary: Accept-Encoding” response header field if the directives gzip, gzip_static, or gunzip are active.

Syntax: gzip_types mime-type ...; Default: gzip_types text/html; Context: http, server, location Enables gzipping of responses for the specified MIME types in addition to “text/html”. The special value “*” matches any MIME type (0.8.29). Responses with the “text/html” type are always compressed.

Syntax: gzip_static on | off | always; Default: gzip_static off; Context: http, server, location Enables (“on”) or disables (“off”) checking the existence of precompressed files. The following directives are also taken into account: gzip_http_version, gzip_proxied, gzip_disable, and gzip_vary. With the “always” value (1.3.6), gzipped file is used in all cases, without checking if the client supports it. It is useful if there are no uncompressed files on the disk anyw

Syntax: gzip_proxied off | expired | no-cache | no-store | private | no_last_modified | no_etag | auth | any ...; Default: gzip_proxied off; Context: http, server, location Enables or disables gzipping of responses for proxied requests depending on the request and response. The fact that the request is proxied is determined by the presence of the “Via” request header field. The directive accepts multiple parameters: off disables compressio

Syntax: gzip_min_length length; Default: gzip_min_length 20; Context: http, server, location Sets the minimum length of a response that will be gzipped. The length is determined only from the “Content-Length” response header field.

Syntax: gzip_http_version 1.0 | 1.1; Default: gzip_http_version 1.1; Context: http, server, location Sets the minimum HTTP version of a request required to compress a response.