Author: mlibbey Date: Wed Aug 21 18:22:32 2013 New Revision: 1516244 URL: http://svn.apache.org/r1516244 Log: Clarified connect to orign based on users@ question
Modified: trafficserver/site/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext Modified: trafficserver/site/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext URL: http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext?rev=1516244&r1=1516243&r2=1516244&view=diff ============================================================================== --- trafficserver/site/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext (original) +++ trafficserver/site/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext Wed Aug 21 18:22:32 2013 @@ -119,7 +119,7 @@ The figure above demonstrates the follow server (the origin serverâs advertised hostname resolves to Traffic Server). 2. Traffic Server locates a map rule in the `remap.config` file and remaps the request to the specified origin server (`realhost.com`). -3. Traffic Server opens an HTTP connection to the origin server. (This step is optional) +3. Traffic Server opens an HTTP connection to the origin server. (If the request is not able to be served from cache) 4. If the request is a cache hit and the content is fresh, then Traffic Server sends the requested object to the client from the cache. Otherwise, Traffic Server obtains the requested object from the origin server, sends the object to the client, and saves a copy in its cache.