auth_basic_user_file

Syntax: auth_basic_user_file file; Default: — Context: http, server, location, limit_except Specifies a file that keeps user names and passwords, in the following format: # comment name1:password1 name2:password2:comment name3:password3 The file name can contain variables. The following password types are supported: encrypted with the crypt() function; can be generated using the “htpasswd” utility from the Apache HTTP Server distribution or the “openssl passwd” command; h

geoip_country

Syntax: geoip_country file; Default: — Context: http Specifies a database used to determine the country depending on the client IP address. The following variables are available when using this database: $geoip_country_code two-letter country code, for example, “RU”, “US”. $geoip_country_code3 three-letter country code, for example, “RUS”, “USA”. $geoip_country_name country name, for example, “Russian Federation”, “United States”.

if_modified_since

Syntax: if_modified_since off | exact | before; Default: if_modified_since exact; Context: http, server, location This directive appeared in version 0.7.24. Specifies how to compare modification time of a response with the time in the “If-Modified-Since” request header field: off the “If-Modified-Since” request header field is ignored (0.7.34); exact exact match; before modification time of a response is less than or equal to the time in the “If-Modified-Since”

uwsgi_busy_buffers_size

Syntax: uwsgi_busy_buffers_size size; Default: uwsgi_busy_buffers_size 8k|16k; Context: http, server, location When buffering of responses from the uwsgi server is enabled, limits the total size of buffers that can be busy sending a response to the client while the response is not yet fully read. In the meantime, the rest of the buffers can be used for reading the response and, if needed, buffering part of the response to a temporary file. By default, size is limited by the size of

limit_zone

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;

zone

Syntax: zone name [size]; Default: — Context: upstream Defines the name and size of the shared memory zone that keeps the group’s configuration and run-time state that are shared between worker processes. Several groups may share the same zone. In this case, it is enough to specify the zone size only once. Additionally, as part of our commercial subscription, such groups allow changing the group membership or modifying the settings of a particular server without the need of resta

load_module

Syntax: load_module file; Default: — Context: main This directive appeared in version 1.9.11. Loads a dynamic module. Example: load_module modules/ngx_mail_module.so;

userid_mark

Syntax: userid_mark letter | digit | = | off; Default: userid_mark off; Context: http, server, location If the parameter is not off, enables the cookie marking mechanism and sets the character used as a mark. This mechanism is used to add or change userid_p3p and/or a cookie expiration time while preserving the client identifier. A mark can be any letter of the English alphabet (case-sensitive), digit, or the “=” character. If the mark is set, it is compared with the

charset_types

Syntax: charset_types mime-type ...; Default: charset_types text/html text/xml text/plain text/vnd.wap.wml application/javascript application/rss+xml; Context: http, server, location This directive appeared in version 0.7.9. Enables module processing in responses with the specified MIME types in addition to “text/html”. The special value “*” matches any MIME type (0.8.29). Until version 1.5.4, “application/x-javascript” was used as the default MIME type instead of “application/j

referer_hash_bucket_size

Syntax: referer_hash_bucket_size size; Default: referer_hash_bucket_size 64; Context: server, location This directive appeared in version 1.0.5. Sets the bucket size for the valid referers hash tables. The details of setting up hash tables are provided in a separate document.