trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dia...@apache.org
Subject svn commit: r897032 - in /incubator/trafficserver/site/trunk/docs/admin: cli.htm configure.htm explicit.htm getstart.htm intro.htm
Date Thu, 07 Jan 2010 22:15:10 GMT
Author: dianes
Date: Thu Jan  7 22:15:07 2010
New Revision: 897032

URL: http://svn.apache.org/viewvc?rev=897032&view=rev
Log: (empty)

Modified:
    incubator/trafficserver/site/trunk/docs/admin/cli.htm
    incubator/trafficserver/site/trunk/docs/admin/configure.htm
    incubator/trafficserver/site/trunk/docs/admin/explicit.htm
    incubator/trafficserver/site/trunk/docs/admin/getstart.htm
    incubator/trafficserver/site/trunk/docs/admin/intro.htm

Modified: incubator/trafficserver/site/trunk/docs/admin/cli.htm
URL: http://svn.apache.org/viewvc/incubator/trafficserver/site/trunk/docs/admin/cli.htm?rev=897032&r1=897031&r2=897032&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/cli.htm (original)
+++ incubator/trafficserver/site/trunk/docs/admin/cli.htm Thu Jan  7 22:15:07 2010
@@ -12,12 +12,12 @@
   <p>    This appendix contains the following sections:  </p>
 
 <ul>
-<li><a href="#1053987"><em>Traffic Line Commands</em></a></li>
-<li><a href="#1025718"><em>Traffic Line Variables</em></a></li>
+<li><a href="#1053987">Traffic Line Commands</a></li>
+<li><a href="#1025718">Traffic Line Variables</a></li>
 </ul>
 <h2>
         <a name="1053987">Traffic Line Commands</a>     </h2>
-     <p>       Use Traffic Line to execute individual Traffic Server commands and to script multiple commands in a shell.   You execute Traffic Line commands from the Traffic Server <code>bin</code> directory. If the Traffic Server <code>bin</code> directory is not in your path, then prepend the Traffic Line command with <code>./</code> (for example: <code>./traffic_line -p</code>).  </p>
+     <p>       Use Traffic Line to execute individual Traffic Server commands and to script multiple commands in a shell.   Execute Traffic Line commands from the Traffic Server <code>bin</code> directory. If the Traffic Server <code>bin</code> directory is not in your path, then prepend the Traffic Line command with <code>./</code> (for example: <code>./traffic_line -p</code>).  </p>
   <p>       The following table describes all the commands available in Traffic Line.  </p>
       <table border="1">
         <tr>
@@ -26,34 +26,33 @@
         </tr>
         <tr>
           <td><p> <code> traffic_line -b</code> </p></td>
-          <td><p> Bounces the Traffic Server on the local node. Bouncing the Traffic Server shuts down and immediately restarts the Traffic Server node.</p></td>
+          <td><p> Bounces  Traffic Server on the local node. Bouncing  Traffic Server shuts down and immediately restarts the Traffic Server node.</p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -c</code> </p></td>
-          <td><p> Clears the accumulated statistics on the local node.</p></td>
+          <td><p> Clears  accumulated statistics on the local node.</p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -h</code> </p></td>
-          <td><p> Displays the list of Traffic Line commands.</p></td>
+          <td><p> Displays a list of Traffic Line commands.</p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -p <em>socket_path</em></code> </p></td>
-          <td><p> Specifies the location (directory and path) of the socket used for Traffic Line  communication.<br /> 
-          The default path is: <br />
-          <code><em>install_dir</em> /config/cli</code> </p></td>
+          <td><p> Specifies  location (directory and path) of the socket used for Traffic Line  communication.<br /> 
+          The default path is:          <code><em>install_dir</em> /config/cli</code> </p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -q</code> </p></td>
           <td><p> Displays a list of the origin servers that are currently congested. </p>
