trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mlib...@apache.org
Subject svn commit: r917681 [4/8] - /incubator/trafficserver/site/trunk/docs/admin/
Date Mon, 01 Mar 2010 19:53:48 GMT
Modified: incubator/trafficserver/site/trunk/docs/admin/intro.htm
URL: http://svn.apache.org/viewvc/incubator/trafficserver/site/trunk/docs/admin/intro.htm?rev=917681&r1=917680&r2=917681&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/intro.htm (original)
+++ incubator/trafficserver/site/trunk/docs/admin/intro.htm Mon Mar  1 19:53:47 2010
@@ -1,90 +1,92 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<title>Traffic Server Administrator's Guide</title>
-
-<!--#include file="top.html" -->
-
-<h1>Overview</h1>
-<p>Traffic Server speeds Internet access, enhances website performance, and delivers
unprecedented web hosting capabilities.  </p>
-<p>This chapter discusses the following topics: </p>
-<ul>
-<li><a href="#WhatIsTrafficEdge">What Is Traffic Server?</a></li>
-<li><a href="#TrafficEdgeDeploymentOptions">Traffic Server Deployment Options</a></li>
-<li><a href="#TrafficEdgeComponents">Traffic Server Components</a></li>
-<li><a href="#TrafficAnalysisOptions">Traffic Analysis Options</a></li>
-<li><a href="#TrafficEdgeSecurityOptions">Traffic Server Security Options</a></li>
-</ul>
-<h2 id="WhatIsTrafficEdge">What Is Traffic Server?</h2>
-<p>Global data networking has become part of  everyday life: internet users request
billions of documents and terabytes of data, on a daily basis, to and from all parts of the
world. Information is free, abundant, and accessible. Unfortunately, global data networking
can also be a nightmare for IT professionals as they struggle with overloaded servers and
congested networks. It can be challenging to consistently and reliably accommodate society’s
growing data demands. </p>
-<p>Traffic Server is a high-performance web proxy cache that improves network efficiency
and performance by caching frequently-accessed information at the edge of the network. This
brings content physically closer to end users, while enabling faster delivery and  reduced
bandwidth use. Traffic Server is designed to improve content delivery for enterprises, Internet
service providers (ISPs), backbone providers, and large intranets by maximizing existing and
available bandwidth.  </p>
-<h2 id="TrafficEdgeDeploymentOptions">Traffic Server Deployment Options </h2>
-<p>To best suit your needs, Traffic Server can be deployed in several ways:</p>
-<ul>
-  <li>As a web proxy cache</li>
-  <li>As a reverse proxy</li>
-  <li>In a cache hierarchy</li>
-</ul>
-<p>The following sections provide a summary of these Traffic Server deployment options.
</p>
-<h3>Traffic Server as a Web Proxy Cache </h3>
-<p>As a <b>web proxy cache</b>, Traffic Server receives user requests for
web content as those requests travel to the destined web server (origin server). If Traffic
Server contains the requested content, then it serves the content directly. If the requested
content is not available from cache, then Traffic Server acts as a proxy: it obtains the content
from the origin server on the user’s behalf and also keeps a copy to satisfy future requests.
</p>
-<p>Traffic Server provides<b> explicit proxy caching</b>, 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="explicit.htm">Explicit Proxy Caching</a>
section.</p>
-<h3>Traffic Server as a Reverse Proxy </h3>
-<p>As a <b>reverse proxy</b>, 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 <b>server acceleration</b>. Reverse proxy is described
in more detail in <a href="reverse.htm">Reverse Proxy and HTTP Redirects</a>.
</p>
-<h3>Traffic Server in a Cache Hierarchy  </h3>
-<p>Traffic Server can participate in flexible <b>cache hierarchies</b>,
in which Internet requests not fulfilled from one cache are routed to other regional caches,
thereby leveraging the contents and proximity of nearby caches. In a hierarchy of proxy servers,
Traffic Server can act either as a parent or a child cache to other Traffic Server systems
or  to similar caching products. </p>
-<p>Traffic Server supports ICP (Internet Cache Protocol) peering. Hierarchical caching
is described in more detail in <a href="hier.htm">Hierarchical Caching</a>.</p>
-<h2 id="TrafficEdgeComponents">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 components are described below. </p>
-<h3>The Traffic Server Cache</h3>
-<p> The Traffic Server cache consists of a high-speed object database called the <b>object
store</b>. The object store indexes objects according to URLs and associated headers.
Using sophisticated object management, the object store can cache alternate versions of the
same object (perhaps in a different language or encoding type). It can also efficiently store
very small and very large objects, thereby minimizing wasted space. When the cache is full,
Traffic Server removes stale data to ensure that the most requested objects are  readily available
and fresh.  </p>
-<p>Traffic Server is designed to tolerate total disk failures on any of the cache disks.
If the disk fails completely, then Traffic Server marks the entire disk as corrupt and continues
to use remaining disks. If all of the cache disks fail, then Traffic Server switches to 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="cache.htm">Configuring the Cache</a>. </p>
-<h3>The RAM Cache </h3>
-<p>Traffic Server maintains a small RAM cache that contains extremely popular objects.
This <b>RAM cache </b>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="cache.htm#ChangingSizeRAMCache">Changing
the Size of the RAM Cache</a>.</p>
-<h3>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 user requests. This information
is used to adapt future protocol interactions and optimize performance.  Along with other
information, the host database tracks: </p>
-<ul>
-  <li>DNS information (for fast conversion of hostnames to IP addresses) </li>
-  <li>The HTTP version of each host (so advanced protocol features can be used with
hosts running modern servers) </li>
-  <li>Host reliability and availability information (so users will not wait for servers
that are not running) </li>
-</ul>
-<h3>The DNS Resolver </h3>
-<p>Traffic Server includes a fast, asynchronous DNS resolver to streamline conversion
of hostnames to IP addresses. Traffic Server implements the DNS resolver natively by directly
issuing DNS command packets rather than relying on slower, conventional resolver libraries.
Since many DNS queries can be issued in parallel and a fast DNS cache maintains popular bindings
in memory, DNS traffic is reduced. </p>
-<h3>Traffic Server Processes </h3>
-<p>Traffic Server contains three processes that work together to serve Traffic Server
requests and manage/control/monitor the health of the Traffic Server system. The three processes
are described below: </p>
-<ul>
-  <li>The <code>traffic_server</code> process is the transaction processing
engine of Traffic Server. It is responsible for accepting connections, processing protocol
requests, and serving documents from the cache or origin server. </li>
-  <li>The <code>traffic_manager</code> process is the command and control
facility of the Traffic Server, responsible for launching, monitoring, and reconfiguring the
<code>traffic_server</code> process. The <code>traffic_manager</code>
process is also responsible for the proxy autoconfiguration port, the statistics interface,
cluster administration, and virtual IP failover. <br />
-    If the <code>traffic_manager</code> process detects a <code>traffic_server</code>
process failure, it instantly restarts the process but also maintains a connection queue of
all incoming requests. All incoming connections that arrive in the several seconds before
full server restart are saved in the connection queue and processed in first-come, first-served
order. This connection queueing shields users from any server restart downtime. </li>
-  <li>The <code>traffic_cop</code> process monitors the health of both
the <code>traffic_server</code> and <code>traffic_manager</code> processes.
The <code>traffic_cop</code> process periodically (several times each minute)
queries the <code>traffic_server</code> and <code>traffic_manager</code>
process by issuing heartbeat requests to fetch synthetic web pages. In the event of failure
(if no response is received within a timeout interval or if an incorrect response is received),
<code>traffic_cop</code> restarts the <code>traffic_manager</code>
and <code>traffic_server</code> processes. </li>
-</ul>
-<p>The figure below illustrates the three Traffic Server processes.</p>
-<p><img src="images/process.jpg" width="848" height="578" /></p>
-<p>&nbsp;</p>
-<h3>Administration Tools</h3>
-<p>Traffic Server offers the following administration options: </p>
-<ul>
-  <li>The  <b>Traffic Line</b> command-line interface is a text-based interface
from which you can monitor Traffic Server performance and network traffic, as well as configure
the Traffic Server system. From Traffic Line, you can execute individual commands or script
a series of commands in a shell. </li>
-  <li>The <b>Traffic Shell </b>command-line interface is an additional
command-line tool that enables you to execute individual commands that monitor and configure
the Traffic Server system. </li>
-  <li>Various <b>configuration</b> <b>files</b> enable you
to configure Traffic Server through a simple file-editing and signal-handling interface. Any
changes you make through Traffic Line or Traffic Shell are automatically made to the configuration
files as well. </li>
-</ul>
-<h2 id="TrafficAnalysisOptions">Traffic Analysis Options </h2>
-<p>Traffic Server provides several options for network traffic analysis and monitoring:
</p>
-<ul>
-  <li><b>Traffic Line</b> and <b>Traffic Shell</b> enable you
to collect and process statistics obtained from network traffic information. </li>
-  <li><b>Transaction logging</b> enables you to record information (in
a log file) about every request  Traffic Server receives and every error it detects. By analyzing
the log files, you can determine how many people used the Traffic Server cache, how much information
each person requested, and what pages were most popular. You can also see why a particular
transaction was in error and what state the Traffic Server was in at a particular time; for
example, you can see that Traffic Server was restarted or that cluster communication timed
out. <br />
-    Traffic Server supports several standard log file formats, such as Squid and Netscape,
and its own custom format. You can analyze the standard format log files with off-the-shelf
analysis packages. To help with log file analysis, you can separate log files so that they
contain information specific to protocol or hosts. </li>
-</ul>
-<p>Traffic analysis options are described in more detail in <a href="monitor.htm">Monitoring
Traffic</a>; Traffic Server logging options are described in <a href="log.htm">Working
with Log Files</a>. </p>
-<h2 id="TrafficEdgeSecurityOptions">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 computers on the network. Using the security options,
you can do the following: </p>
-<ul>
-  <li>Control client access to the Traffic Server proxy cache. </li>
-  <li>Configure Traffic Server to use multiple DNS servers to match your site’s
security configuration. For example, Traffic Server can use different DNS servers, depending
on whether it needs to resolve hostnames located inside or outside a firewall. This enables
you to keep your internal network configuration secure while continuing to provide transparent
access to external sites on the Internet. </li>
-  <li>Configure Traffic Server to verify that clients are authenticated before they
can access content from the Traffic Server cache. </li>
-  <li>Secure connections in reverse proxy mode between a client and Traffic Server,
and Traffic Server and the origin server, using the SSL termination option. </li>
-  <li>Control access via SSL (Secure Sockets Layer). </li>
-</ul>
-<p>Traffic Server security options are described in more detail in <a href="secure.htm">Security
Options</a>.</p>
-
-<!--#include file="bottom.html" -->
\ No newline at end of file
+<html>
+<head>
+<title>Traffic Edge Administrator’s Guide</title>
+<meta content="text/html; charset=UTF-8" http-equiv="content-type"/>
+
+<link rel="stylesheet" href="doc.css" type="text/css" media="all" /></head>
+
+<body>
+<h1>Overview</h1>
+<p>Traffic Server speeds Internet access, enhances website performance, and delivers
unprecedented web hosting capabilities.  </p>
+<p>This chapter discusses the following topics: </p>
+<ul>
+<li><a href="#WhatIsTrafficEdge"><em>What Is Traffic Server?</em></a></li>
+<li><a href="#TrafficEdgeDeploymentOptions"><em>Traffic Server Deployment
Options</em></a></li>
+<li><a href="#TrafficEdgeComponents"><em>Traffic Server Components</em></a></li>
+<li><a href="#TrafficAnalysisOptions"><em>Traffic Analysis Options</em></a></li>
+<li><a href="#TrafficEdgeSecurityOptions"><em>Traffic Server Security Options</em></a></li>
+</ul>
+<h2 id="WhatIsTrafficEdge">What Is Traffic Server?</h2>
+<p>Global data networking has become part of  everyday life: internet users request
billions of documents and terabytes of data, on a daily basis, to and from all parts of the
world. Information is free, abundant, and accessible. Unfortunately, global data networking
can also be a nightmare for IT professionals as they struggle with overloaded servers and
congested networks. It can be challenging to consistently and reliably accommodate society’s
growing data demands. </p>
+<p>Traffic Server is a high-performance web proxy cache that improves network efficiency
and performance by caching frequently-accessed information at the edge of the network. This
brings content physically closer to end users, while enabling faster delivery and  reduced
bandwidth use. Traffic Server is designed to improve content delivery for enterprises, Internet
service providers (ISPs), backbone providers, and large intranets by maximizing existing and
available bandwidth.  </p>
+<h2 id="TrafficEdgeDeploymentOptions">Traffic Server Deployment Options </h2>
+<p>To best suit your needs, Traffic Server can be deployed in several ways:</p>
+<ul>
+  <li>As a web proxy cache</li>
+  <li>As a reverse proxy</li>
+  <li>In a cache hierarchy</li>
+</ul>
+<p>The following sections provide a summary of these Traffic Server deployment options.
</p>
+<h3>Traffic Server as a Web Proxy Cache </h3>
+<p>As a <em>web proxy cache</em>, Traffic Server receives user requests
for web content as those requests travel to the destined web server (origin server). If Traffic
Server contains the requested content, then it serves the content directly. If the requested
content is not available from cache, then Traffic Server acts as a proxy: it obtains the content
from the origin server on the user’s behalf and also keeps a copy to satisfy future requests.
</p>
+<p>Traffic Server provides<em> explicit proxy caching</em>, in which the
user’s client software must be configured to send requests directly to Traffic Server.
Explicit proxy caching is described in more detail in <a href="explicit.htm"><em>Explicit
Proxy Caching</em></a>. </p>
+<h3>Traffic Server as a Reverse Proxy </h3>
+<p>As a <em>reverse proxy</em>, 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 <i>server acceleration</i>. Reverse proxy
is described in more detail in <a href="reverse.htm"><em>Reverse Proxy and HTTP
Redirects</em></a>. </p>
+<h3>Traffic Server in a Cache Hierarchy  </h3>
+<p>Traffic Server can participate in flexible <em>cache hierarchies</em>,
in which Internet requests not fulfilled from one cache are routed to other regional caches,
while taking advantage of the contents and proximity of nearby caches. In a hierarchy of proxy
servers, Traffic Server can act either as a parent or a child cache, to other Traffic Server
systems or  similar caching products. </p>
+<p>Traffic Server supports ICP (Internet Cache Protocol) peering. Hierarchical caching
is described in more detail in <a href="hier.htm"><em>Hierarchical Caching</em></a>.</p>
+<h2 id="TrafficEdgeComponents">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. The main components are described below. </p>
+<h3>The Traffic Server Cache</h3>
+<p> The <em>Traffic Server cache</em> consists of a high-speed object database
called the <em>object store</em>. The object store indexes objects according to
URLs and associated headers. Using sophisticated object management, the object store can cache
alternate versions of the same object (perhaps in a different language or encoding type).
It can also efficiently store very small and very large objects, thereby minimizing wasted
space. When the cache is full, Traffic Server removes stale data to ensure that the most requested
objects are  readily available and fresh.  </p>
+<p>Traffic Server is designed to tolerate total disk failures on any of the cache disks.
If the disk fails completely, then Traffic Server marks the entire disk as corrupt and continues
to use remaining disks. If all of the cache disks fail, then Traffic Server switches to 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="cache.htm"><em>Configuring the Cache</em></a>. </p>
+<h3>The RAM Cache </h3>
+<p>Traffic Server maintains a small RAM cache that contains extremely popular objects.
This <em>RAM cache</em> 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="cache.htm#ChangingSizeRAMCache"><em>Changing
the Size of the RAM Cache</em></a>. </p>
+<h3>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 user requests. This information
is used to adapt future protocol interactions and optimize performance.  Along with other
information, the host database tracks: </p>
+<ul>
+  <li>DNS information (for fast conversion of hostnames to IP addresses) </li>
+  <li>The HTTP version of each host (so advanced protocol features can be used with
hosts running modern servers) </li>
+  <li>Host reliability and availability information (so users will not wait for servers
that are not running) </li>
+</ul>
+<h3>The DNS Resolver </h3>
+<p>Traffic Server includes a fast, asynchronous DNS resolver to streamline conversion
of hostnames to IP addresses. Traffic Server implements the DNS resolver natively bydirectly
issuing DNS command packets, rather than relying on slower, conventional resolver libraries.
Many DNS queries can be issued in parallel and a fast DNS cache maintains popular bindings
in memory, thereby reducing DNS traffic. </p>
+<h3>Traffic Server Processes </h3>
+<p>Traffic Server contains three processes that work together to serve Traffic Server
requests and manage/control/monitor the health of the Traffic Server system. The three processes
are described below: </p>
+<ul>
+  <li>The <code>traffic_server</code> process is the transaction processing
engine of Traffic Server. It is responsible for accepting connections, processing protocol
requests, and serving documents from the cache or origin server. </li>
+  <li>The <code>traffic_manager</code> process is the command and control
facility of the Traffic Server, responsible for launching, monitoring, and reconfiguring the
<code>traffic_server</code> process. The <code>traffic_manager</code>
process is also responsible for the proxy autoconfiguration port, the statistics interface,
cluster administration, and virtual IP failover. <br />
+    If the <code>traffic_manager</code> process detects a <code>traffic_server</code>
process failure, it instantly restarts the process but also maintains a connection queue of
all incoming requests. All incoming connections that arrive in the several seconds before
full server restart are saved in the connection queue and processed in first-come, first-served
order. This connection queueing shields users from any server restart downtime. </li>
+  <li>The <code>traffic_cop</code> process monitors the health of both
the <code>traffic_server</code> and <code>traffic_manager</code> processes.
The <code>traffic_cop</code> process periodically (several times each minute)
queries the <code>traffic_server</code> and <code>traffic_manager</code>
process by issuing heartbeat requests to fetch synthetic web pages. In the event of failure
(if no response is received within a timeout interval or if an incorrect response is received),
<code>traffic_cop</code> restarts the <code>traffic_manager</code>
and <code>traffic_server</code> processes. </li>
+</ul>
+<p>The figure below illustrates the three Traffic Server processes.</p>
+<p><img src="images/process.jpg" width="848" height="578" /></p>
+<p>&nbsp;</p>
+<h3>Administration Tools</h3>
+<p>Traffic Server offers the following administration options: </p>
+<ul>
+  <li>The <em>Traffic Line</em> command-line interface is a text-based
interface from which you can monitor Traffic Server performance and network traffic, as well
as configure the Traffic Server system. From Traffic Line, you can execute individual commands
or script a series of commands in a shell. </li>
+  <li>The <em>Traffic Shell</em> command-line interface is an additional
command-line tool that enables you to execute individual commands that monitor and configure
the Traffic Server system. </li>
+  <li>Various <em>configuration files</em> enable you to configure Traffic
Server through a simple file-editing and signal-handling interface. Any changes you make through
Traffic Line or Traffic Shell are automatically made to the configuration files as well. </li>
+</ul>
+<h2 id="TrafficAnalysisOptions">Traffic Analysis Options </h2>
+<p>Traffic Server provides several options for network traffic analysis and monitoring:
</p>
+<ul>
+  <li><em>Traffic Line </em>and<em> Traffic Shell</em>   enable
you to collect and process statistics obtained from network traffic information. </li>
+  <li><em>Transaction logging</em> enables you to record information (in
a log file) about every request  Traffic Server receives and every error it detects. By analyzing
the log files, you can determine how many people used the Traffic Server cache, how much information
each person requested, and what pages were most popular. You can also see why a particular
transaction was in error and what state the Traffic Server was in at a particular time; for
example, you can see that Traffic Server was restarted or that cluster communication timed
out. <br />
+    Traffic Server supports several standard log file formats, such as Squid and Netscape,
and its own custom format. You can analyze the standard format log files with off-the-shelf
analysis packages. To help with log file analysis, you can separate log files so that they
contain information specific to protocol or hosts. </li>
+</ul>
+<p>Traffic analysis options are described in more detail in <a href="monitor.htm"><em>Monitoring
Traffic</em></a>; Traffic Server logging options are described in <a href="log.htm"><em>Working
with Log Files</em></a>. </p>
+<h2 id="TrafficEdgeSecurityOptions">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 computers on the network. Using the security options,
you can do the following: </p>
+<ul>
+  <li>Control client access to the Traffic Server proxy cache. </li>
+  <li>Configure Traffic Server to use multiple DNS servers to match your site’s
security configuration; for example, Traffic Server can use different DNS servers, depending
on whether it needs to resolve hostnames located inside or outside a firewall. This enables
you to keep your internal network configuration secure while continuing to provide transparent
access to external sites on the Internet. </li>
+  <li>Configure Traffic Server to make sure that clients are authenticated before they
can access content from the Traffic Server cache. </li>
+  <li>Secure connections in reverse proxy mode between a client and Traffic Server,
and Traffic Server and the origin server, using the SSL termination option. </li>
+  <li>Control access via SSL (Secure Sockets Layer) </li>
+</ul>
+<p>Traffic Server security options are described in more detail in <a href="secure.htm"><em>Security
Options</em></a>.</p>
+
+</body>
+</html>
\ No newline at end of file

