nginx-quic: docs/html/http/ngx_http_core

comparison docs/html/http/ngx_http_core_module.html @ 4109:dc1fa52222b4

Regenerated after previous commit.

author	Ruslan Ermilov <ru@nginx.com>
date	Thu, 15 Sep 2011 08:33:25 +0000
parents	b7c944d1a5a8
children

comparison

equal deleted inserted replaced

-:5e2103cffd80
+:dc1fa52222b4
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>HTTP Core Module</title></head><body><a name="directives"></a><center><h4>Directives</h4></center><hr><a name="aio"></a><strong>syntax</strong>:
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>HTTP Core Module</title></head><body><center><h3>HTTP Core Module</h3></center><a name="directives"></a><center><h4>Directives</h4></center><hr><a name="aio"></a><strong>syntax</strong>:
 <code>aio
 <code>on</code> |
 <code>off</code> |
 <code>sendfile</code></code><br><strong>default</strong>:
 <code>aio off</code><br><strong>context</strong>:
 into a file.
 This directive can be used during debugging, or when using the
 <code>$request_body_file</code>
 variable, or the
 <a href="ngx_http_perl_module.html#methods">$r-&gt;request_body_file</a>
-method of the
+method of the module
-<a href="ngx_http_perl_module.html">http_perl</a> module.
+<a href="ngx_http_perl_module.html">ngx_http_perl_module</a>.
 </p><p>
 When set to the value <code>on</code>, temporary files are not
 removed after request processing.
 </p><p>
 The value <code>clean</code> will cause the temporary files
 <code>http</code>, <code>server</code>, <code>location</code><br><p>
 Defines a timeout for reading client request body.
 A timeout is only set between two successive read operations,
 not for the transmission of the whole request body.
 If a client does not transmit anything within this time,
-the error
+the client error
-<i>"Request time out"</i> (408)
+408 (Request Time-out)
 is returned.
 </p><hr><a name="client_header_buffer_size"></a><strong>syntax</strong>:
 <code>client_header_buffer_size <code><i>size</i></code></code><br><strong>default</strong>:
 <code>client_header_buffer_size 1k</code><br><strong>context</strong>:
 <code>http</code>, <code>server</code><br><p>
 <code>client_header_timeout <code><i>time</i></code></code><br><strong>default</strong>:
 <code>client_header_timeout 60</code><br><strong>context</strong>:
 <code>http</code>, <code>server</code><br><p>
 Defines a timeout for reading client request header.
 If a client does not transmit the entire header within this time,
-the error
+the client error
-<i>"Request time out"</i> (408)
+408 (Request Time-out)
 is returned.
 </p><hr><a name="client_max_body_size"></a><strong>syntax</strong>:
 <code>client_max_body_size <code><i>size</i></code></code><br><strong>default</strong>:
 <code>client_max_body_size 1m</code><br><strong>context</strong>:
 <code>http</code>, <code>server</code>, <code>location</code><br><p>
 Sets the maximum allowed size of the client request body,
 specified in the
 <code>Content-Length</code>
 request header field.
-If <code><i>size</i></code> is greater than the configured value, the
+If it exceeds the configured value, the client error
-<i>"Request Entity Too Large"</i> (413)
+413 (Request Entity Too Large)
-error is returned to a client.
+is returned.
 Please be aware that
 <a href="/web/upload.html">browsers cannot correctly display
 this error</a>.
 </p><hr><a name="default_type"></a><strong>syntax</strong>:
 <code>default_type <code><i>mime-type</i></code></code><br><strong>default</strong>:
 </dd></dl></p><hr><a name="internal"></a><strong>syntax</strong>:
 <code>internal</code><br><strong>default</strong>:
 <strong>none</strong><br><strong>context</strong>:
 <code>location</code><br><p>
 Specifies that a given location can only be used for internal requests.
-For external requests, the <i>"Not found"</i> (404)
+For external requests, the client error
-error is returned.
+404 (Not Found)
+is returned.
 Internal requests are the following:
 <ul><li>
 requests redirected by the <a href="#error_page">error_page</a> directive;
 </li><li>
 subrequests formed by the
 <code>include virtual</code>
