trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mlib...@apache.org
Subject svn commit: r833617 [2/6] - in /incubator/trafficserver/site/trunk/docs/admin: cache.htm cli.htm doc.css files.htm http.htm leftnav.html log.htm secure.htm top.html
Date Sat, 07 Nov 2009 00:35:48 GMT
Modified: incubator/trafficserver/site/trunk/docs/admin/files.htm
URL: http://svn.apache.org/viewvc/incubator/trafficserver/site/trunk/docs/admin/files.htm?rev=833617&r1=833616&r2=833617&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/files.htm (original)
+++ incubator/trafficserver/site/trunk/docs/admin/files.htm Sat Nov  7 00:35:48 2009
@@ -2,6 +2,7 @@
   <head>
     <title>Configuration Files</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><a name="63579">Appendix E - Configuration Files</a></h1> 
@@ -31,13 +32,13 @@
 
      <h2>
 <a name="69422">bypass.config</a></h2>
-     <p> The <code> bypass.config</code> file contains static bypass rules that Traffic Server uses in transparent proxy caching mode. <em> Static</em> bypass rules instruct Traffic Server to bypass certain incoming client requests so that they are served by the origin server. The <code>bypass.config</code> file also accepts<em> </em><a href="#62813"><em>Dynamic Deny Bypass Rules</em></a>.</p>
+     <p> The <code> bypass.config</code> file contains static bypass rules that Traffic Server uses in transparent proxy caching mode. <em> Static</em> bypass rules instruct Traffic Server to bypass certain incoming client requests so  they are served by the origin server. The <code>bypass.config</code> file also accepts<em> </em><a href="#62813"><em>Dynamic Deny Bypass Rules</em></a>.</p>
 <p>You can configure three types of static bypass rules:     </p>
 
 <ul>
        <li><em> Source </em>bypass  rules configure Traffic Server to bypass a particular source IP address or range of IP addresses. For example: bypass clients that do not want to use caching. </li><br />
        <li><em> Destination </em>bypass  rules configure Traffic Server to bypass a particular destination IP address or range of IP addresses. For example: bypass origin servers that use IP authentication based on the client's real IP address.<br />
-  <strong>IMPORTANT</strong>: Destination bypass rules prevent Traffic Server from caching an entire site. You will experience hit rate impacts if the site you bypass is popular.  <p></p></li>
+  <strong>IMPORTANT</strong>: Destination bypass rules prevent Traffic Server from caching an entire site. You will experience hit rate impacts if the site you bypass is popular.</li>
        <br />
  <li><em>Source/destination pair </em>bypass rules configure Traffic Server to bypass requests that originate from the specified source to the specified destination. For example:   route around specific client-server pairs that experience broken IP authentication or out-of-band HTTP traffic problems when cached. Source/destination bypass rules can be preferable to destination rules because they block a destination server only for users that experience problems.  </li>
  </ul>
@@ -59,8 +60,7 @@
            - A simple IP address, such as<code> 123.45.67.8</code><br />
            - In CIDR (Classless Inter-Domain Routing) format, such as<code> 1.1.1.0/24</code><br />
            - A range separated by a dash, such as<code> 1.1.1.1-2.2.2.2</code><br />
-         - Any combination of the above separated by commas, such as<code> 1.1.1.0/24, 25.25.25.25, 123.1.23.1-123.1.23.123</code>
-         <p></p></td>
+         - Any combination of the above separated by commas, such as<code> 1.1.1.0/24, 25.25.25.25, 123.1.23.1-123.1.23.123</code></td>
        </tr>
 <tr>
     <td><p><code> dst <em> ipaddress</em> </code></p></td>
@@ -84,7 +84,7 @@
  
   <code>deny_dyn_bypass src <em>ipaddress</em> | dst <em>ipaddress</em> | src <em>ipaddresss</em> AND <em>ipaddress</em></code> </p>
   <p>For a description of the options, refer to the table above.  For the dynamic deny bypass rules to work, you must set the variable <code><i>proxy.config.arm.bypass_dynamic_enabled</i></code> to <code>1</code> in the <code>records.config</code> file.   </p>
-<p><strong>IMPORTANT:</strong> Static bypass rules overwrite dynamic deny bypass rules. Therefore, if a static bypass rule and a dynamic bypass rule contain the same IP address, then the dynamic deny bypass rule is ignored.  </p>
+<p><strong>IMPORTANT:</strong> Static bypass rules overwrite dynamic deny bypass rules. If a static bypass rule and a dynamic bypass rule contain the same IP address, then the dynamic deny bypass rule will be ignored.  </p>
       <h3>
         <a name="157525">Examples</a>  </h3>
   <p>The following example shows source, destination, and source/destination <em>bypass</em> rules:  <br />
@@ -120,54 +120,54 @@
          <th> <p>Allowed Value</p></th>
        </tr>
        <tr>
-         <td><p><code> dest_domain</code> </p></td>
+         <td><p><i><code> dest_domain</code> </i></p></td>
          <td><p>A requested domain name. Traffic Server matches the domain name of the destination from the URL in the request.</p></td>
        </tr>
        <tr>
-         <td><p><code> dest_host</code> </p></td>
+         <td><p><i><code> dest_host</code> </i></p></td>
          <td><p>A requested hostname. Traffic Server matches the hostname of the destination from the URL in the request.</p></td>
        </tr>
        <tr>
-         <td><p><code> dest_ip</code> </p></td>
+         <td><p><i><code> dest_ip</code> </i></p></td>
          <td><p>A requested IP address. Traffic Server matches the IP address of the destination in the request.</p></td>
        </tr>
        <tr>
-         <td><p><code> url_regex</code> </p></td>
+         <td><p><i><code> url_regex</code> </i></p></td>
          <td><p>A regular expression to be found in a URL.</p></td>
        </tr>
      </table>
-     <p>The secondary specifiers are optional in the <code>cache.config</code> file. The following table lists  possible secondary specifiers with allowed values.  </p>
+  <p>The secondary specifiers are optional in the <code>cache.config</code> file. The following table lists  possible secondary specifiers with allowed values.  </p>
      <table border="1">
        <tr>
          <th> <p>Secondary Specifier</p></th>
          <th> <p>Allowed Value</p></th>
        </tr>
        <tr>
-         <td><p><code> port</code> </p></td>
+         <td><p><i><code> port</code> </i></p></td>
          <td><p>A requested URL port.</p></td>
        </tr>
        <tr>
-         <td><p><code> scheme</code> </p></td>
+         <td><p><i><code> scheme</code> </i></p></td>
          <td><p>A request URL protocol: http or https.</p></td>
        </tr>
        <tr>
-         <td><p><code> prefix</code> </p></td>
+         <td><p><i><code> prefix</code> </i></p></td>
          <td><p>A prefix in the path part of a URL.</p></td>
        </tr>
        <tr>
-         <td><p><code> suffix</code> </p></td>
+         <td><p><i><code> suffix</code> </i></p></td>
          <td><p>A file suffix in the URL.</p></td>
        </tr>
        <tr>
-         <td><p><code> method</code> </p></td>
+         <td><p><i><code> method</code> </i></p></td>
          <td><p>A request URL method: <code>get</code>, <code>put</code>, <code>post</code>, <code>trace</code>.</p></td>
        </tr>
        <tr>
-         <td><p><code> time</code> </p></td>
+         <td><p><i><code> time</code> </i></p></td>
          <td><p>A time range, such as<code> 08:00-14:00</code>.</p></td>
        </tr>
        <tr>
-         <td><p><code> src_ip</code> </p></td>
+         <td><p><i><code> src_ip</code> </i></p></td>
          <td><p>A client IP address.</p></td>
        </tr>
      </table>
@@ -178,7 +178,7 @@
           <th> <p>Value</p></th>
         </tr>
         <tr>
-          <td><p><code> action</code> </p></td>
+          <td><p><i><code> action</code> </i></p></td>
           <td><p>One of the following values:</p>
               <p><code> never-cache</code> configures Traffic Server to never cache specified objects. <br />
               <code> ignore-no-cache</code> configures Traffic Server to ignore all Cache-Control: no-cache headers. <br />
@@ -186,7 +186,7 @@
           <code> ignore-server-no-cache</code> configures Traffic Server to ignore Cache-Control: no-cache headers from origin server responses. </p></td>
         </tr>
         <tr>
-          <td><p><code> pin-in-cache</code></p></td>
+          <td><p><i><code> pin-in-cache</code></i></p></td>
           <td><p>The amount of time you want to keep the object(s) in the cache. The following time formats are allowed:</p>
               <p><code> d</code> for days; for example: 2d<br />
             <code> h</code> for hours; for example: 10h<br />
@@ -195,11 +195,11 @@
             mixed units; for example: 1h15m20s</p></td>
         </tr>
         <tr>
-          <td><p><code> revalidate</code> </p></td>
+          <td><p><i><code> revalidate</code> </i></p></td>
           <td><p>The amount of time object(s) are to be considered fresh. Use the same time formats as <code> pin-in-cache</code> .</p></td>
         </tr>
         <tr>
