trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From er...@apache.org
Subject svn commit: r883215 - /incubator/trafficserver/site/trunk/docs/admin/files.htm
Date Mon, 23 Nov 2009 02:28:58 GMT
Author: ericb
Date: Mon Nov 23 02:28:57 2009
New Revision: 883215

URL: http://svn.apache.org/viewvc?rev=883215&view=rev
Log:
removed relative paths in documentation

Modified:
    incubator/trafficserver/site/trunk/docs/admin/files.htm

Modified: incubator/trafficserver/site/trunk/docs/admin/files.htm
URL: http://svn.apache.org/viewvc/incubator/trafficserver/site/trunk/docs/admin/files.htm?rev=883215&r1=883214&r2=883215&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/files.htm (original)
+++ incubator/trafficserver/site/trunk/docs/admin/files.htm Mon Nov 23 02:28:57 2009
@@ -213,7 +213,7 @@
     
 <h2>
         <a name="220539">congestion.config</a>  </h2>
-     <p>The <code>congestion.config</code> file enables you to configure
Traffic Server to stop forwarding HTTP requests to origin servers when they become congested,
and then send the client a message to retry the congested origin server later.  After you
modify the <code>congestion.control</code> file, navigate to the Traffic Server<code>
bin</code> directory; then run the <code>traffic_line -x</code> command
to apply  changes. When you apply the changes to a node in a cluster, Traffic Server automatically
applies the changes to all other nodes in the cluster. Traffic Server uses the <code>congestion.config</code>
file only if you enable the <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/http.htm#UsingCongestionControl"><em>Congestion
Control</em></a> option.</p>
+     <p>The <code>congestion.config</code> file enables you to configure
Traffic Server to stop forwarding HTTP requests to origin servers when they become congested,
and then send the client a message to retry the congested origin server later.  After you
modify the <code>congestion.control</code> file, navigate to the Traffic Server<code>
bin</code> directory; then run the <code>traffic_line -x</code> command
to apply  changes. When you apply the changes to a node in a cluster, Traffic Server automatically
applies the changes to all other nodes in the cluster. Traffic Server uses the <code>congestion.config</code>
file only if you enable the <a href="http.htm#UsingCongestionControl"><em>Congestion
Control</em></a> option.</p>
      <p>You can create rules in the <code>congestion.config</code> file
to specify:  </p>
      <ul>
        <li>Which origin servers Traffic Server tracks for congestion.</li>
@@ -312,7 +312,7 @@
         </tr>
         <tr>
           <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>
+          <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="options.htm#125023"><em>HTTP Responses</em></a>).</p></td>
         </tr>
         <tr>
           <td><p><i><code>congestion_scheme</code></i></p></td>
@@ -438,8 +438,8 @@
      <code>dest_ip=0.0.0.0-255.255.255.255  action=lda</code></p>
   <h2>
 <a name="139053">hosting.config</a>  </h2>
-     <p>The <code>hosting.config</code> file enables you to assign cache
partitions to specific origin servers and/or domains so that you can manage  cache space 
efficiently and restrict disk usage.  For step-by-step instructions on partitioning the cache
according to origin servers and/or domains, refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/cache.htm"><em>Partitioning
the Cache According to Origin Server or Domai</em>n</a>. 
-<br />Before you can assign cache partitions to specific origin servers and/or domains,
you must first partition your cache according to size and protocol in the <code>partition.config</code>
file. For step-by-step instructions about partitioning your cache, refer to <a href="../YTS
 (CPYs)/YTS_AdminG-css_HTML_10.07.09/cache.htm"><em>Partitioning the Cache</em></a>.
For a description of the <code>partition.config</code> file, refer to <a href="#50072"><em>partition.config</em></a>.
 </p>
+     <p>The <code>hosting.config</code> file enables you to assign cache
partitions to specific origin servers and/or domains so that you can manage  cache space 
efficiently and restrict disk usage.  For step-by-step instructions on partitioning the cache
according to origin servers and/or domains, refer to <a href="cache.htm"><em>Partitioning
the Cache According to Origin Server or Domai</em>n</a>. 
+<br />Before you can assign cache partitions to specific origin servers and/or domains,
you must first partition your cache according to size and protocol in the <code>partition.config</code>
file. For step-by-step instructions about partitioning your cache, refer to <a href="cache.htm"><em>Partitioning
the Cache</em></a>. For a description of the <code>partition.config</code>
file, refer to <a href="#50072"><em>partition.config</em></a>.  </p>
      <p>After you modify  <code>hosting.config, </code> navigate to the
