Update transformation.

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

diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en
index d62b961b3c558d91cc347407e8946c16292b231d..3e3b7d803f21c57b674b50e7854cc20529dc7d71 100644 (file)
--- a/docs/manual/mod/core.html.en
+++ b/docs/manual/mod/core.html.en
@@ -972,15 +972,15 @@ the contents of file-system directories matching a regular expression.</td></tr>
     </div>
 
     <p>From 2.5.0 onwards, named groups and backreferences are captured and
-    written to the environment with the corresponding name in upper case.
-    This allows elements of paths to be referenced from within
-    <a href="expr.html">expressions</a> and modules like
+    written to the environment with the corresponding name prefixed with
+    "MATCH_" and in upper case. This allows elements of paths to be referenced
+    from within <a href="expr.html">expressions</a> and modules like
     <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>. In order to prevent confusion, numbered
     (unnamed) backreferences are ignored. Use named groups instead.</p>
 
 <pre class="prettyprint lang-config">
-&lt;DirectoryMatch ^/var/www/combined/(?&lt;SITENAME&gt;[^/]+)&gt;
-    require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+&lt;DirectoryMatch ^/var/www/combined/(?&lt;sitename&gt;[^/]+)&gt;
+    require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
 &lt;/DirectoryMatch&gt;
 </pre>
 
@@ -1819,15 +1819,15 @@ filenames</td></tr>
     <p>would match most common Internet graphics formats.</p>
 
     <p>From 2.5.0 onwards, named groups and backreferences are captured and
-    written to the environment with the corresponding name in upper case.
-    This allows elements of files to be referenced from within
-    <a href="expr.html">expressions</a> and modules like
+    written to the environment with the corresponding name prefixed with
+    "MATCH_" and in upper case. This allows elements of files to be referenced
+    from within <a href="expr.html">expressions</a> and modules like
     <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>. In order to prevent confusion, numbered
     (unnamed) backreferences are ignored. Use named groups instead.</p>
 
 <pre class="prettyprint lang-config">
-&lt;FileMatch ^(?&lt;SITENAME&gt;[^/]+)&gt;
-    require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+&lt;FileMatch ^(?&lt;sitename&gt;[^/]+)&gt;
+    require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
 &lt;/FileMatch&gt;
 </pre>
 
@@ -2792,15 +2792,15 @@ matching URLs</td></tr>
     or <code>/special/data</code>.</p>
 
     <p>From 2.5.0 onwards, named groups and backreferences are captured and
-    written to the environment with the corresponding name in upper case.
-    This allows elements of URLs to be referenced from within
-    <a href="expr.html">expressions</a> and modules like
+    written to the environment with the corresponding name prefixed with
+    "MATCH_" and in upper case. This allows elements of URLs to be referenced
+    from within <a href="expr.html">expressions</a> and modules like
     <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>. In order to prevent confusion, numbered
     (unnamed) backreferences are ignored. Use named groups instead.</p>
 
 <pre class="prettyprint lang-config">
-&lt;LocationMatch ^/combined/(?&lt;SITENAME&gt;[^/]+)&gt;
-    require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+&lt;LocationMatch ^/combined/(?&lt;sitename&gt;[^/]+)&gt;
+    require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
 &lt;/LocationMatch&gt;
 </pre>
 

diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en
index d1a2d5a365e9d49002dd6bb532a7fc9210989dab..f04fa0a94303e5e5acec84370b6461b5bb6d10e5 100644 (file)
--- a/docs/manual/mod/mod_proxy.html.en
+++ b/docs/manual/mod/mod_proxy.html.en
@@ -933,15 +933,15 @@ proxied resources</td></tr>
     using <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expressions</a>.</p>
 
     <p>From 2.5.0 onwards, named groups and backreferences are captured and
-    written to the environment with the corresponding name in upper case.
-    This allows elements of URLs to be referenced from within
-    <a href="expr.html">expressions</a> and modules like
+    written to the environment with the corresponding name prefixed with
+    "MATCH_" and in upper case. This allows elements of URLs to be referenced
+    from within <a href="expr.html">expressions</a> and modules like
     <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>. In order to prevent confusion, numbered
     (unnamed) backreferences are ignored. Use named groups instead.</p>
 
 <pre class="prettyprint lang-config">
-&lt;ProxyMatch ^http://(?&lt;SITENAME&gt;[^/]+)&gt;
-    require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+&lt;ProxyMatch ^http://(?&lt;sitename&gt;[^/]+)&gt;
+    require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
 &lt;/ProxyMatch&gt;
 </pre>
 

diff --git a/docs/manual/mod/mod_rewrite.html.en b/docs/manual/mod/mod_rewrite.html.en
index c0d7ef4a0be4e54f0bc54175d3116c79e6394392..edba50cf32b514b2747818ce4b73d356c84019d8 100644 (file)
--- a/docs/manual/mod/mod_rewrite.html.en
+++ b/docs/manual/mod/mod_rewrite.html.en
@@ -593,13 +593,18 @@ Alias /myapp /opt/myapp-1.2.3
             whether or not it exists, and is a regular file with size greater
             than zero.</li>
 
-            <li>'<strong>-U</strong>' (is existing URL, via
+            <li><p>'<strong>-U</strong>' (is existing URL, via
             subrequest)<br />
             Checks whether or not <em>TestString</em> is a valid URL,
             accessible via all the server's currently-configured
             access controls for that path. This uses an internal
             subrequest to do the check, so use it with care -
-            it can impact your server's performance!</li>
+            it can impact your server's performance!</p>
+            <p> This flag <em>only</em> returns information about things
+            like access control, authentication, and authorization.  This flag
+            <em>does not</em> return information about the status code the 
+            configured handler (static file, CGI, proxy, etc.) would have 
+            returned.</p> </li>
 
             <li>'<strong>-x</strong>' (has e<strong>x</strong>ecutable
             permissions)<br />