<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?>
-<!-- $Revision: 1.29 $ -->
+<!-- $Revision: 1.30 $ -->
<!--
Copyright 2002-2004 The Apache Software Foundation
This means that if the proxied content contains absolute URL
references, they will by-pass the proxy. A third-party module
that will look inside the HTML and rewrite URL references is Nick
- Kew's <a href="http://www.webthing.com/software/mod_proxy_html/"
+ Kew's <a href="http://apache.webthing.com/software/mod_proxy_html/"
>mod_proxy_html</a>.</p>
<p><var>path</var> is the name of a local virtual path. <var>url</var> is a
<example>
ProxyPass /mirror/foo/ http://backend.example.com/<br />
ProxyPassReverse /mirror/foo/ http://backend.example.com/
+ ProxyPassReverseCookieDomain backend.example.com public.example.com
+ ProxyPassReverseCookiePath / /mirror/foo/
</example>
<p>will not only cause a local request for the
</usage>
</directivesynopsis>
+<directivesynopsis>
+<name>ProxyPassReverseCookieDomain</name>
+<description>Adjusts the Domain string in Set-Cookie headers from a reverse-
+proxied server</description>
+<syntax>ProxyPassReverseCookieDomain <var>internal-domain</var> <var>public-domain</var></syntax>
+<contextlist><context>server config</context><context>virtual host</context>
+<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>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-
+proxied server</description>
+<syntax>ProxyPassReverseCookiePath <var>internal-path</var> <var>public-path</var></syntax>
+<contextlist><context>server config</context><context>virtual host</context>
+<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>
+</usage>
+</directivesynopsis>
+
+
<directivesynopsis>
<name>AllowCONNECT</name>
<description>Ports that are allowed to <code>CONNECT</code> through the
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.en.xsl"?>
-<!-- $Revision: 1.12 $ -->
+<!-- $Revision: 1.13 $ -->
<!--
Copyright 2002-2004 The Apache Software Foundation
<directive module="core">Options</directive>
<directive module="mod_proxy">ProxyPass</directive>
<directive module="mod_proxy">ProxyPassReverse</directive>
+<directive module="mod_proxy">ProxyPassReverseCookieDomain</directive>
+<directive module="mod_proxy">ProxyPassReverseCookiePath</directive>
<directive module="mod_alias">Redirect</directive>
<directive module="mod_alias">RedirectMatch</directive>
<directive module="mod_rewrite">RewriteCond</directive>
<example>
ProxyPass /foo/ http://internal.example.com/bar/<br />
ProxyPassReverse /foo/ http://internal.example.com/bar/
+ProxyPassReverseCookieDomain internal.example.com public.example.com
+ProxyPassReverseCookiePath /foo/ /bar/
</example>
<p>The <directive module="mod_proxy">ProxyPass</directive> configures
<directive module="mod_proxy">ProxyPassReverse</directive>
directive rewrites redirects originating at
<code>internal.example.com</code> so that they target the appropriate
-directory on the local server. It is important to note, however, that
+directory on the local server. Similarly, the
+<directive module="mod_proxy">ProxyPassReverseCookieDomain</directive>
+and <directive module="mod_proxy">ProxyPassReverseCookieDomain</directive>
+rewrite cookies set by the backend server.</p>
+<p>It is important to note, however, that
links inside the documents will not be rewritten. So any absolute
links on <code>internal.example.com</code> will result in the client
breaking out of the proxy server and requesting directly from
-<code>internal.example.com</code>.</p>
+<code>internal.example.com</code>. A third-party module
+<a href="http://apache.webthing.com/mod_proxy_html/">mod_proxy_html</a>
+is available to rewrite links in HTML and XHTML.</p>
</section>
<section id="rewrite"><title>Rewriting Engine</title>