Mercurial > hg > nginx-site
comparison xml/en/docs/http/ngx_http_core_module.xml @ 914:474a21f26a2a
Documented location behavior with proxying directives.
author | Vladimir Homutov <vl@nginx.com> |
---|---|
date | Thu, 23 May 2013 16:14:36 +0400 |
parents | 96839d165b8a |
children | ded8f4a5de28 |
comparison
equal
deleted
inserted
replaced
913:9a65d437da42 | 914:474a21f26a2a |
---|---|
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="19"> | 13 rev="20"> |
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> |
1477 Such a location is not used for a regular request processing, but instead | 1477 Such a location is not used for a regular request processing, but instead |
1478 used for request redirection. | 1478 used for request redirection. |
1479 They cannot be nested, and cannot contain nested locations. | 1479 They cannot be nested, and cannot contain nested locations. |
1480 </para> | 1480 </para> |
1481 | 1481 |
1482 <para> | |
1483 If a location is defined by a prefix string that ends with the slash character, | |
1484 and requests are processed by one of | |
1485 <link doc="ngx_http_proxy_module.xml" id="proxy_pass"/>, | |
1486 <link doc="ngx_http_fastcgi_module.xml" id="fastcgi_pass"/>, | |
1487 <link doc="ngx_http_scgi_module.xml" id="scgi_pass"/>, | |
1488 <link doc="ngx_http_uwsgi_module.xml" id="uwsgi_pass"/>, or | |
1489 <link doc="ngx_http_memcached_module.xml" id="memcached_pass"/>, | |
1490 then in response to a request with URI equal to this string, | |
1491 but without the trailing slash, | |
1492 a permanent redirect with the code 301 will be returned to the requested URI | |
1493 with the slash appended. | |
1494 If this is undesired, an exact match of the URI and location could be | |
1495 defined like this: | |
1496 <example> | |
1497 location /user/ { | |
1498 proxy_pass http://user.example.com; | |
1499 } | |
1500 | |
1501 location = /user { | |
1502 proxy_pass http://login.example.com; | |
1503 } | |
1504 </example> | |
1505 </para> | |
1506 | |
1482 <!-- | 1507 <!-- |
1483 <migration from="Apache" directive="Location" /> | 1508 <migration from="Apache" directive="Location" /> |
1484 --> | 1509 --> |
1485 | 1510 |
1486 </directive> | 1511 </directive> |