xforms

</table>

      <p>The <code class="directive">RewriteBase</code> directive specifies the

      URL prefix to be used for per-directory (htaccess)

      <code class="directive">RewriteRule</code> directives that substitute a relative

      path.</p>

      <code class="directive"><a href="#rewriterule">RewriteRule</a></code> directives that

      substitute a relative path.</p>

      <p> This directive is <em>required</em> when you use a relative path

      in a substitution in per-directory (htaccess) context unless either

      of the following conditions are true:</p>

               (as opposed to reachable by other means, such as

               <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>).</li>

          <li> The <em>filesystem</em> path to the directory containing the

               <code class="directive">RewriteRule</code>, suffixed by the relative 

               <code class="directive"><a href="#rewriterule">RewriteRule</a></code>,

               suffixed by the relative

               substitution is also valid as a URL path on the server

               (this is rare).</li>

          <li> In Apache HTTP Server 2.4.11 and later, this directive may be

            <strong>-l</strong> by using the <strong>-L</strong> or

            <strong>-h</strong> variant.</dd>

            <dt><strong>-ne</strong></dt>

            <dd>Is numerically <strong>n</strong>ot <strong>e</strong>qual to<br />

            The <em>TestString</em> is treated as an integer, and is

            numerically compared to the <em>CondPattern</em>. True if

            the two are numerically different. This is equivalent to

            <code>!-ne</code></dd>

           </dl>

        </li>

            it can impact your server's performance!

           </dd>

            <dt><strong>-H</strong></dt>

            <dt><strong>-h</strong></dt>

            <dd>Is symbolic link, bash convention.<br />

            See <strong>-l</strong>.

            </dd>

      <code>RewriteEngine on</code> directive for each virtual host

      in which you wish to use rewrite rules.</p>

      <p><code class="directive">RewriteMap</code> directives of the type <code>prg</code>

      <p><code class="directive"><a href="#rewritemap">RewriteMap</a></code> directives

      of the type <code>prg</code>

      are not started during server initialization if they're defined in a

      context that does not have <code class="directive">RewriteEngine</code> set to

      <code>on</code></p>

      path relative to that per-directory context. Subsequent patterns

      are matched against the output of the last matching RewriteRule.</p>

<div class="note"><h3><a id="what_is_matched" name="what_is_matched">What is matched?</a></h3>

      <p>In <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> context,

      The <em>Pattern</em> will initially be matched against the part of the

<li> If you wish to match against the full URL-path in a per-directory

(htaccess) RewriteRule, use the <code>%{REQUEST_URI}</code> variable in

a <code class="directive">RewriteCond</code>.</li>

a <code class="directive"><a href="#rewritecond">RewriteCond</a></code>.</li>

<li>The removed prefix always ends with a slash, meaning the matching occurs against a string which

<em>never</em> has a leading slash.  Therefore, a <em>Pattern</em> with <code>^/</code> never

      (<strong>N</strong>=0..9), which will be replaced

      by the contents of the <strong>N</strong>th group of the

      matched <em>Pattern</em>. The server-variables are the same

      as for the <em>TestString</em> of a <code>RewriteCond</code>

      as for the <em>TestString</em> of a

      <code class="directive"><a href="#rewritecond">RewriteCond</a></code>

      directive. The mapping-functions come from the

      <code>RewriteMap</code> directive and are explained there.

      <code class="directive"><a href="#rewritemap">RewriteMap</a></code>

      directive and are explained there.

      These three types of variables are expanded in the order above.</p>

      <p>Rewrite rules are applied to the results of previous rewrite

      <p>Additionally you can set special <a name="rewriteflags" id="rewriteflags">actions</a> to be performed by

      appending <strong><code>[</code><em>flags</em><code>]</code></strong>

      as the third argument to the <code>RewriteRule</code>

      as the third argument to the <code class="directive">RewriteRule</code>

      directive. <em>Flags</em> is a comma-separated list, surround by square

      brackets, of any of the flags in the following table. More

      details, and examples, for each flag, are available in the <a href="../rewrite/flags.html">Rewrite Flags document</a>.</p>

<?xml version="1.0" encoding="UTF-8" ?>

<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">

<?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>

<!-- English Revision: 1734259 -->

<!-- English Revision: 1734259:1737772 (outdated) -->

<!-- French translation : Lucien GENTIS -->

<!-- Reviewed by : Vincent Deffontaines -->

  <variants>

    <variant>en</variant>

    <variant>fr</variant>

    <variant outdated="yes">fr</variant>

  </variants>

</metafile>