trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r788042 [1/3] - /websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/
Date Wed, 06 Apr 2011 13:48:33 GMT
Author: buildbot
Date: Wed Apr  6 13:48:33 2011
New Revision: 788042

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/cache.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/congestion.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/icp.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/logs_xml.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/parent.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/remap.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/splitdns.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/storage.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/update.config.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/cache.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/cache.config.en.html
(original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/cache.config.en.html
Wed Apr  6 13:48:33 2011
@@ -61,39 +61,39 @@ recognizes three space-delimited tags:</
 cannot repeat a secondary specifier.
 The following list shows the possible primary destinations with allowed values.</p>
 <dl>
-<dt><em><code>dest_domain</code></em></dt>
+<dt id="dest_domain"><em><code>dest_domain</code></em></dt>
 <dd>A requested domain name. Traffic Server matches the domain name of the
 destination from the URL in the request.</dd>
-<dt><em><code>dest_host</code></em></dt>
+<dt id="dest_host"><em><code>dest_host</code></em></dt>
 <dd>A requested hostname. Traffic Server matches the hostname of the
 destination from the URL in the request.</dd>
-<dt><em><code>dest_ip</code></em></dt>
+<dt id="dest_ip"><em><code>dest_ip</code></em></dt>
 <dd>A requested IP address. Traffic Server matches the IP address of the
 destination in the request.</dd>
-<dt><em><code>url_regex</code></em></dt>
+<dt id="url_regex"><em><code>url_regex</code></em></dt>
 <dd>A regular expression (regex) to be found in a URL.</dd>
 </dl>
 <p>The secondary specifiers are optional in the cache.config file. The
 following list shows possible secondary specifiers with allowed values.</p>
 <dl>
-<dt><em><code>port</code></em></dt>
+<dt id="port"><em><code>port</code></em></dt>
 <dd>A requested URL port.</dd>
-<dt><em><code>scheme</code></em></dt>
+<dt id="scheme"><em><code>scheme</code></em></dt>
 <dd>A request URL protocol: http or https.</dd>
-<dt><em><code>prefix</code></em></dt>
+<dt id="prefix"><em><code>prefix</code></em></dt>
 <dd>A prefix in the path part of a URL.</dd>
-<dt><em><code>suffix</code></em></dt>
+<dt id="suffix"><em><code>suffix</code></em></dt>
 <dd>A file suffix in the URL.</dd>
-<dt><em><code>method</code></em></dt>
+<dt id="method"><em><code>method</code></em></dt>
 <dd>A request URL method: get, put, post, trace.</dd>
-<dt><em><code>time</code></em></dt>
+<dt id="time"><em><code>time</code></em></dt>
 <dd>A time range, such as 08:00-14:00.</dd>
-<dt><em><code>src_ip</code></em></dt>
+<dt id="src_ip"><em><code>src_ip</code></em></dt>
 <dd>A client IP address.</dd>
 </dl>
 <p>The following list shows possible actions and their allowed values.</p>
 <dl>
-<dt><em><code>action</code></em></dt>
+<dt id="action"><em><code>action</code></em></dt>
 <dd>
 <p>One of the following values:</p>
 <ul>
@@ -106,7 +106,7 @@ following list shows possible secondary 
   <code>Cache-Control: no-cache</code> headers from origin server responses.</li>
 </ul>
 </dd>
-<dt><em><code>pin-in-cache</code></em></dt>
+<dt id="pin-in-cache"><em><code>pin-in-cache</code></em></dt>
 <dd>
 <p>The amount of time you want to keep the object(s) in the cache. The
 following time formats are allowed:</p>
@@ -118,12 +118,12 @@ following time formats are allowed:</p>
 <li>mixed units; for example: 1h15m20s</li>
 </ul>
 </dd>
-<dt><em><code>revalidate</code></em></dt>
+<dt id="revalidate"><em><code>revalidate</code></em></dt>
 <dd>
 <p>The amount of time object(s) are to be considered fresh. Use the same
 time formats as <code>pin-in-cache</code>.</p>
 </dd>
-<dt><em><code>ttl-in-cache</code></em></dt>
+<dt id="ttl-in-cache"><em><code>ttl-in-cache</code></em></dt>
 <dd>
 <p>The amount of time object(s) are to be kept in the cache, regardless of
 Cache-Control response headers. Use the same time formats as

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/congestion.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/congestion.config.en.html
(original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/congestion.config.en.html
Wed Apr  6 13:48:33 2011
@@ -71,13 +71,13 @@ Traffic Server recognizes three space-de
 <p>The following list shows possible primary destinations with allowed
 values.</p>
 <dl>
-<dt><em><code>dest_domain</code></em></dt>
+<dt id="dest_domain"><em><code>dest_domain</code></em></dt>
 <dd>A requested domain name.</dd>
-<dt><em><code>dest_host</code></em></dt>
+<dt id="dest_host"><em><code>dest_host</code></em></dt>
 <dd>A requested hostname.</dd>
-<dt><em><code>dest_ip</code></em></dt>
+<dt id="dest_ip"><em><code>dest_ip</code></em></dt>
 <dd>A requested IP address.</dd>
-<dt><em><code>url_regex</code></em></dt>
+<dt id="url_regex"><em><code>url_regex</code></em></dt>
 <dd>A regular expression (regex) to be found in a URL.</dd>
 </dl>
 <p>The secondary specifiers are optional in the congestion.config file. The
@@ -85,57 +85,57 @@ following list shows possible secondary 
 You can use more than one secondary specifier in a rule; however, you
 cannot repeat a secondary specifier.</p>
 <dl>
-<dt><em><code>port</code></em></dt>
+<dt id="port"><em><code>port</code></em></dt>
 <dd>A requested URL port or range of ports.</dd>
-<dt><em><code>prefix</code></em></dt>
+<dt id="prefix"><em><code>prefix</code></em></dt>
 <dd>A prefix in the path part of a URL.</dd>
 </dl>
 <p>The following list shows the possible tags and their allowed values.</p>
 <dl>
-<dt><em><code>max_connection_failures</code></em></dt>
+<dt id="max_connection_failures"><em><code>max_connection_failures</code></em></dt>
 <dd>Default: <code>5</code></dd>
 <dd>The maximum number of connection failures allowed within the fail
 window described below before Traffic Server marks the origin server as
 congested.</dd>
-<dt><em><code>fail_window</code></em></dt>
+<dt id="fail_window"><em><code>fail_window</code></em></dt>
 <dd>Default: <code>120</code> seconds.</dd>
 <dd>The time period during which the maximum number of connection failures
 can occur before Traffic Server marks the origin server as congested.</dd>
-<dt><em><code>proxy_retry_interval</code></em></dt>
+<dt id="proxy_retry_interval"><em><code>proxy_retry_interval</code></em></dt>
 <dd>Default: <code>10</code> seconds.</dd>
 <dd>The number of seconds that Traffic Server waits before contacting a
 congested origin server again.</dd>
-<dt><em><code>client_wait_interval</code></em></dt>
+<dt id="client_wait_interval"><em><code>client_wait_interval</code></em></dt>
 <dd>Default: <code>300</code> seconds.</dd>
 <dd>The number of seconds that the client is advised to wait before
 retrying the congested origin server.</dd>
-<dt><em><code>wait_interval_alpha</code></em></dt>
+<dt id="wait_interval_alpha"><em><code>wait_interval_alpha</code></em></dt>
 <dd>Default: <code>30</code> seconds</dd>
 <dd>The upper limit for a random number that is added to the wait interval.</dd>
-<dt><em><code>live_os_conn_timeout</code></em></dt>
+<dt id="live_os_conn_timeout"><em><code>live_os_conn_timeout</code></em></dt>
 <dd>Default: <code>60</code> seconds.</dd>
 <dd>The connection timeout to the live (uncongested) origin server.
 If a client stops a request before the timeout occurs, then Traffic
 Server does not record a connection failure.</dd>
-<dt><em><code>live_os_conn_retries</code></em></dt>
+<dt id="live_os_conn_retries"><em><code>live_os_conn_retries</code></em></dt>
 <dd>Default: <code>2</code></dd>
 <dd>The maximum number of retries allowed to the live (uncongested) origin
 server.</dd>
-<dt><em><code>dead_os_conn_timeout</code></em></dt>
+<dt id="dead_os_conn_timeout"><em><code>dead_os_conn_timeout</code></em></dt>
 <dd>Default: <code>15</code> secondsj</dd>
 <dd>The connection timeout to the congested origin server.</dd>
-<dt><em><code>dead_os_conn_retries</code></em></dt>
+<dt id="dead_os_conn_retries"><em><code>dead_os_conn_retries</code></em></dt>
 <dd>Default: <code>1</code></dd>
 <dd>The maximum number of retries allowed to the congested origin server.</dd>
-<dt><em><code>max_connection</code></em></dt>
+<dt id="max_connection"><em><code>max_connection</code></em></dt>
 <dd>Default: <code>-1</code></dd>
 <dd>The maximum number of connections allowed from Traffic Server to the
 origin server.</dd>
-<dt><em><code>error_page</code></em></dt>
+<dt id="error_page"><em><code>error_page</code></em></dt>
 <dd>Default: <code>"congestion#retryAfter"</code></dd>
 <dd>The error page sent to the client when a server is congested. You must
 enclose the value in quotes;</dd>
-<dt><em><code>congestion_scheme</code></em></dt>
+<dt id="congestion_scheme"><em><code>congestion_scheme</code></em></dt>
 <dd>Default: <code>"per_ip"</code></dd>
 <dd>
 <p>Specifies if Traffic Server applies the rule on a per-host (<code>"per_host"</code>)

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/icp.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/icp.config.en.html
(original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/icp.config.en.html
Wed Apr  6 13:48:33 2011
@@ -54,19 +54,19 @@ information for a single ICP peer in the
 
 <p>Each field is described in the following list.</p>
 <dl>
-<dt><code>host</code></dt>
+<dt id="host"><em><code>host</code></em></dt>
 <dd>
 <p>The hostname of the ICP peer.</p>
 <p>This field is optional; if you do not specify the hostname of the ICP
 peer, you must specify the IP address.</p>
 </dd>
-<dt><code>host _IP</code></dt>
+<dt id="host_IP"><em><code>host_IP</code></em></dt>
 <dd>
 <p>The IP address of the ICP peer.</p>
 <p>This field is optional; if you do not specify the IP address of the ICP
 peer, you must specify the hostname.</p>
 </dd>
-<dt><code>ctype</code></dt>
+<dt id="ctype"><em><code>ctype</code></em></dt>
 <dd>
 <p>Use the following options:</p>
 <ul>
@@ -74,12 +74,12 @@ peer, you must specify the hostname.</p>
 <li>2 to indicate an ICP sibling cache</li>
 </ul>
 </dd>
-<dt><code>proxy_port</code></dt>
+<dt id="proxy_port"><em><code>proxy_port</code></em></dt>
 <dd>
 <p>The port number of the TCP port used by the ICP peer for proxy
 communication.</p>
 </dd>
-<dt><code>icp_port</code></dt>
+<dt id="icp_port"><em><code>icp_port</code></em></dt>
 <dd>
 <p>The port number of the UDP port used by the ICP peer for ICP
 communication.</p>

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/logs_xml.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/logs_xml.config.en.html
(original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/logs_xml.config.en.html
Wed Apr  6 13:48:33 2011
@@ -59,11 +59,11 @@ and all comments.</p>
 <h2 id="LogFormat">LogFormat</h2>
 <p>The following list shows <strong><code>LogFormat</code></strong>
specifications.</p>
 <dl>
-<dt><code>&lt;Name = "valid_format_name"/&gt;</code></dt>
+<dt id="LogsXMLFormatName"><em><code><Name = "valid_format_name"/></code></em></dt>
 <dd>Required. Valid format names include any name except <code>squid</code>,
 <code>common</code>, <code>extended</code>, or <code>extended2</code>,
which are pre-defined
 formats. There is no default for this tag.</dd>
-<dt><code>&lt;Format = "valid_format_specification"/&gt;</code></dt>
+<dt id="LogsXMLFormat"><em><code><Format = "valid_format_specification"/></code></em></dt>
 <dd>
 <p>Required. A valid format specification is a printf-style string
  describing each log entry when formatted for ASCII output. Use
@@ -83,7 +83,7 @@ formats. There is no default for this ta
 <strong>Note:</strong> You cannot create a format specification that contains
  both aggregate operators and regular fields.</p>
 </dd>
-<dt><code>&lt;Interval = "aggregate_interval_secs"/&gt;</code></dt>
+<dt id="LogsXMLInterval"><em><code><Interval = "aggregate_interval_secs"/></code></em></dt>
 <dd>
 <p>Use this tag when the format contains aggregate operators. The
  value "<code>aggregate_interval_secs</code>" represents the number of seconds
@@ -101,9 +101,9 @@ formats. There is no default for this ta
 <h2 id="LogFilters">LogFilters</h2>
 <p>The following list shows the <code>LogFilter</code> specifications.</p>
 <dl>
-<dt><code>&lt;Name = "valid_filter_name"/&gt;</code></dt>
+<dt id="LogsXMLFilterName"><em><code><Name = "valid_filter_name"/></code></em></dt>
 <dd>Required. All filters must be uniquely named.</dd>
-<dt><code>&lt;Condition = "valid_log_field valid_operator valid_comparison_value"/&gt;</code></dt>
+<dt id="LogsXMLFilterCondition"><em><code><Condition = "valid_log_field
valid_operator valid_comparison_value"/></code></em></dt>
 <dd>
 <p>Required. This field contains the following elements:</p>
 <p><strong><code>valid_log_field</code></strong> - the field
that will be compared against
@@ -129,7 +129,7 @@ value.</p>
 specify a negative condition, then use the <code>Action</code> field to
 <code>REJECT</code> the record.</p>
 </dd>
-<dt><code>&lt;Action = "valid_action_field"/&gt;</code></dt>
+<dt id="LogsXMLFilterAction"><em><code><Action = "valid_action_field"/></code></em></dt>
 <dd>
 <p>Required: <code>ACCEPT</code> or <code>REJECT</code> .</p>
 </dd>
@@ -141,12 +141,12 @@ that satisfy the filter condition.</p>
 <h2 id="LogObject">LogObject</h2>
 <p>The following list shows the <code>LogObject</code> specifications.</p>
 <dl>
-<dt><code>&lt;Format = "valid_format_name"/&gt;</code></dt>
+<dt id="LogsXMLObjectFormat"><em><code><Format = "valid_format_name"/></code></em></dt>
 <dd>Required. Valid format names include the predefined logging
 formats: <code>squid</code>, <code>common</code>, <code>extended</code>,
and <code>extended2</code>, as well as
 any previously-defined custom log formats. There is no default for
 this tag.</dd>
-<dt><code>&lt;Filename = "file_name"/&gt;</code></dt>
+<dt id="LogsXMLObjectFilename"><em><code><Filename = "file_name"/></code></em></dt>
 <dd>
 <p>Required. The filename to which the given log file is written on
 the local file system or on a remote collation server. No local log
@@ -159,7 +159,7 @@ logs and <code>.blog</code> for binary l
 <p>If you do not want an extension to be added, then end the filename with a
 single (.) dot (for example: <code>squid.</code> ).</p>
 </dd>
-<dt><code>&lt;Mode = "valid_logging_mode"/&gt;</code></dt>
+<dt id="LogsXMLOjbectMode"><em><code><Mode = "valid_logging_mode"/></code></em></dt>
 <dd>
 <p>Valid logging modes include <code>ascii</code> , <code>binary</code>
, and <code>ascii_pipe</code> .
 The default is <code>ascii</code> .</p>
@@ -185,37 +185,37 @@ transaction is processed, so you can see
 Traffic Server starts. Pipes on a collation server, however, <em>are</em>
 created when Traffic Server starts.</p>
 </dd>
-<dt><code>&lt;Filters = "list_of_valid_filter_names"/&gt;</code></dt>
+<dt id="LogsXMLObjectFilters"><em><code><Filters = "list_of_valid_filter_names"/></code></em></dt>
 <dd>
 <p>A comma-separated list of names of any previously-defined log
 filters. If more than one filter is specified, then all filters
 must accept a record for the record to be logged.</p>
 </dd>
-<dt><code>&lt;Protocols = "list_of_valid_protocols"/&gt;</code></dt>
+<dt id="LogsXMLObjectProtocols"><em><code><Protocols = "list_of_valid_protocols"/></code></em></dt>
 <dd>
 <p>A comma-separated list of the protocols this object should log.
 Valid protocol names for this release are <code>HTTP</code> (FTP is
 deprecated).</p>
 </dd>
-<dt><code>&lt;ServerHosts = "list_of_valid_servers"/&gt;</code></dt>
+<dt id="LogsXMLObjectServerHosts"><em><code><ServerHosts = "list_of_valid_servers"/></code></em></dt>
 <dd>
 <p>A comma-separated list of valid hostnames.This tag indicates that
 only entries from the named servers will be included in the file.</p>
 </dd>
-<dt><code>&lt;CollationHosts = "list_of_valid_hostnames"/&gt;</code></dt>
+<dt id="LogsXMLObjectCollationHosts"><em><code><CollationHosts = "list_of_valid_hostnames"/></code></em></dt>
 <dd>
 <p>A comma-separated list of collation servers to which all log
 entries (for this object) are forwarded. Collation servers can be
 specified by name or IP address. Specify the collation port with a
 colon after the name; for example, <code>host:port</code> .</p>
 </dd>
-<dt><code>&lt;Header = "header"/&gt;</code></dt>
+<dt id="LogsXMLObjectHeader"><em><code><Header = "header"/></code></em></dt>
 <dd>
 <p>The header text you want the log files to contain. The header text
 appears at the beginning of the log file, just before the first
 record.</p>
 </dd>
-<dt><code>&lt;RollingEnabled = "truth value"/&gt;</code></dt>
+<dt id="LogsXMLObjectRollingEnabled"><em><code><RollingEnabled = "truth
value"/></code></em></dt>
 <dd>
 <p>Enables or disables log file rolling for the <code>LogObject</code>.
This
 setting overrides the value for the
@@ -236,7 +236,7 @@ files reach a specific size (at a specif
 the specified size).</li>
 </ul>
 </dd>
-<dt><code>&lt;RollingIntervalSec = "seconds"/&gt;</code></dt>
+<dt id="LogsXMLObjectRollingIntervalSec"><em><code><RollingIntervalSec
= "seconds"/></code></em></dt>
 <dd>
 <p>The seconds between log file rolling for the <code>LogObject</code>;
enables
 you to specify different rolling intervals for different
@@ -245,7 +245,7 @@ you to specify different rolling interva
 <em><code>proxy.config.log.rolling_interval_sec</code></em> in the
 <code>records.config</code> file.</p>
 </dd>
-<dt><code>&lt;RollingOffsetHr = "hour"/&gt;</code></dt>
+<dt id="LogsXMLObjectRollingOffsetHr"><em><code><RollingOffsetHr = "hour"/></code></em></dt>
 <dd>
 <p>Specifies an hour (from 0 to 23) at which rolling is guaranteed to
 align. Rolling might start before then, but a rolled file will be
@@ -255,7 +255,7 @@ This setting overrides the configuration
 for <em><code>proxy.config.log.rolling_offset_hr</code></em> in the
 <code>records.config</code> file.</p>
 </dd>
-<dt><code>&lt;RollingSizeMb = "size_in_MB"/&gt;</code></dt>
+<dt id="LogsXMLObjectRollingSizeMb"><em><code><RollingSizeMb = "size_in_MB"/></code></em></dt>
 <dd>
 <p>The size at which log files are rolled.</p>
 </dd>

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/parent.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/parent.config.en.html
(original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/parent.config.en.html
Wed Apr  6 13:48:33 2011
@@ -66,28 +66,28 @@ rule. Traffic Server recognizes three sp
 <p>The following list shows the possible primary destinations and
 their allowed values.</p>
 <dl>
-<dt><em><code>dest_domain</code></em></dt>
+<dt id="dest_domain"><em><code>dest_domain</code></em></dt>
 <dd>A requested domain name.</dd>
-<dt><em><code>dest_host</code></em></dt>
+<dt id="dest_host"><em><code>dest_host</code></em></dt>
 <dd>A requested hostname.</dd>
-<dt><em><code>dest_ip</code></em></dt>
+<dt id="dest_ip"><em><code>dest_ip</code></em></dt>
 <dd>A requested IP address or range of IP addresses separated by a dash (-).</dd>
-<dt><em><code>url_regex</code></em></dt>
+<dt id="url_regex"><em><code>url_regex</code></em></dt>
 <dd>A regular expression (regex) to be found in a URL</dd>
 </dl>
 <p>The secondary specifiers are optional in the <code>parent.config</code>
file.
 The following list shows the possible secondary specifiers and
 their allowed values.</p>
 <dl>
-<dt><em><code>port</code></em></dt>
+<dt id="port"><em><code>port</code></em></dt>
 <dd>A requested URL port.</dd>
-<dt><em><code>scheme</code></em></dt>
+<dt id="scheme"><em><code>scheme</code></em></dt>
 <dd>A request URL protocol: <code>http</code> or <code>https</code>.</dd>
-<dt><em><code>prefix</code></em></dt>
+<dt id="prefix"><em><code>prefix</code></em></dt>
 <dd>A prefix in the path part of a URL.</dd>
-<dt><em><code>suffix</code></em></dt>
+<dt id="suffix"><em><code>suffix</code></em></dt>
 <dd>A file suffix in the URL.</dd>
-<dt><em><code>method</code></em></dt>
+<dt id="method"><em><code>method</code></em></dt>
 <dd>
 <p>A request URL method. It can be one of the following:</p>
 <ul>
@@ -97,12 +97,12 @@ their allowed values.</p>
 <li>trace</li>
 </ul>
 </dd>
-<dt><em><code>time</code></em></dt>
+<dt id="time"><em><code>time</code></em></dt>
 <dd>
 <p>A time range, such as 08:00-14:00, during which the parent cache is
 used to serve requests.</p>
 </dd>
-<dt><em><code>src_ip</code></em></dt>
+<dt id="src_ip"><em><code>src_ip</code></em></dt>
 <dd>
 <p>A client IP address.</p>
 </dd>



Mime
View raw message