-          <td><p><code> ttl-in-cache</code> </p></td>
+          <td><p><i><code> ttl-in-cache</code> </i></p></td>
           <td><p>The amount of time object(s) are to be kept  in the cache, regardless of <code>Cache-Control</code> response headers. Use the same time formats as <code> pin-in-cache</code> and <code> revalidate</code> .</p></td>
         </tr>
       </table>
@@ -232,19 +232,19 @@
           <th> <p>Allowed Value</p></th>
         </tr>
         <tr>
-          <td><p><code> dest_domain</code> </p></td>
+          <td><p><i><code> dest_domain</code> </i></p></td>
           <td><p>A requested domain name.</p></td>
         </tr>
         <tr>
-          <td><p><code> dest_host</code> </p></td>
+          <td><p><i><code> dest_host</code> </i></p></td>
           <td><p>A requested hostname.</p></td>
         </tr>
         <tr>
-          <td><p><code> dest_ip</code> </p></td>
+          <td><p><i><code> dest_ip</code> </i></p></td>
           <td><p>A requested IP address.</p></td>
         </tr>
         <tr>
-          <td><p><code> url_regex</code> </p></td>
+          <td><p><i><code> url_regex</code> </i></p></td>
           <td><p>A regular expression to be found in a URL.</p></td>
         </tr>
       </table>
@@ -255,11 +255,11 @@
           <th> <p>Allowed Value</p></th>
         </tr>
         <tr>
-          <td><p><code> port</code> </p></td>
+          <td><p><i><code> port</code> </i></p></td>
           <td><p>A requested URL port or range of ports.</p></td>
         </tr>
         <tr>
-          <td><p><code> prefix</code> </p></td>
+          <td><p><i><code> prefix</code> </i></p></td>
           <td><p>A prefix in the path part of a URL.</p></td>
         </tr>
       </table>
@@ -270,72 +270,73 @@
           <th> <p>Allowed Value</p></th>
         </tr>
         <tr>
-          <td><p><code> max_connection_failures</code> </p></td>
+          <td><p><i><code> max_connection_failures</code> </i></p></td>
           <td><p>The maximum number of connection failures allowed within the fail window described below before Traffic Server marks the origin server as congested. The default value is 5.</p></td>
         </tr>
         <tr>
-          <td><p><code>fail_window</code></p></td>
+          <td><p><i><code>fail_window</code></i></p></td>
           <td><p>The time period during which the maximum number of connection failures can occur before Traffic Server marks the origin server as congested. The default value is 120 seconds.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy_retry_interval</code></p></td>
+          <td><p><i><code>proxy_retry_interval</code></i></p></td>
           <td><p>The number of seconds that Traffic Server waits before contacting a congested origin server again. The default value is 10 seconds</p></td>
         </tr>
         <tr>
-          <td><p><code>client_wait_interval</code></p></td>
+          <td><p><i><code>client_wait_interval</code></i></p></td>
           <td><p>The number of seconds that the client is advised to wait before retrying the congested origin server. The default value is 300 seconds.</p></td>
         </tr>
         <tr>
-          <td><p><code>wait_interval_alpha</code></p></td>
+          <td><p><i><code>wait_interval_alpha</code></i></p></td>
           <td><p>The upper limit for a random number that is added to the wait interval. The default value is 30 seconds.</p></td>
         </tr>
         <tr>
-          <td><p><code>live_os_conn_timeout</code></p></td>
+          <td><p><i><code>live_os_conn_timeout</code></i></p></td>
           <td><p>The connection timeout to the live (uncongested) origin server. The default value is 60 seconds. <br />
           If a client stops a request before the timeout occurs, then Traffic Server does not record a connection failure.</p></td>
         </tr>
         <tr>
-          <td><p><code>live_os_conn_retries</code></p></td>
+          <td><p><i><code>live_os_conn_retries</code></i></p></td>
           <td><p>The maximum number of retries allowed to the live (uncongested) origin server. The default value is 2.</p></td>
         </tr>
         <tr>
-          <td><p><code>dead_os_conn_timeout</code></p></td>
+          <td><p><i><code>dead_os_conn_timeout</code></i></p></td>
           <td><p>The connection timeout to the congested origin server. The default value is 15 seconds.</p></td>
         </tr>
         <tr>
-          <td><p><code>dead_os_conn_retries</code></p></td>
+          <td><p><i><code>dead_os_conn_retries</code></i></p></td>
           <td><p>The maximum number of retries allowed to the congested origin server. The default value is 1.</p></td>
         </tr>
         <tr>
-          <td><p><code>max_connection</code></p></td>
+          <td><p><i><code>max_connection</code></i></p></td>
           <td><p>The maximum number of connections allowed from Traffic Server to the origin server. The default value is -1.</p></td>
         </tr>
         <tr>
-          <td><p><code>error_page</code></p></td>
+          <td><p><i><code>error_page</code></i></p></td>
           <td><p>The error page  sent to the client when a server is congested. You must enclose the value in quotes; the default value is <code> &quot;congestion#retryAfter&quot;</code>.<br />The error page is sent only if the <code>Custom Responses</code> option is enabled (refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/options.htm#125023"><em>HTTP Responses</em></a>).</p></td>
         </tr>
         <tr>
-          <td><p><code>congestion_scheme</code></p></td>
+          <td><p><i><code>congestion_scheme</code></i></p></td>
           <td><p>Specifies if Traffic Server applies the rule on a per-host (<code>&quot;per_host&quot;) </code>  or per-IP basis <code> (&quot;per_ip&quot;)</code>. The default value is <code> &quot;per_ip&quot;</code>; you must enclose the value in quotes.<br />
             For example: if the server <code> www.host1.com</code> has two IP addresses and you use the tag value <code> &quot;per_ip&quot;</code>, then each IP address has its own number of connection failures and is marked as congested independently. If you use the tag value <code> &quot;per_host&quot;</code> and the server <code> www.host1.com</code> is marked as congested, then <i>both</i> IP addresses are marked as congested. </p></td>
         </tr>
   </table>
      <p>
-  <strong><a name="220707">Examples</a></strong>  </p>
+<strong><a name="220707">Examples</a></strong></p>
      <p>The following  <code>congestion.config</code>  rule configures Traffic Server to stop forwarding requests to the server <code>www.host.com</code> on port 80 (HTTP traffic) if the server is congested, according to the timeouts specified. Traffic Server uses the default tag values because no tag has been specified.  
      <br /><code>dest_host=www.host.com port=80</code>    </p>
-     <p>You can use one or more tags in a rule, but each tag must have one value only. If you specify no tags in the rule, then Traffic Server uses  default values.  <br />
- You can override any of the default tag values by adding configuration variables at the end of  <code>records.config</code> as follows:  <br /><code>CONFIG proxy.config.http.congestion_control.default.<em>tag</em> INT|STRING  <em>value</em></code>  </p>
-     <p>where <code>tag</code> is one of the tags described in the table under <a href="#220539"><em>congestion.config</em></a> and <code>value</code> is the value you want to use.</p>
+     <p>You can use one or more tags in a rule, but each tag must have one value only. If you specify no tags in the rule, then Traffic Server uses  default values. </p>
+     <p>You can override any of the default tag values by adding configuration variables at the end of <code>records.config</code> as follows:  <br />
+     <code>CONFIG proxy.config.http.congestion_control.default.<em>tag</em> INT|STRING  <em>value</em></code>  <br />
+     where <code><i><b>tag</b></i></code> is one of the tags described in the table under <a href="#220539"><em>congestion.config</em></a> and <code><i><b>value</b></i></code> is the value you want to use.</p>
      <p>For example: <br /><code>CONFIG<br />
 proxy.config.http.congestion_control.default.congestion_scheme  STRING per_host</code>  </p>
       <p><strong>IMPORTANT: </strong>Rules in the <code>congestion.config</code> file override the following variables in the <code>records.config</code> file:   </p>
-     <p><code>proxy.config.http.connect_attempts_max_retries</code>  <br />
+     <p><code><i>proxy.config.http.connect_attempts_max_retries</i></code>  <i><br />
      <code>proxy.config.http.connect_attempts_max_retries_dead_server</code>  <br />
      <code>proxy.config.http.connect_attempts_rr_retries</code>  <br />
      <code>proxy.config.http.connect_attempts_timeout</code>  <br />
      <code>proxy.config.http.down_server.cache_time</code>  <br />
-<code>proxy.config.http.down_server.abort_threshold</code></p>
+  <code>proxy.config.http.down_server.abort_threshold</code></i></p>
   <h2>
 <a name="234878">filter.config</a></h2>
      <p>The <code>filter.config</code> file enables you to deny or allow particular requests and strip header information from client requests.   After you modify  <code>filter.config</code>, you must restart Traffic Server.  </p>
@@ -350,19 +351,19 @@
           <th> <p>Allowed Value</p></th>
         </tr>
         <tr>
-          <td><p><code> dest_domain</code> </p></td>
+          <td><p><i><code> dest_domain</code> </i></p></td>
           <td><p>A requested domain name. Traffic Server matches the domain name of the destination from the URL in the request.</p></td>
         </tr>
         <tr>
