trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zw...@apache.org
Subject [01/22] git commit: Clarified connect to orign based on users@ question
Date Sun, 06 Oct 2013 14:57:46 GMT
Updated Branches:
  refs/heads/5.0.x 4ab334d3a -> 15d4fb8d5


Clarified connect to orign based on users@ question


Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/8e11d382
Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/8e11d382
Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/8e11d382

Branch: refs/heads/5.0.x
Commit: 8e11d3829aa8eb824f02ae6e52cf93f5c0eed0da
Parents: be93cfb
Author: Miles Libbey <mlibbey@apache.org>
Authored: Wed Aug 21 11:35:59 2013 -0700
Committer: Miles Libbey <mlibbey@apache.org>
Committed: Wed Aug 21 11:35:59 2013 -0700

----------------------------------------------------------------------
 doc/admin/reverse-proxy-http-redirects.en.rst | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/trafficserver/blob/8e11d382/doc/admin/reverse-proxy-http-redirects.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/reverse-proxy-http-redirects.en.rst b/doc/admin/reverse-proxy-http-redirects.en.rst
index 54fb3ed..bacc03e 100644
--- a/doc/admin/reverse-proxy-http-redirects.en.rst
+++ b/doc/admin/reverse-proxy-http-redirects.en.rst
@@ -142,8 +142,7 @@ The figure above demonstrates the following steps:
    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


Mime
View raw message