You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by co...@hyperreal.org on 1998/07/03 22:12:35 UTC
cvs commit: apache-1.3/htdocs/manual/mod core.html
coar 98/07/03 13:12:35
Modified: htdocs/manual sections.html
htdocs/manual/mod core.html
Log:
Clarify some sectional concerns.
Submitted by: Lars Eilebrecht <La...@unix-ag.org>, Ken Coar
Revision Changes Path
1.8 +34 -7 apache-1.3/htdocs/manual/sections.html
Index: sections.html
===================================================================
RCS file: /export/home/cvs/apache-1.3/htdocs/manual/sections.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- sections.html 1998/05/20 14:22:33 1.7
+++ sections.html 1998/07/03 20:12:34 1.8
@@ -30,10 +30,10 @@
Everything that is syntactically allowed in
<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 AllowOverride, make no sense in
-<CODE><Location></CODE>. The same for
+section). Semantically however some things, and the most
+notable are <CODE>AllowOverride</CODE> and the two options
+<CODE>FollowSymLinks</CODE> and <CODE>SymLinksIfOwnerMatch</CODE>,
+make no sense in <CODE><Location></CODE>. The same for
<CODE><Files></CODE> -- syntactically everything is fine, but
semantically some things are different.
@@ -118,13 +118,40 @@
</LI>
</UL>
-Note also that modifying .htaccess parsing during Location doesn't do
-anything because .htaccess parsing has already occurred.
+<P>
+Note about .htaccess parsing:
+</P>
+<UL>
+<LI>
+ Modifying .htaccess parsing during Location doesn't do
+ anything because .htaccess parsing has already occurred.
+</UL>
+
+<P>
+<CODE><Location></CODE> and symbolic links:
+</P>
+<UL>
+<LI>
+ It is not possible to use "<CODE>Options FollowSymLinks</CODE>"
+ or "<CODE>Options SymLinksIfOwnerMatch</CODE>" inside a
+ <CODE><Location></CODE>/<CODE><LocationMatch></CODE> section
+ (the options are simply ignored).
+ Using the options in question is only possible inside a
+ <CODE><Directory></CODE> section (or a <CODE>.htaccess</CODE> file).
+</UL>
<P>
+<CODE><Files></CODE> and <CODE>Options</CODE>:
+</P>
+<UL>
+<LI>
+ Apache won't check for it, but using an <CODE>Options</CODE>
+ directive inside a <CODE><Files></CODE> section has no effect.
+</UL>
-Another note:
<P>
+Another note:
+</P>
<UL>
<LI>
1.126 +11 -2 apache-1.3/htdocs/manual/mod/core.html
Index: core.html
===================================================================
RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/core.html,v
retrieving revision 1.125
retrieving revision 1.126
diff -u -r1.125 -r1.126
--- core.html 1998/06/16 03:37:15 1.125
+++ core.html 1998/07/03 20:12:34 1.126
@@ -1321,7 +1321,8 @@
If an access control directive appears outside a <Limit>
directive, then it applies to all access methods. The method names
listed can be one or more of: GET, POST, PUT, DELETE, CONNECT or
-OPTIONS. If GET is used it will also restrict HEAD requests.
+OPTIONS. <STRONG>The method name is case-sensitive.</STRONG>
+If GET is used it will also restrict HEAD requests.
<STRONG>If you wish to limit all methods, do not include any
<Limit> directive at all.</STRONG> <P><HR>
@@ -1889,7 +1890,7 @@
the extra features are enabled, or one or more of the following:
<DL>
<DT>All
-<DD>All options except for MultiViews.
+<DD>All options except for MultiViews. This is the default setting.
<DT>ExecCGI
<DD>
<!--%plaintext <?INDEX {\tt ExecCGI} option> -->
@@ -1898,10 +1899,15 @@
<DD>
<!--%plaintext <?INDEX {\tt FollowSymLinks} option> -->
The server will follow symbolic links in this directory.
+<br>
<STRONG>Note</STRONG>: even though the server follows the symlink it
does <EM>not</EM>
change the pathname used to match against <CODE><Directory></CODE>
sections.
+<br>
+<STRONG>Note</STRONG>: this option gets ignored if set inside a
+<Location> section.
+
<DT>Includes
<DD>
<!--%plaintext <?INDEX {\tt Includes} option> -->
@@ -1927,6 +1933,9 @@
<!--%plaintext <?INDEX {\tt SymLinksIfOwnerMatch} option> -->
The server will only follow symbolic links for which the target
file or directory is owned by the same user id as the link.
+<br>
+<STRONG>Note</STRONG>: this option gets ignored if set inside a
+<Location> section.
</DL>
Normally, if multiple <CODE>Options</CODE> could apply to a directory,