svn commit: r849368 - in /websites/staging/trafficserver/trunk: cgi-bin/ content/ content/docs/trunk/admin/plugins/header_filter/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Mon Feb  4 17:13:10 2013
New Revision: 849368

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/plugins/header_filter/index.en.html

Propchange: websites/staging/trafficserver/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb  4 17:13:10 2013
@@ -1 +1 @@
-1442184
+1442186

Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb  4 17:13:10 2013
@@ -1 +1 @@
-1442184
+1442186

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/plugins/header_filter/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/plugins/header_filter/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/plugins/header_filter/index.en.html Mon Feb  4 17:13:10 2013
@@ -137,22 +137,24 @@ useful.</p>
 <h1 id="Examples">Examples</h1>
 <h2 id="x-fwd-proto">Set X-Forwarded-Proto https on SSL connections</h2>
 <p>Often times a backend wants to know whether it's running under HTTP or HTTPS. While not
-regulated standard, we can use the <code>X-Forwarded-Proto</code> header for this purpose:</p>
-<div class="codehilite"><pre># plugin.config
-header_filter.so
-
-:::text
-# remap.config
-map http://example.org http://172.16.17.42:8080
-map https://example.org http://172.16.17.42:8080 @plugin=header_filter.so @pparam=/etc/trafficserver/x_fwd_proto.conf
+regulated standard, we can use the <code>X-Forwarded-Proto</code> header for this purpose.</p>
+<p>In <a href="../../configuration-files/plugin.config"><code>plugin.config</code></a> we need to add:</p>
+<div class="codehilite"><pre>header_filter.so
+</pre></div>
 
-:::text
-/etc/trafficserver/x_fwd_proto.config
-[SEND_REQUEST_HDR]
-    X-Forwarded-Proto =https=
+
+<p>Then, in <a href="../../configuration-files/remap.config"><code>remap.config</code></a> we can configure <code>header_filter</code>
+on a case by case basis:</p>
+<div class="codehilite"><pre>map http://example.org http://172.16.17.42:8080
+map https://example.org http://172.16.17.42:8080 @plugin=header_filter.so @pparam=/etc/trafficserver/x_fwd_proto.conf
 </pre></div>
 
 
+<p>The configuration that ties everything together is then <code>/etc/trafficserver/x_fwd_proto.config</code>, to which we add:
+    :::text
+    [SEND_REQUEST_HDR]
+        X-Forwarded-Proto =https=</p>
+<p>To activate this configuration, we need to restart Traffic Server with <code>traffic_line -L</code>.</p>
 <p>In the backend servers we can now pick this up and do appropriately set server variables
 that will be picked up by CGI programs for instance. In the case of Apache httpd backend,
 this can be acomplished with <a href="http://httpd.apache.org/docs/current/mod/mod_setenvif.html#setenvif"><code>mod\_setenvif</code></a>:</p>