Modified: incubator/trafficserver/site/trunk/docs/admin/leftnav.html
URL: http://svn.apache.org/viewvc/incubator/trafficserver/site/trunk/docs/admin/leftnav.html?rev=917681&r1=917680&r2=917681&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/leftnav.html (original)
+++ incubator/trafficserver/site/trunk/docs/admin/leftnav.html Mon Mar  1 19:53:47 2010
@@ -1,19 +1,37 @@
-<ul class="leftnav">
-<li><a href="index.htm">Preface</a></li>
-<li><a href="intro.htm">Overview</a></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>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<link rel="stylesheet" href="doc.css" type="text/css" media="all" />
+<title>Traffic Server Administrator’s Guide</title>
+<style type="text/css">
+ul{
+	margin-left:0px;
+	padding-left:15px;
+	font-family: Tahoma, Geneva, sans-serif;
+	width:170px;
+}
+</style>
+</head>
+
+<body><ul>
+<li><a href="preface.htm" target="mainFrame">Preface</a></li>
+<li><a href="intro.htm" target="mainFrame">Overview</a></li>
+<li><a href="getstart.htm" target="mainFrame">Getting Started</a></li>
+<li><a href="http.htm" target="mainFrame">HTTP Proxy Caching </a></li>
+<li><a href="explicit.htm" target="mainFrame">Explicit Proxy Caching</a></li>
+<li><a href="reverse.htm" target="mainFrame">Reverse Proxy and HTTP Redirects</a></li>
+<li><a href="hier.htm" target="mainFrame">Hierarchical Caching</a></li>
+<li><a href="cache.htm" target="mainFrame">Configuring the Cache</a></li>
+<li><a href="monitor.htm" target="mainFrame">Monitoring Traffic</a></li>
+<li><a href="configure.htm" target="mainFrame">Configuring Traffic Server</a></li>
+<li><a href="secure.htm" target="mainFrame">Security Options</a></li>
+<li><a href="log.htm" target="mainFrame">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>
-</ul>
\ No newline at end of file
+<li><a href="logfmts.htm" target="mainFrame">Event Logging Formats</a></li>
+<li><a href="files.htm" target="mainFrame">Configuration Files</a> </li>
+<li><a href="errors.htm" target="mainFrame">Traffic Server Error Messages</a></li>
+<li><a href="trouble.htm" target="mainFrame">FAQ and Troubleshooting Tips</a></li>
+</ul>
+</body>
+</html>

Propchange: incubator/trafficserver/site/trunk/docs/admin/leftnav.html
            ('svn:executable' removed)



Mime
View raw message