-          <td><p><code> dest_host</code> </p></td>
+          <td><p><i><code> dest_host</code> </i></p></td>
           <td><p>A requested hostname. Traffic Server matches the hostname of the destination from the URL in the request.</p></td>
         </tr>
         <tr>
-          <td><p><code> dest_ip</code> </p></td>
+          <td><p><i><code> dest_ip</code> </i></p></td>
           <td><p>A requested IP address. Traffic Server matches the IP address of the destination in the request.</p></td>
         </tr>
         <tr>
-          <td><p><code> url_regex</code> </p></td>
+          <td><p><i><code> url_regex</code> </i></p></td>
           <td><p>A regular expression to be found in a URL.</p></td>
         </tr>
       </table>
@@ -374,23 +375,23 @@
           <th> <p>Allowed Value</p></th>
         </tr>
         <tr>
-          <td><p><code> port</code> </p></td>
+          <td><p><i><code> port</code> </i></p></td>
           <td><p>A requested URL port.</p></td>
         </tr>
         <tr>
-          <td><p><code> scheme</code> </p></td>
+          <td><p><i><code> scheme</code> </i></p></td>
           <td><p>A request URL protocol: <code>http</code> or <code>https</code>.</p></td>
         </tr>
         <tr>
-          <td><p><code> prefix</code> </p></td>
+          <td><p><i><code> prefix</code> </i></p></td>
           <td><p>A prefix in the path part of a URL.</p></td>
         </tr>
         <tr>
-          <td><p><code> suffix</code> </p></td>
+          <td><p><i><code> suffix</code> </i></p></td>
           <td><p>A file suffix in the URL.</p></td>
         </tr>
         <tr>
-          <td><p><code> method</code> </p></td>
+          <td><p><i><code> method</code> </i></p></td>
           <td><p>A request URL method. You can specify one of the following:<br />
              <code> get</code> <br />
             <code> post</code> <br />
@@ -400,12 +401,13 @@
             <p><b>Note:</b> If the <code>PUSH</code> option is enabled (the <code>PUSH</code> option lets you deliver content directly to the cache without user request), then you must add a filtering rule with the <code>PUSH</code> action to ensure that only known source IP addresses implement <code>PUSH</code> requests to the cache. To enable the <code>PUSH</code> option, set the configuration variable <code> <i>proxy.config.http.push_method_enabled</i></code> to 1 in the <code> records.config</code> file.</p></td>
         </tr>
         <tr>
-          <td><p><code> time</code> </p></td>
+          <td><p><i><code> time</code> </i></p></td>
           <td><p>A time range, such as 08:00-14:00.</p></td>
         </tr>
         <tr>
-          <td><p><code> src_ip</code> </p></td>
-          <td><p>A client IP address.<br /><code> src_ip</code> is not supported for PNA content.</p></td>
+          <td><p><i><code> src_ip</code> </i></p></td>
+          <td><p>A client IP address.<br />
+            <b>Note:</b> <code> src_ip</code> is not supported for PNA content.</p></td>
         </tr>
       </table>
       <h3>
@@ -451,7 +453,8 @@
         <a name="121493">Generic Partition</a> </h4>
      <p>When configuring the <code>hosting.config </code>file, you must assign a generic partition to use for content that does not belong to any of the origin servers or domains listed. If all partitions for a particular origin server become corrupt, Traffic Server will also use the generic partition to store content for that origin server.  </p>
      <p>The generic partition must have the following format:  <br />
-<code>hostname=* partition=<em>partition_numbers</em> </code><br /><code>partition_numbers</code>is a comma-separated list of generic partitions.  </p>
+<code>hostname=* partition=<em>partition_numbers</em> </code><br />
+where <code><i>partition_numbers</i></code> is a comma-separated list of generic partitions.  </p>
      <h3>
         <a name="121477">Examples</a>  </h3>
      <p>The following example configures Traffic Server to store content from the domain <code>mydomain.com</code> in partition 1 and content from <code>www.myhost.com</code> in partition 2. Traffic Server stores content from all other origin servers in partitions 3 and 4.  </p>
@@ -511,8 +514,8 @@
 <a name="52049">Format</a></h3>
      <p>Each line in the <code>ip_allow.config</code> file must have the following format:  <br />
      <code>src_ip=<em>ipaddress </em>action=ip_allow | ip_deny</code> </p>
-<p>where <code><i>ipaddress</i></code> is the IP address or range of IP addresses of the clients allowed to access the Traffic Server proxy cache; the action <code>ip_allow</code> enables the specified clients to access the Traffic Server proxy cache; and <code>ip_deny</code> denies the specified clients to access the Traffic Server proxy cache.   </p>
-<p>By default, the <code>ip_allow.config</code> file contains the following line, which allows all clients to access the Traffic Server proxy cache. Comment out or delete this line before adding rules to restrict access.  <br />
+<p>where <code><i>ipaddress</i></code> is the IP address or range of IP addresses of the clients allowed to access the Traffic Server proxy cache, the action <code>ip_allow</code> enables the specified clients to access the Traffic Server proxy cache, and <code>ip_deny</code> denies the specified clients to access the Traffic Server proxy cache.   </p>
+<p>By default, the <code>ip_allow.config</code> file contains the following line, which allows all clients to access the Traffic Server proxy cache. To restrict access, comment out or delete this line before adding rules.  <br />
   <code>src_ip=0.0.0.0-255.255.255.255 action=ip_allow  </code></p>
 <h3>
 <a name="167137">Examples</a></h3>
@@ -537,42 +540,42 @@
           <th> <p>Allowed Inputs</p></th>
         </tr>
         <tr>
-          <td><p><code> format</code> </p></td>
+          <td><p><i><code> format</code> </i></p></td>
           <td><p>All lines must begin with the word <code> format</code> .</p></td>
         </tr>
         <tr>
-          <td><p><code> activation flag</code> </p></td>
+          <td><p><i><code> activation flag</code> </i></p></td>
           <td><p>Specifies if the custom log file is activated. You can specify one of the following options:</p>
               <p><code> enabled</code> <br />
               <code>disabled</code> </p></td>
         </tr>
         <tr>
-          <td><p><code> unique format identifier</code> </p></td>
+          <td><p><i><code> unique format identifier</code> </i></p></td>
           <td><p>You must use a unique integer for each custom log file you create.</p></td>
         </tr>
         <tr>
-          <td><p><code> format name</code> </p></td>
+          <td><p><i><code> format name</code> </i></p></td>
           <td><p>The name for the format you define.</p></td>
         </tr>
         <tr>
-          <td><p><code> format string</code> </p></td>
+          <td><p><i><code> format string</code> </i></p></td>
           <td><p>Identifies the <code> printf</code> -style format string specifying the field symbols to be displayed and how they should look in ASCII. Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/logfmts.htm"><em> Appendix D</em></a> for a list of the available field symbols and their meanings. Field symbols are indicated by %&lt;<code> field_symbol</code> &gt; format; for example, to indicate that <code> chi</code> is the client host IP and not the string <code> chi</code> to be printed, enter %<code> &lt;chi&gt;</code> . </p></td>
         </tr>
         <tr>
-          <td><p><code> file name</code> </p></td>
+          <td><p><i><code> file name</code> </i></p></td>
           <td><p>The name of the custom log file you create.</p></td>
         </tr>
         <tr>
-          <td><p><code> file type</code> </p></td>
+          <td><p><i><code> file type</code> </i></p></td>
           <td><p>The format of the file: <code>ASCII</code> or <code> BINARY.</code> </p></td>
         </tr>
         <tr>
-          <td><p><code> file header data</code> </p></td>
+          <td><p><i><code> file header data</code> </i></p></td>
           <td><p>The header text; enter <code> none</code> if you do not want header text. Enter the text of the header if you want your custom log file to have a header.</p></td>
         </tr>
       </table>
       <h3>
-        <a name="132135">Examples</a>  </h3>
+  <a name="132135">Examples</a>  </h3>
      <p>The following example shows a custom log format for a file named <code>minimalist</code>. It records the client host IP address (<code>chi</code>), the client request universal resource identifier (<code>cqu</code>), and the proxy response status code (<code>pssc</code>)   <br />
      <code>format:enabled:1:minimal:%&lt;chi&gt; / %&lt;cqu&gt; / %&lt;pssc&gt;:minimalist:ASCII:none</code> </p>
 <p>The output file for the above example format is:  <br />
@@ -593,9 +596,7 @@
 <h3>
   Format </h3>
      <p>Each line in the <code>log_hosts.config</code> file has the following format:  <code><br />
-     </code><code>hostname
-     </code></p>
-     <p>where <code>hostname</code> is the hostname of the origin server. </p>
+  <i>hostname</i> </code><br />where <code><i>hostname</i></code> is the hostname of the origin server. </p>
 <p><strong>Tip:</strong> You can specify keywords in the <code>log_hosts.config</code> file to record all transactions from origin servers with the specified keyword in their names in a separate log file. See the example below.</p>
      <h3>
         <a name="131568">Examples</a>  </h3>
@@ -611,7 +612,7 @@
 
      <h3>
         <a name="109866">Format</a>  </h3>
