httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1200953 - /httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy.xml
Date Fri, 11 Nov 2011 17:03:36 GMT
Author: rbowen
Date: Fri Nov 11 17:03:36 2011
New Revision: 1200953

Patch from Luke Meyer, clarifies usage of ProxyPassReverseCookiePath directive. As per bug


Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy.xml
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy.xml Fri Nov 11 17:03:36 2011
@@ -1231,6 +1231,8 @@ rewriting headers that are a URL, this r
 string in <code>Set-Cookie</code> headers.</p>
 <description>Adjusts the Path string in Set-Cookie headers from a reverse-
@@ -1241,10 +1243,23 @@ proxied server</description>
-<p>Usage is basically similar to
-<directive module="mod_proxy">ProxyPassReverse</directive>, but instead of
-rewriting headers that are a URL, this rewrites the <code>path</code>
-string in <code>Set-Cookie</code> headers.</p>
+Useful in conjunction with
+<directive module="mod_proxy">ProxyPassReverse</directive>
+in situations where backend URL paths are mapped to public paths on the
+reverse proxy. This directive rewrites the <code>path</code> string in
+<code>Set-Cookie</code> headers. If the beginning of the cookie path matches
+<var>internal-path</var>, the cookie path will be replaced with
+In the example given with 
+<directive module="mod_proxy">ProxyPassReverse</directive>, the directive:
+    <example>
+      ProxyPassReverseCookiePath  /  /mirror/foo/
+    </example>
+will rewrite a cookie with backend path <code>/</code> (or
+<code>/example</code> or, in fact, anything) to <code>/mirror/foo/</code>.

View raw message