Traffic Server<code> bin</code> directory and run the <code>traffic_line
-x</code> command to apply the changes. When you apply the changes to a node in a cluster,
Traffic Server automatically applies the changes to all other nodes in the cluster.  </p>
       <p><strong>IMPORTANT:</strong> The partition configuration must be
the same on all nodes in a cluster.  </p>
      <h3>
@@ -528,7 +528,7 @@
 <h2>
 <a name="149839">logs.config</a></h2>
      <p>The <code>logs.config</code> file establishes and formats <em>traditional</em>
custom transaction log files.   <br />
-     Although Traffic Server supports traditional custom logging, you should use the more
versatile XML-based custom logging. Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/log.htm"><em>Using
the Custom Format</em></a>, and <a href="#131440"><em>logs_xml.config</em></a>.
 If you opt to use traditional custom logging instead of the more versatile XML-based custom
logging, then you must enable the traditional custom logging option manually. Refer to <a
href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/log.htm"><em>Support for Traditional
Custom Logging</em></a>.  </p>
+     Although Traffic Server supports traditional custom logging, you should use the more
versatile XML-based custom logging. Refer to <a href="log.htm"><em>Using the Custom
Format</em></a>, and <a href="#131440"><em>logs_xml.config</em></a>.
 If you opt to use traditional custom logging instead of the more versatile XML-based custom
logging, then you must enable the traditional custom logging option manually. Refer to <a
href="log.htm"><em>Support for Traditional Custom Logging</em></a>. 
</p>
 <p><strong>IMPORTANT: </strong>After you modify  <code>logs.config</code>,
navigate to the Traffic Server<code> bin</code> directory and run the <code>traffic_line
-x</code> command to apply  changes. When you apply the changes to a node in a cluster,
Traffic Server automatically applies the changes to all other nodes in the cluster.  </p>
 
      <h3>
@@ -559,7 +559,7 @@
         </tr>
         <tr>
           <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>
+          <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="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><i><code> file name</code> </i></p></td>
@@ -592,7 +592,7 @@
 
   <h2>
         <a name="109741">log_hosts.config</a>  </h2>
-     <p>To record HTTP transactions for different origin servers in separate log files,
you must list each origin server hostname in the <code>log_hosts.config</code>
file. In addition, you must enable the <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/log.htm">HTTP
Host Log Splitting</a> option.  You should use the same <code>log_hosts.config</code>
file on every Traffic Server node in your cluster. <strong>  </strong> After you
modify the <code>log_hosts.config</code> file, navigate to the Traffic Server<code>
bin</code> directory and run the <code>traffic_line -x</code> command to
apply the changes. When you apply the changes to a node in a cluster, Traffic Server automatically
applies the changes to all other nodes in the cluster. </p>
+     <p>To record HTTP transactions for different origin servers in separate log files,
you must list each origin server hostname in the <code>log_hosts.config</code>
file. In addition, you must enable the <a href="log.htm">HTTP Host Log Splitting</a>
option.  You should use the same <code>log_hosts.config</code> file on every Traffic
Server node in your cluster. <strong>  </strong> After you modify the <code>log_hosts.config</code>
file, navigate to the Traffic Server<code> bin</code> directory and run the <code>traffic_line
-x</code> command to apply the changes. When you apply the changes to a node in a cluster,
Traffic Server automatically applies the changes to all other nodes in the cluster. </p>
 <h3>
   Format </h3>
      <p>Each line in the <code>log_hosts.config</code> file has the following
format:  <code><br />
@@ -634,7 +634,7 @@
         </tr>
         <tr>
           <td><p><code>&lt;Format = &quot;valid_format_specification&quot;/&gt;</code></p></td>
