svn commit: r1101413 - /trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext

[ig...@apache.org]

Author: igalic
Date: Tue May 10 11:36:33 2011
New Revision: 1101413

URL: http://svn.apache.org/viewvc?rev=1101413&view=rev
Log:
Minor fixes of the markdown

Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext?rev=1101413&r1=1101412&r2=1101413&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext Tue May 10 11:36:33 2011
@@ -90,7 +90,7 @@ obtains the content from the origin serv
 Server access to the origin server). The sensitive content resides on the origin 
 server, safely inside the firewall. 
 
-### How Does Reverse Proxy Work?  ### {#HowDoesReverseProxyWork?}
+### How Does Reverse Proxy Work?  ### {#HowDoesReverseProxyWork}
 
 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 
@@ -138,19 +138,23 @@ Traffic Server must construct a proxy re
 
 In HTTP, proxy requests specify the entire URL whereas server requests specify only the path. A server request might look like this:
 
+    :::text
     GET /index.html HTTP/1.0 Host: real.dianes-books.com
 
 However, the corresponding proxy request would look like this
 
+    :::text
     GET http://real.dianes-books.com/index.html HTTP/1.0 Host: real.dianes-books.com
 
 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 `real.dianes-books.com`, the server request and host header would be:
 
+    :::text
     GET /index.html HTTP/1.0 Host: www.dianes-books.com
 
  And the correct proxy request should be
 
-     GET http://real.dianes-books.com/index.html HTTP/1.0 Host: real.dianes-books.com
+    :::text
+    GET http://real.dianes-books.com/index.html HTTP/1.0 Host: real.dianes-books.com
 
 To translate `www.dianes-books.com` to `real.dianes-books.com`, Traffic Server 
 needs a set of URL rewriting rules (mapping rules). Mapping rules are described 
@@ -259,6 +263,7 @@ redirects** notify the browser of the UR
 
 The following permanently redirects all HTTP requests for `www.server1.com` to `www.server2.com`:
 
+    :::text
     redirect http://www.server1.com http://www.server2.com