contain some more information about how this all works.
The directive <code class="directive"><a href="../mod/mod_authn_core.html#<authnprovideralias>"><AuthnProviderAlias></a></code>
can also help in simplifying certain authentication configurations.</p>
-
+
+ <p>The various ciphers supported by Apache for authentication data are
+ explained in <a href="../misc/password_encryptions.html">Password
+ Encryptions</a>.</p>
+
<p>And you may want to look at the <a href="access.html">Access
Control</a> howto, which discusses a number of related topics.</p>
contain some more information about how this all works.
The directive <directive module="mod_authn_core"><AuthnProviderAlias></directive>
can also help in simplifying certain authentication configurations.</p>
-
+
+ <p>The various ciphers supported by Apache for authentication data are
+ explained in <a href="../misc/password_encryptions.html">Password
+ Encryptions</a>.</p>
+
<p>And you may want to look at the <a href="access.html">Access
Control</a> howto, which discusses a number of related topics.</p>
brackets, of any of the following flags: </p>
<dl>
+ <dt>'<code>B</code>' (escape backreferences)</dt>
+ <dd><p>Apache has to unescape URLs before mapping them,
+ so backreferences will be unescaped at the time they are applied.
+ Using the B flag, non-alphanumeric characters in backreferences
+ will be escaped. For example, consider the rule:</p>
+ <pre><code> RewriteRule RewriteRule ^(.*)$ index.php?show=$1 </code></pre>
+ <p>This will map <code>/C++</code> to <code>index.php?show=C++</code>.
+ But it will also map <code>/C%2b%2b</code> to
+ <code>index.php?show=C++</code>, because the <code>%2b</code>
+ has been unescaped. With the B flag, it will instead map to
+ <code>index.php?show=>/C%2b%2b</code>.</p>
+ <p>This escaping is particularly necessary in a proxy situation,
+ when the backend may break if presented with an unescaped URL.</p>
+ </dd>
+
<dt>'<code>chain|C</code>'
(chained with next rule)</dt><dd>
This flag chains the current rule with the next rule
when you let an external redirect happen (where the
``<code>.www</code>'' part should not occur!).</dd>
- <dt>
- '<code>cookie|CO=</code><em>NAME</em>:<em>VAL</em>:<em>domain</em>[:<em>lifetime</em>[:<em>path</em>]]'
+ <dt>'<code>cookie|CO=</code><em>NAME</em>:<em>VAL</em>:<em>domain</em>[:<em>lifetime</em>[:<em>path</em>]]'
(set cookie)</dt><dd>
This sets a cookie in the client's browser. The cookie's name
is specified by <em>NAME</em> and the value is