From 1b1404feb153a71dac03a9ce16e9ad4e58b1665f Mon Sep 17 00:00:00 2001
From: Rich Bowen <rbowen@apache.org>
Date: Tue, 12 Jul 2011 13:09:24 +0000
Subject: [PATCH] Remove mention of <If> Directive, as per bug id 51501

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1145575 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/rewrite/avoid.xml | 29 -----------------------------
 1 file changed, 29 deletions(-)

diff --git a/docs/manual/rewrite/avoid.xml b/docs/manual/rewrite/avoid.xml
index 373caf71a3e..3fe116c438b 100644
--- a/docs/manual/rewrite/avoid.xml
+++ b/docs/manual/rewrite/avoid.xml
@@ -206,34 +206,5 @@ accomplish.</p>
 
 </section>
 
-<section id="setenv"><title>Environment Variable Testing</title>
-
-<p><module>mod_rewrite</module> is frequently used to take a particular
-action based on the presence or absense of a particular environment
-variable or request header. This can be done more efficiently using the
-<directive module="core" type="section">If</directive>.</p>
-
-<p>Consider, for example, the common scenario where
-<directive>RewriteRule</directive> is used to enforce a canonical
-hostname, such as <code>www.example.com</code> instead of
-<code>example.com</code>. This can be done using the <directive
-module="core" type="section">If</directive> direct, as shown here:</p>
-
-<example>
-&lt;If "$req{Host} = 'example.com'"&gt;<br />
-RedirectMatch (.*) http://www.example.com$1
-&lt;/If&gt;
-</example>
-
-<p>This technique can be used to take actions based on any request
-header, response header, or environment variable, replacing
-<module>mod_rewrite</module> in many common scenarios.</p>
-
-<p>See especially the <a href="../expr.html">expression evaluation
-documentation</a> for a overview of what types of expressions you can
-use in &lt;If&gt; sections, and in certain other directives.</p>
-
-</section>
-
 </manualpage> 
 
-- 
2.47.2