comparison xml/en/docs/http/ngx_http_core_module.xml @ 738:0914bbb59fd2

Expanded "location" examples with another prefix location.
author Ruslan Ermilov <ru@nginx.com>
date Fri, 19 Oct 2012 12:25:29 +0000
parents 1f383a8bccdb
children 082a725038db
comparison
equal deleted inserted replaced
737:46bb8caea2ab 738:0914bbb59fd2
8 <!DOCTYPE module SYSTEM "../../../../dtd/module.dtd"> 8 <!DOCTYPE module SYSTEM "../../../../dtd/module.dtd">
9 9
10 <module name="Module ngx_http_core_module" 10 <module name="Module ngx_http_core_module"
11 link="/en/docs/http/ngx_http_core_module.html" 11 link="/en/docs/http/ngx_http_core_module.html"
12 lang="en" 12 lang="en"
13 rev="7"> 13 rev="8">
14 14
15 <section id="directives" name="Directives"> 15 <section id="directives" name="Directives">
16 16
17 <directive name="aio"> 17 <directive name="aio">
18 <syntax> 18 <syntax>
1445 1445
1446 location / { 1446 location / {
1447 [ configuration B ] 1447 [ configuration B ]
1448 } 1448 }
1449 1449
1450 location /documents/ {
1451 [ configuration C ]
1452 }
1453
1450 location ^~ /images/ { 1454 location ^~ /images/ {
1451 [ configuration C ] 1455 [ configuration D ]
1452 } 1456 }
1453 1457
1454 location ~* \.(gif|jpg|jpeg)$ { 1458 location ~* \.(gif|jpg|jpeg)$ {
1455 [ configuration D ] 1459 [ configuration E ]
1456 } 1460 }
1457 </example> 1461 </example>
1458 The “<literal>/</literal>” request will match configuration A, 1462 The “<literal>/</literal>” request will match configuration A,
1463 the “<literal>/index.html</literal>” request will match configuration B,
1459 the “<literal>/documents/document.html</literal>” request will match 1464 the “<literal>/documents/document.html</literal>” request will match
1460 configuration B, 1465 configuration C,
1461 the “<literal>/images/1.gif</literal>” request will match configuration C, and 1466 the “<literal>/images/1.gif</literal>” request will match configuration D, and
1462 the “<literal>/documents/1.jpg</literal>” request will match configuration D. 1467 the “<literal>/documents/1.jpg</literal>” request will match configuration E.
1463 </para> 1468 </para>
1464 1469
1465 <para> 1470 <para>
1466 The “<literal>@</literal>” prefix defines a named location. 1471 The “<literal>@</literal>” prefix defines a named location.
1467 Such a location is not used for a regular request processing, but instead 1472 Such a location is not used for a regular request processing, but instead