svn commit: r822424 - in /websites/staging/trafficserver/trunk/content: ./ docs/trunk/admin/configuration-files/records.config.en.html

[bu...@apache.org]

Author: buildbot
Date: Tue Jun 19 22:40:48 2012
New Revision: 822424

Log:
Staging update by buildbot for tserver

Modified:
    websites/staging/trafficserver/trunk/content/   (props changed)
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html

Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jun 19 22:40:48 2012
@@ -1 +1 @@
-1351558
+1351893

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html Tue Jun 19 22:40:48 2012
@@ -310,7 +310,7 @@ the <code>records.config</code> file.</p
 <dd><code>STRING</code></dd>
 <dd>Default: <code>8080</code></dd>
 <dd>
-<p>Ports used for proxying HTTP traffic. This is a list, separated by space or comma, of port descriptors. Each descriptor is a sequence of keywords and values separated by colons. Not all keywords have values, those that do are specifically noted. Keywords with values can have an optional '=' character separating the keyword and value.</p>
+<p>Ports used for proxying HTTP traffic. This is a list, separated by space or comma, of port descriptors. Each descriptor is a sequence of keywords and values separated by colons. Not all keywords have values, those that do are specifically noted. Keywords with values can have an optional '=' character separating the keyword and value. The case of keywords is ignored. The order of keywords is irrelevant unless keywords conflict (e.g. <code>tr-full</code> and <code>ssl</code>) in which case the right most keyword dominates, although in such cases odd behavior may result.</p>
 <p><table><tr><td><strong>Keyword</strong></td><td><strong>Meaning</strong></td></tr>
 <tr><td><em>number</em></td><td>IP port. Required.</td></tr>
 <tr><td>ipv6</td><td>Use IPv6.</td></tr>
@@ -329,9 +329,14 @@ the <code>records.config</code> file.</p
 </tt></p>
 <p>Listen on port 80 on any address for IPv4 and IPv6.</p>
 <p><tt>
+IPv4:8080:tr-FULL TR-full:IP-in=[fc02:10:10:1::1]:8080
+</tt></p>
+<p>Listen transparently on any IPv4 address on port 8080, and transparently on port 8080 on local address <code>fc01:10:10:1::1</code> (which implies <code>ipv6</code>).</p>
+<p><tt>
 8080:ipv6:tr-full 443:ssl 80:ip-in=192.168.17.1:ip-out=[fc01:10:10:1::1]:ip-out=10.10.10.1
 </tt></p>
 <p>Listen on port 8080 any address for IPv6, fully transparent. Set up an SSL port on 443. Listen on IP address 192.168.17.1, port 80, IPv4, and connect to origin servers using the local address 10.10.10.1 for IPv4 and fc01:10:10:1::1 for IPv6.</p>
+<p>Note: All IPv6 addresses must be enclosed in square brackets.</p>
 <p>Note: For SSL you must still configure the certificates, this option handles only the port configuration.</p>
 <p>Note: old style configuration of ports should still work but support for that will be removed at some point in the future.</p>
 </dd>