-              <p> <b>Note:</b> To use this command, you must set the variable <code> <i>proxy.config.raf.enabled</i></code> to 1 and then set the variable <code> <i>proxy.config.raf.port</i></code> to a different port <em CLASS="Emphasis"> only</em> if there is a conflict with the default port 9000.</p></td>
+              <p> <b>Note:</b> To use this command, you must set the variable <code> <i>proxy.config.raf.enabled</i></code> to 1 and  set the variable <code> <i>proxy.config.raf.port</i></code> to a different port <em CLASS="Emphasis"> only</em> if there is a conflict with the default port 9000.</p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -r  <em>variable</em></code> </p></td>
-          <td><p> Displays specific performance statistics or a current configuration setting. For a list of the variables you can specify, refer to <a href="cli.htm#1025718"><em>Traffic Line Variables</em></a>.</p></td>
+          <td><p> Displays specific performance statistics or a current configuration setting. For a list of the variables you can specify, see <a href="cli.htm#1025718">Traffic Line Variables</a>.</p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -s  <em>variable</em> -v  <em>value</em></code> </p></td>
-          <td><p> Sets configuration variables, where <code><i>variable</i></code> is the configuration variable you want to change and <code> <i>value</i></code> is the value you want to set. Refer to <a href="files.htm#115367"><em> records.config</em></a> for a list of the configuration variables you can specify.</p></td>
+          <td><p> Sets configuration variables, where <code><i>variable</i></code> is the configuration variable you want to change and <code> <i>value</i></code> is the value you want to set. Refer to <a href="files.htm#115367"> records.config</a> for a list of the configuration variables you can specify.</p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -x</code> </p></td>
@@ -61,15 +60,15 @@
         </tr>
         <tr>
           <td><p> <code> traffic_line -B</code> </p></td>
-          <td><p> Bounces all the Traffic Server nodes in the cluster. Bouncing the Traffic Server shuts down and immediately restarts Traffic Server node by node.</p></td>
+          <td><p> Bounces all  Traffic Server nodes in the cluster. Bouncing  Traffic Server shuts down and immediately restarts Traffic Server, node-by-node.</p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -C</code> </p></td>
-          <td><p> Clears the accumulated statistics on all the nodes in the cluster.</p></td>
+          <td><p> Clears  accumulated statistics on all  nodes in the cluster.</p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -L</code> </p></td>
-          <td><p> Restarts the <code> traffic_manager</code> process and the <code> traffic_server</code> process on the local node.</p></td>
+          <td><p> Restarts the <code> traffic_manager</code>  and  <code> traffic_server</code> processes on the local node.</p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -M</code> </p></td>
@@ -77,18 +76,18 @@
         </tr>
         <tr>
           <td><p> <code> traffic_line -S</code> </p></td>
-          <td><p> Shuts down the Traffic Server on the local node.</p></td>
+          <td><p> Shuts down  Traffic Server on the local node.</p></td>
         </tr>
         <tr>
           <td><p> <code> traffic_line -U</code> </p></td>
-          <td><p> Starts the Traffic Server on the local node.</p></td>
+          <td><p> Starts  Traffic Server on the local node.</p></td>
         </tr>
       </table>
 <p>
         <strong><a name="1025718">Traffic Line Variables</a></strong>
   </p>
-  <p>       You can view statistics and change configuration options in Traffic Line by using specific variables. The variables used for gathering statistics are described below. The variables used for viewing and changing configuration options are described in <a href="files.htm#115367"><em>records.config</em></a>. For procedures on how to specify the variables, refer to <a href="monitor.htm"><em>Viewing Statistics from Traffic Line</em></a>, and <a href="configure.htm"><em>Configuring Traffic Server Using Traffic Line</em></a>.  </p>
-  <p>       The variables used for viewing individual statistics are described in the following table.  To view a statistic in Traffic Line, enter the command <code>traffic_line -r <em>variable</em> </code>at the prompt.  </p>
+  <p>       You can view statistics and change configuration options in Traffic Line by using specific variables. The variables used for gathering statistics are described below. The variables used for viewing and changing configuration options are described in <a href="files.htm#115367">records.config</a>. For procedures about specifying the variables, refer to <a href="monitor.htm">Viewing Statistics from Traffic Line</a> and <a href="configure.htm">Configuring Traffic Server Using Traffic Line</a>.  </p>
+<p>       The variables used for viewing individual statistics are described in the following table.  To view a statistic in Traffic Line, enter the command <code>traffic_line -r <em>variable</em> </code>at the prompt.  </p>
      <table border="1">
        <tr>
          <td><p><strong> Statistic</strong></p></td>
@@ -338,7 +337,7 @@
          <td><p> <i><code> proxy.process.dns.total_dns_lookups</code> </i></p></td>
        </tr>
        <tr>
-         <td><p> Average lookup time (ms)</p></td>
+         <td><p> Average lookup time (msec)</p></td>
          <td><p> <i><code> proxy.process.dns.lookup_avg_time</code> </i></p></td>
        </tr>
        <tr>
