trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r798328 - /websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/bridge.en.html
Date Wed, 09 Nov 2011 00:01:36 GMT
Author: buildbot
Date: Wed Nov  9 00:01:36 2011
New Revision: 798328

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/bridge.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/bridge.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/bridge.en.html
(original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/bridge.en.html
Wed Nov  9 00:01:36 2011
@@ -87,7 +87,7 @@ one for a gateway of 192.168.1.1.</p>
 <p>At this point it is a good idea to test connectivity to verify the basic bridge

 is functional.</p>
 <p>Once the bridge is verified to work, this is the basic traffic pattern of interest.
</p>
-<p><img alt="" src="/images/admin/ats-traffic-bridge.png" /></p>
+<p><img alt="Picture of traffic flow through a bridge with ATS" src="/images/admin/ats-traffic-bridge.png"
/></p>
 <p>The green arrows are packets originating from the client and the red arrows 
 are packets originating from the origin server. All traffic not directed to 
 the local address will pass through the bridge. We need to break into some 
@@ -100,7 +100,7 @@ arrived on a (forwarding enabled) interf
 intercept all port 80 traffic it will only affect the two flows described above. 
 <code>-j redirect</code> marks the packet as being diverted to the bridge and
not forwarded, 
 and the <code>DROP</code> target puts the packets in the normal <code>iptables</code>
routing so 
-that we can use standard device tests on them[^1]. Although this example 
+that we can use standard device tests on them<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup>.
Although this example 
 handles only port 80, other ports are the same except for the port value. Note 
 also the port here is the port from the point of view of the clients and origin 
 servers, not the Traffic Server server port.</p>
@@ -191,11 +191,22 @@ set it with</p>
 
 
 <hr />
-<p>[^1]: The <code>--redirect-target</code> can be omitted, but then the
<code>iptables</code> rules would 
-need to use <code>--physdev</code> instead of just <code>-i</code>.
The actual packet processing 
+<p>need to use <code>--physdev</code> instead of just <code>-i</code>.
The actual packet processing 
 is identical.</p>
 <!-- Abbr. -->
 *[ATS]: Apache Traffic Server
+
+
+
+<div class="footnote">
+<hr />
+<ol>
+<li id="fn:1">
+<p>The <code>--redirect-target</code> can be omitted, but then the <code>iptables</code>
rules would 
+&#160;<a href="#fnref:1" rev="footnote" title="Jump back to footnote 1 in the text">&#8617;</a></p>
+</li>
+</ol>
+</div>
         </div>
       </div>
       <div class="fourcol last">



Mime
View raw message