You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2026/04/30 20:36:09 UTC
svn commit: r1933623 - httpd/httpd/branches/2.4.x/docs/manual/rewrite
Author: rbowen
Date: Thu Apr 30 20:36:08 2026
New Revision: 1933623
Log:
rewrite guide: merge proxy.xml content into avoid.xml, replace proxy.xml with deprecation stub (BZ 58892, step 5)
Modified:
httpd/httpd/branches/2.4.x/docs/manual/rewrite/avoid.xml
httpd/httpd/branches/2.4.x/docs/manual/rewrite/proxy.xml
Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/avoid.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/rewrite/avoid.xml Thu Apr 30 20:36:04 2026 (r1933622)
+++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/avoid.xml Thu Apr 30 20:36:08 2026 (r1933623)
@@ -189,6 +189,25 @@ other <code>RewriteRule</code>s in effec
<code>ProxyPass</code>, and so may preempt what you're trying to
accomplish.</p>
+<p>One case where <directive module="mod_rewrite">RewriteRule</directive>
+is genuinely useful for proxying is when you want to proxy requests only
+for content that doesn't exist locally — for example, during a migration
+from one server to another:</p>
+
+<highlight language="config">
+RewriteCond "%{REQUEST_FILENAME}" !-f
+RewriteCond "%{REQUEST_FILENAME}" !-d
+RewriteRule "^/(.*)" "http://old.example.com/$1" [P]
+ProxyPassReverse "/" "http://old.example.com/"
+</highlight>
+
+<p>In this example, requests for resources that haven't been migrated
+yet are transparently proxied to the old server. As content is migrated,
+the local files take precedence. Remember to always include a
+<directive module="mod_proxy">ProxyPassReverse</directive> directive to
+ensure that any redirects issued by the backend are correctly passed on
+to the client.</p>
+
</section>
<section id="setenv"><title>Environment Variable Testing</title>
Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/proxy.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/rewrite/proxy.xml Thu Apr 30 20:36:04 2026 (r1933622)
+++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/proxy.xml Thu Apr 30 20:36:08 2026 (r1933623)
@@ -27,78 +27,13 @@
<summary>
-<p>This document supplements the <module>mod_rewrite</module>
-<a href="../mod/mod_rewrite.html">reference documentation</a>. It describes
-how to use the RewriteRule's [P] flag to proxy content to another server.
-A number of recipes are provided that describe common scenarios.</p>
+<note type="warning">This document has been deprecated. Its content has
+been merged into the
+<a href="avoid.html#proxy">When not to use mod_rewrite</a> document,
+since simple proxying is better accomplished using
+<directive module="mod_proxy">ProxyPass</directive>. This page will be
+removed in a future version of this documentation.</note>
</summary>
-<seealso><a href="../mod/mod_rewrite.html">Module documentation</a></seealso>
-<seealso><a href="intro.html">mod_rewrite introduction</a></seealso>
-<seealso><a href="remapping.html">Redirection and remapping</a></seealso>
-<seealso><a href="access.html">Controlling access</a></seealso>
-<seealso><a href="vhosts.html">Virtual hosts</a></seealso>
-<!--<seealso><a href="proxy.html">Proxying</a></seealso>-->
-<seealso><a href="rewritemap.html">Using RewriteMap</a></seealso>
-<seealso><a href="advanced.html">Advanced techniques</a></seealso>
-<seealso><a href="avoid.html">When not to use mod_rewrite</a></seealso>
-
-<section id="dynamic-proxy">
-
- <title>Proxying Content with mod_rewrite</title>
-
- <dl>
- <dt>Description:</dt>
-
- <dd>
- <p>
- <module>mod_rewrite</module> provides the [P] flag, which allows URLs to be passed,
- via <module>mod_proxy</module>, to another server. Two examples are given here. In
- one example, a URL is passed directly to another server, and served
- as though it were a local URL. In the other example, we proxy
- missing content to a back-end server.</p>
- </dd>
-
- <dt>Solution:</dt>
-
- <dd>
- <p>To simply map a URL to another server, we use the [P] flag, as
- follows:</p>
-
-<highlight language="config">
-RewriteEngine on
-RewriteBase "/products/"
-RewriteRule "^widget/(.*)$" "http://product.example.com/widget/$1" [P]
-ProxyPassReverse "/products/widget/" "http://product.example.com/widget/"
-</highlight>
-
- <p>In the second example, we proxy the request only if we can't find
- the resource locally. This can be very useful when you're migrating
- from one server to another, and you're not sure if all the content
- has been migrated yet.</p>
-
-<highlight language="config">
-RewriteCond "%{REQUEST_FILENAME}" !-f
-RewriteCond "%{REQUEST_FILENAME}" !-d
-RewriteRule "^/(.*)" "http://old.example.com/$1" [P]
-ProxyPassReverse "/" "http://old.example.com/"
-</highlight>
- </dd>
-
- <dt>Discussion:</dt>
-
- <dd><p>In each case, we add a <directive
- module="mod_proxy">ProxyPassReverse</directive> directive to ensure
- that any redirects issued by the backend are correctly passed on to
- the client.</p>
-
- <p>Consider using either <directive
- module="mod_proxy">ProxyPass</directive> or <directive
- module="mod_proxy">ProxyPassMatch</directive> whenever possible in
- preference to <module>mod_rewrite</module>.</p>
- </dd>
- </dl>
-
-</section>
</manualpage>