You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by mi...@apache.org on 2014/01/03 23:30:04 UTC
svn commit: r1555268 - in /httpd/httpd/trunk/docs/manual/mod: core.html.en
mod_proxy.html.en mod_rewrite.html.en
Author: minfrin
Date: Fri Jan 3 22:30:04 2014
New Revision: 1555268
URL: http://svn.apache.org/r1555268
Log:
Update transformation.
Modified:
httpd/httpd/trunk/docs/manual/mod/core.html.en
httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en
httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.en
Modified: httpd/httpd/trunk/docs/manual/mod/core.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/core.html.en?rev=1555268&r1=1555267&r2=1555268&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/core.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/core.html.en Fri Jan 3 22:30:04 2014
@@ -972,15 +972,15 @@ the contents of file-system directories
</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">
-<DirectoryMatch ^/var/www/combined/(?<SITENAME>[^/]+)>
- require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+<DirectoryMatch ^/var/www/combined/(?<sitename>[^/]+)>
+ require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
</DirectoryMatch>
</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">
-<FileMatch ^(?<SITENAME>[^/]+)>
- require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+<FileMatch ^(?<sitename>[^/]+)>
+ require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
</FileMatch>
</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">
-<LocationMatch ^/combined/(?<SITENAME>[^/]+)>
- require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+<LocationMatch ^/combined/(?<sitename>[^/]+)>
+ require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
</LocationMatch>
</pre>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en?rev=1555268&r1=1555267&r2=1555268&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en Fri Jan 3 22:30:04 2014
@@ -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">
-<ProxyMatch ^http://(?<SITENAME>[^/]+)>
- require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+<ProxyMatch ^http://(?<sitename>[^/]+)>
+ require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
</ProxyMatch>
</pre>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.en?rev=1555268&r1=1555267&r2=1555268&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.en Fri Jan 3 22:30:04 2014
@@ -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 />