Fix the -H|-h flag as spotted by Pete in the online doc.

Add the missing -ne in RewriteCond

Add some missing hyperlinks to the corresponding directives.

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

diff --git a/docs/manual/mod/mod_rewrite.xml b/docs/manual/mod/mod_rewrite.xml
index ea0fca334cfb219c8d670ff7e0d4485a982513f9..9e6a106d21c20ce23d1bfc5e4c17844b37366c43 100644 (file)
--- a/docs/manual/mod/mod_rewrite.xml
+++ b/docs/manual/mod/mod_rewrite.xml
@@ -117,9 +117,10 @@ URLs on the fly</description>
       <code>RewriteEngine on</code> directive for each virtual host
       in which you wish to use rewrite rules.</p>
 
-      <p><directive>RewriteMap</directive> directives of the type <code>prg</code>
+      <p><directive module="mod_rewrite">RewriteMap</directive> directives
+      of the type <code>prg</code>
       are not started during server initialization if they're defined in a
-      context that does not have <directive>RewriteEngine</directive>  set to
+      context that does not have <directive>RewriteEngine</directive> set to
       <code>on</code></p>
 </usage>
 
@@ -842,6 +843,13 @@ AliasMatch "^/myapp" "/opt/myapp-1.2.3"
             <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>
 
@@ -875,7 +883,7 @@ AliasMatch "^/myapp" "/opt/myapp-1.2.3"
             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>
@@ -1093,7 +1101,7 @@ relative substitutions.</li>
 
 <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 <directive>RewriteCond</directive>.</li>
+a <directive module="mod_rewrite">RewriteCond</directive>.</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
@@ -1204,9 +1212,11 @@ cannot use <code>$N</code> in the substitution string!
       (<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
+      <directive module="mod_rewrite">RewriteCond</directive>
       directive. The mapping-functions come from the
-      <code>RewriteMap</code> directive and are explained there.
+      <directive module="mod_rewrite">RewriteMap</directive>
+      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
@@ -1235,7 +1245,7 @@ cannot use <code>$N</code> in the substitution string!
       <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 <directive>RewriteRule</directive>
       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