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

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-

<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>