-     <p>The <code>logs_xml.config</code> file contains the following specifications: </p>
+     <p>The <code>logs_xml.config</code> file contains the  specifications below: </p>
      <ul>
        <li><code> LogFormat</code> specifies the fields to be gathered from each protocol event access.</li>
        <li><code> LogFilter</code> specifies the filters that are used to include or exclude certain entries being logged based on the value of a field within that entry.</li>
@@ -621,7 +622,7 @@
 
      <h3>
         <a name="104881">LogFormat</a> </h3>
-  <p>The following table lists  <code>LogFormat</code> specifications. </p>
+  <p>The following table lists  <code><b>LogFormat</b></code> specifications. </p>
       <table border="1">
         <tr>
           <th> <p>Field</p></th>
@@ -653,7 +654,7 @@
       </table>
      <h3>
         <a name="105718">LogFilters</a> </h3>
-  <p> The following table lists the <code>LogFilter</code> specifications.</p>
+  <p> The following table lists the <code><b>LogFilter</b></code> specifications.</p>
       <table border="1">
         <tr>
           <th> <p>Field</p></th>
@@ -667,11 +668,12 @@
           <td><p><code>&lt;Condition = &quot;valid_log_field valid_operator valid_comparison_value&quot;/&gt;</code></p></td>
           <td><p>Required. This field contains the following elements:</p>
               <p><code> <b>valid_log_field</b></code> - the field that will be compared against the given value. For more information, refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/logfmts.htm#63460"><em>Logging Format Cross-Reference</em></a>.</p>
-            <p><code> <b>valid_operator_field</b></code> - any one of the following: <code> MATCH</code> , <code> CASE_INSENSITIVE_MATCH</code> , <code> CONTAIN</code> , <code> CASE_INSENSITIVE_CONTAIN</code>. <code> <br />
-MATCH</code> is true if the field and value are identical (case sensitive). <code> <br />
-CASE_INSENSITIVE_MATCH</code> is similar to <code> MATCH</code>, except that it is case-insensitive. <code> <br />
-CONTAIN</code> is true if the field contains the value (the value is a substring of the field). <code> <br />
-CASE_INSENSITIVE_CONTAIN</code> is a case-insensitive version of <code> CONTAIN</code>.</p>
+            <p><code> <b>valid_operator_field</b></code> - any one of the following: <code> MATCH</code> , <code> CASE_INSENSITIVE_MATCH</code> , <code> CONTAIN</code> , <code> CASE_INSENSITIVE_CONTAIN</code>.  
+            </p><ul>
+<li><code>MATCH</code> is true if the field and value are identical (case-sensitive). </li>
+<li><code> CASE_INSENSITIVE_MATCH</code> is similar to <code> MATCH</code>, except that it is case-<b>insensitive</b>.  </li>
+<li> <code>CONTAIN</code> is true if the field contains the value (the value is a substring of the field). </li>
+<li> <code>CASE_INSENSITIVE_CONTAIN</code> is a case-insensitive version of <code> CONTAIN</code>.</li> </ul>
             <p><code> <b>valid_comparison_value</b></code> - any string or integer matching the field type. For integer values, all of the operators are equivalent and mean that the field must be equal to the specified value.</p>
             <p><b>Note: </b>There are no negative comparison operators. If you want to specify a negative condition, then use the <code> Action</code> field to <code> REJECT</code> the record.</p></td>
         </tr>
@@ -682,7 +684,7 @@
       </table>
      <h3>
      <a name="103986">LogObject</a> </h3>
-     <p>The following table lists the <code>LogObject</code> specifications. </p>
+     <p>The following table lists the <code><b>LogObject</b></code> specifications. </p>
       <table border="1">
         <tr>
           <th> <p>Field</p></th>
@@ -751,13 +753,13 @@
       </table>
      <p>
      <strong><a name="106972">Examples</a></strong>  </p>
-     <p>The following is an example of a <code>LogFormat</code> specification collecting information using three common fields:</p>
+     <p>The following is an example of a <code><b>LogFormat</b></code> specification collecting information using three common fields:</p>
      <pre>
      &lt;LogFormat&gt;
          &lt;Name = "minimal"/&gt; 
          &lt;Format = "%&lt;chi&gt; : %&lt;cqu&gt; : %&lt;pssc&gt;"/&gt;
      &lt;/LogFormat&gt;</pre>
-     <p>The following is an example of a <code>LogFormat</code> specification using aggregate operators:</p>
+     <p>The following is an example of a <code><b>LogFormat</b></code> specification using aggregate operators:</p>
      <pre>
      &lt;LogFormat&gt;
          &lt;Name = "summary"/&gt;
@@ -765,7 +767,7 @@
          &lt;Interval = "10"/&gt;
      &lt;/LogFormat&gt; </pre>
 
-<p> The following is an example of a <code>LogFilter</code> that will cause only <code>REFRESH_HIT</code> entries to be logged: </p>
+<p> The following is an example of a <code><b>LogFilter</b></code> that will cause only <code>REFRESH_HIT</code> entries to be logged: </p>
 
      <pre>
      &lt;LogFilter&gt; 
@@ -781,13 +783,13 @@
          &lt;Action = "ACCEPT"/&gt;
          &lt;Condition = "pssc MATCH REFRESH_HIT"/&gt;
      &lt;/LogFilter&gt;      </pre>
-<p> The following is an example of a <code>LogObject</code> specification that creates a local log file for the minimal format defined earlier. The log filename will be <code>minimal.log</code> because this is an ASCII log file (the default).  </p>
+<p> The following is an example of a <code><b>LogObject</b></code> specification that creates a local log file for the minimal format defined earlier. The log filename will be <code>minimal.log</code> because this is an ASCII log file (the default).  </p>
      <pre>
      &lt;LogObject&gt;
          &lt;Format = "minimal"/&gt;
          &lt;Filename = "minimal"/&gt; 
      &lt;/LogObject&gt; </pre>
-  <p>The following is an example of a <code>LogObject</code> specification that includes only HTTP requests served by hosts in the domain <code>company.com</code> or by the specific server <code>server.somewhere.com</code>. Log entries are sent to port 4000 of the collation host <code>logs.company.com</code> and to port 5000 of the collation host <code>209.131.52.129. </code></p><code>
+<p>The following is an example of a <code><b>LogObject</b></code> specification that includes only HTTP requests served by hosts in the domain <code>company.com</code> or by the specific server <code>server.somewhere.com</code>. Log entries are sent to port 4000 of the collation host <code>logs.company.com</code> and to port 5000 of the collation host <code>209.131.52.129. </code></p><code>
 
      <pre>
      &lt;LogObject&gt; 
@@ -800,7 +802,7 @@
      <h3>
         <a name="140052">WELF</a>  </h3>
   <p>
-<a name="140064">Traffic Server supports WELF, the WebTrends Enhanced Log format, so that you can </a>analyze Traffic Server log files with WebTrends reporting tools. A predefined <code>&lt;LogFormat&gt;</code> that is compatible with WELF is provided at the end of the <code><code>logs.config</code></code> file (shown below). To create a WELF format log file, create a <code><code>&lt;LogObject&gt;</code></code> that uses this predefined format.</p><code>
+<a name="140064">Traffic Server supports WELF (WebTrends Enhanced Log Format) so that you can </a>analyze Traffic Server log files with WebTrends reporting tools. A predefined <code>&lt;LogFormat&gt;</code> that is compatible with WELF is provided at the end of the <code><code>logs.config</code></code> file (shown below). To create a WELF format log file, create a <code><code>&lt;LogObject&gt;</code></code> that uses this predefined format.</p><code>
      <pre>
      &lt;LogFormat&gt;
          &lt;Name = "welf"/&gt;
@@ -926,10 +928,9 @@
 <h3>
    <a name="115449">Format</a>  </h3>
      <p>For each partition you want to create, enter a line with the following format:  <br />
-     <code>partition=<em>partition_number</em>  scheme=<em>protocol_type</em>  size=<em>partition_size</em> <br />
-     </code>where <code>partition_number</code> is a number between 1 and 255 (the maximum number of partitions is 255) and
-     <code>protocol_type</code> is  <code>http</code>. </p>
-<p>Traffic Server supports  <code>http</code> for HTTP partition types;     <code>partition_size</code> is the amount of cache space allocated to the partition. This value can be either a percentage of the total cache space or an absolute value. The absolute value must be a multiple of 128 MB, where 128 MB is the smallest value. If you specify a percentage, then the size is rounded down to the closest multiple of 128 MB. </p>
+     <code>partition=<em>partition_number</em>  scheme=<em>protocol_type</em>  size=<em>partition_size</em></code></p>
+     <p>where <code><i>partition_number</i></code> is a number between 1 and 255 (the maximum number of partitions is 255) and
+     <code><i>protocol_type</i></code> is  <code>http</code>. Traffic Server supports  <code>http</code> for HTTP partition types;     <code><i>partition_size</i></code> is the amount of cache space allocated to the partition. This value can be either a percentage of the total cache space or an absolute value. The absolute value must be a multiple of 128 MB, where 128 MB is the smallest value. If you specify a percentage, then the size is rounded down to the closest multiple of 128 MB. </p>
 <p>Each partition is striped across several disks to achieve parallel I/O. For example: if there are four disks, then a 1-GB  partition will have 256 MB on each disk (assuming each disk has enough free space available). If you do not allocate all the disk space in the cache, then the extra disk space is not used. You can use the extra space later to create new partitions without deleting and clearing the existing partitions. </p>
 <h3>
    <a name="121818">Examples</a>  </h3>
