You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by bu...@apache.org on 2013/07/11 01:34:11 UTC
svn commit: r869076 - in /websites/staging/trafficserver/trunk: cgi-bin/
content/ content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html
Author: buildbot
Date: Wed Jul 10 23:34:11 2013
New Revision: 869076
Log:
Staging update by buildbot for trafficserver
Modified:
websites/staging/trafficserver/trunk/cgi-bin/ (props changed)
websites/staging/trafficserver/trunk/content/ (props changed)
websites/staging/trafficserver/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html
Propchange: websites/staging/trafficserver/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 10 23:34:11 2013
@@ -1 +1 @@
-1501754
+1502058
Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 10 23:34:11 2013
@@ -1 +1 @@
-1501754
+1502058
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html Wed Jul 10 23:34:11 2013
@@ -28,7 +28,7 @@
</div>
<div class="fourcol right last" id="searchbox">
- <div id="header-main">Apache Traffic Server</div>
+ <div id="header-main">Adminstrator's Guide</div>
<div id="header-sub">Reverse Proxy and HTTP Redirects </div>
</div>
@@ -91,7 +91,6 @@ like a normal origin server.</p>
</ul>
</li>
<li><a href="#RedirectingHTTPRequests">Redirecting HTTP Requests</a></li>
-<li><a href="#remapconfig">remap.config</a></li>
</ul>
</div>
<h1 id="UnderstandingReverseProxyCaching">Understanding Reverse Proxy Caching</h1>
@@ -175,9 +174,8 @@ serves an HTTP request from a client bro
<ul>
<li>
<p>Create mapping rules in the <code>remap.config</code> file (refer to <a href="#CreatingMappingRulesHTTPRequests">Creating Mapping Rules for HTTP Requests</a>). </p>
-<p>:::text</p>
-<h1 id="remapconfig">remap.config</h1>
-<p>map http://www.host.com http://realhost.com</p>
+<p># remap.config
+map http://www.host.com http://realhost.com</p>
</li>
<li>
<p>Enable the reverse proxy option (refer to <a href="#EnablingHTTPReverseProxy">Enabling HTTP Reverse Proxy</a>). </p>
@@ -194,7 +192,7 @@ as a reverse proxy, it must readdress re
browsers are redirected to Traffic Server and <em>not</em> to another origin server. </p>
<p>To readdress redirects, Traffic Server uses reverse-map rules. Unless you have
<a href="../configuration-files/records.config#proxy.config.url_remap.pristine_host_hdr">proxy.config.url_remap.pristine_host_hdr</a>
-enabled (the default) you should generally set up a reverse-map rule for each map rule.d
+enabled (the default) you should generally set up a reverse-map rule for each map rule.
To create reverse-map rules, refer to <a href="#UsingMappingRulesHTTPRequests">Using Mapping Rules for HTTP Requests</a>. </p>
<h2 id="UsingMappingRulesHTTPRequests">Using Mapping Rules for HTTP Requests</h2>
<p>Traffic Server uses two types of mapping rules for HTTP reverse proxy.</p>
@@ -216,7 +214,7 @@ For the request URL to match a target UR
<p>If Traffic Server finds a match, then it translates the request URL into the replacement URL listed
in the map rule: it sets the host and path of the request URL to match the replacement URL.
If the URL contains path prefixes, then Traffic Server removes the prefix of the path that matches
-the target URL path and substitutes it with the path from the replacement URL. If two mappings match
+the target URL path and substitutes it with the path from the replacement URL. The map rule order matters. If two mappings match
a request URL, then Traffic Server applies the first mapping listed in the
<a href="../configuration-files/remap.config"><code>remap.config</code></a> file.</p>
<h3 id="reversemaprule">reverse-map rule</h3>