nginx-site: xml/en/docs/http/request_processing.xml comparison

comparison xml/en/docs/http/request_processing.xml @ 271:4c6d2c614d2c

Cleaned up XML tag mess: - all of <parameter> and <code>, and some of <dirname>, <value>, and <command> were replaced by <literal>; - the rest of <dirname> were replaced by links; - <argument> were replaced by <value>; - <value> is now rendered in HTML in italic; - <literal> and <path> can now contain <value>. Cleaned up terminology mess: - directives take "parameters".

author	Ruslan Ermilov <ru@nginx.com>
date	Fri, 23 Dec 2011 17:29:59 +0000
parents	682163f2b298
children	6135f3c95bf6

comparison

equal deleted inserted replaced

-:945d7299c26c
+:4c6d2c614d2c
 or the request does not contain this line at all,
 then nginx will route the request to the default server.
 In the configuration above, the default server is the first
 one&mdash;which is nginx&rsquo;s standard default behaviour.
 If you do not want the first server listed to be the default server,
-you may set it explicitly with the <dirname>default_server</dirname> parameter
+you may set it explicitly with the <literal>default_server</literal> parameter
-in the <dirname>listen</dirname> directive:
+in the <link doc="ngx_http_core_module.xml" id="listen"/> directive:
 <programlisting>
 server {
 listen       80  <b>default_server</b>;
 server_name  nginx.net  www.nginx.net;
 ...
 }
 </programlisting>
 <note>
-The <dirname>default_server</dirname> parameter has been available since
+The <literal>default_server</literal> parameter has been available since
 version 0.8.21.
-In earlier versions the <dirname>default</dirname> parameter should be used
+In earlier versions the <literal>default</literal> parameter should be used
 instead.
 </note>
 Note that the default server is a property of the listen port
 and not of the server name. More about this later.
 Here, the server name is set to an empty string which will match
 requests without the <header>Host</header> header line,
 and a special nginx’s non-standard code 444
 is returned that closes the connection.
 Since version 0.8.48, this is the default setting for the
-server name, so the <code>server_name ""</code> can be omitted.
+server name, so the <literal>server_name ""</literal> can be omitted.
 In earlier versions, the machine's <i>hostname</i> was used as
 a default server name.
 </para>
 </section>
 ...
 }
 </programlisting>
 In this configuration, nginx first tests the IP address and port
-of the request against the <dirname>listen</dirname> directives
+of the request against the
-of the <dirname>server</dirname> blocks. It then tests the &ldquo;Host&rdquo;
+<link doc="ngx_http_core_module.xml" id="listen"/> directives
-header line of the request against the <dirname>server_name</dirname>
+of the
-entries of the <dirname>server</dirname> blocks that matched
+<link doc="ngx_http_core_module.xml" id="server"/> blocks.
+It then tests the &ldquo;Host&rdquo;
+header line of the request against the
+<link doc="ngx_http_core_module.xml" id="server_name"/>
+entries of the
+<link doc="ngx_http_core_module.xml" id="server"/>
+blocks that matched
 the IP address and port.
 If the server name is not found, the request will be processed by
 the default server.
 For example, a request for <url>www.nginx.com</url> received on
 </para>
 <para>
 nginx first searches for the most specific location given by literal strings
 regardless of the listed order. In the configuration above
-the only literal location is “<code>/</code>” and since it matches
+the only literal location is “<literal>/</literal>” and since it matches
 any request it will be used as a last resort.
 Then nginx checks locations given by
 regular expression in the order listed in the configuration file.
 The first matching expression stops the search and nginx will use this
 location. If no regular expression matches a request, then nginx uses
 <list>
 <item>
 <para>
-A request “<code>/logo.gif</code>” is matched by the literal location
+A request “<literal>/logo.gif</literal>” is matched by the literal location
-“<code>/</code>” first and then by the regular expression
+“<literal>/</literal>” first and then by the regular expression
-“<code>\.(gif|jpg|png)$</code>”,
+“<literal>\.(gif|jpg|png)$</literal>”,
 therefore, it is handled by the latter location.
-Using the directive “<code>root&nbsp;/data/www</code>” the request
+Using the directive “<literal>root&nbsp;/data/www</literal>” the request
 is mapped to a file <path>/data/www/logo.gif</path>, and the file
 is sent to the client.
 </para>
 </item>
 <item>
 <para>
-A request “<code>/index.php</code>” is also matched by the literal location
+A request “<literal>/index.php</literal>” is also matched by the literal location
-“<code>/</code>” first and then by the regular expression
+“<literal>/</literal>” first and then by the regular expression
-“<code>\.(php)$</code>”. Therefore, it is handled by the latter location
+“<literal>\.(php)$</literal>”. Therefore, it is handled by the latter location
 and the request is passed to a FastCGI server listening on localhost:9000.
-The <dirname>fastcgi_param</dirname> directive sets the FastCGI parameter
+The
-SCRIPT_FILENAME to “<code>/data/www/index.php</code>”,
+<link doc="ngx_http_fastcgi_module.xml" id="fastcgi_param"/>
+directive sets the FastCGI parameter
+SCRIPT_FILENAME to “<literal>/data/www/index.php</literal>”,
 and the FastCGI server executes the file.
 The variable $document_root is equal to
-the value of the <dirname>root</dirname> directive and
+the value of the
+<link doc="ngx_http_core_module.xml" id="root"/>
+directive and
 the variable $fastcgi_script_name is equal to the request URI,
-i.e. “<code>/index.php</code>”.
+i.e. “<literal>/index.php</literal>”.
 </para>
 </item>
 <item>
 <para>
-A request “<code>/about.html</code>” is matched by the literal location
+A request “<literal>/about.html</literal>” is matched by the literal location
-“<code>/</code>” only, therefore, it is handled in this location.
+“<literal>/</literal>” only, therefore, it is handled in this location.
-Using the directive “<code>root /data/www</code>” the request is mapped
+Using the directive “<literal>root /data/www</literal>” the request is mapped
 to the file <path>/data/www/about.html</path>, and the file is sent
 to the client.
 </para>
 </item>
 <item>
 <para>
-Handling a request “<code>/</code>” is more complex.
+Handling a request “<literal>/</literal>” is more complex.
-It is matched by the literal location “<code>/</code>” only,
+It is matched by the literal location “<literal>/</literal>” only,
 therefore, it is handled by this location.
-Then the <dirname>index</dirname> directive tests for the existence
+Then the
+<link doc="ngx_http_index_module.xml" id="index"/>
+directive tests for the existence
 of an index file according to its parameters and
-the “<code>root&nbsp;/data/www</code>” directive.
+the “<literal>root&nbsp;/data/www</literal>” directive.
 If a file <path>/data/www/index.php</path> exists,
-then the directive does an internal redirect to “<code>/index.php</code>”, and
+then the directive does an internal redirect to “<literal>/index.php</literal>”,
-nginx searches the locations again as if the request had been sent by a client.
+and nginx searches the locations again
+as if the request had been sent by a client.
 As we saw before, the redirected request will eventually be handled
 by the FastCGI server.
 </para>
 </item>

Mercurial > hg > nginx-site

comparison xml/en/docs/http/request_processing.xml @ 271:4c6d2c614d2c