diff options
| author | Ken Coar <coar@apache.org> | 1998-01-26 17:54:35 +0100 |
|---|---|---|
| committer | Ken Coar <coar@apache.org> | 1998-01-26 17:54:35 +0100 |
| commit | 07050bb5be522bbf66bb8f053b53beefa295ee68 (patch) | |
| tree | 36dd2244794bae73e5e368d95eb4dcdb53687cb1 /docs/manual/sections.html | |
| parent | PR: (diff) | |
| download | apache2-07050bb5be522bbf66bb8f053b53beefa295ee68.tar.xz apache2-07050bb5be522bbf66bb8f053b53beefa295ee68.zip | |
A truly mighty mod normalising HTML tags to uppercase, and
'i' and 'b' to 'EM' and 'STRONG' respectively. Been threatening
to do this for months.. no-one need try to maintain this when
writing/modifiying the docs.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80021 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/sections.html')
| -rw-r--r-- | docs/manual/sections.html | 122 |
1 files changed, 61 insertions, 61 deletions
diff --git a/docs/manual/sections.html b/docs/manual/sections.html index 6951e7cdbe..b5cce17df2 100644 --- a/docs/manual/sections.html +++ b/docs/manual/sections.html @@ -1,7 +1,7 @@ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> -<html><head> -<title>How Directory, Location and Files sections work</title> -</head> +<HTML><HEAD> +<TITLE>How Directory, Location and Files sections work</TITLE> +</HEAD> <!-- Background white, links blue (unvisited), navy (visited), red (active) --> <BODY @@ -12,12 +12,12 @@ ALINK="#FF0000" > <!--#include virtual="header.html" --> -<h1 ALIGN="CENTER">How Directory, Location and Files sections work</h1> +<h1 ALIGN="CENTER">How Directory, Location and Files sections work</H1> -The sections <a -href="mod/core.html#directory"><code><Directory></code></a>, <a -href="mod/core.html#location"><code><Location></code></a> and <a -href="mod/core.html#files"><code><Files></code></a> can contain +The sections <A +HREF="mod/core.html#directory"><CODE><Directory></CODE></A>, <A +HREF="mod/core.html#location"><CODE><Location></CODE></A> and <A +HREF="mod/core.html#files"><CODE><Files></CODE></A> can contain directives which only apply to specified directories, URLs or files respectively. Also htaccess files can be used inside a directory to apply directives to that directory. This document explains how these @@ -28,112 +28,112 @@ request URL. <h2>Directives allowed in the sections</h2> Everything that is syntactically allowed in -<code><Directory></code> is also allowed in -<code><Location></code> (except a sub-<code><Files></code> +<CODE><Directory></CODE> is also allowed in +<CODE><Location></CODE> (except a sub-<CODE><Files></CODE> section, but the code doesn't test for that, Lars has an open bug report on that). Semantically however some things, and the most notable is AllowOverrides, make no sense in -<code><Location></code>. The same for -<code><Files></code> -- syntactically everything is fine, but +<CODE><Location></CODE>. The same for +<CODE><Files></CODE> -- syntactically everything is fine, but semantically some things are different. <h2>How the sections are merged</h2> The order of merging is: -<ol> +<OL> -<li> +<LI> - <code><Directory></code> (except regular expressions) and + <CODE><Directory></CODE> (except regular expressions) and .htaccess done simultaneously (with .htaccess overriding - <code><Directory></code>) + <CODE><Directory></CODE>) -</li> +</LI> -<li> - <code><DirectoryMatch></code>, and - <code><Directory></code> with regular expressions +<LI> + <CODE><DirectoryMatch></CODE>, and + <CODE><Directory></CODE> with regular expressions -</li> +</LI> - <li><code><Files></code> and <code><FilesMatch></code> done simultaneously - </li> + <LI><CODE><Files></CODE> and <CODE><FilesMatch></CODE> done simultaneously + </LI> - <li><code><Location></code> and <code><LocationMatch></code> done simultaneously - </li> + <LI><CODE><Location></CODE> and <CODE><LocationMatch></CODE> done simultaneously + </LI> -</ol> +</OL> -Apart from <code><Directory></code>, each group is processed in +Apart from <CODE><Directory></CODE>, each group is processed in the order that they appear in the configuration -files. <code><Directory></code> (group 1 above) is processed in +files. <CODE><Directory></CODE> (group 1 above) is processed in the order shortest directory component to longest. If multiple -<code><Directory></code> sections apply to the same directory +<CODE><Directory></CODE> sections apply to the same directory they they are processed in the configuration file order. The configuration files are read in the order httpd.conf, srm.conf and -access.conf. Configurations included via the <code>Include</code> +access.conf. Configurations included via the <CODE>Include</CODE> directive will be treated as if they where inside the including file -at the location of the <code>Include</code> directive. +at the location of the <CODE>Include</CODE> directive. -<p> +<P> -Sections inside <code><VirtualHost></code> sections are applied -<i>after</i> the corresponding sections outside the virtual host +Sections inside <CODE><VirtualHost></CODE> sections are applied +<EM>after</EM> the corresponding sections outside the virtual host definition. This allows virtual hosts to override the main server configuration. (Note: this only works correctly from 1.2.2 and 1.3a2 onwards. Before those releases sections inside virtual hosts were -applied <i>before</i> the main server). +applied <EM>before</EM> the main server). <h2>Notes about using sections</h2> The general guidelines are: -<p> +<P> -<ul> -<li> +<UL> +<LI> If you are attempting to match objects at the filesystem level - then you must use <code><Directory></code> and/or - <code><Files></code>. -</li> + then you must use <CODE><Directory></CODE> and/or + <CODE><Files></CODE>. +</LI> -<li> +<LI> If you are attempting to match objects at the URL level then you - must use <code><Location></code> -</li> -</ul> + must use <CODE><Location></CODE> +</LI> +</UL> But a notable exception is: -<ul> -<li> - proxy control is done via <code><Directory></code>. This is +<UL> +<LI> + proxy control is done via <CODE><Directory></CODE>. This is a legacy mistake because the proxy existed prior to - <code><Location></code>. A future version of the config + <CODE><Location></CODE>. A future version of the config language should probably switch this to - <code><Location></code>. -</li> -</ul> + <CODE><Location></CODE>. +</LI> +</UL> Note also that modifying .htaccess parsing during Location doesn't do anything because .htaccess parsing has already occurred. -<p> +<P> Another note: -<p> +<P> -<ul> -<li> +<UL> +<LI> There is actually a - <code><Location></code>/<code><LocationMatch></code> + <CODE><Location></CODE>/<CODE><LocationMatch></CODE> sequence performed just before the name translation phase (where - <code>Aliases</code> and <code>DocumentRoots</code> are used to + <CODE>Aliases</CODE> and <CODE>DocumentRoots</CODE> are used to map URLs to filenames). The results of this sequence are completely thrown away after the translation has completed. -</li> -</ul> +</LI> +</UL> <!--#include virtual="footer.html" --> -</body></html> +</BODY></HTML> |