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

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1200953 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index 66862a8cc599d0ba06d2cbeb292bee2eda15049f..0cd4a5b8f31f1e528a51c00f1309559e59ad81f5 100644 (file)
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -1231,6 +1231,8 @@ rewriting headers that are a URL, this rewrites the <code>domain</code>
 string in <code>Set-Cookie</code> headers.</p>
 </usage>
 </directivesynopsis>
+
+
 <directivesynopsis>
 <name>ProxyPassReverseCookiePath</name>
 <description>Adjusts the Path string in Set-Cookie headers from a reverse-
@@ -1241,10 +1243,23 @@ proxied server</description>
 <context>directory</context>
 </contextlist>
 <usage>
-<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>
+<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
+<var>public-path</var>.
+</p><p>
+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>.
+</p>
 </usage>
 </directivesynopsis>