-          <td><p>Required. A valid format specification is a printf-style string
describing each log entry when formatted for ASCII output. Use <code> %&lt; <em>
field</em>  &gt;</code>  as a placeholder for valid  field names. For more
information, refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/logfmts.htm#66912"><em>
Custom Logging Fields</em></a>. </p>
+          <td><p>Required. A valid format specification is a printf-style string
describing each log entry when formatted for ASCII output. Use <code> %&lt; <em>
field</em>  &gt;</code>  as a placeholder for valid  field names. For more
information, refer to <a href="logfmts.htm#66912"><em> Custom Logging Fields</em></a>.
</p>
             <p>The specified field can be one of the following types:
             </p><ul> <li>Simple - for example, <code>%&lt;cqu&gt;<br
/>
             </code></li><li>A field within a container, such as an HTTP
header or a statistic. Fields of this type have the syntax: '<code> %&lt;{ <em>
field</em>  } <em> container</em>  &gt;</code> '.</li><li>
@@ -667,7 +667,7 @@
         <tr>
           <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_log_field</b></code> - the
field that will be compared against the given value. For more information, refer to <a
href="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>.
 
             </p><ul>
 <li><code>MATCH</code> is true if the field and value are identical (case-sensitive).
</li>
@@ -697,7 +697,7 @@
         <tr>
           <td><p><code>&lt;Filename = &quot;file_name&quot;/&gt;</code></p></td>
           <td><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 file will be created