@@ -376,7 +375,7 @@
          <td rowspan="1" colspan="2"><p><strong> Logging </strong></p></td>
        </tr>
        <tr>
-         <td><p> Currently open log files</p></td>
+         <td><p> Log files currently open</p></td>
          <td><p> <i><code> proxy.process.log2.log_files_open</code> </i></p></td>
        </tr>
        <tr>
@@ -399,11 +398,11 @@
          <td rowspan="1" colspan="2"><p><strong> Congestion Control</strong></p></td>
        </tr>
        <tr>
-         <td><p> Number of congestions Traffic Server has observed because the maximum number of connections were exceeded.</p></td>
+         <td><p> Number of congestions Traffic Server has observed because the maximum number of connections was exceeded.</p></td>
          <td><p> <i><code>proxy.process.congestion.congested_on_max_connection</code></i></p></td>
        </tr>
        <tr>
-         <td><p> Number of congestions Traffic Server has observed because of an operating system response or timeout failure.</p></td>
+         <td><p> Number of congestions Traffic Server has observed because of an OS response or timeout failure.</p></td>
          <td><p><i><code>proxy.process.congestion.congested_on_conn_failures</code></i></p></td>
        </tr>
      </table>

Modified: incubator/trafficserver/site/trunk/docs/admin/configure.htm
URL: http://svn.apache.org/viewvc/incubator/trafficserver/site/trunk/docs/admin/configure.htm?rev=897032&r1=897031&r2=897032&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/configure.htm (original)
+++ incubator/trafficserver/site/trunk/docs/admin/configure.htm Thu Jan  7 22:15:07 2010
@@ -1,38 +1,38 @@
-<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>Configuring Traffic Server</h1>
-<p>Traffic Server provides several options for configuring the system.</p>
-<p>This chapter discusses the following topics: </p>
-<ul> 
-<li><a href="#ConfiguringTrafficEdgeUsingTrafficLine"><em>Configure Traffic Server Using Traffic Line</em></a></li> 
-<li><a href="#ConfiguringTrafficEdgeUsingConfigFiles"><em>Configure Traffic Server Using Configuration Files</em></a></li>
-</ul>
-<h2 id="ConfiguringTrafficEdgeUsingTrafficLine">Configure Traffic Server Using Traffic Line</h2>
-<p>Traffic Line enables you to quickly and easily change your Traffic Server configuration via command-line interface. Alternatively, you can also use <a href="getstart.htm#StartingTrafficShell"><em>Traffic Shell</em></a> to configure Traffic Server.</p>
-<h5>To view or change configuration options in Traffic Line: </h5>
-<ol>
-  <li>Log on to a Traffic Server node as the Traffic Server administrator and  navigate to the Traffic Server <code>bin</code> directory. </li>
-  <li>To view a configuration setting, enter the following command: <br /><code>traffic_line -r <em>var</em></code><br /> 
-  where <em><code>var</code></em> is the variable associated with the configuration option (for a list of the variables, refer to <a href="files.htm#49000"><em>Configuration Variables</em></a>). </li>
-  <li>To change the value of a configuration setting, enter the following command:
-    <br /><code>traffic_line -s <em>var</em> -v <em>value</em></code> <br />
-    where <em><code>var</code></em> is the variable associated with the configuration option (for a list of the variables, refer to <a href="files.htm#49000"><em>Configuration Variables</em></a>) and <em><code>value</code></em> is the value you want to use.  <br /> <br /> If the Traffic Server <code>bin</code> directory is not in your path, then prepend the Traffic Line command with <code>./</code> (for example, <code>./traffic_line -r variable</code>).</li>
-</ol>
-<h2 id="ConfiguringTrafficEdgeUsingConfigFiles">Configure Traffic Server Using Configuration Files</h2>
-<p>As an alternative to using  Traffic Line or Traffic Shell, you can change Traffic Server configuration options by manually editing specific variables in the <code>records.config</code> file located in the Traffic Server <code>config</code> directory. To edit the variables, open the file in a text editor (such as <code>vi</code> or <code>emacs</code>) and change  variable values. After you modify the <code>records.config</code> file, Traffic Server must reread the configuration files. From the Traffic Server <code>bin</code> directory, enter the Traffic Line command  <code>traffic_line -x</code>. You may need to restart Traffic Server to apply the configuration changes. </p>
-<p>The following is a sample portion of the <code>records.config</code> file: </p>
-<p><img src="images/records.jpg" width="812" height="609" /></p>
-<blockquote>
-  <p><em><b>Sample records.config file </b></em></p>
-</blockquote>
-<p>In addition to the <code>records.config</code> file, Traffic Server provides other configuration files that are used to configure specific features. All  configuration files  that you can  manually edit are described in <em><a href="files.htm">Configuration Files</a></em>. </p>
-<h2 id="SavingRestoringTrafficEdgeConfigs">&nbsp;</h2>
-<p>&nbsp;</p>
-</body>
+<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>Configuring Traffic Server</h1>
+<p>Traffic Server provides several options for configuring the system.</p>
+<p>This chapter discusses the following topics: </p>
+<ul> 
+<li><a href="#ConfiguringTrafficEdgeUsingTrafficLine">Configure Traffic Server Using Traffic Line</a></li> 
+<li><a href="#ConfiguringTrafficEdgeUsingConfigFiles">Configure Traffic Server Using Configuration Files</a></li>
+</ul>
+<h2 id="ConfiguringTrafficEdgeUsingTrafficLine">Configure Traffic Server Using Traffic Line</h2>
+<p>Traffic Line enables you to quickly and easily change your Traffic Server configuration via command-line interface. Alternatively, you can also use <a href="getstart.htm#StartingTrafficShell">Traffic Shell</a> to configure Traffic Server.</p>
+<h5>To view or change configuration options in Traffic Line: </h5>
+<ol>
+  <li>Log on to a Traffic Server node as the Traffic Server administrator and  navigate to the Traffic Server <code>bin</code> directory. </li>
+  <li>To view a configuration setting, enter the following command: <br /><code>traffic_line -r <em>var</em></code><br /> 
+  where <em><code>var</code></em> is the variable associated with the configuration option. For a list of  variables, refer to <a href="files.htm#49000">Configuration Variables</a>.</li>
+  <li>To change the value of a configuration setting, enter the following command:
+    <br /><code>traffic_line -s <em>var</em> -v <em>value</em></code> <br />
+  where <em><code>var</code></em> is the variable associated with the configuration option  and <em><code>value</code></em> is the value you want to use.  For a list of the variables, see <a href="files.htm#49000">Configuration Variables</a>.<br /> <br /> If the Traffic Server <code>bin</code> directory is not in your path, then prepend the Traffic Line command with <code>./</code> (for example, <code>./traffic_line -r variable</code>).</li>
+</ol>
+<h2 id="ConfiguringTrafficEdgeUsingConfigFiles">Configure Traffic Server Using Configuration Files</h2>
+<p>As an alternative to using  Traffic Line or Traffic Shell, you can change Traffic Server configuration options by manually editing specific variables in the <code>records.config</code> file located in the Traffic Server <code>config</code> directory. To edit the variables, open the file in a text editor (such as <code>vi</code> or <code>emacs</code>) and change  variable values. After you modify the <code>records.config</code> file, Traffic Server must reread the configuration files. From the Traffic Server <code>bin</code> directory, enter the Traffic Line command  <code>traffic_line -x</code>. You may need to restart Traffic Server to apply the configuration changes. </p>
+<p>The following is a sample portion of the <code>records.config</code> file: </p>
+<p><img src="images/records.jpg" width="812" height="609" /></p>
+<blockquote>
+  <p><em><b>Sample records.config file </b></em></p>
+</blockquote>
+<p>In addition to the <code>records.config</code> file, Traffic Server provides other configuration files that are used to configure specific features. All  configuration files   you can  manually edit are described in <a href="files.htm">Configuration Files</a>. </p>
+<h2 id="SavingRestoringTrafficEdgeConfigs">&nbsp;</h2>
+<p>&nbsp;</p>
+</body>
 </html>
