Rewrite guide: deduplicate front-controller/FallbackResource content

remapping.xml had two sections (front-controller and fallback-resource)
that duplicated the advice in avoid.xml. Replace front-controller with
a brief cross-reference to avoid.xml and htaccess.xml; remove the
fallback-resource section entirely (it also referenced pre-2.2.16
Apache, which is no longer relevant).

Update htaccess.xml cross-reference link to point to
avoid.html#fallback-resource (its canonical home).

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1934084 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/rewrite/TODO.md b/docs/manual/rewrite/TODO.md
index 44189527db88c871d6d04444fffe2425291e193e..55c75c55ada94cfc95147896e855b02aab08ccc4 100644 (file)
--- a/docs/manual/rewrite/TODO.md
+++ b/docs/manual/rewrite/TODO.md
@@ -14,7 +14,7 @@ result in one file "owning" the content and others cross-referencing it.
       (htaccess.xml, plus both the [L] and [END] sections of flags.xml).
       → htaccess.xml owns the full explanation; flags.xml slims down + xrefs.
 
-- [ ] **FallbackResource / front-controller** recipe appears in four
+- [x] **FallbackResource / front-controller** recipe appears in four
       places across three files (avoid.xml, remapping.xml ×2, htaccess.xml).
       → avoid.xml owns it; others cross-reference.
 

diff --git a/docs/manual/rewrite/htaccess.xml b/docs/manual/rewrite/htaccess.xml
index bd71c0e0481662cbaf2ab85e28a5795a892e9991..432bebfca9bba0e375c3b253ffb712810c01783c 100644 (file)
--- a/docs/manual/rewrite/htaccess.xml
+++ b/docs/manual/rewrite/htaccess.xml
@@ -162,7 +162,7 @@ RewriteRule "^(.*)$" "index.php" [L]
 
 <note>For this particular use case - routing all unmatched
 requests to a front controller - the
-<a href="remapping.html#fallback-resource">FallbackResource</a> directive
+<a href="avoid.html#fallback-resource">FallbackResource</a> directive
 is a simpler and more efficient alternative to mod_rewrite.</note>
 
 <p>Without the <code>RewriteBase "/myapp/"</code> line, the rewritten

diff --git a/docs/manual/rewrite/remapping.xml b/docs/manual/rewrite/remapping.xml
index 47b6aed9e56f187388af47ce98c890b8e358111f..daced54a5a3ebbac209492290681a11c3e2b49ad 100644 (file)
--- a/docs/manual/rewrite/remapping.xml
+++ b/docs/manual/rewrite/remapping.xml
@@ -247,52 +247,19 @@ RewriteRule "^(.*)" "https://%1$1" [R=301,L]
 
   <title>Front Controller / Application Routing</title>
 
-  <dl>
-    <dt>Description:</dt>
-
-    <dd>
-      <p>Most modern web frameworks (PHP, Python, Ruby, etc.) use a
-      single entry point - often called a "front controller" - that
-      handles all requests. URLs like <code>/products/widget</code>
-      are routed to <code>index.php</code> (or equivalent), which
-      parses the URL internally.</p>
-    </dd>
-
-    <dt>Solution:</dt>
-
-    <dd>
-
-    <note>For this use case, the
-    <directive module="mod_dir">FallbackResource</directive> directive is
-    almost always the better choice. See the
-    <a href="#fallback-resource">Fallback Resource</a> recipe above.</note>
-
-      <p>If you need <module>mod_rewrite</module> (for example, to add
-      additional conditions), the standard pattern is:</p>
-
-<highlight language="config">
-RewriteEngine On
-RewriteCond "%{REQUEST_FILENAME}" !-f
-RewriteCond "%{REQUEST_FILENAME}" !-d
-RewriteRule "^(.*)$" "/index.php" [L]
-</highlight>
-
-      <p>The <code>!-f</code> and <code>!-d</code> conditions skip the
-      rule for requests that map to an existing file or directory, so
-      static assets (images, CSS, JavaScript) are still served
-      directly.</p>
-    </dd>
-
-    <dt>Discussion:</dt>
-
-    <dd>
-      <p>In <code>.htaccess</code> context, consider using
-      <code>[END]</code> instead of <code>[L]</code> to avoid
-      reprocessing loops. See the
-      <a href="htaccess.html#loops">.htaccess looping</a> discussion
-      for details.</p>
-    </dd>
-  </dl>
+  <p>Most modern web frameworks route all requests through a single
+  entry point (a "front controller"). The
+  <directive module="mod_dir">FallbackResource</directive> directive
+  handles this more simply and efficiently than
+  <module>mod_rewrite</module>. See <a
+  href="avoid.html#fallback-resource">When NOT to use mod_rewrite</a>
+  for the recommended approach.</p>
+
+  <p>If you genuinely need <module>mod_rewrite</module> for this (for
+  example, to add conditions beyond "file doesn't exist"), see the
+  <a href="htaccess.html#rewritebase">per-directory rewrites</a>
+  document for an annotated example that also demonstrates
+  <directive module="mod_rewrite">RewriteBase</directive> usage.</p>
 
 </section>
 
@@ -700,65 +667,6 @@ rather than rewriting URLs.</p>
 
 </section>
 
-<section id="fallback-resource">
-<title>Fallback Resource</title>
-
-<dl>
-<dt>Description:</dt>
-<dd>You want a single resource (say, a certain file, like index.php) to
-handle all requests that come to a particular directory, except those
-that should go to an existing resource such as an image, or a css file.</dd>
-
-<dt>Solution:</dt>
-<dd>
-<p>As of version 2.2.16, you should use the <directive
-module="mod_dir">FallbackResource</directive> directive for this:</p>
-
-<highlight language="config">
-&lt;Directory "/var/www/my_blog"&gt;
-  FallbackResource index.php
-&lt;/Directory&gt;
-</highlight>
-
-<p>However, in earlier versions of Apache, or if your needs are more
-complicated than this, you can use a variation of the following rewrite
-set to accomplish the same thing:</p>
-
-<highlight language="config">
-&lt;Directory "/var/www/my_blog"&gt;
-  RewriteBase "/my_blog"
-
-  RewriteCond "/var/www/my_blog/%{REQUEST_FILENAME}" !-f
-  RewriteCond "/var/www/my_blog/%{REQUEST_FILENAME}" !-d
-  RewriteRule "^"                                    "index.php" [PT]
-&lt;/Directory&gt;
-</highlight>
-
-<p>If, on the other hand, you wish to pass the requested URI as a query
-string argument to index.php, you can replace that RewriteRule with:</p>
-
-<highlight language="config">
-RewriteRule "(.*)" "index.php?$1" [PT,QSA]
-</highlight>
-
-<p>Note that these rulesets can be used in a <code>.htaccess</code>
-file, as well as in a &lt;Directory&gt; block.</p>
-
-</dd>
-
-<dt>Discussion:</dt>
-
-<dd>
-<p>The <directive module="mod_dir">FallbackResource</directive> directive
-is almost always the better choice for this use case. See the
-<a href="avoid.html#fallback-resource">When not to use mod_rewrite</a>
-document for a simpler one-line alternative.</p>
-</dd>
-
-</dl>
-
-</section>
-
 <section id="rewrite-query">
 <title>Rewrite query string</title>