@@ -944,13 +945,13 @@
  <a name="48806">Format</a></h3>
      <p>Each variable has the following format:  <code><br />
      CONFIG <em>variable_name</em> DATATYPE <em>variable_value</em> </code></p>
-<p>where <code>DATATYPE</code> is <code>INT</code> (an integer), <code>STRING</code> (a string), or <code>FLOAT</code> (a floating point).  </p>
+<p>where <code>DATATYPE</code> is <code>INT</code> (integer), <code>STRING</code> (string), or <code>FLOAT</code> (floating point).  </p>
 
      <h3>
         <a name="48839">Examples</a>  </h3>
-     <p>In the following example, the variable<code> <i>proxy.config.proxy_name</i></code> is of datatype string and its value is <code>my_server</code>. This means that the name of the Traffic Server proxy is <code>my_server</code>.<br />
+     <p>In the following example, the variable<code> <i>proxy.config.proxy_name</i></code> is a <code>STRING</code> datatype with the value <code>my_server</code>. This means that the name of the Traffic Server proxy is <code>my_server</code>.<br />
 <code>CONFIG proxy.config.proxy_name STRING my_server  </code></p>
-     <p>In the following example, the variable <code><em>proxy.config.arm.enabled </em></code>is a yes/no flag. A value of <code>0</code> (zero) disables the option. A value of <code>1</code> enables the option.  <br />
+     <p>In the following example, the variable <code><em>proxy.config.arm.enabled </em></code>is a yes/no flag. A value of <code>0</code> (zero) disables the option; a value of <code>1</code> enables the option.  <br />
 <code>CONFIG proxy.config.arm.enabled INT 0  </code></p>
      <p>In the following example, the variable sets the cluster startup timeout to 10 seconds.  <br />
         <code>CONFIG proxy.config.cluster.startup_timeout INT 10  </code></p>
@@ -969,163 +970,175 @@
           <td rowspan=="1" colspan="3"><p><Strong> System Variables</Strong> </p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.proxy_name </code></p>
+          <td><p><code><i>proxy.config.proxy_name</i></code></p>
               <p><code>STRING </code></p></td>
           <td><p><code></code> </p></td>
           <td><p>The  name of the Traffic Server node.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.bin_path </code></p>
+          <td><p><code><i>proxy.config.bin_path</i></code></p>
               <p><code>STRING </code></p></td>
           <td><p><code>bin</code></p></td>
           <td><p>The  location of the Traffic Server <code> bin</code> directory.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.proxy_binary </code></p>
+          <td><p><code><i>proxy.config.proxy_binary </i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>traffic_server </code></p></td>
           <td><p>The  name of the executable that runs the <code>traffic_server</code> process.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.proxy_binary_opts </code></p>
+          <td><p><code><i>proxy.config.proxy_binary_opts</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>-M</code></p></td>
           <td><p>The  command-line options for starting Traffic Server.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.manager_binary </code></p>
+          <td><p><code><i>proxy.config.manager_binary</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>traffic_manager</code></p></td>
           <td><p>The  name of the executable that runs the <code>traffic_manager</code> process.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.cli_binary </code></p>
+          <td><p><code><i>proxy.config.cli_binary</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>traffic_line </code></p>
               <p>&nbsp;</p></td>
           <td><p>The  name of the executable that runs the command-line interface (Traffic Line).</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.watch_script </code></p>
+          <td><p><code><i>proxy.config.watch_script</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>traffic_cop </code></p></td>
           <td><p>The  name of the executable that runs the <code>traffic_cop</code> process.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.env_prep </code></p>
+          <td><p><code><i>proxy.config.env_prep</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>example_prep.sh</code></p>
               <p>&nbsp;</p></td>
-          <td><p>The  script that is executed before the <code>traffic_manager</code> process spawns the <code>traffic_server</code> process.</p></td>
+          <td><p>The  script executed before the <code>traffic_manager</code> process spawns the <code>traffic_server</code> process.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.config_dir </code></p>
+          <td><p><code><i>proxy.config.config_dir</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>config</code></p></td>
-          <td><p>The  directory that contains the Traffic Server configuration files.</p></td>
+          <td><p>The  directory that contains  Traffic Server configuration files.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.temp_dir </code></p>
+          <td><p><code><i>proxy.config.temp_dir </i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>/tmp</code></p></td>
           <td><p>The  directory used for Traffic Server temporary files.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.alarm_email</code></p>
+          <td><p><code><i>proxy.config.alarm_email</i></code></p>
               <p><code>STRING</code></p></td>
-          <td><p><b><code>???????</code></b></p></td>
+          <td><p>&nbsp;</p></td>
           <td><p>The  email address to which Traffic Server sends alarm messages.</p>
               <p>During a custom Traffic Server installation, you can specify the email address; otherwise, Traffic Server uses the Traffic Server user account name as the default value for this variable.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.syslog_facility </code></p>
+          <td><p><code><i>proxy.config.syslog_facility</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>LOG_DAEMON</code></p></td>
           <td><p>The  facility used to record system log files.</p>
               <p>Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/log.htm#UnderstandingTrafficEdgeLogFiles">Understanding Traffic Server Log Files</a>.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.cop.core_signal </code></p>
+          <td><p><code><i>proxy.config.cop.core_signal</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>The  signal  sent to <code>traffic_cop</code>'s managed processes to stop them. </p>
               <p>0 = no signal is sent.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.cop.linux_min_swapfree_kb</code></p>
+          <td><p><code><i>proxy.config.cop.linux_min_swapfree_kb</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>10240</code></p></td>
           <td><p>The  minimum amount of free swap space allowed before Traffic Server stops the <code>traffic_server </code>and <code>traffic_manager</code> processes to prevent the system from hanging. </p>
               <p>This configuration variable applies if swap is enabled in Linux 2.2 only.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.cop.linux_min_memfree_kb</code></p>
+          <td><p><code><i>proxy.config.cop.linux_min_memfree_kb</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>10240</code></p></td>
           <td><p>The  minimum amount of free memory allowed before Traffic Server stops the<code> traffic_server</code> and <code>traffic_manager</code> processes to prevent the system from hanging.</p>
               <p>This configuration variable applies if swap is <em> disabled </em> in Linux 2.2 only.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.output.logfile</code></p>
+          <td><p><code><i>proxy.config.output.logfile</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>traffic.out</code></p></td>
           <td><p>The  name and location of the file that contains warnings, status messages, and error messages produced by the Traffic Server processes.</p>
               <p>If no path is specified, then Traffic Server creates the file in its logging directory.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.snapshot_dir</code></p>
+          <td><p><code><i>proxy.config.snapshot_dir</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>snapshots</code></p></td>
           <td><p>The  directory in which Traffic Server stores configuration snapshots on the local system. Unless you specify an absolute path, this directory is located in the Traffic Server <code> config</code> directory.</p></td>
         </tr>
         <tr>
+          <td><p><code><i>proxy.config.accept_threads</i></code></p>
+            <p><code>INT</code></p></td>
+          <td><code>0</code></td>
+          <td>When enabled (1), runs a separate thread for accept processing. If disabled (0), then only 1 thread can be created.</td>
+        </tr>
+        <tr>
+          <td><p><code><i>proxy.config.thread.default.stacksize</i></code></p>
+            <p><code>INT</code></p></td>
+          <td><code>1096908</code></td>
+          <td>The new default thread stack size, for all threads. Original default is set at 1 MB.</td>
+        </tr>
+        <tr>
           <td rowspan=="1" colspan="3"><p><strong> Local Manager</strong></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.lm.sem_id </code></p>
+          <td><p><code><i>proxy.config.lm.sem_id </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>11452</code></p></td>
           <td><p>The  semaphore ID for the local manager.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.local.cluster.type </code></p>
+          <td><p><code><i>proxy.local.cluster.type</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>3</code></p></td>
           <td><p>Sets the clustering mode:</p>
-              <p>1 = full-clustering mode</p>
-            <p>2 = management-only mode</p>
-            <p>3 = no clustering</p></td>
+              <p>1 = full-clustering mode<br />
+              2 = management-only mode<br />
+              3 = no clustering</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.cluster.rsport </code></p>
+          <td><p><code><i>proxy.config.cluster.rsport</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>8088</code></p></td>
           <td><p>The  reliable service port. The reliable service port is used to send configuration information between the nodes in a cluster. All nodes in a cluster must use the same reliable service port.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.admin.autoconf_port </code></p>
+          <td><p><code><i>proxy.config.admin.autoconf_port </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>8083</code></p></td>
           <td><p>The  autoconfiguration port.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.admin.overseer_port </code></p>
