Author: buildbot
Date: Thu Apr 18 09:36:00 2013
New Revision: 858926
Log:
Staging update by buildbot for trafficserver
Modified:
websites/staging/trafficserver/trunk/cgi-bin/ (props changed)
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/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Apr 18 09:36:00 2013
@@ -1 +1 @@
-1469069
+1469246
Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Apr 18 09:36:00 2013
@@ -1 +1 @@
-1469069
+1469246
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
Thu Apr 18 09:36:00 2013
@@ -400,7 +400,7 @@ IPv4:8080:tr-FULL TR-full:IP-in=[fc02:10
CONFIG proxy.config.http.server_other_ports STRING 6060:X 9090:X
would listen to ports <code>6060</code>, <code>9090</code>, and the port
specified by <em><code>proxy.config.http.server_port</code></em>.</p>
</dd>
-<dt
id="proxy.config.http.ssl_ports"><em><code>proxy.config.http.ssl_ports</code></em></dt>
+<dt
id="proxy.config.http.connect_ports"><em><code>proxy.config.http.connect_ports</code></em></dt>
<dd>
<p><code>STRING</code></p>
</dd>
@@ -408,10 +408,7 @@ would listen to ports <code>6060</code>,
<p>Default: <code>443 563</code></p>
</dd>
<dd>
-<p>DEPRECATED: 3.2</p>
-</dd>
-<dd>
-<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, a tunnel must be established to an origin server via Traffic
Server.</p>
+<p>The range of ports that can be used for tunneling. Traffic Server allows
tunnels only to the specified ports. Supports both wildcards ('*') and ranges
("0-1023").</p>
</dd>
<dt
id="proxy.config.http.insert_request_via_str"><em><code>proxy.config.http.insert_request_via_str</code></em></dt>
<dd>
@@ -430,7 +427,7 @@ would listen to ports <code>6060</code>,
<li><code>1</code> = all extra information is added.</li>
<li><code>2</code> = some extra information is added.</li>
</ul>
-<p>Note: the Via: header string interpretation can be <a
href="/tools/via">docoded here.</a></p>
+<p>Note: the Via: header string interpretation can be <a
href="/tools/via">decoded here.</a></p>
</dd>
<dt
id="proxy.config.http.insert_response_via_str"><em><code>proxy.config.http.insert_response_via_str</code></em></dt>
<dd>