-command of the
+command of the module
-<a href="ngx_http_ssi_module.html">http_ssi</a> module;
+<a href="ngx_http_ssi_module.html">ngx_http_ssi_module</a>;
 </li><li>
 requests changed by the
 <a href="ngx_http_rewrite_module.html#rewrite">rewrite</a>
-directive of the
+directive of the module
-<a href="ngx_http_rewrite_module.html">http_rewrite</a> module.
+<a href="ngx_http_rewrite_module.html">ngx_http_rewrite_module</a>.
 </li></ul></p><p>
 Example:
 <blockquote><pre>
 error_page 404 /404.html;
 <code>large_client_header_buffers <code><i>number size</i></code></code><br><strong>default</strong>:
 <code>large_client_header_buffers 4 4k/8k</code><br><strong>context</strong>:
 <code>http</code>, <code>server</code><br><p>
 Sets the maximum <code><i>number</i></code> and <code><i>size</i></code> of
 buffers used when reading large client request headers.
-A request line cannot exceed the size of one buffer, or the
+A request line cannot exceed the size of one buffer, or the client error
-<i>"Request URI too large"</i> (414)
+414 (Request-URI Too Large)
-error is returned.
+is returned.
 A request header field cannot exceed the size of one buffer as well, or the
-<i>"Bad request"</i> (400)
+client error
-error is returned.
+400 (Bad Request)
+is returned.
 Buffers are allocated only on demand.
 By default, the buffer size is equal to one memory page size.
 It is either 4K or 8K, platform dependent.
 If after the end of request processing a connection is transitioned
 into the keep-alive state, these buffers are freed.
 <strong>none</strong><br><strong>context</strong>:
 <code>location</code><br><p>
 Limits allowed HTTP methods inside a location.
 The GET method also implies the HEAD method.
 Access to other methods can be limited using the
-<a href="ngx_http_access_module.html">http_access</a>
+<a href="ngx_http_access_module.html">ngx_http_access_module</a>
 and
-<a href="ngx_http_auth_basic_module.html">http_auth_basic</a>
+<a href="ngx_http_auth_basic_module.html">ngx_http_auth_basic_module</a>
 modules directives:
 <blockquote><pre>
 limit_except GET {
 allow 192.168.1.0/32;
 deny  all;
 </p><hr><a name="satisfy"></a><strong>syntax</strong>:
 <code>satisfy <code>all</code> | <code>any</code></code><br><strong>default</strong>:
 <code>satisfy all</code><br><strong>context</strong>:
 <code>location</code><br><p>
 Allows access if any of the
-<a href="ngx_http_access_module.html">http_access</a>
+<a href="ngx_http_access_module.html">ngx_http_access_module</a>
-or <a href="ngx_http_auth_basic_module.html">http_auth_basic</a>
+or <a href="ngx_http_auth_basic_module.html">ngx_http_auth_basic_module</a>
 modules grant access.
 <blockquote><pre>
 location / {
 satisfy any;
 <code>underscores_in_headers <code>on</code> | <code>off</code></code><br><strong>default</strong>:
 <code>underscores_in_headers off</code><br><strong>context</strong>:
 <code>http</code>, <code>server</code><br><p>
 Enables or disables the use of underscores in client request header fields.
 </p><a name="variables"></a><center><h4>Embedded Variables</h4></center><p>
-The http_core module supports embedded variables with names matching
+The module <code>ngx_http_core_module</code> supports embedded variables with
-those of the Apache Server.
+names matching those of the Apache Server.
 First of all, these are variables representing client request header
 fields, such as, <code>$http_user_agent</code>, <code>$http_cookie</code>,
 and so on.
 It also supports other variables:
 <dl compact><dt><code>$args</code></dt><dd>

Mercurial > hg > nginx-quic

comparison docs/html/http/ngx_http_core_module.html @ 4109:dc1fa52222b4