+          <td><p><code><i>proxy.config.admin.overseer_port </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>8082</code></p></td>
           <td><p>The  port used for retrieving and setting statistics and configuration variables.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.admin.number_config_bak </code></p>
+          <td><p><code><i>proxy.config.admin.number_config_bak</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>3</code></p></td>
           <td><p>The  maximum number of copies of rolled configuration files to keep.</p></td>
         </tr>
-		<tr>
-          <td><p><code>proxy.config.admin.admin_password </code></p>
+    		<tr>
+          <td><p><code><i>proxy.config.admin.admin_password</i></code></p>
               <p><code>STRING</code></p></td>
           <td></td>
           <td>Specifies the encrypted administrator password that controls access to Traffic Manager. The format can be recreated with:<br>
-		 <code>
+     <code>
 #!/usr/bin/php<br>
 &lt;?php<br>
 $foo = md5('admin',true); <br>
@@ -1133,16 +1146,17 @@
 ?&gt;</code></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.admin.user_id </code></p>
+          <td><p><code><i>proxy.config.admin.user_id </i></code></p>
               <p><code>STRING</code></p></td>
-          <td><p><code><b>?????</b></code></p></td>
-          <td><p>The  nonprivileged user account designated to Traffic Server.</p></td>
+          <td><p><code>nobody</code></p></td>
+          <td><p>Option used to specify who to  run the <code>traffic_server </code>process as; also used to specify ownership of config and log files.</p>
+          <p>The  nonprivileged user account designated to Traffic Server.</p></td>
         </tr>
         <tr>
           <td rowspan=="1" colspan="3"><p><strong> Process Manager</strong></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.process_manager.mgmt_port </code></p>
+          <td><p><code><i>proxy.config.process_manager.mgmt_port</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>8084</code></p></td>
           <td><p>The  port used for internal communication between the <code>traffic_manager</code> process and the <code>traffic_server</code> process.</p></td>
@@ -1151,22 +1165,22 @@
           <td rowspan=="1" colspan="3"><p><strong> Alarm Configuration</strong></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.alarm.bin </code></p>
+          <td><p><code><i>proxy.config.alarm.bin</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>example_alarm_bin.sh </code></p></td>
           <td><p>The  name of the script file that can execute certain actions when an alarm is signaled. The default file is a sample script named <code> example_alarm_bin.sh</code> located in the <code> bin</code> directory. You must edit the script to suit your needs.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.alarm.abs_path </code></p>
+          <td><p><code><i>proxy.config.alarm.abs_path</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>NULL</code></p></td>
-          <td><p>The  full path to the script file that sends email to alert someone of Traffic Server problems.</p></td>
+          <td><p>The  full path to the script file that sends email to alert someone about Traffic Server problems.</p></td>
         </tr>
         <tr>
           <td rowspan=="1" colspan="3"><p><strong> Authentication Basic Realm</strong></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.proxy.authenticate.basic.realm</code></p></td>
+          <td><p><code><i>proxy.config.proxy.authenticate.basic.realm</i></code></p></td>
           <td><p><code>NULL</code></p></td>
           <td><p>The  authentication realm name. If the default of <code> NULL</code> is specified, then<code> traffic_edge</code> is used.</p></td>
         </tr>
@@ -1174,76 +1188,78 @@
           <td rowspan=="1" colspan="3"><p><strong> HTTP Engine</strong></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.server_port </code></p>
+          <td><p><code><i>proxy.config.http.server_port</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>8080</code></p></td>
-          <td><p>The  port that Traffic Server uses when acting as a web proxy server for web traffic or when serving web traffic transparently.</p></td>
+          <td><p>The  port that Traffic Server uses when acting as a web proxy server for web traffic.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.server_port_attr </code></p>
+          <td><p><code><i>proxy.config.http.server_port_attr </i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>X</code></p></td>
           <td><p>The  server port options. You can specify one of the following:</p>
-              <p><code>C=SERVER_PORT_COMPRESSED</code></p>
-            <p><code>X=SERVER_PORT_DEFAULT</code></p>
-            <p><code>T=SERVER_PORT_BLIND_TUNNEL</code></p></td>
+              <p><code>C=SERVER_PORT_COMPRESSED<br />
+          </code><code>X=SERVER_PORT_DEFAULT<br />
+          </code><code>T=SERVER_PORT_BLIND_TUNNEL</code></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.server_other_ports </code></p>
+          <td><p><code><i>proxy.config.http.server_other_ports </i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>NULL</code></p></td>
-          <td><p>The  ports other than the port specified by the variable <code>proxy.config.http.server_port </code>to bind for incoming http requests.</p></td>
+          <td><p>The  ports other than the port specified by the variable<i> <code>proxy.config.http.server_port</code></i><code> </code>to bind for incoming HTTP requests.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.ssl_ports </code></p>
+          <td><p><code><i>proxy.config.http.ssl_ports</i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>443 563</code></p></td>
-          <td><p>The  range of ports used for tunneling. Traffic Server allows tunnels only to the specified ports; for example, to retrieve an object using HTTPS via Traffic Server requires establishing a tunnel via Traffic Server to an origin server.</p></td>
+          <td><p>The  range of ports used for tunneling. Traffic Server allows tunnels only to the specified ports. </p>
+            <p>          For example: to retrieve an object using HTTPS via Traffic Server, a tunnel must be  established  to an origin server via Traffic Server.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.insert_request_via_str </code></p>
+          <td><p><code><i>proxy.config.http.insert_request_via_str </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>1</code></p></td>
           <td><p>You can specify one of the following:</p>
-              <p>0 = no extra information is added to the string.</p>
-            <p>1 = all extra information is added.</p>
-            <p>2 = some extra information is added.</p></td>
+              <p>0 = no extra information is added to the string.<br />
+            1 = all extra information is added.<br />
+            2 = some extra information is added.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.insert_response_via_str </code></p>
+          <td><p><code><i>proxy.config.http.insert_response_via_str </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>1</code></p></td>
           <td><p>You can specify one of the following:</p>
-              <p>0 = no extra information is added to the string.</p>
-            <p>1 = all extra information is added.</p>
-            <p>2 = some extra information is added.</p></td>
+              <p>0 = no extra information is added to the string.<br />
+          1 = all extra information is added.<br />
+          2 = some extra information is added.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.enable_url_expandomatic </code></p>
+          <td><p><code><i>proxy.config.http.enable_url_expandomatic</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>1</code></p></td>
-          <td><p>Enables (1) or disables (0) <code> .com</code> domain expansion, which configures the Traffic Server to attempt to resolve unqualified hostnames by redirecting them to the expanded address, prepended with <code> www.</code> and appended with <code> .com</code> ; for example, if a client makes a request to <code> host</code> , Traffic Server redirects the request to <code> www.host.com</code> .</p></td>
+          <td><p>Enables (1) or disables (0) <code> .com</code> domain expansion. This configures the Traffic Server to resolve unqualified hostnames by prepending with <code> www.</code> and appending with <code> .com</code> before redirecting  to the expanded address. </p>
+          <p>For example: if a client makes a request to <code> host</code> , then Traffic Server redirects the request to <code> www.host.com</code> .</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.no_dns_just_forward_to_parent </code></p>
+          <td><p><code><i>proxy.config.http.no_dns_just_forward_to_parent </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
-          <td><p>When enabled (1), and if parent caching is enabled, Traffic Server does no DNS lookups on request hostnames.</p></td>
+          <td><p>When enabled (1) and if parent caching is enabled, then Traffic Server does no DNS lookups on request hostnames.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.uncacheable_requests_bypass_parent </code></p>
+          <td><p><code><i>proxy.config.http.uncacheable_requests_bypass_parent</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>1</code></p></td>
           <td><p>When enabled (1), Traffic Server bypasses the parent proxy for a request that is not cacheable.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.keep_alive_enabled </code></p>
+          <td><p><code><i>proxy.config.http.keep_alive_enabled </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>1</code></p></td>
           <td><p>Enables (1) or disables (0) the use of keep-alive connections to either origin servers or clients.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.chunking_enabled </code></p>
+          <td><p><code><i>proxy.config.http.chunking_enabled </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>Specifies whether Traffic Sever can generate a chunked response:</p>
@@ -1253,7 +1269,7 @@
             3 = Generate a chunked response if the client request is HTTP 1.1 and the origin server has returned HTTP 1.1 before<p></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.send_http11_requests </code></p>
+          <td><p><code><i>proxy.config.http.send_http11_requests </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>3</code></p></td>
           <td><p>Configures Traffic Server to use HTTP Version 1.1 when communicating with origin servers. You can specify one of the following values:</p>
@@ -1263,59 +1279,59 @@
             <p><b>Note:</b> If HTTP 1.1 is used, then Traffic Server can use keep-alive connections with pipelining to origin servers. If HTTP 0.9 is used, then Traffic Server does not use keep-alive connections to origin servers. If HTTP 1.0 is used, then Traffic Server can use keep-alive connections without pipelining to origin servers.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.share_server_sessions </code></p>
