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: ntlm; Default: — Context: upstream This directive appeared in version 1.9.2. Allows proxying requests with NTLM Authentication. The upstream connection is bound to the client connection once the client sends a request with the “Authorization” header field value starting with “Negotiate” or “NTLM”. Further client requests will be proxied through the same upstream connection, keeping the authentication context. In order for NTLM authentication to work, it is necessary to e

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: multi_accept on | off; Default: multi_accept off; Context: events If multi_accept is disabled, a worker process will accept one new connection at a time. Otherwise, a worker process will accept all new connections at a time. The directive is ignored if kqueue connection processing method is used, because it reports the number of new connections waiting to be accepted.

Syntax: msie_refresh on | off; Default: msie_refresh off; Context: http, server, location Enables or disables issuing refreshes instead of redirects for MSIE clients.

Syntax: msie_padding on | off; Default: msie_padding on; Context: http, server, location Enables or disables adding comments to responses for MSIE clients with status greater than 400 to increase the response size to 512 bytes.

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

Syntax: mp4_limit_rate_after time; Default: mp4_limit_rate_after 60s; Context: http, server, location Sets the initial amount of media data (measured in playback time) after which the further transmission of the response to a client will be rate limited. This directive is available as part of our commercial subscription.

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: mp4_buffer_size size; Default: mp4_buffer_size 512K; Context: http, server, location Sets the initial size of the buffer used for processing MP4 files.