svn commit: r789431 - /websites/staging/trafficserver/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Tue May 10 11:36:42 2011
New Revision: 789431

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html

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 Tue May 10 11:36:42 2011
@@ -98,7 +98,7 @@ the cache. If the content is sensitive a
 obtains the content from the origin server (the firewall allows only Traffic 
 Server access to the origin server). The sensitive content resides on the origin 
 server, safely inside the firewall. </p>
-<h3 id="how_does_reverse_proxy_work___howdoesreverseproxywork">How Does Reverse Proxy Work?  ### {#HowDoesReverseProxyWork?}</h3>
+<h3 id="HowDoesReverseProxyWork">How Does Reverse Proxy Work?</h3>
 <p>When a browser makes a request, it normally sends that request directly to 
 the origin server. When Traffic Server is in reverse proxy mode, it intercepts 
 the request before it reaches the origin server. Typically, this is done by 
@@ -135,22 +135,22 @@ as an origin server rather than a proxy 
 server requests and not proxy requests. Therefore, to satisfy proxy requests, 
 Traffic Server must construct a proxy request from the server request. </p>
 <p>In HTTP, proxy requests specify the entire URL whereas server requests specify only the path. A server request might look like this:</p>
-<div class="codehilite"><pre><span class="n">GET</span> <span class="sr">/index.html HTTP/</span><span class="mf">1.0</span> <span class="n">Host:</span> <span class="n">real</span><span class="o">.</span><span class="n">dianes</span><span class="o">-</span><span class="n">books</span><span class="o">.</span><span class="n">com</span>
+<div class="codehilite"><pre>GET /index.html HTTP/1.0 Host: real.dianes-books.com
 </pre></div>
 
 
 <p>However, the corresponding proxy request would look like this</p>
-<div class="codehilite"><pre><span class="n">GET</span> <span class="n">http:</span><span class="sr">//</span><span class="n">real</span><span class="o">.</span><span class="n">dianes</span><span class="o">-</span><span class="n">books</span><span class="o">.</span><span class="n">com</span><span class="sr">/index.html HTTP/</span><span class="mf">1.0</span> <span class="n">Host:</span> <span class="n">real</span><span class="o">.</span><span class="n">dianes</span><span class="o">-</span><span class="n">books</span><span class="o">.</span><span class="n">com</span>
+<div class="codehilite"><pre>GET http://real.dianes-books.com/index.html HTTP/1.0 Host: real.dianes-books.com
 </pre></div>
 
 
 <p>Traffic Server can construct a proxy request from a server request by using the server information in the host header. However, the correct proxy request must contain the hostname of the origin server, not the advertised hostname that name servers associate to Traffic Server. The advertised hostname is the name that appears in the host header; for the origin server <code>real.dianes-books.com</code>, the server request and host header would be:</p>
-<div class="codehilite"><pre><span class="n">GET</span> <span class="sr">/index.html HTTP/</span><span class="mf">1.0</span> <span class="n">Host:</span> <span class="n">www</span><span class="o">.</span><span class="n">dianes</span><span class="o">-</span><span class="n">books</span><span class="o">.</span><span class="n">com</span>
+<div class="codehilite"><pre>GET /index.html HTTP/1.0 Host: www.dianes-books.com
 </pre></div>
 
 
 <p>And the correct proxy request should be</p>
-<div class="codehilite"><pre> <span class="n">GET</span> <span class="n">http:</span><span class="sr">//</span><span class="n">real</span><span class="o">.</span><span class="n">dianes</span><span class="o">-</span><span class="n">books</span><span class="o">.</span><span class="n">com</span><span class="sr">/index.html HTTP/</span><span class="mf">1.0</span> <span class="n">Host:</span> <span class="n">real</span><span class="o">.</span><span class="n">dianes</span><span class="o">-</span><span class="n">books</span><span class="o">.</span><span class="n">com</span>
+<div class="codehilite"><pre>GET http://real.dianes-books.com/index.html HTTP/1.0 Host: real.dianes-books.com
 </pre></div>
 
 
@@ -243,7 +243,7 @@ redirects</strong> notify the browser of
 </ol>
 <p><strong>Example</strong></p>
 <p>The following permanently redirects all HTTP requests for <code>www.server1.com</code> to <code>www.server2.com</code>:</p>
-<div class="codehilite"><pre><span class="n">redirect</span> <span class="n">http:</span><span class="sr">//</span><span class="n">www</span><span class="o">.</span><span class="n">server1</span><span class="o">.</span><span class="n">com</span> <span class="n">http:</span><span class="sr">//</span><span class="n">www</span><span class="o">.</span><span class="n">server2</span><span class="o">.</span><span class="n">com</span>
+<div class="codehilite"><pre>redirect http://www.server1.com http://www.server2.com
 </pre></div>
     </div>
   </div><!-- main -->