+          <td><p><code><i>proxy.config.http.share_server_sessions </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>1</code></p></td>
-          <td><p>Enables (1) or disables (0) the re-use of server sessions.</p></td>
+          <td><p>Enables (1) or disables (0) the reuse of server sessions.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.record_heartbeat </code></p>
+          <td><p><code><i>proxy.config.http.record_heartbeat </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
-          <td><p>Enables (1) or disables (0) traffic_cop heartbeat logging.</p></td>
+          <td><p>Enables (1) or disables (0) <code>traffic_cop</code> heartbeat logging.</p></td>
         </tr>
         <tr>
           <td rowspan=="1" colspan="3"><p><b>Parent Proxy Configuration</b></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.parent_proxy_routing_enable </code></p>
+          <td><p><code><i>proxy.config.http.parent_proxy_routing_enable</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>Enables (1) or disables (0) the parent caching option.</p>
               <p>Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/hier.htm">Hierarchical Caching</a>.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.parent_proxy.retry_time </code></p>
+          <td><p><code><i>proxy.config.http.parent_proxy.retry_time </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>300</code></p></td>
           <td><p>The  amount of time allowed between connection retries to a parent cache that is unavailable.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.parent_proxy.fail_threshold </code></p>
+          <td><p><code><i>proxy.config.http.parent_proxy.fail_threshold</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>10</code></p></td>
           <td><p>The  number of times the connection to the parent cache can fail before Traffic Server considers the parent unavailable.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.parent_proxy.total_connect_attempts </code></p>
+          <td><p><code><i>proxy.config.http.parent_proxy.total_connect_attempts</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>4</code></p></td>
           <td><p>The  total number of connection attempts allowed to a parent cache before Traffic Server bypasses the parent or fails the request (depending on the <code>go_direct</code> option in the <code> bypass.config</code> file).</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.parent_proxy.per_parent_connect_attempts </code></p>
+          <td><p><code><i>proxy.config.http.parent_proxy.per_parent_connect_attempts </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>2</code></p></td>
-          <td><p>The  total number of connection attempts allowed per parent if multiple parents are used.</p></td>
+          <td><p>The  total number of connection attempts allowed per parent, if multiple parents are used.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.parent_proxy.connect_attempts_timeout</code></p>
+          <td><p><code><i>proxy.config.http.parent_proxy.connect_attempts_timeout</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>30</code></p></td>
-          <td><p>The  timeout value in seconds for parent cache connection attempts.</p></td>
+          <td><p>The  timeout value (in seconds) for parent cache connection attempts.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.forward.proxy_auth_to_parent </code></p>
+          <td><p><code><i>proxy.config.http.forward.proxy_auth_to_parent </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>Configures Traffic Server to send proxy authentication headers on to the parent cache.</p></td>
@@ -1324,102 +1340,116 @@
           <td rowspan=="1" colspan="3"><p><b>HTTP Connection Timeouts (secs)</b></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.keep_alive_no_activity_timeout_in </code></p>
+          <td><p><code><i>proxy.config.http.keep_alive_no_activity_timeout_in</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>10</code></p></td>
           <td><p>Specifies how long Traffic Server keeps connections to clients open for a subsequent request after a transaction ends.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.keep_alive_no_activity_timeout_out </code></p>
+          <td><p><code><i>proxy.config.http.keep_alive_no_activity_timeout_out </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>10</code></p></td>
           <td><p>Specifies how long Traffic Server keeps connections to origin servers open for a subsequent transfer of data after a transaction ends. </p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.transaction_no_activity_timeout_in </code></p>
+          <td><p><code><i>proxy.config.http.transaction_no_activity_timeout_in </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>120</code></p></td>
           <td><p>Specifies how long Traffic Server keeps connections to clients open if a transaction stalls.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.transaction_no_activity_timeout_out </code></p>
+          <td><p><code><i>proxy.config.http.transaction_no_activity_timeout_out</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>120</code></p></td>
           <td><p>Specifies how long Traffic Server keeps connections to origin servers open if the transaction stalls.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.transaction_active_timeout_in </code></p>
+          <td><p><code><i>proxy.config.http.transaction_active_timeout_in </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>The  maximum amount of time Traffic Server can remain connected to a client. If the transfer to the client is not complete before this timeout expires, Traffic Server closes the connection.</p>
               <p>The default value of 0 specifies that there is no timeout.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.transaction_active_timeout_out </code></p>
+          <td><p><code><i>proxy.config.http.transaction_active_timeout_out</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
-          <td><p>The  maximum amount of time Traffic Server waits for fulfillment of a connection request to an origin server. If Traffic Server does not complete the transfer to the origin server before this timeout expires, Traffic Server terminates the connection request.</p>
+          <td><p>The  maximum amount of time Traffic Server waits for fulfillment of a connection request to an origin server. If Traffic Server does not complete the transfer to the origin server before this timeout expires, then Traffic Server terminates the connection request.</p>
               <p>The default value of 0 specifies that there is no timeout.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.accept_no_activity_timeout </code></p>
+          <td><p><code><i>proxy.config.http.accept_no_activity_timeout </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>120</code></p></td>
           <td><p>The  timeout interval in seconds before Traffic Server closes a connection that has no activity.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.background_fill_active_timeout</code></p>
+          <td><p><code><i>proxy.config.http.background_fill_active_timeout</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>60</code></p></td>
           <td><p>Specifies how long Traffic Server continues a background fill before giving up and dropping the origin server connection.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.background_fill_completed_threshold</code></p>
+          <td><p><code><i>proxy.config.http.background_fill_completed_threshold</i></code></p>
               <p><code>FLOAT</code></p></td>
           <td><p><code>0.50000</code></p></td>
-          <td><p>The  proportion of total document size already transferred when a client aborts at which the proxy continues fetching the document from the origin server to get it into the cache (a <em> background fill</em> ).</p></td>
+          <td><p>The  proportion of total document size already transferred when a client aborts at which the proxy continues fetching the document from the origin server to get it into the cache (a  background fill ).</p></td>
         </tr>
         <tr>
           <td rowspan=="1" colspan="3"><p><b>Origin Server Connect Attempts</b></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.connect_attempts_max_retries </code></p>
+          <td><p><code><i>proxy.config.http.connect_attempts_max_retries</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>6</code></p></td>
           <td><p>The  maximum number of connection retries Traffic Server can make when the origin server is not responding.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.connect_attempts_max_retries_dead_server</code></p>
+          <td><p><code><i>proxy.config.http.connect_attempts_max_retries_dead_server</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>2</code></p></td>
           <td><p>The  maximum number of connection retries Traffic Server can make when the origin server is unavailable.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.connect_attempts_rr_retries </code></p>
+          <td><p><code><i>proxy.config.http.server_max_connections</i></code></p>
               <p><code>INT</code></p></td>
-          <td><p><code>2</code></p></td>
-          <td><p>The  maximum number of failed connection attempts allowed before a round-robin entry is marked as down if a server has round-robin DNS entries.</p></td>
+          <td><p><code>0</code></p></td>
+          <td><p>Limits the number of socket connections across all origin servers to the value specified.</p>
+          <p>To disable, set to zero (0). </p></td>
+        </tr>
+        <tr>
+          <td><p><code><i>proxy.config.http.origin_max_connections</i></code></p>
+          <p><code>INT</code></p></td>
+          <td>0</td>
+          <td><p>Limits the number of socket connections per origin server to the value specified.</p>
+          <p>To disable, set to zero (0). </p></td>
+        </tr>
+        <tr>
+          <td><p><code><i>proxy.config.http.connect_attempts_rr_retries </i></code></p>
+          <p><code>INT</code></p></td>
+          <td>2</td>
+          <td>The  maximum number of failed connection attempts allowed before a round-robin entry is marked as down if a server has round-robin DNS entries.</td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.connect_attempts_timeout </code></p>
+          <td><p><code><i>proxy.config.http.connect_attempts_timeout </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>30</code></p></td>
-          <td><p>The  timeout value in seconds for an origin server connection.</p></td>
+          <td><p>The  timeout value (in seconds) for an origin server connection.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.post_connect_attempts_timeout</code></p>
+          <td><p><code><i>proxy.config.http.post_connect_attempts_timeout</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>1800</code></p></td>
-          <td><p>The  timeout value in seconds for an origin server connection when the client request is a <code> POST</code> or <code> PUT</code> request.</p></td>
+          <td><p>The  timeout value (in seconds) for an origin server connection when the client request is a <code> POST</code> or <code> PUT</code> request.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.down_server.cache_time </code></p>
+          <td><p><code><i>proxy.config.http.down_server.cache_time</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>900</code></p></td>
-          <td><p>Specifies how long in seconds Traffic Server remembers that an origin server was unreachable.</p></td>
+          <td><p>Specifies how long (in seconds) Traffic Server remembers that an origin server was unreachable.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.down_server.abort_threshold </code></p>
+          <td><p><code><i>proxy.config.http.down_server.abort_threshold </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>10</code></p></td>
           <td><p>The  number of seconds before Traffic Server marks an origin server as unavailable when a client abandons a request because the origin server was too slow in sending the response header.</p></td>
@@ -1428,20 +1458,21 @@
           <td rowspan=="1" colspan="3"><p><strong> Congestion Control</strong></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.congestion_control.enabled</code></p>
