Syntax: protocol imap | pop3 | smtp; Default: — Context: server Sets the protocol for a proxied server. Supported protocols are IMAP, POP3, and SMTP. If the directive is not set, the protocol can be detected automatically based on the well-known port specified in the listen directive: imap: 143, 993 pop3: 110, 995 smtp: 25, 587, 465 Unnecessary protocols can be disabled using the configuration parameters --without-mail_imap_module, --without-mail_pop3_module, and

Syntax: userid on | v1 | log | off; Default: userid off; Context: http, server, location Enables or disables setting cookies and logging the received cookies: on enables the setting of version 2 cookies and logging of the received cookies; v1 enables the setting of version 1 cookies and logging of the received cookies; log disables the setting of cookies, but enables logging of the received cookies; off disables the setting of cookies and logging of the rec

Syntax: expires [modified] time;expires epoch | max | off; Default: expires off; Context: http, server, location, if in location Enables or disables adding or modifying the “Expires” and “Cache-Control” response header fields provided that the response code equals 200, 201, 204, 206, 301, 302, 303, 304, or 307. The parameter can be a positive or negative time. The time in the “Expires” field is computed as a sum of the current time and time specified in the directive

Syntax: server_tokens on | off | string; Default: server_tokens on; Context: http, server, location Enables or disables emitting nginx version in error messages and in the “Server” response header field. Additionally, as part of our commercial subscription, starting from version 1.9.13 the signature in error messages and the “Server” response header field value can be set explicitly using the string with variables. An empty string disables the emission of the “Server

Syntax: uwsgi_limit_rate rate; Default: uwsgi_limit_rate 0; Context: http, server, location This directive appeared in version 1.7.7. Limits the speed of reading the response from the uwsgi server. The rate is specified in bytes per second. The zero value disables rate limiting. The limit is set per a request, and so if nginx simultaneously opens two connections to the uwsgi server, the overall rate will be twice as much as the specified limit. The limitation works only if bufferi

Syntax: server_names_hash_max_size size; Default: server_names_hash_max_size 512; Context: http Sets the maximum size of the server names hash tables. The details of setting up hash tables are provided in a separate document.

Syntax: resolver address ... [valid=time] [ipv6=on|off]; Default: — Context: stream, server This directive appeared in version 1.11.3. Configures name servers used to resolve names of upstream servers into addresses, 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. If port is not specified, the port 53 is used. Name servers are queried in a round-robin fashion. By default, nginx will lo

Configuration file measurement units Sizes can be specified in bytes, kilobytes (suffixes k and K) or megabytes (suffixes m and M), for example, “1024”, “8k”, “1m”. Time intervals can be specified in milliseconds, seconds, minutes, hours, days and so on, using the following suffixes: ms milliseconds s seconds m minutes h hours d days w weeks M months, 30 days y years, 365 days Multiple units can be combined in a single value by specifying them in the order from the most to the least sign

Syntax: dav_access users:permissions ...; Default: dav_access user:rw; Context: http, server, location Sets access permissions for newly created files and directories, e.g.: dav_access user:rw group:rw all:r; If any group or all access permissions are specified then user permissions may be omitted: dav_access group:rw all:r;

Syntax: uwsgi_temp_path path [level1 [level2 [level3]]]; Default: uwsgi_temp_path uwsgi_temp; Context: http, server, location Defines a directory for storing temporary files with data received from uwsgi servers. Up to three-level subdirectory hierarchy can be used underneath the specified directory. For example, in the following configuration uwsgi_temp_path /spool/nginx/uwsgi_temp 1 2; a temporary file might look like this: /spool/nginx/uwsgi_temp/7/45/0000