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: lock_file file; Default: lock_file logs/nginx.lock; Context: main nginx uses the locking mechanism to implement accept_mutex and serialize access to shared memory. On most systems the locks are implemented using atomic operations, and this directive is ignored. On other systems the “lock file” mechanism is used. This directive specifies a prefix for the names of lock files.

About nginScript What is currently supported What is not supported yet Download and install Installing as a Linux package Building from the sources Known Issues nginScript is a subset of the JavaScript language that allows implementing location and variable handlers in http and stream. nginScript is created in compliance with ECMAScript 5.1 with some ECMAScript 6 extensions. The compliance is still evolving.

Syntax: proxy_ssl_server_name on | off; Default: proxy_ssl_server_name off; Context: http, server, location This directive appeared in version 1.7.0. Enables or disables passing of the server name through TLS Server Name Indication extension (SNI, RFC 6066) when establishing a connection with the proxied HTTPS server.

Syntax: fastcgi_temp_file_write_size size; Default: fastcgi_temp_file_write_size 8k|16k; Context: http, server, location Limits the size of data written to a temporary file at a time, when buffering of responses from the FastCGI server to temporary files is enabled. By default, size is limited by two buffers set by the fastcgi_buffer_size and fastcgi_buffers directives. The maximum size of a temporary file is set by the fastcgi_max_temp_file_size directive.

Syntax: open_file_cache off;open_file_cache max=N [inactive=time]; Default: open_file_cache off; Context: http, server, location Configures a cache that can store: open file descriptors, their sizes and modification times; information on existence of directories; file lookup errors, such as “file not found”, “no read permission”, and so on. Caching of errors should be enabled separately by the open_file_cache_errors directive. The directive has the following parameters

Syntax: resolver address ... [valid=time];resolver off; Default: resolver off; Context: mail, server Configures name servers used to find the client’s hostname to pass it to the authentication server, and in the XCLIENT command when proxying SMTP. For example: resolver 127.0.0.1 [::1]:5353; An address can be specified as a domain name or IP address, and an optional port (1.3.1, 1.2.2). If port is not specified, the port 53 is used. Name servers are queried in a round-robin fas

Syntax: proxy_ssl_session_reuse on | off; Default: proxy_ssl_session_reuse on; Context: stream, server Determines whether SSL sessions can be reused when working with the proxied server. If the errors “SSL3_GET_FINISHED:digest check failed” appear in the logs, try disabling session reuse.

Connection processing methods nginx supports a variety of connection processing methods. The availability of a particular method depends on the platform used. On platforms that support several methods nginx will normally select the most efficient method automatically. However, if needed, a connection processing method can be selected explicitly with the use directive. The following connection processing methods are supported: select — standard method. The supporting module is built automa

Syntax: real_ip_header field | X-Real-IP | X-Forwarded-For | proxy_protocol; Default: real_ip_header X-Real-IP; Context: http, server, location Defines the request header field whose value will be used to replace the client address. The X-Real-IP and X-Forwarded-For parameters may contain an optional port (1.11.0). The address and port should be specified according to RFC 3986. The proxy_protocol parameter (1.5.12) changes the client address to the one from the