+          <td><p><code><i>proxy.config.http.congestion_control.enabled</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
-          <td><p>Enables (1) or disables (0) the congestion control option, which configures Traffic Server to stop forwarding HTTP requests to origin servers when they become congested. Traffic Server sends the client a message to retry the congested origin server later. Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/http.htm#UsingCongestionControl">Using Congestion Control</a>.</p></td>
+          <td><p>Enables (1) or disables (0) the congestion control option, which configures Traffic Server to stop forwarding HTTP requests to origin servers when they become congested. Traffic Server sends the client a message to retry the congested origin server later. Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/http.htm#UsingCongestionControl"><i>Using Congestion Control</i></a>.</p></td>
         </tr>
         <tr>
           <td rowspan=="1" colspan="3"><p><strong> Negative Response Caching</strong></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.negative_caching_enabled</code></p>
+          <td><p><code><i>proxy.config.http.negative_caching_enabled</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
-          <td><p>When enabled (1), Traffic Server caches negative responses, such as  <code>404 Not Found</code>,  if a requested page does not exist. The next time a client requests the same page, Traffic Server serves the negative response from the cache.</p>
-              <p>The following lists the negative responses that Traffic Server caches:</p>
+          <td><p>When enabled (1), Traffic Server caches negative responses (such as  <code>404 Not Found</code>)  when a requested page does not exist. The next time a client requests the same page, Traffic Server serves the negative response from  cache.</p>
+            <p><b>Note</b>: <code>Cache-Control</code> directives from the server forbidding cache are ignored for the following HTTP response codes, regardless of the value specified for the <code><i>proxy.config.http.negative_caching_enabled</i></code> variable. </p>
+            <p>The following negative responses are cached by Traffic Server:            </p>
             <p><code>204  No Content <br />
             305  Use Proxy <br />
             400  Bad Request <br />
@@ -1455,73 +1486,84 @@
             504  Gateway Timeout </code></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.negative_caching_lifetime</code></p>
+          <td><p><code><i>proxy.config.http.negative_caching_lifetime</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>1800</code></p></td>
-          <td><p>The  how long Traffic Server keeps the negative responses as valid in cache.</p></td>
+          <td><p>The  how long (in seconds) Traffic Server keeps the negative responses as valid in cache. </p>
+            <p><b>Note:</b> This value only affects negative responses that do have explicit <code>Expires</code>: or <code>Cache-Control:</code> lifetimes set by the server.</p></td>
         </tr>
         <tr>
           <td rowspan=="1" colspan="3"><p><strong> Proxy User Variables</strong></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.anonymize_remove_from </code></p>
+          <td><p><code><i>proxy.config.http.anonymize_remove_from</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server removes the <code> From</code> header to protect the privacy of your users.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.anonymize_remove_referer </code></p>
+          <td><p><code><i>proxy.config.http.anonymize_remove_referer </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server removes the <code> Referer</code> header to protect the privacy of your site and users.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.anonymize_remove_user_agent </code></p>
+          <td><p><code><i>proxy.config.http.anonymize_remove_user_agent </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server removes the <code> User-agent</code> header to protect the privacy of your site and users.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.anonymize_remove_cookie </code></p>
+          <td><p><code><i>proxy.config.http.anonymize_remove_cookie</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server removes the <code> Cookie</code> header to protect the privacy of your site and users.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.anonymize_remove_client_ip </code></p>
+          <td><p><code><i>proxy.config.http.anonymize_remove_client_ip</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server removes <code> Client-IP</code> headers for more privacy.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.anonymize_insert_client_ip </code></p>
+          <td><p><code><i>proxy.config.http.anonymize_insert_client_ip </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>1</code></p></td>
           <td><p>When enabled (1), Traffic Server inserts <code> Client-IP </code> headers to retain the client IP address.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.append_xforwards_header </code></p>
+          <td><p><code><i>proxy.config.http.append_xforwards_header </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server appends                  <code> X-Forwards</code> headers to outgoing requests.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.anonymize_other_header_list </code></p>
+          <td><p><code><i>proxy.config.http.anonymize_other_header_list </i></code></p>
               <p><code>STRING</code></p></td>
           <td><p><code>NULL</code></p></td>
           <td><p>The  headers  Traffic Server should remove from outgoing requests.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.insert_squid_x_forwarded_for </code></p>
+          <td><p><code><i>proxy.config.http.insert_squid_x_forwarded_for </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server adds the client IP address to the <code> X-Forwarded-For</code> header.</p></td>
         </tr>
         <tr>
+          <td><p><code><i>proxy.config.http.normalize_ae_gzip</i></code></p>
+          <p><code>INT</code></p></td>
+          <td><code>0</code></td>
+          <td><p>Enable (1) to normalize all <code>Accept-Encoding:</code> headers to one of the following:</p><ul><li><code>Accept-Encoding: gzip</code> (if the header has gzip or x-gzip with any q)<br /> 
+            <b>OR</b></li>
+            <li><i>blank</i> (for any header that does not include gzip)</li>
+            <p></p>
+          <p>This  is useful for minimizing cached alternates of documents (e.g. <code>gzip,deflate</code> vs.  <code>deflate,gzip</code>). Enabling this option is recommended if your origin servers use no encodings other than gzip. </p></ul></td>
+        </tr>
+        <tr>
           <td rowspan=="1" colspan="3"><p><strong> Security</strong></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.push_method_enabled </code></p>
+          <td><p><code><i>proxy.config.http.push_method_enabled </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>Enables (1) or disables (0) the HTTP <code>PUSH</code> option, which allows you to deliver content directly to the cache without user request.</p>
@@ -1531,128 +1573,196 @@
           <td rowspan=="1" colspan="3"><p><strong> Cache Control</strong></p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.cache.http </code></p>
+          <td><p><code><i>proxy.config.http.cache.http</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>1</code></p></td>
           <td><p>Enables (1) or disables (0) caching of HTTP requests.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.cache.ignore_client_no_cache </code></p>
+          <td><p><code><i>proxy.config.http.cache.ignore_client_no_cache</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server ignores client requests to bypass the cache.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.cache.ims_on_client_no_cache </code></p>
+          <td><p><code><i>proxy.config.http.cache.ims_on_client_no_cache </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server issues a conditional request to the origin server if an incoming request has a <code> No-Cache</code> header.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.cache.ignore_server_no_cache </code></p>
+          <td><p><code><i>proxy.config.http.cache.ignore_server_no_cache </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server ignores origin server requests to bypass the cache.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.cache.cache_responses_to_cookies </code></p>
+          <td><p><code><i>proxy.config.http.cache.cache_responses_to_cookies</i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>3</code></p></td>
           <td><p>Specifies how cookies are cached:</p>
-              <p>0 = do not cache any responses to cookies<br />
-            1 = cache for any content-type<br />
-            2 = cache only for image types<br />
-            3 = cache for all but text content-types</p></td>
+              <p><code>0</code> = do not cache any responses to cookies<br />
+                <code>1</code> = cache for any content-type<br />
+                <code>2</code> = cache only for image types<br />
+            <code>3</code> = cache for all but text content-types</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.cache.ignore_authentication </code></p>
+          <td><p><code><i>proxy.config.http.cache.ignore_authentication </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>When enabled (1), Traffic Server ignores                  <code> WWW-Authentication</code> headers in responses. <br /><code> WWW-Authentication</code> headers are removed and not cached.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.cache.cache_urls_that_look_dynamic </code></p>
+          <td><p><code><i>proxy.config.http.cache.cache_urls_that_look_dynamic </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>Enables (1) or disables (0) caching of URLs that look dynamic.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.cache.enable_default_vary_headers </code></p>
+          <td><p><code><i>proxy.config.http.cache.enable_default_vary_headers </i></code></p>
               <p><code>INT</code></p></td>
           <td><p>0</p></td>
           <td><p>Enables (1) or disables (0) caching of alternate versions of HTTP objects that do not contain the <code>Vary</code> header.</p></td>
         </tr>
         <tr>
-          <td><p><code>proxy.config.http.cache.when_to_revalidate </code></p>
+          <td><p><code><i>proxy.config.http.cache.when_to_revalidate </i></code></p>
               <p><code>INT</code></p></td>
           <td><p>0</p></td>
           <td><p>Specifies when to revalidate content:</p>
-              <p><b>0</b> = Use cache directives or heuristic (the default value).<br />
-                <b>1</b> = Stale if heuristic.<br />
-                <b>2</b> = Always stale (always revalidate).<br />
-                <b>3</b> = Never stale.<br />
-                <b>4</b> = Use cache directives or heuristic (0) unless the request has an <code>If-Modified-Since</code> header. <BR />
-            If the request has an<code>If-Modified-Since</code> header, then Traffic Server always revalidates the cached content and uses the client's <code>If-Modified-Since</code> header for the proxy request.</p></td>
+              <p><code>0</code> = Use cache directives or heuristic (the default value).<br />
+                <code>1</code> = Stale if heuristic.<br />
+                <code>2</code> = Always stale (always revalidate).<br />
+                <code>3</code> = Never stale.<br />

[... 1027 lines stripped ...]


Mime
View raw message