Reference the config file syntax in the htaccess tutorial.

PR: 17236

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

diff --git a/docs/manual/howto/htaccess.html.en b/docs/manual/howto/htaccess.html.en
index 6e6734662a6337fbcc5e76c3d9b3337dfd59f3a6..e61b85e7741fb15fbbb3ade1e1365ff48dddcde1 100644 (file)
--- a/docs/manual/howto/htaccess.html.en
+++ b/docs/manual/howto/htaccess.html.en
@@ -60,13 +60,16 @@ changes on a per-directory basis.</p>
       </code></p></div>
     </div>
 
-    <p>What you can put in these files is determined by the <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
-    directive. This directive specifies, in categories, what directives
-    will be honored if they are found in a <code>.htaccess</code> file. If
-    a directive is permitted in a <code>.htaccess</code> file, the
+    <p>In general, <code>.htaccess</code> files use the same syntax as
+    the <a href="../configuring.html#syntax">main configuration
+    files</a>.  What you can put in these files is determined by the
+    <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> directive. This
+    directive specifies, in categories, what directives will be
+    honored if they are found in a <code>.htaccess</code> file. If a
+    directive is permitted in a <code>.htaccess</code> file, the
     documentation for that directive will contain an Override section,
-    specifying what value must be in <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> in order
-    for that directive to be permitted.</p>
+    specifying what value must be in <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> in order for that
+    directive to be permitted.</p>
 
     <p>For example, if you look at the documentation for the <code class="directive"><a href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a></code>
     directive, you will find that it is permitted in <code>.htaccess</code>

diff --git a/docs/manual/howto/htaccess.xml b/docs/manual/howto/htaccess.xml
index ce834e90ceffc081cbd44d6a58bfa6a2aa6a1f61..17665c7fb31aabd480bfe1294eefab07850e3ca8 100755 (executable)
--- a/docs/manual/howto/htaccess.xml
+++ b/docs/manual/howto/htaccess.xml
@@ -76,15 +76,17 @@ changes on a per-directory basis.</p>
       </example>
     </note>
 
-    <p>What you can put in these files is determined by the <directive
-    module="core">AllowOverride</directive>
-    directive. This directive specifies, in categories, what directives
-    will be honored if they are found in a <code>.htaccess</code> file. If
-    a directive is permitted in a <code>.htaccess</code> file, the
+    <p>In general, <code>.htaccess</code> files use the same syntax as
+    the <a href="../configuring.html#syntax">main configuration
+    files</a>.  What you can put in these files is determined by the
+    <directive module="core">AllowOverride</directive> directive. This
+    directive specifies, in categories, what directives will be
+    honored if they are found in a <code>.htaccess</code> file. If a
+    directive is permitted in a <code>.htaccess</code> file, the
     documentation for that directive will contain an Override section,
-    specifying what value must be in <directive 
-    module="core">AllowOverride</directive> in order
-    for that directive to be permitted.</p>
+    specifying what value must be in <directive
+    module="core">AllowOverride</directive> in order for that
+    directive to be permitted.</p>
 
     <p>For example, if you look at the documentation for the <directive
     module="core">AddDefaultCharset</directive>