Syntax: client_body_in_single_buffer on | off; Default: client_body_in_single_buffer off; Context: http, server, location Determines whether nginx should save the entire client request body in a single buffer. The directive is recommended when using the $request_body variable, to save the number of copy operations involved.

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: client_body_buffer_size size; Default: client_body_buffer_size 8k|16k; Context: http, server, location Sets buffer size for reading client request body. In case the request body is larger than the buffer, the whole body or only its part is written to a temporary file. By default, buffer size is equal to two memory pages. This is 8K on x86, other 32-bit platforms, and x86-64. It is usually 16K on other 64-bit platforms.

Syntax: chunked_transfer_encoding on | off; Default: chunked_transfer_encoding on; Context: http, server, location Allows disabling chunked transfer encoding in HTTP/1.1. It may come in handy when using a software failing to support chunked encoding despite the standard’s requirement.

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

Syntax: charset_map charset1 charset2 { ... } Default: — Context: http Describes the conversion table from one charset to another. A reverse conversion table is built using the same data. Character codes are given in hexadecimal. Missing characters in the range 80-FF are replaced with “?”. When converting from UTF-8, characters missing in a one-byte charset are replaced with “&#XXXX;”. Example: charset_map koi8-r windows-1251 { C0 FE ; # small yu C1 E0 ; # small a

Syntax: charset charset | off; Default: charset off; Context: http, server, location, if in location Adds the specified charset to the “Content-Type” response header field. If this charset is different from the charset specified in the source_charset directive, a conversion is performed. The parameter off cancels the addition of charset to the “Content-Type” response header field. A charset can be defined with a variable: charset $charset; In such a case, all possible value

Building nginx on the Win32 platform with Visual C Build steps See also

Building nginx from Sources The build is configured using the configure command. It defines various aspects of the system, including the methods nginx is allowed to use for connection processing. At the end it creates a Makefile. The configure command supports the following parameters: --prefix=path — defines a directory that will keep server files. This same directory will also be used for all relative paths set by configure (except for paths to libraries sources) and in the nginx.conf con

Syntax: break; Default: — Context: server, location, if Stops processing the current set of ngx_http_rewrite_module directives. If a directive is specified inside the location, further processing of the request continues in this location. Example: if ($slow) { limit_rate 10k; break; }