\ No newline at end of file

Modified: incubator/trafficserver/site/trunk/docs/admin/explicit.htm
URL: http://svn.apache.org/viewvc/incubator/trafficserver/site/trunk/docs/admin/explicit.htm?rev=897032&r1=897031&r2=897032&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/explicit.htm (original)
+++ incubator/trafficserver/site/trunk/docs/admin/explicit.htm Thu Jan  7 22:15:07 2010
@@ -1,60 +1,58 @@
-<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>Explicit Proxy Caching</h1>
-<p>If you want to use Traffic Server as an explicit proxy cache, you must configure client software (i.e., browsers) to send requests directly to Traffic Server.</p>
-<h2 id="ExplicitProxyCachingHTTP">Explicit Proxy Caching for HTTP</h2>
-<p>  If you do not configure Traffic Server to use the transparency option (with which client requests are intercepted on the way to origin servers by a switch or router and rerouted to the Traffic Server machine), then clients must configure their web browsers to send HTTP requests to the Traffic Server proxy cache by configuring their browsers to download proxy configuration instructions from a  <a href="#UsingPACFile"><em>PAC file</em></a> (Proxy Auto-Configuration file).</p>
-<h3 id="ConfiguringBrowsersManually">Configuring Browsers Manually </h3>
-<p>To manually configure a browser to send HTTP requests to Traffic Server, clients must provide the following information: </p>
-<ul>
-  <li>The fully-qualified hostname or IP address of the Traffic Server node</li>
-  <li>The Traffic Server proxy server port (port 8080)</li>
-</ul>
-<p>In addition, clients can specify <i>not</i> to use Traffic Server for certain sites - in such cases, requests to the listed sites go directly to the origin server. The procedures for manual configuration vary among browser versions; refer to specific browser documentation for complete proxy configuration instructions. You do not need to set any special configuration options on Traffic Server if you want to accept requests from manually-configured browsers. </p>
-<h3 id="UsingPACFile">Using a PAC File </h3>
-<p>A PAC file is a specialized JavaScript function definition that a browser calls to determine how requests are handled. Clients must specify (in their browser settings) the URL from which the PAC file is loaded.  You can store a PAC file on Traffic Server (or on any server in your network) and then provide the URL for this file to your clients. </p>
-<p>If you want to store a PAC file on the Traffic Server system, then you must perform the following configuration: </p>
-<ul>
-  <li>Either copy an existing PAC file into the Traffic Server <code>config</code> directory or enter a script that defines the proxy server configuration settings in the <code>proxy.pac</code> file provided (the file is empty by default). </li>
-  <li>Specify the port that Traffic Server uses to serve the PAC file. The default port is 8083.</li>
-</ul>
-<h5>Configure Traffic Server to provide a PAC file manually: </h5>
-<ol>
-  <li>If you have an existing PAC file, then replace the <code>proxy.pac</code> file located in the Traffic Server <code>config</code> directory with the existing file. </li>
-  <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>
-<br />
-<table width="1232" border="1">
-    <tr>
-      <th width="322" scope="col">Variable</th>
-      <th width="894" scope="col">Description</th>
-    </tr>
-    <tr>
-      <td><code><i>proxy.config.admin.autoconf_port</i></code></td>
-      <td><p>Set this variable to specify the port  Traffic Server uses to serve the PAC file. The default port is 8083.</p>      </td>
-    </tr>
-</table>
-<br />
-  <li>Save and close the <code>records.config</code> file. </li>
-  <li>In a text editor, open the <code>proxy.pac</code> file located in the Traffic Server <code>config</code> directory.  </li>
- <ul>
- <li>If you copied an existing PAC file into the Traffic Server config directory, then the <code>proxy.pac</code> file contains your proxy configuration settings. Check the settings and make changes if necessary.  </li>
-  <li>If you did not copy an existing PAC file into the Traffic Server <code>config</code> directory, then the <code>proxy.pac</code> file is empty. Enter a script that will provide the proxy server configuration settings. A sample script is provided in <a href="#SamplePACFile"><em>Sample PAC File</em></a>. </li>
-</ul>
-<li>Save and close the <code>proxy.pac</code> file. </li>
-  <li>Restart Traffic Server.  </li>
-  <li>Inform your users to set their browsers to point to this PAC file; <a href="#SetBrowsersPointPACFile"><em>click here for browser settings</em></a>. </li>
-</ol>
-<h4 id="SamplePACFile">Sample PAC File </h4>
-<p>The following sample PAC file instructs browsers to connect directly to all hosts without a fully-qualified domain name and to all hosts in the local domain. All other requests go to the Traffic Server named <code>myproxy.company.com</code>.</p>
-<pre>function FindProxyForURL(url, host) <br />{<br /> 		if (isPlainHostName(host)) ||<br />  		(localHostOrDomainIs(host, &quot;.company.com&quot;)) {<br /> 		 return &quot;DIRECT&quot;;<br /> 		}<br /> 		else<br /> 		return &quot;PROXY myproxy.company.com:8080;&quot; +<br /> 				&quot;DIRECT&quot;; <br />} </pre>
-<h3 id="UsingWPAD">&nbsp;</h3>
-<p>&nbsp;</p>
-</body>
+<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>Explicit Proxy Caching</h1>
+<p>If you want to use Traffic Server as an explicit proxy cache, you must configure client software (i.e., browsers) to send requests directly to Traffic Server.</p>
+<h2 id="ExplicitProxyCachingHTTP">Explicit Proxy Caching for HTTP</h2>
+<p>  If you do not configure Traffic Server to use the transparency option (with which client requests are intercepted en route to origin servers by a switch/router and rerouted to the Traffic Server machine), then clients must configure their web browsers to send HTTP requests to the Traffic Server proxy cache by configuring their browsers to download proxy configuration instructions from a  <a href="#UsingPACFile">PAC file</a> (Proxy Auto-Configuration file).</p>
+<h3 id="ConfiguringBrowsersManually">Configuring Browsers Manually </h3>
+<p>To manually configure a browser to send HTTP requests to Traffic Server, clients must provide the following information: </p>
+<ul>
+  <li>The fully-qualified hostname or IP address of the Traffic Server node</li>
+  <li>The Traffic Server proxy server port (port 8080)</li>
+</ul>
+<p>In addition, clients can specify <i>not</i> to use Traffic Server for certain sites - in such cases, requests to the listed sites go directly to the origin server. The procedures for manual configuration vary among browser versions; refer to specific browser documentation for complete proxy configuration instructions. You do not need to set any special configuration options on Traffic Server if you want to accept requests from manually-configured browsers. </p>
+<h3 id="UsingPACFile">Using a PAC File </h3>
+<p>A <b>PAC file</b> is a specialized JavaScript function definition that a browser calls to determine how requests are handled. Clients must specify (in their browser settings) the URL from which the PAC file is loaded.  You can store a PAC file on Traffic Server (or on any server in your network) and then provide the URL for this file to your clients. </p>
+<p>If you want to store a PAC file on the Traffic Server system, then you must perform the following configuration: </p>
+<ul>
+  <li>Either copy an existing PAC file into the Traffic Server <code>config</code> directory or enter a script that defines the proxy server configuration settings in the <code>proxy.pac</code> file provided (the file is empty by default). </li>
+  <li>Specify the port  Traffic Server uses to serve the PAC file. The default port is 8083.</li>
+</ul>
+<h5>Configure Traffic Server to provide a PAC file manually: </h5>
+<ol>
+  <li>If you have an existing PAC file, then replace the <code>proxy.pac</code> file located in the Traffic Server <code>config</code> directory with the existing file. </li>
+  <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>
+  <table width="1232" border="1">
+    <tr>
+      <th width="322" scope="col">Variable</th>
+      <th width="894" scope="col">Description</th>
+    </tr>
+    <tr>
+      <td><code><i>proxy.config.admin.autoconf_port</i></code></td>
+      <td><p>Set this variable to specify the port  Traffic Server uses to serve the PAC file. The default port is 8083.</p>      </td>
+    </tr>
+</table>
+  <li>Save and close the <code>records.config</code> file. </li>
+  <li>In a text editor, open the <code>proxy.pac</code> file located in the Traffic Server <code>config</code> directory.  </li>
+ <ul>
+ <li>If you copied an existing PAC file into the Traffic Server config directory, then the <code>proxy.pac</code> file contains your proxy configuration settings. Check the settings and make changes if necessary.  </li>
+  <li>If you did not copy an existing PAC file into the Traffic Server <code>config</code> directory, then the <code>proxy.pac</code> file is empty. Enter a script that will provide the proxy server configuration settings. A sample script is provided in <a href="#SamplePACFile">Sample PAC File</a>. </li>
+</ul>
+<li>Save and close the <code>proxy.pac</code> file. </li>
+  <li>Restart Traffic Server.  </li>
+  <li>Inform your users to set their browsers to point to this PAC file; <a href="#SetBrowsersPointPACFile">click here for browser settings</a>. </li>
+</ol>
+<h4 id="SamplePACFile">Sample PAC File </h4>
+<p>The following sample PAC file instructs browsers to connect directly to all hosts without a fully-qualified domain name and to all hosts in the local domain. All other requests go to the Traffic Server named <code>myproxy.company.com</code>.</p>
+<pre>function FindProxyForURL(url, host) <br />{<br /> 		if (isPlainHostName(host)) ||<br />  		(localHostOrDomainIs(host, &quot;.company.com&quot;)) {<br /> 		 return &quot;DIRECT&quot;;<br /> 		}<br /> 		else<br /> 		return &quot;PROXY myproxy.company.com:8080;&quot; +<br /> 				&quot;DIRECT&quot;; <br />} </pre>
+<h3 id="UsingWPAD">&nbsp;</h3>
+<p>&nbsp;</p>
+</body>
 </html>
