trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r786762 - /websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html
Date Wed, 09 Mar 2011 21:22:16 GMT
Author: buildbot
Date: Wed Mar  9 21:22:16 2011
New Revision: 786762

Log:
Staging update by buildbot

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

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html Wed Mar  9
21:22:16 2011
@@ -83,14 +83,14 @@ satisfy future requests.</p>
 <p>Traffic Server provides explicit proxy caching, in which the user’s
 client software must be configured to send requests directly to Traffic
 Server. Explicit proxy caching is described in the
-<a href="/docs/admin/explicit">Explicit Proxy Caching</a> section.</p>
+<a href="explicit-proxy-caching">Explicit Proxy Caching</a> section.</p>
 <h3 id="reverse-proxy">Traffic Server as a Reverse Proxy</h3>
 <p>As a reverse proxy, Traffic Server is configured to be the origin
 server to which the user is trying to connect (typically, the origin
 server’s advertised hostname resolves to Traffic Server, which acts as
 the real origin server). The reverse proxy feature is also called
 server acceleration. Reverse proxy is described in more detail in
-<a href="/docs/admin/reverse">Reverse Proxy and HTTP Redirects</a>.</p>
+<a href="reverse-proxy-http-redirects">Reverse Proxy and HTTP Redirects</a>.</p>
 <h3 id="cache-hierachy">Traffic Server in a Cache Hierarchy</h3>
 <p>Traffic Server can participate in flexible cache hierarchies, in which
 Internet requests not fulfilled from one cache are routed to other
@@ -100,7 +100,7 @@ either as a parent or a child cache to o
 to similar caching products.</p>
 <p>Traffic Server supports ICP (Internet Cache Protocol) peering.
 Hierarchical caching is described in more detail in
-<a href="/docs/admin/hier">Hierarchical Caching</a>.</p>
+<a href="hierachical-caching">Hierarchical Caching</a>.</p>
 <h2 id="ats-components">Traffic Server Components</h2>
 <p>Traffic Server consists of several components that work together to
 form a web proxy cache you can easily monitor and configure. These main
@@ -121,14 +121,14 @@ If all of the cache disks fail, then Tra
 proxy-only mode. You can partition the cache to reserve a certain
 amount of disk space for storing data for specific protocols and origin
 servers. For more information about the cache, see
-<a href="/docs/admin/cache">Configuring the Cache</a>.</p>
+<a href="configuring-cache">Configuring the Cache</a>.</p>
 <h3 id="ram-cache">The RAM Cache</h3>
 <p>Traffic Server maintains a small RAM cache that contains extremely
 popular objects. This RAM cache serves the most popular objects as fast
 as possible and reduces load on disks, especially during temporary
 traffic peaks. You can configure the RAM cache size to suit your needs;
 for detailed information, refer to
-<a href="/docs/admin/cache#ChangingSizeRAMCache">Changing the Size of the RAM Cache</a>.</p>
+<a href="configuring-cache#ChangingSizeRAMCache">Changing the Size of the RAM Cache</a>.</p>
 <h3 id="host-db">The Host Database</h3>
 <p>The Traffic Server host database stores the domain name server (DNS)
 entries of origin servers to which Traffic Server connects to fulfill
@@ -220,9 +220,9 @@ and monitoring:</p>
   they contain information specific to protocol or hosts.</li>
 </ul>
 <p>Traffic analysis options are described in more detail in
-<a href="/docs/admin/monitor">Monitoring Traffic</a>;
+<a href="monitoring-traffic">Monitoring Traffic</a>;
 Traffic Server logging options are described in
-<a href="/docs/admin/log">Working with Log Files</a>.</p>
+<a href="working-log-files">Working with Log Files</a>.</p>
 <h2 id="security">Traffic Server Security Options</h2>
 <p>Traffic Server provides numerous options that enable you to establish
 secure communication between the Traffic Server system and other
@@ -244,7 +244,7 @@ following:</p>
 <li>Control access via SSL (Secure Sockets Layer).</li>
 </ul>
 <p>Traffic Server security options are described in more detail in
-<a href="/docs/admin/secure">Security Options</a>.</p>
+<a href="security-options">Security Options</a>.</p>
     </div>
   </div><!-- main -->
 



Mime
View raw message