From: Eric Covener <covener@apache.org>
Date: Sun, 1 Nov 2009 16:24:59 +0000 (+0000)
Subject: address FAQ of SetEnv environment variables not being available to early
X-Git-Tag: 2.3.3~105
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2eb4d470d406e22d207fa057c959acd004d18ece;p=apache

address FAQ of SetEnv environment variables not being available to early
directives such as RewriteRule.


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

diff --git a/docs/manual/mod/mod_env.html.en b/docs/manual/mod/mod_env.html.en
index 0a744a34ec..c365f09085 100644
--- a/docs/manual/mod/mod_env.html.en
+++ b/docs/manual/mod/mod_env.html.en
@@ -88,6 +88,16 @@ SSI pages</td></tr>
       SetEnv SPECIAL_PATH /foo/bin
     </code></p></div>
 
+    <div class="note"><p>The internal environment variables set by this directive are set
+    <em>after</em> most early request processing directives are run, such as access
+    control and URI-to-filename mapping.  If the environment variable you're
+    setting is meant as input into this early phase of processing such as the
+    <code class="directive"><a href="../mod/mod_rerite.html#rewriterule">RewriteRule</a></code> directive, you should 
+    instead set the environment variable with
+    <code class="directive"><a href="../mod/mod_setenvif.html# setenvif"> SetEnvIf</a></code>.</p>
+    </div>
+     
+
 </div>
 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="directive-section"><h2><a name="UnsetEnv" id="UnsetEnv">UnsetEnv</a> <a name="unsetenv" id="unsetenv">Directive</a></h2>
diff --git a/docs/manual/mod/mod_env.xml b/docs/manual/mod/mod_env.xml
index fbbfb24626..e7937674c0 100644
--- a/docs/manual/mod/mod_env.xml
+++ b/docs/manual/mod/mod_env.xml
@@ -72,6 +72,16 @@ SSI pages</description>
     <example><title>Example</title>
       SetEnv SPECIAL_PATH /foo/bin
     </example>
+
+    <note><p>The internal environment variables set by this directive are set
+    <em>after</em> most early request processing directives are run, such as access
+    control and URI-to-filename mapping.  If the environment variable you're
+    setting is meant as input into this early phase of processing such as the
+    <directive module="mod_rerite">RewriteRule</directive> directive, you should 
+    instead set the environment variable with
+    <directive module="mod_setenvif"> SetEnvIf</directive>.</p>
+    </note>
+     
 </usage>
 </directivesynopsis>