cvs commit: apachen/htdocs/manual/mod core.html
dgaudet 98/01/22 15:18:59 Modified:htdocs/manual/misc FAQ.html htdocs/manual/mod core.html Log: Support users with older versions of the server. Revision ChangesPath 1.98 +3 -2 apachen/htdocs/manual/misc/FAQ.html Index: FAQ.html === RCS file: /export/home/cvs/apachen/htdocs/manual/misc/FAQ.html,v retrieving revision 1.97 retrieving revision 1.98 diff -u -r1.97 -r1.98 --- FAQ.html 1998/01/22 23:11:48 1.97 +++ FAQ.html 1998/01/22 23:18:56 1.98 @@ -15,7 +15,7 @@ !--#include virtual=header.html -- H1 ALIGN=CENTERApache Server Frequently Asked Questions/H1 P - $Revision: 1.97 $ ($Date: 1998/01/22 23:11:48 $) + $Revision: 1.98 $ ($Date: 1998/01/22 23:18:56 $) /P P The latest version of this FAQ is always available from the main @@ -1805,7 +1805,8 @@ As a last-resort workaround, you can comment out the CODE#define USE_SHMGET_SCOREBOARD/CODE definition in the SAMPLINUX/SAMP section of - SAMPsrc/conf.h/SAMP and rebuild the server. This will produce + SAMPsrc/conf.h/SAMP and rebuild the server (prior to 1.3b4 the + definition was named CODE#define HAVE_SHMGET/CODE). This will produce a server which is slower and less reliable. /P HR 1.90 +2 -2 apachen/htdocs/manual/mod/core.html Index: core.html === RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v retrieving revision 1.89 retrieving revision 1.90 diff -u -r1.89 -r1.90 --- core.html 1998/01/22 23:11:51 1.89 +++ core.html 1998/01/22 23:18:58 1.90 @@ -1480,12 +1480,12 @@ Linux 1.x users might be able to add code-DUSE_SHMGET_SCOREBOARD/code to the codeEXTRA_CFLAGS/code in your codeConfiguration/code. This might work with some 1.x installations, but won't work with all of -them.p +them. (Prior to 1.3b4 this define was named codeHAVE_SHMGET/code.)p SVR4 users should consider adding code-DUSE_SHMGET_SCOREBOARD/code to the codeEXTRA_CFLAGS/code in your codeConfiguration/code. This is believed to work, but we were unable to test it in time for 1.2 -release.p +release. (Prior to 1.3b4 this define was named codeHAVE_SHMGET/code.)p strongSee Also/strong: a href=../stopping.htmlStopping and Restarting Apache/a/p
cvs commit: apachen/htdocs/manual/mod core.html
marc97/12/22 13:25:11
Modified:htdocs/manual/mod core.html
Log:
Misc cleanups:
- cleanup HTML, e -- em
- remove bogus security warning about LockFile
- add warning about possible denial of service attack with
LockFile in world writable directory
- remove security encouragement to use inetd; add warning that
inetd isn't well supported.
Revision ChangesPath
1.88 +11 -10apachen/htdocs/manual/mod/core.html
Index: core.html
===
RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -r1.87 -r1.88
--- core.html 1997/12/14 01:04:56 1.87
+++ core.html 1997/12/22 21:25:10 1.88
@@ -371,7 +371,7 @@
lt;Directory ~ quot;^/www/.*/[0-9]{3}quot;gt;
/pre
-would match directories in /www/ that consisted of three numbers./p
+would match directories in /www/ that consisted of three numbers.
pIf multiple (non-regular expression) directory sections match the
directory (or its parents) containing
@@ -1029,8 +1029,11 @@
must be stored on a local disk/b. The PID of the main
server process is automatically appended to the filename. p
-The LockFile is subject to the same warnings about log file placement and
-a href=../misc/security_tips.html#serverrootsecurity/a.
+STRONGSECURITY:/STRONG It is best to avoid putting this file in a
+world writable directory such as CODE/var/tmp/CODE because someone
+could create a denial of service attack and prevent the server from
+starting by creating a lockfile with the same name as the one the
+server will try to create.p
PHR
@@ -1369,7 +1372,7 @@
H2A name=rlimitRLimitCPU/A A NAME=rlimitcpudirective/A/H2
!--%plaintext lt;?INDEX {\tt RLimitCPU} directivegt; --
strongSyntax:/strong RLimitCPU em# or 'max'/em em[# or
'max']/embr
-strongDefault:/strong eUnset; uses operating system defaults/ebr
+strongDefault:/strong emUnset; uses operating system defaults/embr
strongContext:/strong server config, virtual hostbr
strongStatus:/strong corebr
strongCompatibility:/strong RLimitCPU is only available in Apache 1.2
and laterp
@@ -1388,7 +1391,7 @@
h2A name=rlimitmemRLimitMEM directive/A/h2
!--%plaintext lt;?INDEX {\tt RLimitMEM} directivegt; --
strongSyntax:/strong RLimitMEM em# or 'max'/em em[# or
'max']/embr
-strongDefault:/strong eUnset; uses operating system defaults/ebr
+strongDefault:/strong emUnset; uses operating system defaults/embr
strongContext:/strong server config, virtual hostbr
strongStatus:/strong corebr
strongCompatibility:/strong RLimitMEM is only available in Apache 1.2
and laterp
@@ -1407,7 +1410,7 @@
h2A name=rlimitnprocRLimitNPROC directive/A/h2
!--%plaintext lt;?INDEX {\tt RLimitNPROC} directivegt; --
strongSyntax:/strong RLimitNPROC em# or 'max'/em em[# or
'max']/embr
-strongDefault:/strong eUnset; uses operating system defaults/ebr
+strongDefault:/strong emUnset; uses operating system defaults/embr
strongContext:/strong server config, virtual hostbr
strongStatus:/strong corebr
strongCompatibility:/strong RLimitNPROC is only available in Apache 1.2
and laterp
@@ -1605,16 +1608,14 @@
connection received, a new copy of the server is started from scratch;
after the connection is complete, this program exits. There is a high price
to
pay per connection, but for security reasons, some admins prefer this option.
+FONT COLOR=redInetd mode is no longer recommended and does not always
+work properly. Avoid it if at all possible./FONT
p
Standalone is the most common setting for ServerType since
it is far more efficient. The server is started once, and services all
subsequent connections. If you intend running Apache to serve a busy site,
standalone will probably be your only option.p
-
-SECURITY: if you are paranoid about security, run in inetd mode. Security
-cannot be guaranteed in either, but whilst most people are happy to use
-standalone, inetd is probably least prone to attack.phr
h2A name=startserversStartServers directive/A/h2
!--%plaintext lt;?INDEX {\tt StartServers} directivegt; --
cvs commit: apachen/htdocs/manual/mod core.html mod_log_config.html
dgaudet 97/12/13 16:57:47
Modified:htdocs/manual/misc security_tips.html
htdocs/manual/mod core.html mod_log_config.html
Log:
More tweaks related to serverroot/logs/etc.
Revision ChangesPath
1.12 +6 -2 apachen/htdocs/manual/misc/security_tips.html
Index: security_tips.html
===
RCS file: /export/home/cvs/apachen/htdocs/manual/misc/security_tips.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- security_tips.html1997/12/14 00:49:19 1.11
+++ security_tips.html1997/12/14 00:57:44 1.12
@@ -62,8 +62,12 @@
pIf you allow non-root users to modify any files that root either
executes or writes on then you open your system to root compromises.
For example, someone could replace the httpd binary so that the next
-time you start it, it will execute some arbitrary code. Or someone
-could overwrite the logs with arbitrary data.
+time you start it, it will execute some arbitrary code. If the logs
+directory is writeable (by a non-root user), someone
+could replace a log file with a symlink to some other system file,
+and then root might overwrite that file with arbitrary data. If the
+log files themselves are writeable (by a non-root user), then someone
+may be able to overwrite the log itself with bogus data.
P
HR
H2Server Side Includes/H2
1.86 +15 -7 apachen/htdocs/manual/mod/core.html
Index: core.html
===
RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v
retrieving revision 1.85
retrieving revision 1.86
diff -u -r1.85 -r1.86
--- core.html 1997/11/15 00:16:48 1.85
+++ core.html 1997/12/14 00:57:45 1.86
@@ -570,7 +570,7 @@
blockquotecodeErrorLog /dev/null/code/blockquote
This effectively turns off error logging.p
-SECURITY: See the A HREF=../misc/security_tips.htmlsecurity tips/A
+SECURITY: See the A HREF=../misc/security_tips.html#serverrootsecurity
tips/A
document for details on why your security could be compromised if
the directory where logfiles are stored is writable by anyone other
than the user that starts the server.
@@ -1025,9 +1025,12 @@
Apache is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be
left at its default value. The main reason for changing it is if
-the codelogs/code directory is NFS mounted, since the lockfile
-should be stored on a local disk if possible. The PID of the main
-server process is automatically appended to the filename.
+the codelogs/code directory is NFS mounted, since bthe lockfile
+must be stored on a local disk/b. The PID of the main
+server process is automatically appended to the filename. p
+
+The LockFile is subject to the same warnings about log file placement and
+a href=../misc/security_tips.html#serverrootsecurity/a.
PHR
@@ -1245,7 +1248,7 @@
signal to the process id listed in the PidFile.p
The PidFile is subject to the same warnings about log file placement and
-a href=../misc/security_tips.htmlsecurity/a.
+a href=../misc/security_tips.html#serverrootsecurity/a.
phr
@@ -1569,8 +1572,13 @@
The ServerRoot directive sets the directory in which the server lives.
Typically it will contain the subdirectories codeconf//code and
codelogs//code. Relative paths for other configuration files are taken
-as relative to this directory.br
-See also a href=../invoking.htmlthe code-d/code option to
httpd/a.phr
+as relative to this directory.p
+
+See also a href=../invoking.htmlthe code-d/code option to
httpd/a.p
+See also a href=../misc/security_tips.html#serverrootthe security
tips/a
+for information on how to properly set permissions on the ServerRoot.p
+
+hr
h2A name=servertypeServerType directive/A/h2
!--%plaintext lt;?INDEX {\tt ServerType} directivegt; --
1.20 +4 -4 apachen/htdocs/manual/mod/mod_log_config.html
Index: mod_log_config.html
===
RCS file: /export/home/cvs/apachen/htdocs/manual/mod/mod_log_config.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- mod_log_config.html 1997/09/12 14:50:47 1.19
+++ mod_log_config.html 1997/12/14 00:57:46 1.20
@@ -173,10 +173,10 @@
h2Security Considerations/h2
-See the A HREF=../misc/security_tips.htmlsecurity tips/A document
-for details on why your security could be compromised if the directory
-where logfiles are stored is writable by anyone other than the user
-that starts the server.
+See the A HREF=../misc/security_tips.html#securitysecurity tips/A
+document for details on why your security could be
cvs commit: apachen/htdocs/manual/mod core.html
dgaudet 97/12/13 17:04:57 Modified:htdocs/manual/mod core.html Log: The port documentation was a little unclear on its overlap with the Listen directive. PR: 975 Revision ChangesPath 1.87 +3 -1 apachen/htdocs/manual/mod/core.html Index: core.html === RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v retrieving revision 1.86 retrieving revision 1.87 diff -u -r1.86 -r1.87 --- core.html 1997/12/14 00:57:45 1.86 +++ core.html 1997/12/14 01:04:56 1.87 @@ -1272,7 +1272,9 @@ li In the absence of any a href=#listenListen/a or a href=#bindaddressBindAddress/a directives specifying a port number, -the Port directive sets the network port on which the server listens. +a Port directive given in the main server +(i.e. outside any a href=#virtualhostlt;VirtualHostgt/a section) +sets the network port on which the server listens. If there are any Listen or BindAddress directives specifying code:number/code then Port has no effect on what address the server listens at.
cvs commit: apachen/htdocs/manual/mod core.html
coar97/11/13 20:02:45 Modified:htdocs/manual/mod core.html Log: Include directive isn't a container.. Revision ChangesPath 1.84 +1 -1 apachen/htdocs/manual/mod/core.html Index: core.html === RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v retrieving revision 1.83 retrieving revision 1.84 diff -u -r1.83 -r1.84 --- core.html 1997/11/11 23:47:17 1.83 +++ core.html 1997/11/14 04:02:44 1.84 @@ -43,7 +43,7 @@ liA HREF=#hostnamelookupsHostNameLookups/A liA HREF=#identitycheckIdentityCheck/A liA HREF=#ifmodulelt;IfModulegt;/A -liA HREF=#includelt;Includegt;/A +liA HREF=#includeInclude/A liA HREF=#keepaliveKeepAlive/A liA HREF=#keepalivetimeoutKeepAliveTimeout/A liA HREF=#limitlt;Limitgt;/A
cvs commit: apachen/htdocs/manual/mod core.html
martin 97/11/11 15:11:12 Modified:htdocs/manual sections.html htdocs/manual/misc known_bugs.html htdocs/manual/mod core.html Log: Minor Documentation Update: broken and mis-typed links, and a reference to a resource which is available only at http://www.apache.org/, not in the user's tree. Reviewed by:Dean Gaudet, Jim Jagielski, Ken Coar Revision ChangesPath 1.2 +1 -1 apachen/htdocs/manual/sections.html Index: sections.html === RCS file: /home/cvs/apachen/htdocs/manual/sections.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -u -r1.1 -r1.2 --- sections.html 1997/08/24 14:16:02 1.1 +++ sections.html 1997/11/11 23:10:45 1.2 @@ -17,7 +17,7 @@ The sections a href=mod/core.html#directorycodelt;Directorygt;/code/a, a href=mod/core.html#locationcodelt;Locationgt;/code/a and a -href=mode/core.html#filescodelt;Filesgt;/code/a can contain +href=mod/core.html#filescodelt;Filesgt;/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 1.34 +1 -1 apachen/htdocs/manual/misc/known_bugs.html Index: known_bugs.html === RCS file: /home/cvs/apachen/htdocs/manual/misc/known_bugs.html,v retrieving revision 1.33 retrieving revision 1.34 diff -u -u -r1.33 -r1.34 --- known_bugs.html 1997/11/08 23:27:59 1.33 +++ known_bugs.html 1997/11/11 23:11:10 1.34 @@ -209,7 +209,7 @@ Negotiation/A should pick the smallest variant if there are several that are equally acceptable. A bug in 1.2 means it no longer does this unless all the variants have character sets. -This A HREF=../../dist/contrib/patches/1.2/conneg-bug.patchpatch/A +This A HREF=http://www.apache.org/dist/contrib/patches/1.2/conneg-bug.patch;patch/A fixes this problem. It also fixes the problem which makes Apache pick the last equally acceptable variant instead of the first. This will be tracked as 1.82 +1 -1 apachen/htdocs/manual/mod/core.html Index: core.html === RCS file: /home/cvs/apachen/htdocs/manual/mod/core.html,v retrieving revision 1.81 retrieving revision 1.82 diff -u -u -r1.81 -r1.82 --- core.html 1997/10/25 22:35:13 1.81 +++ core.html 1997/11/11 23:11:11 1.82 @@ -873,7 +873,7 @@ href=#portPort/a/code directive./p ttListen/tt can be used instead of tta -href=bindaddressBindAddress/a/tt and ttPort/tt. It tells +href=#bindaddressBindAddress/a/tt and ttPort/tt. It tells the server to accept incoming requests on the specified port or address-and-port combination. If the first format is used, with a port number only, the server listens to the given port on all interfaces,
cvs commit: apachen/htdocs/manual/mod core.html
brian 97/08/25 12:26:06 Modified:htdocs/manual/mod core.html Log: Submitted by: Martin Kraemer [EMAIL PROTECTED] Directive had been moved. Revision ChangesPath 1.75 +1 -1 apachen/htdocs/manual/mod/core.html Index: core.html === RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v retrieving revision 1.74 retrieving revision 1.75 diff -u -r1.74 -r1.75 --- core.html 1997/08/24 14:16:04 1.74 +++ core.html 1997/08/25 19:26:03 1.75 @@ -177,7 +177,7 @@ A HREF=mod_autoindex.html#addiconbyencodingAddIconByEncoding/A, A HREF=mod_autoindex.html#addiconbytypeAddIconByType/A, A HREF=mod_autoindex.html#defaulticonDefaultIcon/A, -A HREF=mod_autoindex.html#directoryindexDirectoryIndex/A, +A HREF=mod_dir.html#directoryindexDirectoryIndex/A, A HREF=mod_autoindex.html#fancyindexingFancyIndexing/A, A HREF=mod_autoindex.html#headernameHeaderName/A, A HREF=mod_autoindex.html#indexignoreIndexIgnore/A,
cvs commit: apachen/htdocs/manual/mod core.html directives.html
brian 97/08/25 18:20:38
Modified:htdocs/manual/mod core.html directives.html
Log:
Submitted by: Lars Eilebrecht [EMAIL PROTECTED]
Reviewed by: Brian Behlendorf
Document ContentDigest.
Revision ChangesPath
1.76 +31 -0 apachen/htdocs/manual/mod/core.html
Index: core.html
===
RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -r1.75 -r1.76
--- core.html 1997/08/25 19:26:03 1.75
+++ core.html 1997/08/26 01:20:34 1.76
@@ -29,6 +29,7 @@
liA HREF=#authtypeAuthType/A
liA HREF=#bindaddressBindAddress/A
liA HREF=#clearmodulelistClearModuleList/A
+liA HREF=#contentdigestContentDigest/A
liA HREF=#coredumpdirectoryCoreDumpDirectory/A
liA HREF=#defaulttypeDefaultType/A
liA HREF=#directorylt;Directorygt;/A
@@ -272,6 +273,36 @@
The server comes with a built-in list of active modules. This
directive clears the list. It is assumed that the list will then be
re-populated using the A HREF=#addmoduleAddModule/A directive.phr
+
+h2A name=contentdigestContentDigest directive/A/h2
+!--%plaintext lt;?INDEX {\tt ContentDigest} directivegt; --
+strongSyntax:/strong ContentDigest emon|off/embr
+strongDefault:/strong codeContentDigest off/codebr
+strongContext:/strong anybr
+strongOverride:/strong AuthConfigbr
+strongStatus:/strong experimentalp
+strongCompatibility:/strong ContentDigest is only available in Apache
1.1 and laterp
+
+This directive enables the generation of codeContent-MD5/code headers
+as defined in RFC1864 respectively RFC2068.P
+
+MD5 is an algorithm for computing a message digest (sometimes called
+fingerprint) of arbitrary-length data, with a high degree of confidence
+that any alterations in the data will be reflected in alterations in the
+message digest.P
+
+The codeContent-MD5/code header provides an end-to-end message
+integrity check (MIC) of the entity-body. A proxy or client may check this
+header for detecting accidental modification of the entity-body
+in transit.
+Example header:
+pre Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA==/preP
+
+Note that this can cause performance problems on your server
+since the message digest is computed on every request
+(the values are not cached).
+
+hr
h2A name=coredumpdirectoryCoreDumpDirectory directive/A/h2
!--%plaintext lt;?INDEX {\tt CoreDumpDirectory} directivegt; --
1.31 +1 -0 apachen/htdocs/manual/mod/directives.html
Index: directives.html
===
RCS file: /export/home/cvs/apachen/htdocs/manual/mod/directives.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- directives.html 1997/08/23 03:10:54 1.30
+++ directives.html 1997/08/26 01:20:35 1.31
@@ -69,6 +69,7 @@
liA HREF=mod_proxy.html#cacherootCacheRoot/A
liA HREF=mod_proxy.html#cachesizeCacheSize/A
liA HREF=core.html#clearmodulelistClearModuleList/A
+liA HREF=core.html#contentdigestContentDigest/A
liA HREF=mod_usertrack.html#cookieexpiresCookieExpires/A
liA HREF=mod_cookies.html#cookielogCookieLog/A (mod_cookies)
liA HREF=mod_log_config.html#cookielogCookieLog/A (mod_log_config)
cvs commit: apachen/htdocs/manual/mod core.html
brian 97/08/25 18:51:34 Modified:htdocs/manual/mod core.html Log: Document the type of responses which contain content-md5. Revision ChangesPath 1.77 +5 -1 apachen/htdocs/manual/mod/core.html Index: core.html === RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v retrieving revision 1.76 retrieving revision 1.77 diff -u -r1.76 -r1.77 --- core.html 1997/08/26 01:20:34 1.76 +++ core.html 1997/08/26 01:51:32 1.77 @@ -300,7 +300,11 @@ Note that this can cause performance problems on your server since the message digest is computed on every request -(the values are not cached). +(the values are not cached).P + +codeContent-MD5/code is only sent for documents served by the +core, and not by any module. For example, SSI documents, output from +CGI scripts, and byte range responses do not have this header. hr
cvs commit: apachen/htdocs/manual/mod core.html
pcs 97/08/24 06:17:57 Modified:htdocs/manual/mod core.html Log: Attempt to clarify relationship between VirtualHost and Listen/BindAddress/Port. PR: 1046 Revision ChangesPath 1.73 +53 -6 apachen/htdocs/manual/mod/core.html Index: core.html === RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v retrieving revision 1.72 retrieving revision 1.73 diff -u -r1.72 -r1.73 --- core.html 1997/08/23 03:10:53 1.72 +++ core.html 1997/08/24 13:17:56 1.73 @@ -245,9 +245,15 @@ every IP address, otherwise it will only listen on the IP address specified. p -This option can be used as an alternative method for supporting -A HREF=../virtual-host.htmlvirtual hosts/A instead of using -A HREF=#virtualhostlt;VirtualHostgt;/A sections. +Only one codeBindAddress/code directive can be used. For more +control over which address and ports Apache listens to, use the +codea href=#listenListen/a/code directive instead of +codeBindAddress/code.p + +codeBindAddress/code can be used as an alternative method for +supporting A HREF=../virtual-host.htmlvirtual hosts/A using +multiple independent servers, instead of using codeA +HREF=#virtualhostlt;VirtualHostgt;/A/code sections. pstrongSee Also:/strong a href=../dns-caveats.htmlDNS Issues/abr @@ -783,8 +789,41 @@ pThe Listen directive instructs Apache to listen to more than one IP address or port; by default it responds to requests on all IP -interfaces, but only on the port given by the a href=#portPort/a -directive./p +interfaces, but only on the port given by the codea +href=#portPort/a/code directive./p + +ttListen/tt can be used instead of tta +href=bindaddressBindAddress/a/tt and ttPort/tt. It tells +the server to accept incoming requests on the specified port or +address-and-port combination. If the first format is used, with a port +number only, the server listens to the given port on all interfaces, +instead of the port given by the ttPort/tt directive. If an IP +address is given as well as a port, the server will listen on the +given port and interface. p + +Note that you may still require a ttPort/tt directive so +that URLs that Apache generates that point to your server still +work.p + +Multiple Listen directives may be used +to specify a number of addresses and ports to listen to. The server +will respond to requests from any of the listed addresses and +ports. +p + +For example, to make the server accept connections on both port +80 and port 8000, use: +pre + Listen 80 + Listen 8000 +/pre + +To make the server accept connections on two specified +interfaces and port numbers, use +pre + Listen 192.170.2.1:80 + Listen 192.170.2.5:8000 +/pre pstrongSee Also:/strong a href=../dns-caveats.htmlDNS Issues/abr @@ -1626,6 +1665,12 @@ the directory where logfiles are stored is writable by anyone other than the user that starts the server. +pstrongNOTE/strong: The use of lt;VirtualHostgt; does +strongnot/strong affect what addresses Apache listens on. You may +need to ensure that Apache is listening on the correct addresses using +either a href=#bindaddressBindAddress/a or a +href=#listenListen/a. + pstrongSee also:/strong A HREF=../dns-caveats.htmlWarnings about DNS and Apache/abr strongSee also:/strong @@ -1634,7 +1679,9 @@ strongSee also:/strong a href=../host.htmlNon-IP address-based Virtual Hosts/abr strongSee also:/strong -a href=../vhosts-in-depth.htmlIn-depth description of Virtual Host matching/a +a href=../vhosts-in-depth.htmlIn-depth description of Virtual Host matching/abr +strongSee also:/strong +a href=../bind.htmlSetting which addresses and ports Apache uses/a /p !--#include virtual=footer.html --
cvs commit: apachen/htdocs/manual/mod core.html
pcs 97/08/24 07:16:05 Modified:htdocs/manual/mod core.html Added: htdocs/manual sections.html Log: Add document explaining how Directory, Location and Files sections are merged. Based on Dean's explanation from PR#586. Link to this doc from the directive descriptions in core.html. PR: 586 Revision ChangesPath 1.1 apachen/htdocs/manual/sections.html Index: sections.html === !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2 Final//EN htmlhead titleHow Directory, Location and Files sections work/title /head !-- Background white, links blue (unvisited), navy (visited), red (active) -- BODY BGCOLOR=#FF TEXT=#00 LINK=#FF VLINK=#80 ALINK=#FF !--#include virtual=header.html -- h1 ALIGN=CENTERHow Directory, Location and Files sections work/h1 The sections a href=mod/core.html#directorycodelt;Directorygt;/code/a, a href=mod/core.html#locationcodelt;Locationgt;/code/a and a href=mode/core.html#filescodelt;Filesgt;/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 different sections differ and how they relate to each other when Apache decides which directives apply for a particular directory or request URL. h2Directives allowed in the sections/h2 Everything that is syntactically allowed in codelt;Directorygt;/code is also allowed in codelt;Locationgt;/code (except a sub-codelt;Filesgt;/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 codelt;Locationgt;/code. The same for codelt;Filesgt;/code -- syntactically everything is fine, but semantically some things are different. h2How the sections are merged/h2 The order of merging is: ol li codelt;Directorygt;/code (except regular expressions) and .htaccess done simultaneously (with .htaccess overriding codelt;Directorygt;/code) /li li codelt;DirectoryMatchgt;/code, and codelt;Directorygt;/code with regular expressions /li licodelt;Filesgt;/code and codelt;FilesMatchgt;/code done simultaneously /li licodelt;Locationgt;/code and codelt;LocationMatchgt;/code done simultaneously /li /ol Apart from codelt;Directorygt;/code, each group is processed in the order that they appear in the configuration files. codelt;Directorygt;/code (group 1 above) is processed in the order shortest directory component to longest. If multiple codelt;Directorygt;/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 codeInclude/code directive will be treated as if they where inside the including file at the location of the codeInclude/code directive. p Sections inside codelt;VirtualHostgt;/code sections are applied iafter/i 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 ibefore/i the main server). h2Notes about using sections/h2 The general guidelines are: p ul li If you are attempting to match objects at the filesystem level then you must use codelt;Directorygt;/code and/or codelt;Filesgt;/code. /li li If you are attempting to match objects at the URL level then you must use codelt;Locationgt;/code /li /ul But a notable exception is: ul li proxy control is done via codelt;Directorygt;/code. This is a legacy mistake because the proxy existed prior to codelt;Locationgt;/code. A future version of the config language should probably switch this to codelt;Locationgt;/code. /li /ul Note also that modifying .htaccess parsing during Location doesn't do anything because .htaccess parsing has already occured. p Another note: p ul li There is actually a codelt;Locationgt;/code/codelt;LocationMatchgt;/code sequence performed just before the name translation phase (where codeAliases/code and codeDocumentRoots/code are used to map URLs to filenames). The results of this sequence are completely thrown away after the translation has completed. /li /ul !--#include virtual=footer.html -- /body/html 1.74 +37 -4 apachen/htdocs/manual/mod/core.html Index: core.html
cvs commit: apachen/htdocs/manual/mod core.html directives.html
randy 97/08/22 20:10:56 Modified:htdocs/manual/mod core.html directives.html Log: Document 'Include' Revision ChangesPath 1.72 +11 -0 apachen/htdocs/manual/mod/core.html Index: core.html === RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v retrieving revision 1.71 retrieving revision 1.72 diff -u -r1.71 -r1.72 --- core.html 1997/08/14 01:24:49 1.71 +++ core.html 1997/08/23 03:10:53 1.72 @@ -42,6 +42,7 @@ liA HREF=#hostnamelookupsHostNameLookups/A liA HREF=#identitycheckIdentityCheck/A liA HREF=#ifmodulelt;IfModulegt;/A +liA HREF=#includelt;Includegt;/A liA HREF=#keepaliveKeepAlive/A liA HREF=#keepalivetimeoutKeepAliveTimeout/A liA HREF=#limitlt;Limitgt;/A @@ -721,6 +722,16 @@ plt;IfModulegt; sections are nest-able, which can be used to implement simple multiple-module tests. + +P hr + +h2a name=includeInclude directive/a/h2 +strongSyntax: (Apache 1.2)/strong Include emfilename/embr +strongContext:/strong server configbr +strongStatus:/strong Corebr +strongCompatibility:/strong Include is only available in Apache 1.3 and later. +P +This directive allows inclusion of other configuration files from within the server configuration files. P hr 1.30 +1 -0 apachen/htdocs/manual/mod/directives.html Index: directives.html === RCS file: /export/home/cvs/apachen/htdocs/manual/mod/directives.html,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- directives.html 1997/08/03 20:29:16 1.29 +++ directives.html 1997/08/23 03:10:54 1.30 @@ -101,6 +101,7 @@ liA HREF=mod_imap.html#imapbaseImapBase/A liA HREF=mod_imap.html#imapdefaultImapDefault/A liA HREF=mod_imap.html#imapmenuImapMenu/A +liA HREF=core.html#includeInclude/A liA HREF=mod_autoindex.html#indexignoreIndexIgnore/A liA HREF=mod_autoindex.html#indexoptionsIndexOptions/A liA HREF=core.html#keepaliveKeepAlive/A
cvs commit: apachen/htdocs/manual/mod core.html
coar97/08/13 18:24:51
Modified:htdocs/manual/mod core.html
Log:
Some typos and other cleanup from Martin the doc-walloper.
(.htaccess changes reverted to generic htaccess after some
discussion.)
Submitted by: Martin Kraemer [EMAIL PROTECTED]
Reviewed by: Paul Sutton, Marc Slemko, Ken Coar
Revision ChangesPath
1.71 +12 -12apachen/htdocs/manual/mod/core.html
Index: core.html
===
RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -r1.70 -r1.71
--- core.html 1997/08/06 20:21:16 1.70
+++ core.html 1997/08/14 01:24:49 1.71
@@ -457,7 +457,7 @@
h2A name=errordocumentErrorDocument directive/A/h2
!--%plaintext lt;?INDEX {\tt ErrorDocument} directivegt; --
strongSyntax:/strong ErrorDocument emerror-code document/embr
-strongContext/strong server config, virtual host, directory,
.htaccessbr
+strongContext:/strong server config, virtual host, directory,
.htaccessbr
strongStatus:/strong corebr
strongOverride:/strong FileInfobr
strongCompatibility:/strong The directory and .htaccess contexts
@@ -527,7 +527,7 @@
h2A name=fileslt;Filesgt; directive/A/h2
strongSyntax:/strong lt;Files emfilename/emgt;
... lt;/Filesgt;br
-strongContext:/strong server config, virtual host, htaccessbr
+strongContext:/strong server config, virtual host, .htaccessbr
strongStatus:/strong corebr
strongCompatibility:/strong only available in Apache
1.2 and above.p
@@ -554,7 +554,7 @@
/pre
would match most common Internet graphics formats. In Apache 1.3 and
-later, a href=#filesmatchlt;FilesMatchgt;/a is perferred,
+later, a href=#filesmatchlt;FilesMatchgt;/a is preferred,
however.
pNote that unlike a
@@ -571,7 +571,7 @@
h2A name=filesmatchlt;FilesMatchgt;/A/h2
strongSyntax:/strong lt;FilesMatch emregex/emgt;
... lt;/Filesgt;br
-strongContext:/strong server config, virtual host, htaccessbr
+strongContext:/strong server config, virtual host, .htaccessbr
strongStatus:/strong corebr
strongCompatibility:/strong only available in Apache
1.3 and above.p
@@ -745,7 +745,7 @@
pstrongApache 1.2 and later/strong: Set to On to enable
persistent connections, Off to disable. See also the a
-href=#maxkeepaliverequestsMaxKeepAliveRequests/a directive./p
+href=#maxkeepaliverequestsMaxKeepAliveRequests/a directive./phr
h2a name=keepalivetimeoutKeepAliveTimeout directive/a/h2
strongSyntax:/strong KeepAliveTimeout emseconds/embr
@@ -794,7 +794,7 @@
The maximum length of the queue of pending connections. Generally no
tuning is needed or desired, however on some systems it is desirable
to increase this when under a TCP SYN flood attack. See
-the backlog parameter to the codelisten(2)/code system call.
+the backlog parameter to the codelisten(2)/code system call./phr
h2A name=limitlt;Limitgt; directive/A/h2
!--%plaintext lt;?INDEX {\tt Limit} section directivegt; --
@@ -854,7 +854,7 @@
pwould match URLs that contained the substring /extra/data or
/special/data. However, in Apache 1.3 and above, use of a
-href=#locationmatchlt;LocationMatchgt;/a is perferred./p
+href=#locationmatchlt;LocationMatchgt;/a is preferred./p
pThe codeLocation/code functionality is especially useful when
combined with the codea
@@ -933,7 +933,7 @@
allowed per connection when a href=#keepaliveKeepAlive/a is
on. If it is set to code0/code, unlimited requests will be
allowed. We recommend that this setting be kept to a high value for
-maximum server performance.
+maximum server performance./phr
h2A name=maxrequestsperchildMaxRequestsPerChild directive/A/h2
!--%plaintext lt;?INDEX {\tt MaxRequestsPerChild} directivegt; --
@@ -1215,7 +1215,7 @@
H2A name=rlimitRLimitCPU/A A NAME=rlimitcpudirective/A/H2
!--%plaintext lt;?INDEX {\tt RLimitCPU} directivegt; --
strongSyntax:/strong RLimitCPU em# or 'max'/em em[# or
'max']/embr
-strongDefault:/strong codeUnset uses operating system
defaults/codebr
+strongDefault:/strong eUnset; uses operating system defaults/ebr
strongContext:/strong server config, virtual hostbr
strongStatus:/strong corebr
strongCompatibility:/strong RLimitCPU is only available in Apache 1.2
and laterp
@@ -1234,7 +1234,7 @@
h2A name=rlimitmemRLimitMEM directive/A/h2
!--%plaintext lt;?INDEX {\tt RLimitMEM} directivegt; --
strongSyntax:/strong RLimitMEM em# or 'max'/em em[# or
'max']/embr
-strongDefault:/strong codeUnset uses operating system
defaults/codebr
+strongDefault:/strong eUnset; uses operating system defaults/ebr
strongContext:/strong server config, virtual hostbr
strongStatus:/strong corebr
strongCompatibility:/strong RLimitMEM is only available in Apache 1.2
and laterp
@@ -1253,7 +1253,7 @@
h2A
