underscores_in_headers

Syntax: underscores_in_headers on | off; Default: underscores_in_headers off; Context: http, server Enables or disables the use of underscores in client request header fields. When the use of underscores is disabled, request header fields whose names contain underscores are marked as invalid and become subject to the ignore_invalid_headers directive. If the directive is specified on the server level, its value is only used if a server is a default one. The value specified also ap

scgi_cache_path

Syntax: scgi_cache_path path [levels=levels] [use_temp_path=on|off] keys_zone=name:size [inactive=time] [max_size=size] [manager_files=number] [manager_sleep=time] [manager_threshold=time] [loader_files=number] [loader_sleep=time] [loader_threshold=time] [purger=on|off] [purger_files=number] [purger_sleep=time] [purger_threshold=time]; Default: — Context: http Sets the path and other parameters of a cache. Cache data

proxy_ignore_headers

Syntax: proxy_ignore_headers field ...; Default: — Context: http, server, location Disables processing of certain response header fields from the proxied server. The following fields can be ignored: “X-Accel-Redirect”, “X-Accel-Expires”, “X-Accel-Limit-Rate” (1.1.6), “X-Accel-Buffering” (1.1.6), “X-Accel-Charset” (1.1.6), “Expires”, “Cache-Control”, “Set-Cookie” (0.8.44), and “Vary” (1.7.7). If not disabled, processing of these header fields has the following effect: “X-Accel-E

proxy_ssl_name

Syntax: proxy_ssl_name name; Default: proxy_ssl_name host from proxy_pass; Context: stream, server Allows overriding the server name used to verify the certificate of the proxied server and to be passed through SNI when establishing a connection with the proxied server. The server name can also be specified using variables (1.11.3). By default, the host part of the proxy_pass address is used.

ssl_session_cache

Syntax: ssl_session_cache off | none | [builtin[:size]] [shared:name:size]; Default: ssl_session_cache none; Context: http, server Sets the types and sizes of caches that store session parameters. A cache can be of any of the following types: off the use of a session cache is strictly prohibited: nginx explicitly tells a client that sessions may not be reused. none the use of a session cache is gently disallowed: nginx tells a client that sessions may be reused

proxy_upload_rate

Syntax: proxy_upload_rate rate; Default: proxy_upload_rate 0; Context: stream, server This directive appeared in version 1.9.3. Limits the speed of reading the data from the client. The rate is specified in bytes per second. The zero value disables rate limiting. The limit is set per a connection, so if the client simultaneously opens two connections, the overall rate will be twice as much as the specified limit.

scgi_temp_file_write_size

Syntax: scgi_temp_file_write_size size; Default: scgi_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 SCGI server to temporary files is enabled. By default, size is limited by two buffers set by the scgi_buffer_size and scgi_buffers directives. The maximum size of a temporary file is set by the scgi_max_temp_file_size directive.

proxy_next_upstream

Syntax: proxy_next_upstream on | off; Default: proxy_next_upstream on; Context: stream, server When a connection to the proxied server cannot be established, determines whether a client connection will be passed to the next server. Passing a connection to the next server can be limited by the number of tries and by time.

uwsgi_no_cache

Syntax: uwsgi_no_cache string ...; Default: — Context: http, server, location Defines conditions under which the response will not be saved to a cache. If at least one value of the string parameters is not empty and is not equal to “0” then the response will not be saved: uwsgi_no_cache $cookie_nocache $arg_nocache$arg_comment; uwsgi_no_cache $http_pragma $http_authorization; Can be used along with the uwsgi_cache_bypass directive.

mp4_max_buffer_size

Syntax: mp4_max_buffer_size size; Default: mp4_max_buffer_size 10M; Context: http, server, location During metadata processing, a larger buffer may become necessary. Its size cannot exceed the specified size, or else nginx will return the 500 (Internal Server Error) server error, and log the following message: "/some/movie/file.mp4" mp4 moov atom is too large: 12583268, you may want to increase mp4_max_buffer_size