if you fail to specify this tag. All filenames are relative to the default logging directory.</p>
-              <p>If the name does not contain an extension (for example, <code>
squid</code>), then the extension <code> .log</code> is automatically appended
to it for ASCII logs and <code> .blog</code> for binary logs (refer to <a href="../YTS
 (CPYs)/YTS_AdminG-css_HTML_10.07.09/files.htm#0_73225"><em>&lt;Mode = &quot;valid_logging_mode&quot;/&gt;</em></a>).
If you do not want an extension to be added, then end the filename with a single  (.) dot
(for example: <code> squid.</code> ).</p></td>
+              <p>If the name does not contain an extension (for example, <code>
squid</code>), then the extension <code> .log</code> is automatically appended
to it for ASCII logs and <code> .blog</code> for binary logs (refer to <a href="files.htm#0_73225"><em>&lt;Mode
= &quot;valid_logging_mode&quot;/&gt;</em></a>). If you do not want
an extension to be added, then end the filename with a single  (.) dot (for example: <code>
squid.</code> ).</p></td>
         </tr>
         <tr>
           <td><p><code><a name="0_73225"></a>&lt;Mode =
&quot;valid_logging_mode&quot;/&gt;</code></p></td>
@@ -820,7 +820,7 @@
        <li>Set up parent cache hierarchies, with multiple parents and parent failover</li>
        <li>Configure selected URL requests to bypass parent proxies </li>
      </ul>
-     <p>Traffic Server uses the <code>parent.config</code> file only when
the parent caching option is enabled; refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/hier.htm"><em>Configuring
Traffic Server to Use a Parent Cache</em></a>. </p>
+     <p>Traffic Server uses the <code>parent.config</code> file only when
the parent caching option is enabled; refer to <a href="hier.htm"><em>Configuring
Traffic Server to Use a Parent Cache</em></a>. </p>
       <p><strong>IMPORTANT:</strong> After you modify the <code>parent.config</code>
file, navigate to the Traffic Server<code> bin</code> directory and run the <code>traffic_line
-x</code> command to apply the changes. When you apply the changes to a node in a cluster,
Traffic Server automatically applies the changes to all other nodes in the cluster. </p>
 
      <h3>
@@ -924,7 +924,7 @@
      <h2>
         <a name="50072">partition.config</a>  </h2>
      <p>The <code>partition.config</code> file lets you manage your cache
space more efficiently and restrict disk usage by creating cache partitions of different sizes
for specific protocols. You can further configure these partitions to store data from certain
origin servers and/or domains in the <code>hosting.config</code> file (refer to
<a href="#139053"><em>hosting.config</em></a>).     </p>
-     <p><strong>IMPORTANT: </strong> The partition configuration must be
the same on all nodes in a cluster.  You must stop Traffic Server before you change the cache
partition size and protocol assignment. For step-by-step instructions about partitioning the
cache, refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/cache.htm"><em>Partitioning
the Cache</em></a>. </p>
+     <p><strong>IMPORTANT: </strong> The partition configuration must be
the same on all nodes in a cluster.  You must stop Traffic Server before you change the cache
partition size and protocol assignment. For step-by-step instructions about partitioning the
cache, refer to <a href="cache.htm"><em>Partitioning the Cache</em></a>.
</p>
 <h3>
    <a name="115449">Format</a>  </h3>
      <p>For each partition you want to create, enter a line with the following format:
 <br />
@@ -1043,7 +1043,7 @@
               <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>
+              <p>Refer to <a href="log.htm#UnderstandingTrafficEdgeLogFiles">Understanding
Traffic Server Log Files</a>.</p></td>
         </tr>
         <tr>
           <td><p><code><i>proxy.config.cop.core_signal</i></code></p>
@@ -1298,7 +1298,7 @@
               <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>
+              <p>Refer to <a href="hier.htm">Hierarchical Caching</a>.</p></td>
         </tr>
         <tr>
           <td><p><code><i>proxy.config.http.parent_proxy.retry_time
</i></code></p>
@@ -1461,7 +1461,7 @@
           <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"><i>Using
Congestion Control</i></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="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>
@@ -1567,7 +1567,7 @@
               <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>
-              <p><b>Important:</b> If you enable this option, then you
must also specify a filtering rule in the<a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/files.htm#234878"><code>
filter.config</code></a><code> </code>file to allow only certain machines
to push content into the cache.</p></td>
+              <p><b>Important:</b> If you enable this option, then you
must also specify a filtering rule in the<a href="files.htm#234878"><code> filter.config</code></a><code>
</code>file to allow only certain machines to push content into the cache.</p></td>
         </tr>
         <tr>
           <td rowspan=="1" colspan="3"><p><strong> Cache Control</strong></p></td>
@@ -1836,7 +1836,7 @@
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>Enables (1) or disables (0) DNS server selection.<br />

-            When enabled, Traffic Server refers to the <code> splitdns.config</code>
file for the selection specification. Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/secure.htm#ConfiguringDNSServerSelectionSplit"><em>Configuring
DNS Server Selection (Split DNS)</em></a>.</p></td>
+            When enabled, Traffic Server refers to the <code> splitdns.config</code>
file for the selection specification. Refer to <a href="secure.htm#ConfiguringDNSServerSelectionSplit"><em>Configuring
DNS Server Selection (Split DNS)</em></a>.</p></td>
         </tr>
         <tr>
           <td><p><code><i>proxy.config.dns.splitdns.def_domain </i></code></p>
@@ -1926,7 +1926,7 @@
             1 = log errors only<br />
             2 = log transactions only<br />
             3 = full logging (errors + transactions)</p>
-            <p>Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/log.htm">Working
with Log Files</a>.</p></td>
+            <p>Refer to <a href="log.htm">Working with Log Files</a>.</p></td>
         </tr>
         <tr>
           <td><p><code><i>proxy.config.log2.max_secs_per_buffer</i></code></p>
@@ -2103,7 +2103,7 @@
           <td><p><code><i>proxy.config.log2.separate_host_logs </i></code></p>
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
-          <td><p>When enabled (1), configures Traffic Server to create a separate
log file for HTTP transactions for each origin server listed in the <code> log_hosts.config</code>
file (refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/log.htm#HTTPHostLogSplitting">HTTP
Host Log Splitting</a>).</p></td>
+          <td><p>When enabled (1), configures Traffic Server to create a separate
log file for HTTP transactions for each origin server listed in the <code> log_hosts.config</code>
file (refer to <a href="log.htm#HTTPHostLogSplitting">HTTP Host Log Splitting</a>).</p></td>
         </tr>
         <tr>
           <td><p><code><i>proxy.local.log2.collation_mode</i></code></p>
@@ -2115,7 +2115,7 @@
             2 = This host is a collation client and sends entries using standard formats
to the collation server.<br />
             3 = This host is a collation client and sends entries using the traditional custom
formats to the collation server.<br />
             4 = This host is a collation client and sends entries that use both the standard
and traditional custom formats to the collation server.</p>
-            <p>For information on sending XML-based custom formats to the collation
server, refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/files.htm#131440"><em>logs_xml.config</em></a>.</p>
+            <p>For information on sending XML-based custom formats to the collation
server, refer to <a href="files.htm#131440"><em>logs_xml.config</em></a>.</p>
             <p><b>Note:</b> Although Traffic Server supports traditional
custom logging,  you should use the more versatile XML-based custom formats.</p></td>
         </tr>
         <tr>
@@ -2158,7 +2158,7 @@
             <p>2 to enable log file rolling when log files reach a specific size (specified
with the <i><code>proxy.config.log2.rolling_size_mb</code></i> variable).</p>
             <p>3 to enable log file rolling at specific intervals during the day or
when log files reach a specific size (whichever occurs first).</p>
             <p>4 to enable log file rolling at specific intervals during the day when
log files reach a specific size (at a specified time if the file is of the specified size).</p>
-            <p>Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/log.htm#RollingEventLogFiles"></a>.</p></td>
+            <p>Refer to <a href="log.htm#RollingEventLogFiles"></a>.</p></td>
         </tr>
         <tr>
           <td><p><code><i>proxy.config.log2.rolling_interval_sec</i></code></p>
@@ -2269,7 +2269,7 @@
               <p><code>INT</code></p></td>
           <td><p><code>0</code></p></td>
           <td><p>Enables (1) or disables (0) the SSL termination option.</p>
-              <p>Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/secure.htm#UsingSSLTermination"><em>Using
SSL Termination</em></a>.</p></td>
+              <p>Refer to <a href="secure.htm#UsingSSLTermination"><em>Using
SSL Termination</em></a>.</p></td>
         </tr>
         <tr>
           <td><p><code><i>proxy.config.ssl.SSLv2</i></code></p>
@@ -2413,7 +2413,7 @@
           <td><p><code>0</code></p></td>
           <td><p>Sets ICP mode for hierarchical caching:</p>
               <p>0 = disables ICP.<br />1 = allows Traffic Server to receive
ICP queries only.<br />2 = allows Traffic Server to send and receive ICP queries.</p>
-            <p>Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/hier.htm#ICPPeering"><em>ICP
Peering</em></a>.</p></td>
+            <p>Refer to <a href="hier.htm#ICPPeering"><em>ICP Peering</em></a>.</p></td>
         </tr>
         <tr>
           <td><p><code><i>proxy.config.icp.icp_interface </i></code></p>
@@ -2553,7 +2553,7 @@
        <li>Redirect HTTP requests permanently or temporarily without Traffic Server
having to contact any origin servers
 </li>
   </ul>
-     <p>Refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/reverse.htm"><em>Reverse
Proxy and HTTP Redirects</em></a>, for information about redirecting HTTP requests
and using reverse proxy.  </p>
+     <p>Refer to <a href="reverse.htm"><em>Reverse Proxy and HTTP Redirects</em></a>,
for information about redirecting HTTP requests and using reverse proxy.  </p>
       <p><strong>IMPORTANT: </strong>After you modify the <code>remap.config</code>
file, navigate to the Traffic Server<code> bin</code> directory; then run the
<code>traffic_line -x</code> command to apply the changes. When you apply the
changes to a node in a cluster, Traffic Server automatically applies the changes to all other
nodes in the cluster.  </p>
      <h3>
         <a name="133269">Format</a>  </h3>
@@ -2700,7 +2700,7 @@
   <code>redirect_temporary http://www.company1.com http://www.company2.com  </code></p>
 <h2>
  <a name="132448">splitdns.config</a></h2>
-     <p>The <code>splitdns.config</code> file enables you to specify the
DNS server that Traffic Server should use for resolving hosts under specific conditions. 
For more information, refer to <a href="../YTS  (CPYs)/YTS_AdminG-css_HTML_10.07.09/secure.htm"><em>Configuring
DNS Server Selection (Split DNS)</em></a>. </p>
+     <p>The <code>splitdns.config</code> file enables you to specify the
DNS server that Traffic Server should use for resolving hosts under specific conditions. 
For more information, refer to <a href="secure.htm"><em>Configuring DNS Server
Selection (Split DNS)</em></a>. </p>
   <p>To specify a DNS server, you must supply the following information in each active
line within the file: </p>
      <ul>
        <li>A primary destination specifier in the form of a destination domain, a destination
host, or a URL regular expression</li>



Mime
View raw message