Use Require instead of Allow and Deny.

While at it, removes the "based on the value of" because, it is not really based on the value of the environment variable, but on its existence or not.

PR 65048

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

diff --git a/docs/manual/env.xml b/docs/manual/env.xml
index db8c204c7c95410198b3f42123b13cf6919c09b9..812f4b3eb4e867464dd08add248c195372e1e283 100644 (file)
--- a/docs/manual/env.xml
+++ b/docs/manual/env.xml
@@ -182,6 +182,7 @@
       <directivelist>
         <directive module="mod_authz_core">Require</directive>
         <directive module="mod_log_config">CustomLog</directive>
+        <directive module="mod_access_compat">Allow</directive>
         <directive module="mod_access_compat">Deny</directive>
         <directive module="mod_ext_filter">ExtFilterDefine</directive>
         <directive module="mod_headers">Header</directive>
@@ -219,9 +220,9 @@
     <section id="access-control">
         <title>Access Control</title>
 
-        <p>Access to the server can be controlled based on the value of
-        environment variables using the <code>allow from env=</code>
-        and <code>deny from env=</code> directives. In combination with
+        <p>Access to the server can be controlled based on
+        environment variables using the <code>Require env</code>
+        and <code>Require not env</code> directives. In combination with
         <directive module="mod_setenvif">SetEnvIf</directive>, this
         allows for flexible control of access to the server based on
         characteristics of the client. For example, you can use these