Syntax: uwsgi_connect_timeout time; Default: uwsgi_connect_timeout 60s; Context: http, server, location Defines a timeout for establishing a connection with a uwsgi server. It should be noted that this timeout cannot usually exceed 75 seconds.

Syntax: mp4_limit_rate on | off | factor; Default: mp4_limit_rate off; Context: http, server, location Limits the rate of response transmission to a client. The rate is limited based on the average bitrate of the MP4 file served. To calculate the rate, the bitrate is multiplied by the specified factor. The special value “on” corresponds to the factor of 1.1. The special value “off” disables rate limiting. The limit is set per a request, and so if a client simultaneousl

Syntax: absolute_redirect on | off; Default: absolute_redirect on; Context: http, server, location This directive appeared in version 1.11.8. If disabled, redirects issued by nginx will be relative. See also server_name_in_redirect and port_in_redirect directives.

nginx for Windows Known issues Possible future enhancements Version of nginx for Windows uses the native Win32 API (not the Cygwin emulation layer). Only the select() connection processing method is currently used, so high performance and scalability should not be expected. Due to this and some other known issues version of nginx for Windows is considered to be a beta version. At this time, it provides almost the same functionality as a UNIX version of nginx except for XSLT filter, image fil

Syntax: client_body_in_file_only on | clean | off; Default: client_body_in_file_only off; Context: http, server, location Determines whether nginx should save the entire client request body into a file. This directive can be used during debugging, or when using the $request_body_file variable, or the $r->request_body_file method of the module ngx_http_perl_module. When set to the value on, temporary files are not removed after request processing. The value clean

Syntax: fastcgi_limit_rate rate; Default: fastcgi_limit_rate 0; Context: http, server, location This directive appeared in version 1.7.7. Limits the speed of reading the response from the FastCGI 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 FastCFI server, the overall rate will be twice as much as the specified limit. The limitation works only if

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

Syntax: fastcgi_buffering on | off; Default: fastcgi_buffering on; Context: http, server, location This directive appeared in version 1.5.6. Enables or disables buffering of responses from the FastCGI server. When buffering is enabled, nginx receives a response from the FastCGI server as soon as possible, saving it into the buffers set by the fastcgi_buffer_size and fastcgi_buffers directives. If the whole response does not fit into memory, a part of it can be saved to a tempora

Syntax: proxy_cache_bypass string ...; Default: — Context: http, server, location Defines conditions under which the response will not be taken from 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 taken from the cache: proxy_cache_bypass $cookie_nocache $arg_nocache$arg_comment; proxy_cache_bypass $http_pragma $http_authorization; Can be used along with the proxy_no_cache directive.

Syntax: http { ... } Default: — Context: main Provides the configuration file context in which the HTTP server directives are specified.