On Mon, 21 Jul 2003 [EMAIL PROTECTED] wrote:
> I just wanted to know whether the introduction of <proxy> had been missed
> at this point (as mod_headers is much older).
> But I agree with Joshua that this issue should rather be handled in detail
> in just one document (including your helpful comment about .htaccess), and
> then consistently linked to it from all other sections where it would
> matter.
Using the notes from Bill, I have tried to hit a few places in the docs
that needed to be updated to deal with <proxy> sections. Here's a patch.
Since I neither use nor code with mod_proxy, review would be appreciated.
Index: sections.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/sections.xml,v
retrieving revision 1.6
diff -u -r1.6 sections.xml
--- sections.xml 12 Apr 2003 15:04:43 -0000 1.6
+++ sections.xml 21 Jul 2003 18:57:55 -0000
@@ -400,6 +400,12 @@
the virtual host definition. This allows virtual hosts to
override the main server configuration.</p>
+ <p>When the request is served by <module>mod_proxy</module>, the
+ <directive module="mod_proxy" type="section">Proxy</directive>
+ container takes the place of the <directive module="core"
+ type="section">Directory</directory> container in the processing
+ order.</p>
+
<p>Later sections override earlier ones.</p>
<note><title>Technical Note</title>
Index: mod/directive-dict.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/directive-dict.xml,v
retrieving revision 1.4
diff -u -r1.4 directive-dict.xml
--- mod/directive-dict.xml 12 Apr 2003 15:04:46 -0000 1.4
+++ mod/directive-dict.xml 21 Jul 2003 18:57:55 -0000
@@ -147,12 +147,13 @@
<dd>A directive marked as being valid in this context may be
used inside <directive module="core"
- type="section">Directory</directive>,
- <directive type="section" module="core">Location</directive>,
- and <directive module="core" type="section">Files</directive>
- containers in the server configuration files, subject to the
- restrictions outlined in <a href="../sections.html">How
- Directory, Location and Files sections work</a>.</dd>
+ type="section">Directory</directive>, <directive type="section"
+ module="core">Location</directive>, <directive module="core"
+ type="section">Files</directive>, and <directive
+ module="mod_proxy" type="section">Proxy</directive> containers
+ in the server configuration files, subject to the restrictions
+ outlined in <a href="../sections.html">Configuration
+ Sections</a>.</dd>
<dt>.htaccess</dt>
Index: mod/mod_headers.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_headers.xml,v
retrieving revision 1.6
diff -u -r1.6 mod_headers.xml
--- mod/mod_headers.xml 11 Apr 2003 01:25:52 -0000 1.6
+++ mod/mod_headers.xml 21 Jul 2003 18:57:55 -0000
@@ -20,27 +20,15 @@
<section id="order"><title>Order of Processing</title>
- <p>The directives provided by <module>mod_headers</module> can occur
- almost anywhere within the server configuration. They are valid in the
- main server config and virtual host sections, inside
- <directive module="core" type="section">Directory</directive>,
- <directive module="core" type="section">Location</directive> and
- <directive module="core" type="section">Files</directive> sections,
- and within <code>.htaccess</code> files.</p>
+ <p>The directives provided by <module>mod_headers</module> can
+ occur almost anywhere within the server configuration, and can be
+ limited in scope by enclosing them in <a
+ href="../sections.html">configuration sections</a>.
- <p>The directives are processed in the following order:</p>
-
- <ol>
- <li>main server</li>
- <li>virtual host</li>
- <li><directive type="section">Directory</directive> sections and
- <code>.htaccess</code></li>
- <li><directive type="section">Files</directive></li>
- <li><directive type="section">Location</directive></li>
- </ol>
-
- <p>Order is important. These two headers have a different
- effect if reversed:</p>
+ <p>Order of processing is important and is affected both by the
+ order in the configuration file and by placement in <a
+ href="../sections.html#mergin">configuration sections</a>. These
+ two headers have a different effect if reversed:</p>
<example>
RequestHeader append MirrorID "mirror 12"<br />
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
