svn commit: r787358 - /websites/staging/trafficserver/trunk/content/docs/trunk/admin/hierachical-caching/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Tue Mar 22 12:46:20 2011
New Revision: 787358

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/hierachical-caching/index.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/hierachical-caching/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/hierachical-caching/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/hierachical-caching/index.en.html Tue Mar 22 12:46:20 2011
@@ -71,7 +71,7 @@ HTTP and HTTPS requests. </p>
 <p><strong>Note:</strong> If you do not want all requests to go to the parent cache, then simply 
 configure Traffic Server to route certain requests (such as requests containing 
 specific URLs) directly to the origin server. SImply set parent proxy rules 
-in <a href="files.htm#parent.config">parent.config</a>.</p>
+in <a href="../configuration-files/parent.config">parent.config</a></p>
 <p>The figure below illustrates a simple cache hierarchy with a Traffic Server 
 node configured to use a parent cache. In the following scenario, a client 
 sends a request to a Traffic Server node that is a child in the cache hierarchy 
@@ -81,10 +81,7 @@ parent cache, where it is a cache hit. T
 to the Traffic Server, where it is cached and then served to the client. Future 
 requests for this content can now be served directly from the Traffic Server 
 cache (until the data is stale or expired).</p>
-<p><img alt="" src="images/cachehrc.jpg" /></p>
-<blockquote>
-<p><em><strong>Parent caching</strong></em></p>
-</blockquote>
+<p><img alt="Parent caching" src="/images/admin/cachehrc.jpg" /></p>
 <p><strong>Note:</strong> If the request is a cache miss on the parent, then the parent retrieves 
 the content from the origin server (or from another cache, depending on the 
 parent’s configuration). The parent caches the content and then sends a copy 
@@ -105,38 +102,35 @@ in the configuration file. </p>
 the following steps: </p>
 <ul>
 <li>Enable the parent caching option. </li>
-<li>Identify the parent cache you want to use to service missed requests. To use <strong>parent failover</strong>, you must identify more than one parent cache so that when a parent cache is unavailable, requests are sent to another parent cache.</li>
+<li>Identify the parent cache you want to use to service missed requests.
+ To use <strong>parent failover</strong>, you must identify more than one parent cache
+ so that when a parent cache is unavailable, requests are sent to another parent cache.</li>
 </ul>
 <p><strong>Note:</strong> You need to configure the child cache only. No additional configuration 
 is needed for the Traffic Server parent cache. </p>
 <h5 id="ConfigureTSuseaparentcache">Configure Traffic Server to use a parent cache:</h5>
-<ol>
-<li>In a text editor, open the <code>records.config</code> file located in the Traffic Server <code>config</code> directory. </li>
-<li>Edit the following variable:</li>
-<li />
-<li>
+<p>Edit the following variable in <code>records.config</code> file located in the Traffic Server <code>config</code> directory. </p>
 <dl>
-<dt><strong>Variable</strong> <strong>Description</strong></dt>
 <dt><em><code>proxy.config.http.parent_proxy_routing_enable</code></em></dt>
 <dd>Set this variable to 1 to enable the parent caching option.</dd>
 </dl>
-</li>
-<li />
-<li>Save and close the <code>records.config</code> file. </li>
-<li>In a text editor, open the <code>parent.config</code> file located in the Traffic Server <code>config</code> directory. </li>
-<li>Set parent proxy rules to specify the parent cache to which you want missed requests to be forwarded; refer to <a href="files.htm#parent.config">parent.config</a>. <br />
- The following example configures Traffic Server to route all requests containing the regular expression <code>politics</code> and the path <code>/viewpoint</code> directly to the origin server (bypassing any parent hierarchies): <br />
-<code>url_regex=politics prefix=/viewpoint go_direct=true</code><br />
-</li>
-</ol>
-<p>The following example configures Traffic Server to direct all missed requests with URLs beginning with <code>mms://host1</code> to the parent cache <code>parent1</code>. If <code>parent1</code> cannot serve the requests, then requests are forwarded to <code>parent2</code>. Because <code>round-robin=true</code>, Traffic Server goes through the parent cache list in a round-robin based on client IP address. <br />
-<code>dest_host=host1 scheme=mms parent=”parent1;parent2” round-robin=strict</code><br />
-</p>
-<ol>
-<li>Save and close <code>parent.config</code></li>
-<li>Navigate to the Traffic Server <code>bin</code> directory.</li>
-<li>Run the command <code>traffic_line -x</code> to apply the configuration changes.</li>
-</ol>
+<p>Edit the <a href="../configuration-files/parent.config"><code>parent.config</code></a> file located in the Traffic Server <code>config</code> directory to set
+parent proxy rules to specify the parent cache to which you want missed requests to be forwarded;</p>
+<p>The following example configures Traffic Server to route all requests containing the regular expression <code>politics</code>
+and the path <code>/viewpoint</code> directly to the origin server (bypassing any parent hierarchies):</p>
+<div class="codehilite"><pre><span class="n">url_regex</span><span class="o">=</span><span class="n">politics</span> <span class="n">prefix</span><span class="o">=/</span><span class="n">viewpoint</span> <span class="n">go_direct</span><span class="o">=</span><span class="n">true</span>
+</pre></div>
+
+
+<p>The following example configures Traffic Server to direct all missed requests with URLs beginning
+with <code>http://host1</code> to the parent cache <code>parent1</code>. If <code>parent1</code> cannot serve the requests, then
+requests are forwarded to <code>parent2</code>. Because <code>round-robin=true</code>, Traffic Server goes through the
+parent cache list in a round-robin based on client IP address.</p>
+<div class="codehilite"><pre><span class="n">dest_host</span><span class="o">=</span><span class="n">host1</span> <span class="n">scheme</span><span class="o">=</span><span class="n">http</span> <span class="n">parent</span><span class="o">=</span><span class="err">”</span><span class="n">parent1</span><span class="p">;</span><span class="n">parent2</span><span class="err">”</span> <span class="n">round</span><span class="o">-</span><span class="n">robin</span><span class="o">=</span><span class="n">strict</span>
+</pre></div>
+
+
+<p>Run the command <code>traffic_line -x</code> to apply the configuration changes.</p>
 <h2 id="ICPPeering">ICP Peering</h2>
 <p>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 