\ No newline at end of file

Modified: incubator/trafficserver/site/trunk/docs/admin/getstart.htm
URL: http://svn.apache.org/viewvc/incubator/trafficserver/site/trunk/docs/admin/getstart.htm?rev=897032&r1=897031&r2=897032&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/getstart.htm (original)
+++ incubator/trafficserver/site/trunk/docs/admin/getstart.htm Thu Jan  7 22:15:07 2010
@@ -1,54 +1,54 @@
-<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>Getting Started</h1>
-<p>After you have installed Traffic Server on your system, you can do any of the following:</p>
-<ul>
-  <li><a href="#StartingTrafficEdge"><em>Start Traffic Server</em></a></li>
-  <li><a href="#StartingTrafficLine"><em>Start Traffic Line</em></a></li>
-  <li><a href="#StartingTrafficShell"><em>Start Traffic Shell</em></a></li>
-  <li><a href="#StoppingTrafficEdge"><em>Stop Traffic Server</em></a></li>
-</ul>
-<h2 id="StartingTrafficEdge">Start Traffic Server</h2>
-<p>Start Traffic Server manually by issuing the <code>start_traffic_server</code> command. This command starts all the processes that work together to process Traffic Server requests and manage, control, and monitor the health of the Traffic Server system. </p>
-<h5>To run the start_traffic_server command: </h5>
-<ol>
-  <li>Log on to the Traffic Server node as the Traffic Server administrator and navigate to the Traffic Server <code>bin</code> directory. </li>
-  <li>Enter the following command:<br />
-  <code>./start_traffic_server</code></li>
-</ol>
-<h2 id="StartingTrafficLine">Start Traffic Line</h2>
-<p>Traffic Line provides a quick way of viewing Traffic Server statistics and configuring the Traffic Server system via command-line interface. To execute individual commands or script multiple commands, refer to <em><a href="cli.htm">Traffic Line Commands</a></em>. </p>
-<h5>To start a Traffic Line session: </h5>
-<ol>
-  <li>Log on to a Traffic Server node as the Traffic Server administrator and navigate to the Traffic Server <code>bin</code> directory. <br />
-  Traffic Line commands take the following form:<br /><code>traffic_line <em>-command argument</em></code></li>
-  <li>For a list of <code>traffic_line</code> commands, enter:<br />
-    <code>traffic_line -h</code><br />
-    If the Traffic Server <code>bin</code> directory is not in your path, then prepend the Traffic Line command with <code>./</code> (for example, <code>./traffic_line -h</code>). </li>
-</ol>
-<h2 id="StartingTrafficShell">Start Traffic Shell </h2>
-<p>Traffic Shell is a command-line tool that enables you   to monitor and configure Traffic Server; it can be used instead of Traffic Line. Traffic Server provides documentation for Traffic Shell in the form of manual pages (<code>man</code> pages). </p>
-<h5>To start Traffic Shell and read an overview <code>man</code> page:</h5>
-<ol>
-  <li>Log on to a Traffic Server node as the Traffic Server administrator and navigate to the Traffic Server <code>bin</code> directory. </li>
-  <li>
-    Enter the following command: <br />
-   <code>./start_traffic_shell</code>
-  </li>
-  <li>Enter the following command to display the <code>traffic_shell</code> overview <code>man</code> page:<br /><code>man traffic_shell</code><br />The <code>man</code> page describes how to use Traffic Shell, how to obtain a list of available commands, and how to obtain documentation about each command.</li>
-</ol>
-<h2 id="StoppingTrafficEdge">Stop Traffic Server </h2>
-<p>To stop Traffic Server, always use the <code>stop_traffic_server</code> command. This command stops all the Traffic Server processes (<code>traffic_manager</code>, <code>traffic_server</code>, and <code>traffic_cop</code>). Do not manually stop processes, as this can lead to unpredictable results.</p>
-<p><b>To run the <code>stop_traffic_server</code> command:</b></p>
-<ol>
-  <li>Log on to the node as the Traffic Server administrator and navigate to the Traffic Server <code>bin</code> directory.</li>
-  <li>Enter the following command: <br /> <code>./stop_traffic_server</code></li>
-</ol>
-</body>
+<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>Getting Started</h1>
+<p>After you have installed Traffic Server on your system, you can do any of the following:</p>
+<ul>
+  <li><a href="#StartingTrafficEdge">Start Traffic Server</a></li>
+  <li><a href="#StartingTrafficLine">Start Traffic Line</a></li>
+  <li><a href="#StartingTrafficShell">Start Traffic Shell</a></li>
+  <li><a href="#StoppingTrafficEdge">Stop Traffic Server</a></li>
+</ul>
+<h2 id="StartingTrafficEdge">Start Traffic Server</h2>
+<p>Start Traffic Server manually by issuing the <code>start_traffic_server</code> command. This command starts all the processes that work together to process Traffic Server requests as well as manage, control, and monitor the health of the Traffic Server system. </p>
+<h5>To run the start_traffic_server command: </h5>
+<ol>
+  <li>Log on to the Traffic Server node as the Traffic Server administrator and navigate to the Traffic Server <code>bin</code> directory. </li>
+  <li>Enter the following command:<br />
+  <code>./start_traffic_server</code></li>
+</ol>
+<h2 id="StartingTrafficLine">Start Traffic Line</h2>
+<p>Traffic Line provides a quick way of viewing Traffic Server statistics and configuring the Traffic Server system via command-line interface. To execute individual commands or script multiple commands, refer to <a href="cli.htm">Traffic Line Commands</a>.</p>
+<h5>To start a Traffic Line session: </h5>
+<ol>
+  <li>Log on to a Traffic Server node as the Traffic Server administrator and navigate to the Traffic Server <code>bin</code> directory. <br />
+  Traffic Line commands take the following form:<br /><code>traffic_line <em>-command argument</em></code></li>
+  <li>For a list of <code>traffic_line</code> commands, enter:<br />
+    <code>traffic_line -h</code><br />
+    If the Traffic Server <code>bin</code> directory is not in your path, then prepend the Traffic Line command with <code>./</code> (for example, <code>./traffic_line -h</code>). </li>
+</ol>
+<h2 id="StartingTrafficShell">Start Traffic Shell </h2>
+<p>Traffic Shell is a command-line tool that enables you   to monitor and configure Traffic Server; it can be used instead of Traffic Line. Traffic Server provides documentation for Traffic Shell in the form of manual (<code>man</code>) pages. </p>
+<h5>To start Traffic Shell and read an overview <code>man</code> page:</h5>
+<ol>
+  <li>Log on to a Traffic Server node as the Traffic Server administrator and navigate to the Traffic Server <code>bin</code> directory. </li>
+  <li>
+    Enter the following command: <br />
+   <code>./start_traffic_shell</code>
+  </li>
+  <li>Enter the following command to display the <code>traffic_shell</code> overview <code>man</code> page:<br /><code>man traffic_shell</code><br />The <code>man</code> page describes how to use Traffic Shell, how to obtain a list of available commands, and how to obtain documentation about each command.</li>
+</ol>
+<h2 id="StoppingTrafficEdge">Stop Traffic Server </h2>
+<p>To stop Traffic Server, always use the <code>stop_traffic_server</code> command. This command stops all the Traffic Server processes (<code>traffic_manager</code>, <code>traffic_server</code>, and <code>traffic_cop</code>). Do not manually stop processes, as this can lead to unpredictable results.</p>
+<p><b>To run the <code>stop_traffic_server</code> command:</b></p>
+<ol>
+  <li>Log on to the node as the Traffic Server administrator and navigate to the Traffic Server <code>bin</code> directory.</li>
+  <li>Enter the following command: <br /> <code>./stop_traffic_server</code></li>
+</ol>
+</body>
 </html>
\ No newline at end of file

Modified: incubator/trafficserver/site/trunk/docs/admin/intro.htm
URL: http://svn.apache.org/viewvc/incubator/trafficserver/site/trunk/docs/admin/intro.htm?rev=897032&r1=897031&r2=897032&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/intro.htm (original)
+++ incubator/trafficserver/site/trunk/docs/admin/intro.htm Thu Jan  7 22:15:07 2010
@@ -1,92 +1,92 @@
-<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>
+<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">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>
+
+</body>
 </html>
\ No newline at end of file



Mime
View raw message