trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mlib...@apache.org
Subject [01/20] trafficserver git commit: Uncomment ICP doc section
Date Thu, 22 Jan 2015 23:23:32 GMT
Repository: trafficserver
Updated Branches:
  refs/heads/master cc6b44fad -> 729cb8003


Uncomment ICP doc section


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

Branch: refs/heads/master
Commit: 49067c416459869241f475ba8107a306036fd1f2
Parents: 38b83c1
Author: Miles Libbey <mlibbey@apache.org>
Authored: Mon Jan 12 13:04:03 2015 -0800
Committer: Miles Libbey <mlibbey@apache.org>
Committed: Thu Jan 22 15:22:29 2015 -0800

----------------------------------------------------------------------
 doc/admin/hierachical-caching.en.rst | 92 +++++++++++++++----------------
 1 file changed, 46 insertions(+), 46 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/trafficserver/blob/49067c41/doc/admin/hierachical-caching.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/hierachical-caching.en.rst b/doc/admin/hierachical-caching.en.rst
index 69ba2cc..e1c9019 100644
--- a/doc/admin/hierachical-caching.en.rst
+++ b/doc/admin/hierachical-caching.en.rst
@@ -134,50 +134,50 @@ address.::
 
 Run the command :option:`traffic_line -x` to apply the configuration changes.
 
-.. XXX As of yet, this is unsupported.
-
-.. # ICP Peering # {#ICPPeering}
-
-.. The Internet Cache Protocol (ICP) is used by proxy caches to exchange information
-   about their content. ICP query messages ask other caches if they are storing 
-   a particular URL; ICP response messages reply with a hit or miss answer. A
-   cache exchanges ICP messages only with specific **ICP peers**, which are neighboring
-   caches that can receive ICP messages. An ICP peer can be a **sibling cache
-   **(which is at the same level in the hierarchy) or a **parent cache** (which 
-   is one level up in the hierarchy).
-
-.. If Traffic Server has ICP caching enabled, then it sends ICP queries to its
-   ICP peers when the HTTP request is a cache miss. If there are no hits but parents
-   exist, then a parent is selected using a round-robin policy. If no ICP parents
-   exist, then Traffic Server forwards the request to its HTTP parents. If there
-   are no HTTP parent caches established, then Traffic Server forwards the request
-   to the origin server.
-
-.. If Traffic Server receives a hit message from an ICP peer, then Traffic Server
-   sends the HTTP request to that peer. However, it might turn out to be a cache
-   miss because the original HTTP request contains header information that is
-   not communicated by the ICP query. For example, the hit might not be the requested
-   alternate. If an ICP hit turns out to be a miss, then Traffic Server forwards
-   the request to either its HTTP parent caches or to the origin server.
-
-.. To configure a Traffic Server node to be part of an ICP cache hierarchy, you 
-   must perform the following tasks:
-
-.. * Determine if the Traffic Server can receive ICP messages only, or if it can send _and_
receive ICP messages.
-   * Determine if Traffic Server can send messages directly to each ICP peer or send a single
message on a specified multicast channel.
-   * Specify the port used for ICP messages.
-   * Set the ICP query timeout.
-   * Identify the ICP peers (siblings and parents) with which Traffic Server can communicate.
-
-.. To configure Traffic Server to use an ICP cache hierarchy edit the following variables
in :file:`records.config` file:
-
-.. * :ts:cv:`proxy.config.icp.enabled`
-   * :ts:cv:`proxy.config.icp.icp_port`
-   * :ts:cv:`proxy.config.icp.multicast_enabled`
-   * :ts:cv:`proxy.config.icp.query_timeout`
-
-.. Edit :file:`icp.config` file located in the Traffic Server `config` directory:
-   For each ICP peer you want to identify, enter a separate rule in the :file:`icp.config`
file.
-
-.. Run the command :option:`traffic_line -x` to apply the configuration changes.
+.. _admin-icp-peering:
+
+ICP Peering
+===========
+
+The Internet Cache Protocol (ICP) is used by proxy caches to exchange information
+about their content. ICP query messages ask other caches if they are storing 
+a particular URL; ICP response messages reply with a hit or miss answer. A
+cache exchanges ICP messages only with specific ICP peers, which are neighboring
+caches that can receive ICP messages. An ICP peer can be a sibling cache
+(which is at the same level in the hierarchy) or a parent cache (which 
+is one level up in the hierarchy).
+
+If Traffic Server has ICP caching enabled, then it sends ICP queries to its
+ICP peers when the HTTP request is a cache miss. If there are no hits but parents
+exist, then a parent is selected using a round-robin policy. If no ICP parents
+exist, then Traffic Server forwards the request to its HTTP parents. If there
+are no HTTP parent caches established, then Traffic Server forwards the request
+to the origin server.
+
+If Traffic Server receives a hit message from an ICP peer, then Traffic Server
+sends the HTTP request to that peer. However, it might turn out to be a cache
+miss because the original HTTP request contains header information that is
+not communicated by the ICP query. For example, the hit might not be the requested
+alternate. If an ICP hit turns out to be a miss, then Traffic Server forwards
+the request to either its HTTP parent caches or to the origin server.
+
+To configure a Traffic Server node to be part of an ICP cache hierarchy, you 
+must perform the following tasks:
+
+* Determine if the Traffic Server can receive ICP messages only, or if it can send *and*
receive ICP messages.
+* Determine if Traffic Server can send messages directly to each ICP peer or send a single
message on a specified multicast channel.
+* Specify the port used for ICP messages.
+* Set the ICP query timeout.
+* Identify the ICP peers (siblings and parents) with which Traffic Server can communicate.
+
+To configure Traffic Server to use an ICP cache hierarchy edit the following variables in
:file:`records.config` file:
+
+* :ts:cv:`proxy.config.icp.enabled`
+* :ts:cv:`proxy.config.icp.icp_port`
+* :ts:cv:`proxy.config.icp.multicast_enabled`
+* :ts:cv:`proxy.config.icp.query_timeout`
+
+Edit :file:`icp.config` file located in the Traffic Server `config` directory:
+For each ICP peer you want to identify, enter a separate rule in the :file:`icp.config` file.
 
+Run the command :option:`traffic_line -x` to apply the configuration changes.


Mime
View raw message