@@ -167,63 +161,23 @@ must perform the following tasks: </p>
 <li>Identify the ICP peers (siblings and parents) with which Traffic Server can communicate.</li>
 </ul>
 <h5 id="configureTSuseanICPcachehierarchy">To configure Traffic Server to use an ICP cache hierarchy:</h5>
-<ol>
-<li>In a text editor, open the <code>records.config</code> file located in the Traffic Server <code>config</code> directory. </li>
-<li>Edit the following variables:</li>
-<li />
-<li>
+<p>Edit the following variables in <code>records.config</code> file located in the Traffic Server <code>config</code> directory. </p>
 <dl>
-<dt><strong>Variable</strong> <strong>Description</strong></dt>
 <dt><em><code>proxy.config.icp.enabled</code></em></dt>
-<dd>Set this variable to:<br />
-       0 to disable ICP.<br />
-       1 to allow Traffic Server to receive ICP queries only.<br />
-       2 to allow Traffic Server to send and receive ICP queries.</dd>
+<dd>0 disables ICP.</dd>
+<dd>1 allows Traffic Server to receive ICP queries only</dd>
+<dd>2 allows Traffic Server to send and receive ICP queries.</dd>
 <dt><em><code>proxy.config.icp.icp_port</code></em></dt>
-<dd>Set this variable to specify the UDP port that you want to use for ICP messages. 
-    The default is 3130. </dd>
+<dd>This variable specifes the UDP port that you want to use for ICP messages (default is 3130).</dd>
 <dt><em><code>proxy.config.icp.multicast_enabled</code></em></dt>
-<dd>Set this variable to:<br />
-       0 to disable ICP multicast.<br />
-       1 to enable ICP multicast.</dd>
+<dd>0 disables ICP multicast.</dd>
+<dd>1 enables ICP multicast.</dd>
 <dt><em><code>proxy.config.icp.query_timeout</code></em></dt>
-<dd>Set this variable to specify the timeout used for ICP queries. The default 
-    is 2 seconds.</dd>
+<dd>This variable specifes the timeout used for ICP queries (default is 2 seconds).</dd>
 </dl>
-</li>
-<li />
-<li>Save and close <code>records.config</code></li>
-<li>In a text editor, open the <code>icp.config</code> file located in the Traffic Server <code>config</code> directory. </li>
-<li>For each ICP peer you want to identify, enter a separate rule in the <a href="files.htm#icp.config">icp.config</a> file.</li>
-<li>Save and close <code>icp.config</code></li>
-<li>Navigate to the Traffic Server <code>bin</code> directory. </li>
-<li>
+<p>Edit <code>icp.config</code> file located in the Traffic Server <code>config</code> directory: 
+For each ICP peer you want to identify, enter a separate rule in the <a href="../configuration-files/icp.config">icp.config</a> file.</p>
 <p>Run the command <code>traffic_line -x</code> to apply the configuration changes.</p>
-</li>
-<li>
-<p><a href="intro.htm">Overview</a></p>
-</li>
-<li><a href="getstart.htm">Getting Started</a></li>
-<li><a href="http.htm">HTTP Proxy Caching </a></li>
-<li><a href="explicit.htm">Explicit Proxy Caching</a></li>
-<li><a href="reverse.htm">Reverse Proxy and HTTP Redirects</a></li>
-<li><a href="hier.htm">Hierarchical Caching</a></li>
-<li><a href="cache.htm">Configuring the Cache</a></li>
-<li><a href="monitor.htm">Monitoring Traffic</a></li>
-<li><a href="configure.htm">Configuring Traffic Server</a></li>
-<li><a href="secure.htm">Security Options</a></li>
-<li><a href="log.htm">Working with Log Files</a></li>
-<li><a href="cli.htm">Traffic Line Commands</a></li>
-<li><a href="logfmts.htm">Event Logging Formats</a></li>
-<li><a href="files.htm">Configuration Files</a> </li>
-<li><a href="errors.htm">Traffic Server Error Messages</a></li>
-<li><a href="trouble.htm">FAQ and Troubleshooting Tips</a></li>
-<li><a href="ts_admin_chinese.pdf">Traffic Server 管理员指南</a> (PDF)</li>
-</ol>
-<p>Copyright © 2011 <a href="http://www.apache.org/">The Apache Software Foundation</a>. 
-Licensed under the <a href="http://www.apache.org/licenses/">Apache License</a>, Version 
-2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the 
-Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>
   </div><!-- main -->