Binding

From d51898fae4cfd481836d7cfa3c27403669b35aef Mon Sep 17 00:00:00 2001 From: Erik Abele Date: Thu, 5 Sep 2002 23:18:19 +0000 Subject: [PATCH] Updated XML plus transformations. This was the last one. Puhh. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96656 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/bind.html.en | 66 +++---- docs/manual/bind.html.ja.jis | 76 ++++---- docs/manual/configuring.html.en | 42 ++-- docs/manual/configuring.html.ja.jis | 54 +++--- docs/manual/content-negotiation.html.en | 148 ++++++++------- docs/manual/content-negotiation.html.ja.jis | 168 ++++++++-------- docs/manual/dso.html.en | 54 +++--- docs/manual/env.html.en | 108 +++++------ docs/manual/filter.html.ja.jis | 34 ++-- docs/manual/handler.html.en | 48 ++--- docs/manual/install.html.en | 128 +++++++------ docs/manual/invoking.html.en | 26 +-- docs/manual/invoking.html.ja.jis | 42 ++-- docs/manual/logs.html.en | 200 ++++++++++---------- docs/manual/logs.xml | 4 +- docs/manual/mpm.html.en | 30 +-- docs/manual/mpm.html.ja.jis | 44 +++-- docs/manual/new_features_2_0.html.de | 132 ++++++------- docs/manual/new_features_2_0.html.en | 18 +- docs/manual/server-wide.html.en | 36 ++-- docs/manual/stopping.html.en | 50 ++--- docs/manual/suexec.html.en | 172 ++++++++--------- docs/manual/suexec.xml | 92 ++++----- docs/manual/upgrading.html.de | 133 ++++++------- docs/manual/upgrading.html.en | 45 +++-- docs/manual/upgrading.xml | 13 +- docs/manual/upgrading.xml.de | 13 +- docs/manual/urlmapping.html.en | 100 +++++----- 28 files changed, 1064 insertions(+), 1012 deletions(-) diff --git a/docs/manual/bind.html.en b/docs/manual/bind.html.en index ee5ff531ac..0369f2eee5 100644 --- a/docs/manual/bind.html.en +++ b/docs/manual/bind.html.en @@ -1,13 +1,15 @@ -Binding - Apache HTTP Server

Apache HTTP Server Version 2.0
Binding
+ -->Binding - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Binding

Configuring Apache to listen on specific addresses and ports.
-
Overview
Special IPv6 Considerations
How This Works With Virtual Hosts
See also
Virtual Hosts
DNS Issues
Overview
+
Overview
Special IPv6 Considerations
How This Works With Virtual Hosts
See also
Virtual Hosts
DNS Issues
Overview
-
Related Modules

core
mpm_common
Related Directives

VirtualHost
Listen
+
Related Modules Related Directives
core
mpm_common
VirtualHost
Listen

When Apache starts, it binds to some port and address on @@ -18,11 +20,11 @@ Virtual Host feature which determines how Apache responds to different IP addresses, hostnames and ports.
-
The Listen +
The Listen directive tells the server to accept incoming requests only on the specified port or address-and-port combinations. If only a port number is - specified in the Listen + specified in the Listen directive, the server listens to the given port on all interfaces. If an IP address is given as well as a port, the server will listen on the given @@ -34,83 +36,83 @@
For example, to make the server accept connections on both port 80 and port 8000, use:
-
- Listen 80 + + Listen 80 Listen 8000 -
+

To make the server accept connections on two specified interfaces and port numbers, use
-
- Listen 192.170.2.1:80 + + Listen 192.170.2.1:80 Listen 192.170.2.5:8000 -
+

IPv6 addresses must be surrounded in square brackets, as in the following example:
-
+ Listen [fe80::a00:20ff:fea7:ccea]:80 -
-
Special IPv6 Considerations
+
+
Special IPv6 Considerations

When APR supports IPv6, Apache will create IPv6-capable listening sockets by default (i.e., when no IP address is specified on the Listen directive). In other words, when APR supports IPv6,
-
+ Listen 80 -
+

is equivalent to
-
+ Listen [::]:80 -
+

When APR does not support IPv6,
-
+ Listen 80 -
+

is equivalent to
-
+ Listen 0.0.0.0:80 -
+

On some platforms, such as NetBSD, binding to the IPv6 wildcard address ("::") does not allow Apache to accept connections on IPv4 interfaces. In this situation, multiple Listen directives are required, as shown below:
-
- Listen 0.0.0.0:80 + + Listen 0.0.0.0:80 Listen [::]:0 -
+

Apache does not currently detect this, so the Listen statements must be edited manually by the administrator.
-
How This Works With Virtual Hosts
+
How This Works With Virtual Hosts

Listen does not implement Virtual Hosts. It only tells the main server what addresses and ports to listen to. If no - <VirtualHost> + <VirtualHost> directives are used, the server will behave the same for all accepted requests. However, - <VirtualHost> + <VirtualHost> can be used to specify a different behavior for one or more of the addresses and ports. To implement a VirtualHost, the server must first be told to listen to the address and port to be used. Then a - <VirtualHost> section + <VirtualHost> section should be created for a specified address and port to set the behavior of this virtual host. Note that if the - <VirtualHost> + <VirtualHost> is set for an address and port that the server is not listening to, it cannot be accessed.
-

Related Modules	Related Directives
`core` `mpm_common`	`VirtualHost` `Listen`

Apache HTTP Server Version 2.0

\ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/bind.html.ja.jis b/docs/manual/bind.html.ja.jis index 8eacb3fae2..0f570d8bbe 100644 --- a/docs/manual/bind.html.ja.jis +++ b/docs/manual/bind.html.ja.jis @@ -1,27 +1,29 @@ -$B%P%$%s%I(B - Apache HTTP Server

Apache HTTP Server Version 2.0
$B%P%$%s%I(B
-
Apache $B$,;HMQ$9$k(B$B%"%I%l%9$H%]!<%H$N@_Dj$r$7$^$9!#(B
-
$B35MW(B
IPv6 $B$NFC5-;v9`(B
$B%P!<%A%c%k%[%9%H$KBP$7$F$I$&F/$/$N$+(B
$B;2>H(B
$B%P!<%A%c%k%[%9(B$B%H(B
DNS $B$NLdBj(B
$B35MW(B
+ -->$B%P%$%s%I(B - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
$B%P%$%s%I(B
+
Apache $B$,;HMQ$9$k%"%I%l%9$H%]!<%H$N@_Dj$r$7$^$9!#(B
+
$B35MW(B
IPv6 $B$NFC5-;v9`(B
$B%P!<%A%c%k%[%9%H$KBP$7$F$I$&F/$/$N$+(B
$B;2>H(B
$B%P!<%A%c%k%[%9%H(B
DNS $B$NLdBj(B
$B35MW(B
-
$B4XO"%b%8%e!<%k(B

core
mpm_common
$B4XO"%G%#%l%/%F%#%V(B

VirtualHost
Listen
+
$B4XO"%b%8%e!<%k(B $B4XO"%G%#%l%/%F%#%V(B
core
mpm_common
VirtualHost
Listen

Apache $B$O5/F0;~$K!"%m!<%+%k%^%7%s$N$"$k%]!<%H$"$h$S%"%I%l%9(B - $B$KBP$7$F@\B3$7(B$B!"%j%/%(%9%H$,Mh$k$N$rBT$A$^$9!#(B + $B$KBP$7$F@\B3$7!"%j%/%(%9%H$,Mh$k$N$rBT$A$^$9!#(B $B%G%U%)%k%H$G$O%^%7%s$N$9$Y$F$N%"%I%l%9$KBP$7$F(B listen $B$7$^$9!#(B $B$7$+$7$J$,$i!"FCDj$N%]!<%H$+!"FCDj$N%"%I%l%9$N$_$+!"(B - $B$^$?$O$=$l$i$NAH$_9g$o$;$N$$$:$l$+$r(B listen $B$9$k$h$&$K$9$kI,MW$,(B$B$"$j$^$9!#(B + $B$^$?$O$=$l$i$NAH$_9g$o$;$N$$$:$l$+$r(B listen $B$9$k$h$&$K$9$kI,MW$,$"$j$^$9!#(B $B$3$l$O!"0[$J$k(B IP $B%"%I%l%9!"%[%9%HL>!"%]!<%H$KBP$9$k(B Apache $B$N1~EzJ}K!$r7hDj$9$k%P!<%A%c%k%[%9%H5!G=$HAH$_9g$o$;$F;H$o$l$^$9!#(B
-
Listen - $B%G%#%l%/%F%#%V$G!"FCDj$N%]!<%H$d%"%I%l%9!&%]!<%H$NAH$+$i(B$B$N$_F~$C$F$/$k(B +
Listen + $B%G%#%l%/%F%#%V$G!"FCDj$N%]!<%H$d%"%I%l%9!&%]!<%H$NAH$+$i$N$_F~$C$F$/$k(B $B%j%/%(%9%H$rListen + $B$b$7%]!<%HHV9f$N$_$,(B Listen $B%G%#%l%/%F%#%V$G;XDj$5$l$?>l9g$O!"(B $B$9$Y$F$N%$%s%?!<%U%'!<%9$NM?$($i$l$?%]!<%HHV9f$r(B listen $B$7$^$9!#(B IP $B%"%I%l%9$,%]!<%HHV9f$HF1;~$KM?$($i$l$?>l9g$O!"(B @@ -33,27 +35,27 @@
$B$?$H$($P!"%]!<%H(B 80 $B$H(B 8000 $B$NN>J}$KBP$7$F$N@\B3$r -
- Listen 80 + + Listen 80 Listen 8000 -
+

$B$H$7$^$9!#(B $BFs$D$N;XDj$5$l$?%$%s%?%U%'!<%9$H%]!<%HHV9f$KBP$7$F$N@\B3$r -
- Listen 192.170.2.1:80 + + Listen 192.170.2.1:80 Listen 192.170.2.5:8000 -
+

$B$H$7$^$9!#(B IPv6 $B%"%I%l%9$O!"3Q3g8L$G -
+ Listen [fe80::a00:20ff:fea7:ccea]:80 -
-
IPv6 $B$NFC5-;v9`(B
+
+
IPv6 $B$NFC5-;v9`(B

APR $B$,(B IPv6 $B$r%5%]!<%H$9$k>l9g$O!"(BApache $B$O%G%U%)%k%H$G(B IPv6 @@ -61,53 +63,53 @@ IP $B%"%I%l%9$,L5;XDj$N>l9g(B)$B!#(B $B$D$^$j!"(BAPR $B$,(B IPv6 $B$r%5%]!<%H$7$F$$$k>l9g!"(B
-
+ Listen 80 -
+

$B$O!" -
+ Listen [::]:80 -
+

APR $B$,(B IPv6 $B$r%5%]!<%H$7$F$$$J$$>l9g$O!"(B
-
+ Listen 80 -
+

$B$O!" -
+ Listen 0.0.0.0:80 -
+

NetBSD $BEy$N$$$/$D$+$N%W%i%C%H%[!<%`$G$O!"(BIPv6 - $B$N%o%$%k%I%+!<(B$B%I%"%I%l%9(B ($B!V(B::$B!W(B) $B$N%P%$%s%I$G$O(B IPv4 + $B$N%o%$%k%I%+!<%I%"%I%l%9(B ($B!V(B::$B!W(B) $B$N%P%$%s%I$G$O(B IPv4 $B%$%s%?!<%U%'!<%9$K%3%M%/%7%g%s$rD%$l$^$;$s!#(B $B$3$N$h$&$J>u67$G$O!" -
- Listen 0.0.0.0:80 + + Listen 0.0.0.0:80 Listen [::]:0 -
+

Apache $B$O8=:_$3$l$r<+F08!=P$9$k$3$H$,$G$-$J$$$N$G!"(B $B$=$N$h$&$J>l9g$O(B Listen $BL?NaJ8$O4IM} -
$B%P!<%A%c%k%[%9%H$KBP$7$F$I$&F/$/$N$+(B
+
$B%P!<%A%c%k%[%9%H$KBP$7$F$I$&F/$/$N$+(B

Listen $B$G%P!<%A%c%k%[%9%H$,<VirtualHost> + <VirtualHost> $B%G%#%l%/%F%#%V$,;H$o$l$J$$>l9g$O!"(B $B<VirtualHost> + <VirtualHost> $B$r;H$C$F!"(B $B0l$D0J>e$N%"%I%l%9$d%]!<%H$KBP$7$F0[$J$k5sF0$r$9$k$h$&$K(B $B;XDj$9$k$3$H$,$G$-$^$9!#(B @@ -115,10 +117,10 @@ $B$^$:=i$a$K%5!<%P$KDLCN$7$J$1$l$P$J$j$^$;$s!#(B $B$=$7$F!"$=$N;XDj$7$?%"%I%l%9$H%]!<%H$G$N(B $B$3$N%P!<%A%c%k%[%9%H$N5sF0$r@_Dj$9$k$?$a$K!"(B - <VirtualHost> + <VirtualHost> $B%;%/%7%g%s$r:n$j$^$9!#$b$7(B - <VirtualHost> + <VirtualHost> $B$,(B listen $B$7$F$$$J$$%"%I%l%9$H%]!<%H$KBP$7$F(B $B@_Dj$5$l$F$7$^$&$H!"(B $B$=$l$K$O%"%/%;%9$G$-$J$$$H$$$&$3$H$KCm0U$7$F$/$@$5$$!#(B
-

$B4XO"%b%8%e!<%k(B	$B4XO"%G%#%l%/%F%#%V(B
`core` `mpm_common`	`VirtualHost` `Listen`

Apache HTTP Server Version 2.0

\ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/configuring.html.en b/docs/manual/configuring.html.en index 51b951e1ff..3d840d9bcb 100644 --- a/docs/manual/configuring.html.en +++ b/docs/manual/configuring.html.en @@ -1,20 +1,22 @@ -Configuration Files - Apache HTTP Server

Apache HTTP Server Version 2.0
Configuration Files
+ -->Configuration Files - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Configuration Files

This document describes the files used to configure the Apache HTTP server.
-
Main Configuration Files
Syntax of the Configuration Files
Modules
Scope of Directives
.htaccess Files
Main Configuration Files
+
Main Configuration Files
Syntax of the Configuration Files
Modules
Scope of Directives
.htaccess Files
Main Configuration Files
-
Related Modules

mod_mime
Related Directives

<IfDefine>
Include
TypesConfig
+
Related Modules Related Directives
mod_mime
<IfDefine>
Include
TypesConfig

Apache is configured by placing directives in plain text configuration files. The main configuration file is usually called httpd.conf. The location of this file is set at compile-time, but may be overridden with the -f command line flag. In addition, other - configuration files may be added using the Include directive. Any + configuration files may be added using the Include directive. Any directive may be placed in any of these configuration files. Changes to the main configuration files are only recognized by Apache when it is started or restarted.
@@ -30,9 +32,9 @@ HTTP server.
makes automating such processes much easier.

The server also reads a file containing mime document types; - the filename is set by the TypesConfig directive, + the filename is set by the TypesConfig directive, and is mime.types by default.
-
Syntax of the Configuration Files
+
Syntax of the Configuration Files

Apache configuration files contain one directive per line. @@ -53,10 +55,10 @@ HTTP server.
without starting the server by using apachectl configtest or the -t command line option.
-
Modules
+
Modules
-
Related Modules

mod_so
Related Directives

<IfModule>
LoadModule
+
Related Modules Related Directives
mod_so
<IfModule>
LoadModule

Apache is a modular server. This implies that only the most basic functionality is included in the core server. Extended @@ -65,23 +67,23 @@ HTTP server.
included in the server at compile-time. If the server is compiled to use dynamically loaded modules, then modules can be compiled separately and added at - any time using the LoadModule + any time using the LoadModule directive. Otherwise, Apache must be recompiled to add or remove modules. Configuration directives may be included conditional on a - presence of a particular module by enclosing them in an<IfModule> block.
+ presence of a particular module by enclosing them in an<IfModule> block.

To see which modules are currently compiled into the server, you can use the -l command line option.
-
Scope of Directives
+
Scope of Directives
-
Related Modules

Related Directives

<Directory>
<DirectoryMatch>
<Files>
<FilesMatch>
<Location>
<LocationMatch>
<VirtualHost>
+
Related Modules Related Directives
<Directory>
<DirectoryMatch>
<Files>
<FilesMatch>
<Location>
<LocationMatch>
<VirtualHost>

Directives placed in the main configuration files apply to the entire server. If you wish to change the configuration for only a part of the server, you can scope your directives by - placing them in <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, and <LocationMatch> + placing them in <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, and <LocationMatch> sections. These sections limit the application of the directives which they enclose to particular filesystem locations or URLs. They can also be nested, allowing for very @@ -90,7 +92,7 @@ HTTP server.

Apache has the capability to serve many different websites simultaneously. This is called Virtual Hosting. Directives can also be scoped by placing them - inside <VirtualHost> + inside <VirtualHost> sections, so that they will only apply to requests for a particular website.
@@ -101,15 +103,15 @@ HTTP server.
can be placed in which sections, check the Context of the directive. For further information, we provide details on How Directory, Location and Files sections work.
-
.htaccess Files
+
.htaccess Files
-
Related Modules

Related Directives

AccessFileName
AllowOverride
+
Related Modules Related Directives
AccessFileName
AllowOverride

Apache allows for decentralized management of configuration via special files placed inside the web tree. The special files are usually called .htaccess, but any name can be - specified in the AccessFileName + specified in the AccessFileName directive. Directives placed in .htaccess files apply to the directory where you place the file, and all sub-directories. The .htaccess files follow the @@ -121,10 +123,10 @@ HTTP server.
.htaccess files, check the Context of the directive. The server administrator further controls what directives may be placed in .htaccess files by - configuring the AllowOverride + configuring the AllowOverride directive in the main configuration files.

For more information on .htaccess files, see Ken Coar's tutorial on Using .htaccess Files with Apache.
-

Related Modules	Related Directives
`mod_mime`	`<IfDefine>` `Include` `TypesConfig`

Related Modules	Related Directives
`mod_so`	`<IfModule>` `LoadModule`

Related Modules	Related Directives
	`<Directory>` `<DirectoryMatch>` `<Files>` `<FilesMatch>` `<Location>` `<LocationMatch>` `<VirtualHost>`

Related Modules	Related Directives
	`AccessFileName` `AllowOverride`

Apache HTTP Server Version 2.0

\ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/configuring.html.ja.jis b/docs/manual/configuring.html.ja.jis index fb9f7cbdd4..ecc9bb225c 100644 --- a/docs/manual/configuring.html.ja.jis +++ b/docs/manual/configuring.html.ja.jis @@ -1,24 +1,26 @@ -$B@_Dj%U%!%$%k(B - Apache HTTP Server

Apache HTTP Server Version 2.0
$B@_Dj%U%!%$%k(B
+ -->$B@_Dj%U%!%$%k(B - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
$B@_Dj%U%!%$%k(B

$B$3$NJ8=q$G$O!"(BApache HTTP $B%5!<%P$r@_Dj$9$k$N$K;HMQ$9$k%U%!%$%k$K$D$$$F(B -$B5-=R$7$F$$$^$9(B$B!#(B
-
$B%a%$%s$N@_Dj%U%!%$%k(B
$B@_Dj%U%!%$%k$N9=J8(B
$B%b%8%e!<%k(B
$B%G%#%l%/%F%#%V$NE,MQHO0O(B
.htaccess $B%U%!%$%k(B
$B%a%$%s$N@_Dj%U%!%$%k(B
+$B5-=R$7$F$$$^$9!#(B
+
$B%a%$%s$N@_Dj%U%!%$%k(B
$B@_Dj%U%!%$%k$N9=J8(B
$B%b%8%e!<%k(B
$B%G%#%l%/%F%#%V$NE,MQHO0O(B
.htaccess $B%U%!%$%k(B
$B%a%$%s$N@_Dj%U%!%$%k(B
-
$B4XO"%b%8%e!<%k(B

mod_mime
$B4XO"%G%#%l%/%F%#%V(B

<IfDefine>
Include
TypesConfig
+
$B4XO"%b%8%e!<%k(B $B4XO"%G%#%l%/%F%#%V(B
mod_mime
<IfDefine>
Include
TypesConfig

Apache $B$O(B $B%G%#%l%/%F%#%V(B $B$r@_Dj%U%!%$%k$KJ?J8$G=q$/$3$H$K$h$j@_Dj$7$^$9!#(B - $B%a%$%s$N@_Dj%U%!%$%k$O(B$BIaDL$O(B httpd.conf $B$H$$$&L>A0$G$9!#(B + $B%a%$%s$N@_Dj%U%!%$%k$OIaDL$O(B httpd.conf $B$H$$$&L>A0$G$9!#(B $B$3$N%U%!%$%k$N0LCV$O%3%s%Q%$%k;~$K@_Dj$5$l$^$9$,!"%3%^%s%I%i%$%s$N(B -f $B%U%i%0$K$h$j>e=q$-$G$-$^$9!#(B - $B$=$N>e!"B>$N@_Dj%U%!%$%k$,(B Include - $B%G%#%l%/%F%#%V$K$h$C$FDI2C$5(B$B$l$F$$$k$+$b$7$l$^$;$s!#(B + $B$=$N>e!"B>$N@_Dj%U%!%$%k$,(B Include + $B%G%#%l%/%F%#%V$K$h$C$FDI2C$5$l$F$$$k$+$b$7$l$^$;$s!#(B $B$I$N%G%#%l%/%F%#%V$b$3$l$i$N@_Dj%U%!%$%k$N$I$l$K$G$bF~$l$i$l$^$9!#(B Apache $B$O5/F0;~$+:F5/F0;~$N$_%a%$%s@_Dj%U%!%$%k$NJQ99$rG'<1$7$^$9!#(B
-
Apache 1.3.13 $B$N?7$7$$5!G=$H$7$F!"@_Dj%U%!%$%k(B$B$,Apache 1.3.13 $B$N?7$7$$5!G=$H$7$F!"@_Dj%U%!%$%k$,$l$N%[%9%H$KBP$7$F>.$5$J@_Dj(B @@ -29,16 +31,16 @@
$B%5!<%P$O(B MIME $B%I%-%e%a%s%H%?%$%W$r4^$s$G$$$k%U%!%$%k$bFI$_9~$_$^$9!#%U%!%$%kL>$O(B - TypesConfig + TypesConfig $B$G@_Dj$5$l!"%G%U%)%k%H$G$O(B mime.types $B$K$J$C$F$$$^$9!#(B
-
$B@_Dj%U%!%$%k$N9=J8(B
+
$B@_Dj%U%!%$%k$N9=J8(B

Apache $B$N@_Dj%U%!%$%k$O(B 1 $B9T$K(B 1 $B$D$N%G%#%l%/%F%#%V$+$i$J$j$^$9!#(B $B%P%C%/%9%i%C%7%e(B "\" $B$O%G%#%l%/%F%#%V$,$NJ8;z$d6uGr$,$"$C$F$O$$$1$^$;$s!#(B + $B9T$N:G8e$H%P%C%/%9%i%C%7%e$N4V$KB>$NJ8;z$d6uGr$,$"$C$F$O$$$1$^$;$s!#(B

$B@_Dj%U%!%$%k$N%G%#%l%/%F%#%V$OBgJ8;z>.J8;z$r6hJL$7$^$;$s$,!"(B @@ -52,33 +54,33 @@ apachectl configtest $B$+%3%^%s%I%i%$%s%*%W%7%g%s(B -t $B$r;H$C$FD4$Y$i$l$^$9!#(B
-
$B%b%8%e!<%k(B
+
$B%b%8%e!<%k(B
-
$B4XO"%b%8%e!<%k(B

mod_so
$B4XO"%G%#%l%/%F%#%V(B

<IfModule>
LoadModule
+
$B4XO"%b%8%e!<%k(B $B4XO"%G%#%l%/%F%#%V(B
mod_so
<IfModule>
LoadModule

Apache $B$O%b%8%e!<%k2=$5$l$?%5!<%P$G$9!#(B $B%3%"%5!<%P$K$O:G$b4pK\E*$J5!G=$@$1$,4^$^$l$F$$$^$9!#3HD%5!G=$O(B - Apache $B$K%m!<%I(B$B$5$l$k(B$B%b%8%e!<%k(B$B$H$7$FMxMQ2DG=$G$9!#%G%U%)%k%H$G$O!"%3%s%Q%$%k;~$K%b%8%e!<%k$N(B + Apache $B$K%m!<%I$5$l$k(B$B%b%8%e!<%k(B$B$H$7$FMxMQ2DG=$G$9!#%G%U%)%k%H$G$O!"%3%s%Q%$%k;~$K%b%8%e!<%k$N(B Base $B%;%C%H(B ($B4pK\%;%C%H(B) $B$,(B $B%5!<%P$K4^$^$l$^$9!#%5!<%P$,(B$BF0E*%m!<%I(B$B%b%8%e!<%k$r;H$&$h$&$K%3%s%Q%$%k$5$l$F$$$k>l9g$O!"(B $B%b%8%e!<%k$rJL$K%3%s%Q%$%k$7$F!"$$$D$G$b(B - LoadModule + LoadModule $B%G%#%l%/%F%#%V$r;H$C$FDI2C$G$-$^$9!#(B $B$=$&$G$J$$>l9g$O!"%b%8%e!<%k$NDI2C$d:o=|$r$9$k$?$a$K$O(B Apache - $B$r:F%3%s%Q%$%k$9$kI,MW$,$"$j$^$9!#@_Dj%G%#%l%/%F%#%V$O(B <IfModule> + $B$r:F%3%s%Q%$%k$9$kI,MW$,$"$j$^$9!#@_Dj%G%#%l%/%F%#%V$O(B <IfModule> $B%V%m%C%/$KF~$l$k$3$H$GFCDj$N%b%8%e!<%k$,B8:_$9$k$H$-$@$1(B $B@_Dj%U%!%$%k$K4^$^$l$k$h$&$K$9$k$3$H$,$G$-$^$9!#(B

$B%3%^%s%I%i%$%s%*%W%7%g%s(B -l $B$r;H$C$F8=;~E@$G(B $B$I$N%b%8%e!<%k$,%5!<%P$K%3%s%Q%$%k$5$l$F$$$k$+$rCN$k$3$H$,$G$-$^$9!#(B
-
$B%G%#%l%/%F%#%V$NE,MQHO0O(B
+
$B%G%#%l%/%F%#%V$NE,MQHO0O(B
-
$B4XO"%b%8%e!<%k(B

$B4XO"%G%#%l%/%F%#%V(B

<Directory>
<DirectoryMatch>
<Files>
<FilesMatch>
<Location>
<LocationMatch>
<VirtualHost>
+
$B4XO"%b%8%e!<%k(B $B4XO"%G%#%l%/%F%#%V(B
<Directory>
<DirectoryMatch>
<Files>
<FilesMatch>
<Location>
<LocationMatch>
<VirtualHost>

$B%a%$%s@_Dj%U%!%$%k$K$"$k%G%#%l%/%F%#%V$O%5!<%PA4BN$KE,MQ$5$l$^$9!#(B - $B%5!<%P$N0lItJ,$N@_Dj$@$1$rJQ99$7$?$$>l9g$O(B <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, <LocationMatch> + $B%5!<%P$N0lItJ,$N@_Dj$@$1$rJQ99$7$?$$>l9g$O(B <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, <LocationMatch> $B%;%/%7%g%s$NCf$KCV$/$3$H$GE,MQHO0O$r7h$a$i$l$^$9!#(B $B$3$l$i$N%;%/%7%g%s$O$=$NCf$K$"$k%G%#%l%/%F%#%V$NE,MQHO0O$r(B $BFCDj$N%U%!%$%k%7%9%F%`$N0LCV$d(B URL $B$K8BDj$7$^$9!#(B @@ -89,7 +91,7 @@ $B$3$l$O(B $B%P!<%A%c%k%[%9%H(B $B$H8F$P$l$F$$$^$9!#(B $BFCDj$N%&%'%V%5%$%H$K$N$_E,MQ$5$l$k$h$&$K$9$k$?$a$K!"(B $B%G%#%l%/%F%#%V$O(B - <VirtualHost> + <VirtualHost> $B%;%/%7%g%s$NCf$KCV$/$3$H$G$bE,MQHO0O$rJQ$($k$3$H$,$G$-$^$9!#(B

$B$[$H$s$I$N%G%#%l%/%F%#%V$O$I$N%;%/%7%g%s$K$G$b=q$1$^$9$,!"(B @@ -100,15 +102,15 @@ $B%G%#%l%/%F%#%V$N(B $B%3%s%F%-%9%H(B $B$rD4$Y$F$/$@$5$$!#>\$7$$>pJs$O!"(B Directory, Location, Files $B%;%/%7%g%s$NF0:nK!(B$B$K$"$j$^$9!#(B
-
.htaccess $B%U%!%$%k(B
+
.htaccess $B%U%!%$%k(B
-
$B4XO"%b%8%e!<%k(B

$B4XO"%G%#%l%/%F%#%V(B

AccessFileName
AllowOverride
+
$B4XO"%b%8%e!<%k(B $B4XO"%G%#%l%/%F%#%V(B
AccessFileName
AllowOverride

Apache $B$G$O%&%'%V%D%j!<$NCf$KCV$+$l$?FCJL$J%U%!%$%k$r;H$C$F(B $BHsCf1{=88"E*$J@_Dj4IM}$r$G$-$^$9!#$=$NFCJL$J%U%!%$%k$OIaDL$O(B .htaccess $B$H$$$&L>A0$G!"(B - AccessFileName + AccessFileName $B%G%#%l%/%F%#%V$G$I$s$JL>A0$K$G$b;XDj$G$-$^$9!#(B .htaccess $B%U%!%$%k$K=q$+$l$?%G%#%l%/%F%#%V$O%U%!%$%k$rCV$$$?(B @@ -120,7 +122,7 @@
$B$I$N%G%#%l%/%F%#%V$,(B .htaccess $B%U%!%$%k$K=q$1$k$+$rD4$Y$k$K$O!"%G%#%l%/%F%#%V$N(B$B%3%s%F%-%9%H(B $B$rD4$Y$F$/$@$5$$!#%5!<%P4IM}AllowOverride + AllowOverride $B$r@_Dj$9$k$3$H$G$I$N%G%#%l%/%F%#%V$r(B .htaccess $B%U%!%$%k$K=q$1$k$h$&$K$9$k$+$r@)8f$9$k$3$H$,$G$-$^$9!#(B
@@ -128,4 +130,4 @@ Ken Coar $B$5$s$N%A%e!<%H%j%"%k(B Using .htaccess Files with Apache $B$r;2>H$7$F$/$@$5$$!#(B
-

$B4XO"%b%8%e!<%k(B	$B4XO"%G%#%l%/%F%#%V(B
`mod_mime`	`<IfDefine>` `Include` `TypesConfig`

$B4XO"%b%8%e!<%k(B	$B4XO"%G%#%l%/%F%#%V(B
`mod_so`	`<IfModule>` `LoadModule`

$B4XO"%b%8%e!<%k(B	$B4XO"%G%#%l%/%F%#%V(B
	`<Directory>` `<DirectoryMatch>` `<Files>` `<FilesMatch>` `<Location>` `<LocationMatch>` `<VirtualHost>`

$B4XO"%b%8%e!<%k(B	$B4XO"%G%#%l%/%F%#%V(B
	`AccessFileName` `AllowOverride`

Apache HTTP Server Version 2.0

\ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/content-negotiation.html.en b/docs/manual/content-negotiation.html.en index e8bac484c3..6cf4c01fc0 100644 --- a/docs/manual/content-negotiation.html.en +++ b/docs/manual/content-negotiation.html.en @@ -1,8 +1,10 @@ -Content Negotiation - Apache HTTP Server

Apache HTTP Server Version 2.0
Content Negotiation
+ -->Content Negotiation - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Content Negotiation

Apache's supports content negotiation as described in the HTTP/1.1 specification. It can choose the best @@ -13,11 +15,11 @@ incomplete negotiation information.

Content negotiation is provided by the - mod_negotiation module. + mod_negotiation module. which is compiled in by default.
-
About Content Negotiation
Negotiation in Apache
Using a type-map file
Multiviews
The Negotiation Methods
Dimensions of Negotiation
Apache Negotiation Algorithm
Fiddling with Quality - Values
Media Types and Wildcards
Language Negotiation Exceptions
Extensions to Transparent Content -Negotiation
Note on hyperlinks and naming conventions
Note on Caching
More Information
About Content Negotiation
+
About Content Negotiation
Negotiation in Apache
The Negotiation Methods
Fiddling with Quality + Values
Extensions to Transparent Content +Negotiation
Note on hyperlinks and naming conventions
Note on Caching
More Information
About Content Negotiation

A resource may be available in several different representations. For example, it might be available in @@ -32,7 +34,7 @@ Negotiation
Note on hyperlinks and naming conventi preferences by headers in the request. To request only French representations, the browser would send
-
Accept-Language: fr
+
Accept-Language: fr

Note that this preference will only be applied when there is a choice of representations and they vary by language.
@@ -44,10 +46,10 @@ Negotiation
Note on hyperlinks and naming conventi other media types, but also allowing any other media type as a last resort:
-
- Accept-Language: fr; q=1.0, en; q=0.5 + + Accept-Language: fr; q=1.0, en; q=0.5 Accept: text/html; q=1.0, text/*; q=0.8, image/gif; q=0.6, image/jpeg; q=0.6, image/*; q=0.5, */*; q=0.1 -
+

Apache supports 'server driven' content negotiation, as defined in the HTTP/1.1 specification. It fully supports the @@ -69,7 +71,7 @@ Negotiation
Note on hyperlinks and naming conventi representations is termed a variant. The ways in which the variants for a negotiable resource vary are called the dimensions of negotiation.
-
Negotiation in Apache
+
Negotiation in Apache

In order to negotiate a resource, the server needs to be given information about each of the variants. This is done in @@ -85,7 +87,7 @@ Negotiation
Note on hyperlinks and naming conventi results.
-
Using a type-map file
+
Using a type-map file

A type map is a document which is associated with the handler named type-map (or, for @@ -94,7 +96,7 @@ Negotiation
Note on hyperlinks and naming conventi use this feature, you must have a handler set in the configuration that defines a file suffix as type-map; this is best done with a
-
AddHandler type-map .var
+
AddHandler type-map .var

in the server configuration file.

Type map files should have the same name as the resource @@ -108,35 +110,35 @@ Negotiation
Note on hyperlinks and naming conventi This file would be named foo.var, as it describes a resource named foo.
-
- URI: foo - - URI: foo.en.html - Content-type: text/html - Content-language: en - - URI: foo.fr.de.html - Content-type: text/html;charset=iso-8859-2 - Content-language: fr, de -
+
+ URI: foo + + URI: foo.en.html + Content-type: text/html + Content-language: en + + URI: foo.fr.de.html + Content-type: text/html;charset=iso-8859-2 + Content-language: fr, de +

Note also that a typemap file will take precedence over the filename's extension, even when Multiviews is on. If the variants have different source qualities, that may be indicated by the "qs" parameter to the media type, as in this picture (available as jpeg, gif, or ASCII-art):
-
- URI: foo - - URI: foo.jpeg - Content-type: image/jpeg; qs=0.8 - - URI: foo.gif - Content-type: image/gif; qs=0.5 - - URI: foo.txt - Content-type: text/plain; qs=0.01 -
+
+ URI: foo + + URI: foo.jpeg + Content-type: image/jpeg; qs=0.8 + + URI: foo.gif + Content-type: image/gif; qs=0.5 + + URI: foo.txt + Content-type: text/plain; qs=0.01 +

qs values can vary in the range 0.000 to 1.000. Note that any variant with a qs value of 0.000 will never be chosen. @@ -156,12 +158,12 @@ Negotiation
Note on hyperlinks and naming conventi typemap documentation.
-
Multiviews
+
Multiviews

MultiViews is a per-directory option, meaning it - can be set with an Options - directive within a <Directory>, <Location> or <Files> section in - access.conf, or (if AllowOverride is properly set) in + can be set with an Options + directive within a <Directory>, <Location> or <Files> section in + access.conf, or (if AllowOverride is properly set) in .htaccess files. Note that Options All does not set MultiViews; you have to ask for it by name.
@@ -177,10 +179,10 @@ Negotiation
Note on hyperlinks and naming conventi then chooses the best match to the client's requirements.

MultiViews may also apply to searches for the file - named by the DirectoryIndex directive, if the + named by the DirectoryIndex directive, if the server is trying to index a directory. If the configuration files specify
-
DirectoryIndex index
+
DirectoryIndex index

then the server will arbitrate between index.html and index.html3 if both are present. If neither are present, and index.cgi is there, the server @@ -189,11 +191,11 @@ Negotiation
Note on hyperlinks and naming conventi
If one of the files found when reading the directory does not have an extension recognized by mod_mime to designate its Charset, Content-Type, Language, or Encoding, then the result - depends on the setting of the MultiViewsMatch directive. This + depends on the setting of the MultiViewsMatch directive. This directive determines whether handlers, filters, and other extension types can participate in MultiViews negotiation.
-
The Negotiation Methods
+
The Negotiation Methods

After Apache has obtained a list of the variants for a given resource, either from a type-map file or from the filenames in @@ -225,7 +227,7 @@ Negotiation
Note on hyperlinks and naming conventi variant selection algorithm' defined in RFC 2296.
-
Dimensions of Negotiation
+
Dimensions of Negotiation
@@ -270,7 +272,7 @@ Negotiation
Note on hyperlinks and naming conventi

-
Apache Negotiation Algorithm
+
Apache Negotiation Algorithm

Apache can use the following algorithm to select the 'best' variant (if any) to return to the browser. This algorithm is @@ -355,7 +357,7 @@ Negotiation
Note on hyperlinks and naming conventi dimensions of variance.
-
Fiddling with Quality +
Fiddling with Quality Values

Apache sometimes changes the quality values from what would @@ -368,23 +370,23 @@ Negotiation
Note on hyperlinks and naming conventi sends full and correct information these fiddles will not be applied.
-
Media Types and Wildcards
+
Media Types and Wildcards

The Accept: request header indicates preferences for media types. It can also include 'wildcard' media types, such as "image/*" or "*/*" where the * matches any string. So a request including:
-
Accept: image/*, */*
+
Accept: image/*, */*

would indicate that any type starting "image/" is acceptable, as is any other type (so the first "image/*" is redundant). Some browsers routinely send wildcards in addition to explicit types they can handle. For example:
-
+ Accept: text/html, text/plain, image/gif, image/jpeg, */* -
+

The intention of this is to indicate that the explicitly listed types are preferred, but if a different representation is available, that is ok too. However under the basic algorithm, @@ -392,9 +394,9 @@ Negotiation
Note on hyperlinks and naming conventi to all the other types, so they are not being preferred. The browser should really have sent a request with a lower quality (preference) value for *.*, such as:
-
+ Accept: text/html, text/plain, image/gif, image/jpeg, */*; q=0.01 -
+

The explicit types have no quality factor, so they default to a preference of 1.0 (the highest). The wildcard */* is given a low preference of 0.01, so other types will only be returned if @@ -410,7 +412,7 @@ Negotiation
Note on hyperlinks and naming conventi correct information to start with work as expected.
-
Language Negotiation Exceptions
+
Language Negotiation Exceptions

New in Apache 2.0, some exceptions have been added to the negotiation algorithm to allow graceful fallback when language @@ -422,10 +424,10 @@ Negotiation
Note on hyperlinks and naming conventi Variant" or "Multiple Choices" response to the client. To avoid these error messages, it is possible to configure Apache to ignore the Accept-language in these cases and provide a document that - does not explictly match the client's request. The ForceLanguagePriority + does not explictly match the client's request. The ForceLanguagePriority directive can be used to override one or both of these error messages and subsitute the servers judgement in the form of the - LanguagePriority + LanguagePriority directive.

The server will also attempt to match language-subsets when no @@ -440,7 +442,7 @@ Negotiation
Note on hyperlinks and naming conventi general. Unfortunately, many current clients have default configurations that resemble this.) However, if no other language match is possible and the server is about to return a "No - Acceptable Variants" error or fallback to the LanguagePriority, the server + Acceptable Variants" error or fallback to the LanguagePriority, the server will ignore the subset specification and match en-GB against en documents. Implicitly, Apache will add the parent language to the client's acceptable language list with @@ -451,7 +453,7 @@ Negotiation
Note on hyperlinks and naming conventi specification and to work effectively with properly configured clients.
-
Extensions to Transparent Content +
Extensions to Transparent Content Negotiation

Apache extends the transparent content negotiation protocol (RFC @@ -463,7 +465,7 @@ to use them as candidate variants whenever their encodings are acceptable according to the Accept-Encoding request header. The RVSA/1.0 implementation does not round computed quality factors to 5 decimal places before choosing the best variant.
-
Note on hyperlinks and naming conventions
+
Note on hyperlinks and naming conventions

If you are using language negotiation you can choose between different naming conventions, because files can have more than @@ -490,7 +492,7 @@ decimal places before choosing the best variant.

Here some more examples of filenames together with valid and invalid hyperlinks:
- +
@@ -502,7 +504,7 @@ decimal places before choosing the best variant.
- @@ -519,10 +521,10 @@ decimal places before choosing the best variant.
- - @@ -531,16 +533,16 @@ decimal places before choosing the best variant.
- - @@ -549,8 +551,8 @@ decimal places before choosing the best variant.
- @@ -570,7 +572,7 @@ decimal places before choosing the best variant.
extension (including an encoding extension if there is one) must be on the right hand side of the MIME-type extension (e.g., foo.html.en).
-
Note on Caching
+
Note on Caching

When a cache stores a representation, it associates it with the request URL. The next time that URL is requested, the cache @@ -584,15 +586,15 @@ decimal places before choosing the best variant.
responses.

For requests which come from a HTTP/1.0 compliant client - (either a browser or a cache), the directive CacheNegotiatedDocs can be + (either a browser or a cache), the directive CacheNegotiatedDocs can be used to allow caching of responses which were subject to negotiation. This directive can be given in the server config or virtual host, and takes no arguments. It has no effect on requests from HTTP/1.1 clients.
-
More Information
+
More Information

For more information about content negotiation, see Alan J. Flavell's Language Negotiation Notes. But note that this document may not be updated to include changes in Apache 2.0.
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/content-negotiation.html.ja.jis b/docs/manual/content-negotiation.html.ja.jis index 1fc3239d03..dfe49f3850 100644 --- a/docs/manual/content-negotiation.html.ja.jis +++ b/docs/manual/content-negotiation.html.ja.jis @@ -1,30 +1,32 @@ -$B%3%s%F%s%H%M%4%7%(!<%7%g%s(B - Apache HTTP Server
Apache HTTP Server Version 2.0
$B%3%s%F%s%H%M%4%7%(!<%7%g%s(B
+ -->$B%3%s%F%s%H%M%4%7%(!<%7%g%s(B - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
$B%3%s%F%s%H%M%4%7%(!<%7%g%s(B
-
Apache $B$O(B HTTP/1.1 $B$N5,3J$K5-=R$5$l$F$$$k%3%s%F%s%H%M%4%7%(!<(B$B%7%g%s$r(B +
Apache $B$O(B HTTP/1.1 $B$N5,3J$K5-=R$5$l$F$$$k%3%s%F%s%H%M%4%7%(!<%7%g%s$r(B $B%5%]!<%H$7$F$$$^$9!#(B - $B%V%i%&%6$K$h$jDs(B$B6!$5$l$?%a%G%#%"%?%$%W!"(B - $B8@8l!"J8;z%;%C%H!"%(%s%3!<%G%#(B$B%s%0$NM%@h798~$K4p$E$$$F!"(B + $B%V%i%&%6$K$h$jDs6!$5$l$?%a%G%#%"%?%$%W!"(B + $B8@8l!"J8;z%;%C%H!"%(%s%3!<%G%#%s%0$NM%@h798~$K4p$E$$$F!"(B $B:GE,$J%j%=!<%9$NI=8=$rA*Br$G$-$^$9!#(B $B$^$?!"IT40A4$J%M%4%7%(!<%7%g%s>pJs$rAw$C$F$/$k%V%i%&%6$+$i$N%j%/%(%9%H$r(B $B$b$C$H8-$/ -
$B%3%s%F%s%H%M%4%7%(!<%7(B$B%g%s$O(B - mod_negotiation +
$B%3%s%F%s%H%M%4%7%(!<%7%g%s$O(B + mod_negotiation $B%b%8%e!<%k$K$h$C$F(B $BDs6!$5$l$F$$$F!"%G%U%)%k%H$GAH$_9~$^$l$F$$$^$9!#(B
-
$B%3%s%F%s%H%M%4%7%(!<%7%g%s$K$D$$$F(B
Apache $B$K$*$1$k%M%4%7%(!<%7%g%s(B
type-map $B%U%!%$%k$r;H$&(B
Multiviews
$B%M%4%7%(!<%7%g%sJ}K!(B
$B%M%4%7%(!<%7%g%s$N
Apache $B%M%4%7%(!<%7%g%s%"%k%4%j%:%`(B
$BIJ
$B%a%G%#%"%?%$%W$H%o%$%k%I%+!<%I(B
$B8@8l%M%4%7%(!<%7%g%s$NNc30=hM}(B
Transparent Content Negotiation -$B$N3HD%(B
$B%j%s%/$HL>A0$NJQ49$K4X$9$kCm0UE@(B
$B%-%c%C%7%e$K4X$9$kCm0U;v9`(B
$BDI2C>pJs(B
$B%3%s%F%s%H%M%4%7%(!<%7%g%s$K$D$$$F(B
+
$B%3%s%F%s%H%M%4%7%(!<%7%g%s$K$D$$$F(B
Apache $B$K$*$1$k%M%4%7%(!<%7%g%s(B
$B%M%4%7%(!<%7%g%sJ}K!(B
$BIJ
Transparent Content Negotiation +$B$N3HD%(B
$B%j%s%/$HL>A0$NJQ49$K4X$9$kCm0UE@(B
$B%-%c%C%7%e$K4X$9$kCm0U;v9`(B
$BDI2C>pJs(B
$B%3%s%F%s%H%M%4%7%(!<%7%g%s$K$D$$$F(B

$B%j%=!<%9$O!"4v$D$+0[$J$C$?I=8=$GMxMQ$G$-$k>l9g$,$"$j$^$9!#(B - $BNc$((B$B$P!"0[$J$k8@8l$d0[$J$k%a%G%#%"%?%$%W!"(B + $BNc$($P!"0[$J$k8@8l$d0[$J$k%a%G%#%"%?%$%W!"(B $B$^$?$O$=$l$i$NAH$_9g$o$;$GMxMQ$G$-$k$+$bCN$l$^$;$s!#(B $B$b$C$H$bE,$7$?A*Br$r$9$kJ}K!$N0l$D$K$O!"%$%s%G%C%/%9%Z!<%8$r(B $B%f!<%6$K8+$;$F!"%f!<%6$KA*$s$G$b$i$&J}K!$,$"$j$^$9!#(B - $B$7$+$7!"%5!<%P(B$B$,<+F0E*$KA*$V$3$H$,$G$-$k>l9g$,B?$/$"$j$^$9!#(B + $B$7$+$7!"%5!<%P$,<+F0E*$KA*$V$3$H$,$G$-$k>l9g$,B?$/$"$j$^$9!#(B $B$3$l$O!"%V%i%&%6$,%j%/%(%9%H>pJsKh$N>pJs$N0lIt$K!"(B $B$I$NI=8=$rSO9%$9$k$+$rAw$k$3$H$GF0:n$7$F$$$^$9!#(B $BNc$($P%V%i%&%6$O!"2DG=$J$i%U%i%s%98l$G>pJs$r8+$?$$!"(B @@ -33,7 +35,7 @@ $B%V%i%&%6$O%j%/%(%9%H$N%X%C%@$G<+J,$NM%@h798~$rCN$i$;$^$9!#(B $B%U%i%s%98l$N$_$NI=8=$rMW5a$9$k>l9g$O!"%V%i%&%6$O -

Filename
foo.html.en foo
+ foo
foo.html -
foo.html.en.gz foo
+ foo
foo.html foo.gz
+ foo.gz
foo.html.gz

foo foo.html
- foo.html.gz
+ foo.html
+ foo.html.gz
foo.gz

foo.gz.html.en foo
- foo.gz
+ foo
+ foo.gz
foo.gz.html foo.html
foo.html.gz.en foo
- foo.html
+ foo
+ foo.html
foo.html.gz foo.gz
Accept-Language: fr

Filename
foo.html.en	foo +	foo foo.html	-
foo.html.en.gz	foo +	foo foo.html	foo.gz +	foo.gz foo.html.gz
foo	foo.html - foo.html.gz +	foo.html + foo.html.gz foo.gz
foo.gz.html.en	foo - foo.gz +	foo + foo.gz foo.gz.html	foo.html
foo.html.gz.en	foo - foo.html +	foo + foo.html foo.html.gz	foo.gz

Accept-Language: fr

$B$3$NM%@h798~$O!"A*Br2DG=$JI=8=$,B8:_$7$F!"(B $B8@8l$K$h$C$FMM!9$JI=8=$,$"$k>l9g$K$N$_E,MQ$5$l$k(B @@ -44,12 +46,12 @@ $B$=$7$FMM!9$J%a%G%#%"%?%$%W$r$N%?%$%W$h$j$O(B HTML $B$r9%$`!"(B $BB>$N%a%G%#%"%?%$%W$h$j$O(B GIF $B$d(B JPEG $B$r9%$`!"$7$+$7:G=*$N%a%G%#%"%?%$%W$b + $BB>$N%a%G%#%"%?%$%W$b -

- Accept-Language: fr; q=1.0, en; q=0.5 + + Accept-Language: fr; q=1.0, en; q=0.5 Accept: text/html; q=1.0, text/*; q=0.8, image/gif; q=0.6, image/jpeg; q=0.6, image/*; q=0.5, */*; q=0.1 -

Apache $B$O(B HTTP/1.1 $B5,3J$GDj5A$5$l$F$$$k(B 'server driven' $B%3%s%F%s%H%M%4%7%(!<%7%g%s$r%5%]!<%H$7$F$$$^$9!#(B @@ -61,7 +63,7 @@ $B$3$l$i$N(B RFC$B$GDj5A$5$l$F$$$k(B 'feature negotiation' $B$O%5%]!<%H$7$F$$$^$;$s!#(B

$B%j%=(B$B!<%9(B$B$H$O(B URI +

$B%j%=!<%9(B$B$H$O(B URI $B$GFCDj$5$l$k35G0>e$N$b$N$N$3$H$G$9(B (RFC 2396)$B!#(B Apache $B$N$h$&$J(B HTTP $B%5!<%P$O!"$=$NL>A06u4V$NCf$G$N(B $B%j%=!<%9$N(B$BI=8=(B$B$X$N%"%/%;%9$rDs6!$7$^$9!#(B @@ -75,7 +77,7 @@ $B%M%4%7%(!<%7%g%s2DG=$J%j%=!<%9$N(B variant $B$,0[$J$k!"(B $B$=$N>uBV$r;X$7$F!"(B $B%M%4%7%(!<%7%g%s$N(B$B$B$H8F$S$^$9!#(B

-
Apache $B$K$*$1$k%M%4%7%(!<%7%g%s(B
+
Apache $B$K$*$1$k%M%4%7%(!<%7%g%s(B

$B%j%=!<%9$r%M%4%7%(!<%7%g%s$9$k$?$a$K$O!"(B $B%5!<%P$O(B variant $B$=$l$>$l$K$D$$$F$N>pJs$rCN$C$F$*$/I,MW$,$"$j$^$9!#(B @@ -92,7 +94,7 @@ $B9T$J$C$F$=$N7k2L$+$iA*Br$9$kJ}K!!#(B -
type-map $B%U%!%$%k$r;H$&(B
+
type-map $B%U%!%$%k$r;H$&(B

$B%?%$%W%^%C%W$O(B type-map $B%O%s%I%i(B ($B$b$7$/$O!"8E$$(B Apache @@ -104,7 +106,7 @@ $B$H$7$FDj5A$9$k$h$&$J%O%s%I%i$r!"(B $B@_Dj%U%!%$%kCf$KCV$/I,MW$,$"$k$3$H$KCm0U$7$F$/$@$5$$!#(B $B$3$l$O(B
-
AddHandler type-map .var
+
AddHandler type-map .var

$B$r%5!<%P@_Dj%U%!%$%kCf$K=q$/$3$H$,0lHVNI$$J}K!$G$9!#(B

$B%?%$%W%^%C%W%U%!%$%k$O5-=R$9$k%j%=!<%9$HF1$8L>A0$r;}$C$F$$$F!"(B @@ -117,17 +119,17 @@ $Bfoo $B$r5-=R$7$F$$$k$N$G!"(Bfoo.var $B$H$$$&L>A0$K$J$j$^$9!#(B
-
- URI: foo - - URI: foo.en.html - Content-type: text/html - Content-language: en - - URI: foo.fr.de.html - Content-type: text/html;charset=iso-8859-2 - Content-language: fr, de -
+
+ URI: foo + + URI: foo.en.html + Content-type: text/html + Content-language: en + + URI: foo.fr.de.html + Content-type: text/html;charset=iso-8859-2 + Content-language: fr, de +

$B$?$H$((B MultiViews $B$r;HMQ$9$k$h$&$K$J$C$F$$$?$H$7$F$b!"(B $B%U%!%$%kL>$N3HD%;R$h$j%?%$%W%^%C%W$NJ}$,M%@h8"$r;}$D$H$$$&$3$H$K$b(B $BCm0U$7$F$/$@$5$$!#(B @@ -135,18 +137,18 @@ $B%"!<%H$,$"$j$^$9(B) $B%a%G%#%"%?%$%W$N(B "qs" $B%Q%i%a!<%?$G;XDj$5$l$^$9!#(B
-
- URI: foo - - URI: foo.jpeg - Content-type: image/jpeg; qs=0.8 - - URI: foo.gif - Content-type: image/gif; qs=0.5 - - URI: foo.txt - Content-type: text/plain; qs=0.01 -
+
+ URI: foo + + URI: foo.jpeg + Content-type: image/jpeg; qs=0.8 + + URI: foo.gif + Content-type: image/gif; qs=0.5 + + URI: foo.txt + Content-type: text/plain; qs=0.01 +

qs $BCM$NHO0O$O(B 0.000 $B$+$i(B 1.000 $B$G$9!#(Bqs $BCM$,(B 0.000 $B$N(B variant $B$O7h$7$F(B @@ -168,15 +170,15 @@ $B%I%-%e%a%s%H$K$"$j$^$9!#(B
-
Multiviews
+
Multiviews

MultiViews $B$O%G%#%l%/%H%jKh$N%*%W%7%g%s$G!"(B - <Directory>, - <Location>, - <Files> - $B$d!"(B(AllowOverride + <Directory>, + <Location>, + <Files> + $B$d!"(B(AllowOverride $B$,E,@Z$JCM$K(B $B@_Dj$5$l$F$$$k$H(B) .htaccess - $B%U%!%$%k$G(B Options + $B%U%!%$%k$G(B Options $B%G%#%l%/%F%#%V$K$h$C$F@_Dj$9$k$3$H$,$G$-$^$9!#(B Options All $B$O(B MultiViews @@ -197,10 +199,10 @@
$B%5!<%P$,%G%#%l%/%H%j$N:w0z$r:n$m$&$H$7$F$$$k>l9g!"(B MultiViews - $B$O(B DirectoryIndex + $B$O(B DirectoryIndex $B%G%#%l%/%F%#%V$G;XDj$5$l$?%U%!%$%k$rC5$92aDx$K$b(B $BE,MQ$5$l$^$9!#@_Dj%U%!%$%k$K(B
-
DirectoryIndex index
+
DirectoryIndex index

$B$,=q$+$l$F$$$F!"(Bindex.html $B$H(B index.html3 $B$,(B $BN>J}B8:_$7$F$$$k$H!"%5!<%P$O$=$NCf$+$i$I$A$i$+$rE,Ev$KA*$S$^$9!#(B @@ -211,12 +213,12 @@ $BJ8;z%;%C%H!"%3%s%F%s%H%?%$%W!"8@8l!"%(%s%3!<%G%#%s%0$r(B $B;XDj$9$k$?$a$N(B mod_mime $B$GG'<1$G$-$k3HD%;R$r;}$?$J$$%U%!%$%k$,8+$D$+$k$H!"7k2L$O(B - MultiViewsMatch + MultiViewsMatch $B%G%#%l%/%F%#%V$N@_Dj$K0MB8$7$^$9!#$3$N%G%#%l%/%F%#%V$O(B $B%O%s%I%i!"%U%#%k%?!"B>$N%U%!%$%k3HD%;R%?%$%W$N$I$l$,(B MultiViews $B%M%4%7%(!<%7%g%s$G;HMQ$G$-$k$+$r7hDj$7$^$9!#(B
-
$B%M%4%7%(!<%7%g%sJ}K!(B
+
$B%M%4%7%(!<%7%g%sJ}K!(B

Apache $B$O%j%=!<%9$N(B variant $B$N0lMw$r!"%?%$%W%^%C%W%U%!%$%k$+(B $B%G%#%l%/%H%jFb$N%U%!%$%kL>$+$i$+$G -
$B%M%4%7%(!<%7%g%s$N
+
$B%M%4%7%(!<%7%g%s$N
@@ -298,7 +300,7 @@

-
Apache $B%M%4%7%(!<%7%g%s%"%k%4%j%:%`(B
+
Apache $B%M%4%7%(!<%7%g%s%"%k%4%j%:%`(B

$B%V%i%&%6$KJV$9!V:GE,$J!W(Bvariant $B$r(B ($B$b$7$"$l$P(B) $BA*Br$9$k$h$&$K(B Apache $B$O($B$b$7$"$l$P(B) Accept-Language $B%X%C%@$N8@8l=g$+!"(B ($B$b$7$"$l$P(B) - LanguagePriority + LanguagePriority $B%G%#%l%/%F%#%V$N8@8l=g$G:GE,$J8@8l$N(B variant $B$rA*$S$^$9!#(B
$B:G9b!V%l%Y%k!W$N%a%G%#%"%Q%i%a!<%?(B @@ -384,7 +386,7 @@ $BAj0c$N -
$BIJ
+
$BIJ

$B>e5-$N(B Apaceh $B%M%4%7%(!<%7%g%s%"%k%4%j%:%`$N873J$J2rpJs$rAw$C$F$$$l$P!"(B $B$3$N?tCMJQ2=$OE,MQ$5$l$^$;$s!#(B
-
$B%a%G%#%"%?%$%W$H%o%$%k%I%+!<%I(B
+
$B%a%G%#%"%?%$%W$H%o%$%k%I%+!<%I(B

Accept: $B%j%/%(%9%H%X%C%@$O%a%G%#%"%?%$%W$NM%@h798~$r;XDj$7$^$9!#(B $B$3$l$O$^$?!"(B"image/*" $B$d(B "*/*" @@ -404,7 +406,7 @@ $B$3$3$G(B * $B$OG$0U$NJ8;zNs$K%^%C%A$7$^$9!#(B $B$G$9$+$i!" -
Accept: image/*, */*
+
Accept: image/*, */*

$B$r4^$`%j%/%(%9%H$O!"(B"image/" $B$G$O$8$^$k%?%$%WA4$F$,5vMF$G$-$k!"(B $B$=$7$FB>$N$I$s$J%?%$%W$b5vMF$G$-$k(B @@ -413,18 +415,18 @@ $B07$&$3$H$N$G$-$kL@<(E*$J%?%$%W$K2C$($F!"5!3#E*$K(B $B%o%$%k%I%+!<%I$rAw$k%V%i%&%6$b$"$j$^$9!#Nc$($P(B:
-
+ Accept: text/html, text/plain, image/gif, image/jpeg, */* -
+

$B$3$&$9$k$3$H$NA@$$$O!"L@<(E*$K%j%9%H$7$F$$$k%?%$%W$,M%@h$5$l$k$1$l$I$b!"(B $B0[$J$kI=8=$,MxMQ2DG=$G$"$l$P$=$l$G$bNI$$!"$H$$$&$3$H$G$9!#(B $B$7$+$7$J$,$i!">e$N4pK\E*$J%"%k%4%j%:%`$G$O!"(B */* $B%o%$%k%I%+!<%I$OB>$NA4$F$N%?%$%W$HA4$/F1Ey$J$N$GM%@h$5$l$^$;$s!#(B $B%V%i%&%6$O(B */* $B$K$b$C$HDc$$IJ -
+ Accept: text/html, text/plain, image/gif, image/jpeg, */*; q=0.01 -
+

$BL@<(E*$J%?%$%W$K$OIJ -
$B8@8l%M%4%7%(!<%7%g%s$NNc30=hM}(B
+
$B8@8l%M%4%7%(!<%7%g%s$NNc30=hM}(B

Apache 2.0 $B$G$O?7$?$K!"8@8l%M%4%7%(!<%7%g%s$,E,9g$9$k$b$N$r(B $B8+$D$1$k$N$K<:GT$7$?;~$K!"M%2m$K%U%)!<%k%P%C%/$G$-$k$h$&$J(B @@ -456,10 +458,10 @@ $B$3$N$h$&$J>l9g$K$O(B Apache $B$,(B Accept-Language $B$rL5;k$7$F!"(B $B%/%i%$%"%s%H$N%j%/%(%9%H$KL@<(E*$K$O9gCW$7$J$$%I%-%e%a%s%H$r(B $BDs6!$9$k$h$&$K@_Dj$G$-$^$9!#(B - ForceLanguagePriority + ForceLanguagePriority $B%G%#%l%/%F%#%V$O!"$3$l$i$N%(%i!<$N0l$D$+N>J}$r%*!<%P!<%i%$%I$9$k$?$a$K(B $B;HMQ$G$-$F!"(B - LanguagePriority + LanguagePriority $B%G%#%l%/%F%#%V$NFbMF$r;H$C$F%5!<%P$NH=CG$rBe9T$9$k$h$&$K$G$-$^$9!#(B

$B%5!<%P$OB>$KE,9g$9$k$b$N$,8+$D$+$i$J$1$l$P!"(B @@ -476,7 +478,7 @@ $B$3$N$h$&$J@_Dj$K$J$C$F$$$^$9!#(B) $B$7$+$7$J$,$i!"B>$N8@8l$K$O%^%C%A$;$:!"(B"No Acceptable Variants" $B%(%i!<$rJV$7$?$j!"(B - LanguagePriority + LanguagePriority $B$K%U%)!<%k%P%C%/$7$h$&$H$7$F$$$k$H$-$O!"(B $B%5%V%;%C%H;XDj$rL5;k$7$F!"(Ben-GB $B$r(B en $B$K%^%C%A$7$^$9!#(B @@ -489,7 +491,7 @@ $BE,@Z$K@_Dj$5$l$?%/%i%$%"%s%H$H$b$-$A$s$HF0:n$9$k$?$a$K(B $BI,MW$G$9!#(B
-
Transparent Content Negotiation +
Transparent Content Negotiation $B$N3HD%(B

Apache $B$O(B transparent content negotiation $B%W%m%H%3%k(B @@ -504,7 +506,7 @@ Accept-Encoding $B%j%/%(%9%H%X%C%@$K=>$C$F5vMF$5$l$k(B RVSA/1.0 $B%"%k%4%j%:%`(B (RFC 2296) $B$N.?tE@0J2<(B 5 $B7e$^$G4]$a$^$;$s!#(B
-
$B%j%s%/$HL>A0$NJQ49$K4X$9$kCm0UE@(B
+
$B%j%s%/$HL>A0$NJQ49$K4X$9$kCm0UE@(B

$B8@8l%M%4%7%(!<%7%g%s$r;H$C$F$$$k>l9g$O!"(B $B%U%!%$%k$,0l$D0J>e$N3HD%;R$r;}$F$F!"(B @@ -532,7 +534,7 @@ RVSA/1.0 $B$N$B%U%!%$%kL>$H!"$=$l$KBP$7$F;H$($k%j%s%/$H;H$($J$$%j%s%/$NNc$G$9(B:
- +
@@ -544,7 +546,7 @@ RVSA/1.0 $B$N - @@ -561,10 +563,10 @@ RVSA/1.0 $B$N - - @@ -573,16 +575,16 @@ RVSA/1.0 $B$Nfoo - - @@ -591,8 +593,8 @@ RVSA/1.0 $B$N - @@ -612,7 +614,7 @@ RVSA/1.0 $B$N$BNc$($P(B foo.html.en)$B!#(B
-
$B%-%c%C%7%e$K4X$9$kCm0U;v9`(B
+
$B%-%c%C%7%e$K4X$9$kCm0U;v9`(B

$B%-%c%C%7%e$,0l$D$NI=8=$rJ]B8$7$F$$$k$H$-$O!"(B $B%j%/%(%9%H(B URL $B$H4XO"$E$1$i$l$F$$$^$9!#(B @@ -630,16 +632,16 @@ RVSA/1.0 $B$NHTTP/1.0 $B=`5r$N%/%i%$%"%s%H$+$i$N%j%/%(%9%H$KBP$7$F$O!"(B ($B%V%i%&%6$G$"$m$&$H%-%c%C%7%e$G$"$m$&$H(B) $B%M%4%7%(!<%7%g%s$rCacheNegotiatedDocs + CacheNegotiatedDocs $B%G%#%l%/%F%#%V$r;HMQ$G$-$^$9!#(B $B$3$N%G%#%l%/%F%#%V$O!"%5!<%P@_Dj%U%!%$%k$d%P!<%A%c%k%[%9%H$K=q$/$3$H$,$G$-!"(B $B0z?t$r$H$j$^$;$s!#(B HTTP/1.1 $B%/%i%$%"%s%H$+$i$N%j%/%(%9%H$K$O8zNO$r;}$A$^$;$s!#(B
-
$BDI2C>pJs(B
+
$BDI2C>pJs(B

$B%3%s%F%s%H%M%4%7%(!<%7%g%s$K4X$9$kDI2C>pJs$O!"(B Alan J. Flavell $B$5$s$N(BLanguage Negotiation Notes $B$r$4Mw2<$5$$!#$G$9$,!"(B Apache 2.0 $B$G$NJQ99E@$r4^$`$?$a$K$O99?7$5$l$F$$$J$$$+$b$7$l$J$$(B $B$H$$$&$3$H$KCm0U$7$F$/$@$5$$!#(B
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/dso.html.en b/docs/manual/dso.html.en index 8784a5a77a..8f537e788f 100644 --- a/docs/manual/dso.html.en +++ b/docs/manual/dso.html.en @@ -1,8 +1,10 @@ -Dynamic Shared Object (DSO) Support - Apache HTTP Server
Apache HTTP Server Version 2.0
Dynamic Shared Object (DSO) Support
+ -->Dynamic Shared Object (DSO) Support - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Dynamic Shared Object (DSO) Support

The Apache HTTP Server is a modular program where the administrator can choose the functionality to include in the server by selecting a set of modules. The modules can be @@ -16,21 +18,21 @@
This document describes how to use DSO modules as well as the theory behind their use.
-
Implementation
Usage Summary
Background
Advantages and Disadvantages
Implementation
+
Implementation
Usage Summary
Background
Advantages and Disadvantages
Implementation
-

$B%U%!%$%kL>(B foo.html.en foo
+ foo
foo.html - foo.html.en.gz foo
+ foo
foo.html foo.gz
+ foo.gz
foo.html.gz
foo.html
- foo.html.gz
+ foo.html
+ foo.html.gz
foo.gz

foo.gz.html.en foo
- foo.gz
+ foo
+ foo.gz
foo.gz.html foo.html foo.html.gz.en foo
- foo.html
+ foo
+ foo.html
foo.html.gz foo.gz
Related Modules

mod_so
Related Directives

LoadModule
+
Related Modules Related Directives
mod_so
LoadModule

The DSO support for loading individual Apache modules is based - on a module named mod_so which must be statically + on a module named mod_so which must be statically compiled into the Apache core. It is the only module besides - core which cannot be put into a DSO + core which cannot be put into a DSO itself. Practically all other distributed Apache modules can then be placed into a DSO by individually enabling the DSO build for them via configure's --enable-module=shared option as disucussed in the install documentation. After a module is compiled into a DSO named mod_foo.so you - can use mod_so's LoadModule command in your + can use mod_so's LoadModule command in your httpd.conf file to load this module at server startup or restart.
@@ -48,7 +50,7 @@ source tree and without having to fiddle with the platform-dependent compiler and linker flags for DSO support.
-
Usage Summary
+
Usage Summary

To give you an overview of the DSO features of Apache 2.0, here is a short and concise summary:
@@ -59,10 +61,10 @@ mod_foo.c, into its own DSO mod_foo.so: -
-$ ./configure --prefix=/path/to/install --enable-foo=shared + +$ ./configure --prefix=/path/to/install --enable-foo=shared $ make install -
+

@@ -70,20 +72,20 @@ $ make install mod_foo.c, into its own DSO mod_foo.so: -
-$ ./configure --add-module=module_type:/path/to/3rdparty/mod_foo.c --enable-foo=shared + +$ ./configure --add-module=module_type:/path/to/3rdparty/mod_foo.c --enable-foo=shared $ make install -
+

Configure Apache for later installation of shared modules: -
-$ ./configure --enable-so + +$ ./configure --enable-so $ make install -
+

@@ -92,19 +94,19 @@ $ make install mod_foo.so outside of the Apache source tree using apxs: -
-$ cd /path/to/3rdparty -$ apxs -c mod_foo.c + +$ cd /path/to/3rdparty +$ apxs -c mod_foo.c $ apxs -i -a -n foo mod_foo.la -
+

In all cases, once the shared module is compiled, you must - use a LoadModule + use a LoadModule directive in httpd.conf to tell Apache to activate the module.
-
Background
+
Background

On modern Unix derivatives there exists a nifty mechanism usually called dynamic linking/loading of Dynamic Shared @@ -204,7 +206,7 @@ $ apxs -i -a -n foo mod_foo.la modules into the Apache core functionality. So, Apache is really predestined for using DSO to load its modules at run-time.
-
Advantages and Disadvantages
+
Advantages and Disadvantages

The above DSO based features have the following advantages:
@@ -212,7 +214,7 @@ $ apxs -i -a -n foo mod_foo.la

The server package is more flexible at run-time because the actual server process can be assembled at run-time via - LoadModule + LoadModule httpd.conf configuration commands instead of configure options at build-time. For instance this way one is able to run different server instances @@ -267,4 +269,4 @@ $ apxs -i -a -n foo mod_foo.la loading the code yourself via dlopen().

-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/env.html.en b/docs/manual/env.html.en index d5235e61d7..d34e6da803 100644 --- a/docs/manual/env.html.en +++ b/docs/manual/env.html.en @@ -1,8 +1,10 @@ -Environment Variables in Apache - Apache HTTP Server
Apache HTTP Server Version 2.0
Environment Variables in Apache
+ -->Environment Variables in Apache - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Environment Variables in Apache

The Apache HTTP Server provides a mechanism for storing information in named variables that are called environment variables. This information can be used to control various @@ -22,20 +24,20 @@ server itself runs, you must use the standard environment manipulation mechanisms provided by your operating system shell.
-
Setting Environment Variables
Basic Environment Manipulation
Conditional Per-Request Settings
Unique Identifiers
Standard CGI Variables
Some Caveats
Using Environment Variables
CGI Scripts
SSI Pages
Access Control
Conditional Logging
Conditional Response Headers
External Filter Activation
URL Rewriting
Special Purpose Environment Variables
downgrade-1.0
force-no-vary
force-response-1.0
gzip-only-text/html
nokeepalive
redirect-carefully
suppress-error-charset
Examples
Changing protocol behavior with misbehaving clients
Do not log requests for images in the access log
Prevent "Image Theft"
Setting Environment Variables
+
Setting Environment Variables
Using Environment Variables
Special Purpose Environment Variables
Examples
Setting Environment Variables
-
Related Modules

mod_env
mod_rewrite
mod_setenvif
mod_unique_id
Related Directives

BrowserMatch
BrowserMatchNoCase
PassEnv
RewriteRule
SetEnv
SetEnvIf
SetEnvIfNoCase
UnsetEnv
+
Related Modules Related Directives
mod_env
mod_rewrite
mod_setenvif
mod_unique_id
BrowserMatch
BrowserMatchNoCase
PassEnv
RewriteRule
SetEnv
SetEnvIf
SetEnvIfNoCase
UnsetEnv
-
Basic Environment Manipulation
+
Basic Environment Manipulation

The most basic way to set an environment variable in Apache - is using the unconditional SetEnv directive. Variables may also be passed from + is using the unconditional SetEnv directive. Variables may also be passed from the environment of the shell which started the server using the - PassEnv directive.
+ PassEnv directive.
-
Conditional Per-Request Settings
+
Conditional Per-Request Settings

For additional flexibility, the directives provided by @@ -44,11 +46,11 @@ requests. For example, a variable could be set only when a specific browser (User-Agent) is making a request, or only when a specific Referer [sic] header is found. Even more flexibility - is available through the mod_rewrite's RewriteRule which uses the + is available through the mod_rewrite's RewriteRule which uses the [E=...] option to set environment variables.
-
Unique Identifiers
+
Unique Identifiers

Finally, mod_unique_id sets the environment variable @@ -57,7 +59,7 @@ specific conditions.
-
Standard CGI Variables
+
Standard CGI Variables

In addition to all environment variables set within the @@ -68,7 +70,7 @@ specification.
-
Some Caveats
+
Some Caveats

@@ -89,12 +91,12 @@ CGI scripts and SSI pages.
-
Using Environment Variables
+
Using Environment Variables
-
Related Modules

mod_access
mod_cgi
mod_ext_filter
mod_headers
mod_include
mod_log_config
mod_rewrite
Related Directives

Allow
CustomLog
Deny
ExtFilterDefine
Header
LogFormat
RewriteCond
RewriteRule
+
Related Modules Related Directives
mod_access
mod_cgi
mod_ext_filter
mod_headers
mod_include
mod_log_config
mod_rewrite
Allow
CustomLog
Deny
ExtFilterDefine
Header
LogFormat
RewriteCond
RewriteRule
-
CGI Scripts
+
CGI Scripts

One of the primary uses of environment variables is to @@ -105,7 +107,7 @@ CGI tutorial.
-
SSI Pages
+
SSI Pages

Server-parsed (SSI) documents processed by mod_include's @@ -117,39 +119,39 @@ as discussed above. For more details, see the SSI tutorial.
-
Access Control
+
Access Control

Access to the server can be controlled based on the value of environment variables using the allow from env= and deny from env= directives. In combination with - SetEnvIf, this + SetEnvIf, this allows for flexible control of access to the server based on characteristics of the client. For example, you can use these directives to deny access to a particular browser (User-Agent).
-
Conditional Logging
+
Conditional Logging

Environment variables can be logged in the access log using - the LogFormat + the LogFormat option %e. In addition, the decision on whether or not to log requests can be made based on the status of environment variables using the conditional form of the - CustomLog - directive. In combination with SetEnvIf this allows for flexible control of which + CustomLog + directive. In combination with SetEnvIf this allows for flexible control of which requests are logged. For example, you can choose not to log requests for filenames ending in gif, or you can choose to only log requests from clients which are outside your subnet.
-
Conditional Response Headers
+
Conditional Response Headers
-
The Header +
The Header directive can use the presence or absence of an environment variable to determine whether or not a certain HTTP header will be placed in the response to the @@ -159,20 +161,20 @@ -
External Filter Activation
+
External Filter Activation
-
External filters configured by mod_ext_filter - using the ExtFilterDefine directive can +
External filters configured by mod_ext_filter + using the ExtFilterDefine directive can by activated conditional on an environment variable using the disableenv= and enableenv= options.
-
URL Rewriting
+
URL Rewriting

The %{ENV:...} form of TestString in - the RewriteCond + the RewriteCond allows mod_rewrite's rewrite engine to make decisions conditional on environment variables. Note that the variables accessible in mod_rewrite without the @@ -180,26 +182,26 @@ variables. Rather, they are variables special to mod_rewrite which cannot be accessed from other modules.
-
Special Purpose Environment Variables
+
Special Purpose Environment Variables

Interoperability problems have led to the introduction of mechanisms to modify the way Apache behaves when talking to particular clients. To make these mechanisms as flexible as possible, they are invoked by defining environment variables, - typically with BrowserMatch, - though SetEnv and - PassEnv could also be used, + typically with BrowserMatch, + though SetEnv and + PassEnv could also be used, for example.
-
downgrade-1.0
+
downgrade-1.0

This forces the request to be treated as a HTTP/1.0 request even if it was in a later dialect.
-
force-no-vary
+
force-no-vary

This causes any Vary fields to be removed from @@ -210,7 +212,7 @@ force-response-1.0.
-
force-response-1.0
+
force-response-1.0

This forces an HTTP/1.0 response when set. It was originally @@ -219,21 +221,21 @@ response, and this can be used to interoperate with them.
-
gzip-only-text/html
+
gzip-only-text/html

When set to a value of "1", this variable disables the DEFLATE - output filter provided by mod_deflate for + output filter provided by mod_deflate for content-types other than text/html.
-
nokeepalive
+
nokeepalive
-
This disables KeepAlive when set.
+
This disables KeepAlive when set.
-
redirect-carefully
+
redirect-carefully

This forces the server to be more careful when sending a redirect @@ -245,7 +247,7 @@ -
suppress-error-charset
+
suppress-error-charset

Available in versions after 2.0.40
@@ -265,15 +267,15 @@ -
Examples
+
Examples
-
Changing protocol behavior with misbehaving clients
+
Changing protocol behavior with misbehaving clients

We recommend that the following lines be included in httpd.conf to deal with known client problems.
-
+
# # The following directives modify normal HTTP response behavior. # The first directive disables keepalive for Netscape 2.x and browsers that @@ -292,24 +294,24 @@ BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0 # BrowserMatch "RealPlayer 4\.0" force-response-1.0 BrowserMatch "Java/1\.0" force-response-1.0 -BrowserMatch "JDK/1\.0" force-response-1.0
+BrowserMatch "JDK/1\.0" force-response-1.0
-
Do not log requests for images in the access log
+
Do not log requests for images in the access log

This example keeps requests for images from appearing in the access log. It can be easily modified to prevent logging of particular directories, or to prevent logging of requests coming from particular hosts.
-
+
SetEnvIf Request_URI \.gif image-request SetEnvIf Request_URI \.jpg image-request SetEnvIf Request_URI \.png image-request -CustomLog logs/access_log common env=!image-request
+CustomLog logs/access_log common env=!image-request
-
Prevent "Image Theft"
+
Prevent "Image Theft"

This example shows how to keep people not on your server @@ -317,7 +319,7 @@ CustomLog logs/access_log common env=!image-request -
+
SetEnvIf Referer "^http://www.example.com/" local_referal # Allow browsers that do not send Referer info SetEnvIf Referer "^$" local_referal @@ -325,10 +327,10 @@ SetEnvIf Referer "^$" local_referal Order Deny,Allow Deny from all Allow from env=local_referal -</Directory>
+</Directory>
For more information about this technique, see the ApacheToday tutorial " Keeping Your Images from Adorning Other Sites".
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/filter.html.ja.jis b/docs/manual/filter.html.ja.jis index 8d7734cb75..5cf1cbf9b3 100644 --- a/docs/manual/filter.html.ja.jis +++ b/docs/manual/filter.html.ja.jis @@ -1,30 +1,32 @@ -$B%U%#%k%?(B - Apache HTTP Server
Apache HTTP Server Version 2.0
$B%U%#%k%?(B
-
Apache $B$G$N%U%#%k(B$B%?$N;H$$J}$K$D$$$F5-=R$7$F$$$^$9!#(B
-
$B%U%#%k(B$B%?(B
+ -->$B%U%#%k%?(B - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
$B%U%#%k%?(B
+
Apache $B$G$N%U%#%k%?$N;H$$J}$K$D$$$F5-=R$7$F$$$^$9!#(B
+
$B%U%#%k%?(B
-
$B4XO"%b%8%e!<%k(B

mod_deflate
mod_ext_filter
mod_include
$B4XO"%G%#%l%/%F%#%V(B

AddInputFilter
AddOutputFilter
ExtFilterDefine
ExtFilterOptions
SetInputFilter
SetOutputFilter
+
$B4XO"%b%8%e!<%k(B $B4XO"%G%#%l%/%F%#%V(B
mod_deflate
mod_ext_filter
mod_include
AddInputFilter
AddOutputFilter
ExtFilterDefine
ExtFilterOptions
SetInputFilter
SetOutputFilter

$B%U%#%k%?(B $B$H$O!"%5!<%P$,Aw$BF~NO%U%#%k%?(B $B$K$h$C$F!"%5!<%P$+$i(B + $BAw$i$l$?%G!<%?$O(B $BF~NO%U%#%k%?(B $B$K$h$C$F!"%5!<%P$+$i(B $B%/%i%$%"%s%H$KAw$i$l$k%G!<%?$O(B$B=PNO%U%#%k%?(B$B$K$h$C$F(B $B=hM}$5$l$^$9!#J#?t$N%U%#%k%?$rE,MQ$9$k$3$H$,$G$-!"(B $B$=$N=gHV$r87L)$K;XDj$9$k$3$H$b$G$-$^$9!#(B
-
Apache $BFbIt$G$O!"%A(B$B%c%s%/(B ($B%G!<%?$N$V$D@Z$j(B) $B$r9T$C$?$j!"(B +
Apache $BFbIt$G$O!"%A%c%s%/(B ($B%G!<%?$N$V$D@Z$j(B) $B$r9T$C$?$j!"(B $B%P%$%HHO0O$N;XDj$5$l$?%j%/%(%9%H$r07$C$?$j$H$$$C$?5!G=$r(B $B9T$&:]$K!"%U%#%k%?$,;H$o$l$F$$$^$9!#$=$l$K2C$($F!"(B $BSetInputFilter, - SetOutputFilter, - AddInputFilter, - AddOutputFilter + SetInputFilter, + SetOutputFilter, + AddInputFilter, + AddOutputFilter $B%G%#%l%/%F%#%V$G@)8f$G$-$^$9!#(B

$B8=9T$N(B Apache HTTP $B%5!<%P$NG[I[$G$O!"(B @@ -32,12 +34,12 @@

INCLUDES
-
mod_include $B$G(B Server-Side Include $B$r$7$^$9!#(B
+
mod_include $B$G(B Server-Side Include $B$r$7$^$9!#(B

DEFLATE
-
mod_deflate +
mod_deflate $B$r;H$C$F!"%/%i%$%"%s%H$KAw?.$9$kA0$K=PNO$r05=L$7$^$9!#(B

-
$B$^$?!"(Bmod_ext_filter $B%b%8%e!<%k$G(B - $B30It%W%m%0%i%`$r%U%#%k%?$H$7$F;XDj$9$k$3$H$,(B$B$G$-$^$9!#(B
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
$B$^$?!"(Bmod_ext_filter $B%b%8%e!<%k$G(B + $B30It%W%m%0%i%`$r%U%#%k%?$H$7$F;XDj$9$k$3$H$,$G$-$^$9!#(B
+
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/handler.html.en b/docs/manual/handler.html.en index a17d135beb..ab5d3b7b59 100644 --- a/docs/manual/handler.html.en +++ b/docs/manual/handler.html.en @@ -1,12 +1,14 @@ -Apache's Handler Use - Apache HTTP Server
Apache HTTP Server Version 2.0
Apache's Handler Use
+ -->Apache's Handler Use - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Apache's Handler Use

This document describes the use of Apache's Handlers.
-
What is a Handler
Examples
Modifying static content using a CGI script
Files with HTTP headers
Programmer's Note
What is a Handler
+
What is a Handler
Examples
Programmer's Note
What is a Handler
-
Related Modules

mod_actions
mod_asis
mod_cgi
mod_imap
mod_info
mod_mime
mod_negotiation
mod_status
Related Directives

Action
AddHandler
RemoveHandler
SetHandler
+
Related Modules Related Directives
mod_actions
mod_asis
mod_cgi
mod_imap
mod_info
mod_mime
mod_negotiation
mod_status
Action
AddHandler
RemoveHandler
SetHandler

A "handler" is an internal Apache representation of the @@ -24,7 +26,7 @@ Extensions.)

Handlers can either be built into the server or included in - a module, or they can be added with the Action directive. The + a module, or they can be added with the Action directive. The built-in handlers in the standard distribution are as follows:
@@ -34,37 +36,37 @@ default to handle static content. (core)
send-as-is: Send file with HTTP headers - as is. (mod_asis)
+ as is. (mod_asis)
cgi-script: Treat the file as a CGI - script. (mod_cgi)
+ script. (mod_cgi)
imap-file: Parse as an imagemap rule - file. (mod_imap)
+ file. (mod_imap)
server-info: Get the server's - configuration information. (mod_info)
+ configuration information. (mod_info)
server-status: Get the server's status - report. (mod_status)
+ report. (mod_status)
type-map: Parse as a type map file for - content negotiation. (mod_negotiation)
+ content negotiation. (mod_negotiation) -
Examples
+
Examples
-
Modifying static content using a CGI script
+
Modifying static content using a CGI script

The following directives will cause requests for files with the html extension to trigger the launch of the footer.pl CGI script.
-
- Action add-footer /cgi-bin/footer.pl + + Action add-footer /cgi-bin/footer.pl AddHandler add-footer .html -
+

Then the CGI script is responsible for sending the originally requested document (pointed to by the @@ -72,7 +74,7 @@ whatever modifications or additions are desired.
-
Files with HTTP headers
+
Files with HTTP headers

The following directives will enable the @@ -82,14 +84,14 @@ the send-as-is handler, regardless of their filename extensions.
-
- <Directory /web/htdocs/asis> - SetHandler send-as-is + + <Directory /web/htdocs/asis> + SetHandler send-as-is </Directory> -
+
-
Programmer's Note
+
Programmer's Note

In order to implement the handler features, an addition has @@ -108,4 +110,4 @@ type. While it is not necessary, the naming convention for handlers is to use a dash-separated word, with no slashes, so as to not invade the media type name-space.
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/install.html.en b/docs/manual/install.html.en index 33b8e7fbcb..4273d5e0ca 100644 --- a/docs/manual/install.html.en +++ b/docs/manual/install.html.en @@ -1,8 +1,10 @@ -Compiling and Installing - Apache HTTP Server
Apache HTTP Server Version 2.0
Compiling and Installing
+ -->Compiling and Installing - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Compiling and Installing

This document covers compilation and installation of Apache on Unix and Unix-like systems only. For compiling and @@ -15,8 +17,8 @@ uses libtool and autoconf to create an environment that looks like many other Open Source projects.
-
Overview for the - impatient
Requirements
Download
Extract
Configuring the source tree
Environment Variables
autoconf Output Options
Pathnames
Modules
DBM
Suexec
Build
Install
Customize
Test
Overview for the +
Overview for the + impatient
Requirements
Download
Extract
Configuring the source tree
Build
Install
Customize
Test
Overview for the impatient
@@ -31,7 +33,7 @@ - @@ -77,34 +79,34 @@
Each section of the compilation and installation process is described in more detail below, beginning with the requirements for compiling and installing Apache HTTPD.
-
Requirements
+
Requirements

The following requirements exist for building Apache:

-
Disk Space
-
+
Disk Space
+
Make sure you have at least 50 MB of temporary free disk space available. After installation Apache occupies approximately 10 MB of disk space. The actual disk space requirements will vary considerably based on your chosen - configuration options and any third-party modules.
-
+ configuration options and any third-party modules.
+

-
ANSI-C Compiler and Build System
-
+
ANSI-C Compiler and Build System
+
Make sure you have an ANSI-C compiler installed. The GNU C compiler (GCC) from the Free Software Foundation (FSF) is recommended (version 2.7.2 is fine). If you don't have GCC then at least make sure your vendor's compiler is ANSI compliant. In addition, your PATH must contain - basic build tools such as make.
-
+ basic build tools such as make.
+

-
Accurate time keeping
-
+
Accurate time keeping
+
Elements of the HTTP protocol are expressed as the time of day. So, it's time to investigate setting some time synchronization facility on your system. Usually the ntpdate @@ -113,13 +115,13 @@ comp.protocols.time.ntp and the NTP homepage for more details about NTP software and public - time servers.
-
+ time servers.
+

Perl 5 - [OPTIONAL]
-
+ [OPTIONAL]
+
For some of the support scripts like apxs or dbmmanage (which are written in Perl) the Perl 5 interpreter is required (versions 5.003 and 5.004 are fine). If no such interpreter is found by @@ -129,11 +131,11 @@ installed (perhaps a Perl 4 from the vendor and a Perl 5 from your own), then it is recommended to use the --with-perl option (see below) to make sure the correct one is selected - by ./configure.
-
+ by ./configure.
+

-
Download
+
Download

Apache can be downloaded from the Apache Software Foundation download site or from a nearby @@ -161,11 +163,11 @@ key ring using one of the following commands (depending on your pgp version):
-
Extract $ gzip -d httpd-2_0_NN.tar.gz + $ gzip -d httpd-2_0_NN.tar.gz $ tar xvf httpd-2_0_NN.tar
$ pgp < KEYS
+
$ pgp < KEYS

or
-
$ gpg --import KEYS
+
$ gpg --import KEYS

The next step is to test the tarball against the PGP signature, which should always be obtained from the main Apache @@ -174,16 +176,16 @@ can check the distribution with one of the following commands (again, depending on your pgp version):
-
$ pgp httpd-2_0_NN.tar.gz.asc
+
$ pgp httpd-2_0_NN.tar.gz.asc

or
-
$ gpg --verify httpd-2_0_NN.tar.gz.asc
+
$ gpg --verify httpd-2_0_NN.tar.gz.asc

You should receive a message like
-
Good signature from user "Martin Kraemer - <martin@apache.org>".
+
Good signature from user "Martin Kraemer + <martin@apache.org>".

Depending on the trust relationships contained in your key ring, you may also receive a message saying that the @@ -191,21 +193,21 @@ be verified. This is not a problem if you trust the authenticity of the KEYS file.
-
Extract
+
Extract

Extracting the source from the Apache HTTPD tarball is a simple matter of uncompressing, and then untarring:
-
- $ gzip -d httpd-2_0_NN.tar.gz + + $ gzip -d httpd-2_0_NN.tar.gz $ tar xvf httpd-2_0_NN.tar -
+

This will create a new directory under the current directory containing the source code for the distribution. You should cd into that directory before proceeding with compiling the server.
-
Configuring the source tree
+
Configuring the source tree

The next step is to configure the Apache source tree for your particular platform and personal requirements. This is @@ -234,12 +236,12 @@ the two additional modules mod_rewrite and mod_speling for later loading through the DSO mechanism:
-
- $ CC="pgcc" CFLAGS="-O2" \ - ./configure --prefix=/sw/pkg/apache \ - --enable-rewrite=shared \ + + $ CC="pgcc" CFLAGS="-O2" \ + ./configure --prefix=/sw/pkg/apache \ + --enable-rewrite=shared \ --enable-speling=shared -
+

When configure is run it will take several minutes to test for the availability of features on your system and build @@ -250,7 +252,7 @@ description of most of the arguments and environment variables.
-
Environment Variables
+
Environment Variables

The autoconf build process uses several environment variables to configure the build environment. In general, these @@ -314,7 +316,7 @@ -
autoconf Output Options
+
autoconf Output Options

--help
@@ -334,7 +336,7 @@
-
Pathnames
+
Pathnames

There are currently two ways to configure the pathnames under which Apache will install its files. First, you can @@ -389,7 +391,7 @@ --enable-layout option.
-
Modules
+
Modules

Apache is a modular server. Only the most basic functionality is included in the core server. Extended features @@ -409,7 +411,7 @@ modules may be dynamically compiled. DSO modules are stored separately from the Apache binary, and may be included or excluded from the server using the run-time configuration - directives provided by mod_so. + directives provided by mod_so. The mod_so is automatically included in the server if any dynamic modules are included in the compilation. If you would like to make your server capable of loading DSOs without @@ -449,11 +451,11 @@ space-separated list of module identifiers. For example, to enable mod_dav and mod_info, you can either use
-
./configure --enable-dav --enable-info
+
./configure --enable-dav --enable-info

or, equivalently,
-
./configure --enable-modules="dav info"
+
./configure --enable-modules="dav info"

In addition, the special keywords all or most can be used to add all or most of the modules @@ -462,10 +464,10 @@ For example, to include all modules as DSOs with the exception of mod_info, you can use
-
+ ./configure --enable-mods-shared=all --disable-info -
+

In addition to the standard set of modules, Apache 2.0 also includes a choice of Multi-Processing @@ -482,11 +484,11 @@ -
DBM
+
DBM

Several Apache features, including - mod_auth_dbm and mod_rewrite's - DBM RewriteMap use + mod_auth_dbm and mod_rewrite's + DBM RewriteMap use simple key/value databases for quick lookups of information. Apache includes SDBM with its source-code, so this database is always available. If you would like to use other database types, the @@ -508,7 +510,7 @@ seperated by a colon. -
Suexec
+
Suexec

Apache includes a support program called suexec which can be used to isolate user CGI programs. However, if suexec is improperly configured, it @@ -516,50 +518,50 @@ seperated by a colon. carefully read and consider the suexec documentation before implementing this feature.
-
Build
+
Build

Now you can build the various parts which form the Apache package by simply running the command:
-
$ make
+
$ make

Please be patient here, since a base configuration takes approximately 3 minutes to compile under a Pentium III/Linux 2.2 system, but this will vary widely depending on your hardware and the number of modules which you have enabled.
-
Install
+
Install

Now its time to install the package under the configured installation PREFIX (see --prefix option above) by running:
-
$ make install
+
$ make install

If you are upgrading, the installation will not overwrite your configuration files or documents.
-
Customize
+
Customize

Next, you can customize your Apache HTTP server by editing the configuration files under PREFIX/conf/.
-
$ vi PREFIX/conf/httpd.conf
+
$ vi PREFIX/conf/httpd.conf

Have a look at the Apache manual under docs/manual/ or http://httpd.apache.org/docs-2.0/ for a complete reference of available configuration directives.
-
Test
+
Test

Now you can start your Apache HTTP server by immediately running:
-
$ PREFIX/bin/apachectl start
+
$ PREFIX/bin/apachectl start

and then you should be able to request your first document via URL http://localhost/. The web page you see is located - under the DocumentRoot + under the DocumentRoot which will usually be PREFIX/htdocs/. Then stop the server again by running:
-
$ PREFIX/bin/apachectl stop
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
$ PREFIX/bin/apachectl stop
+
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/invoking.html.en b/docs/manual/invoking.html.en index f7933d0add..074abe3705 100644 --- a/docs/manual/invoking.html.en +++ b/docs/manual/invoking.html.en @@ -1,8 +1,10 @@ -Starting Apache - Apache HTTP Server
Apache HTTP Server Version 2.0
Starting Apache
+ -->Starting Apache - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Starting Apache

On Windows, Apache is normally run as a service on Windows NT, or as a console application on Windows 95. For details, see running Apache for @@ -12,9 +14,9 @@ is run as a daemon that executes continuously in the background to handle requests. This document describes how to invoke httpd.
-
How Apache Starts
Errors During Start-up
Starting at Boot-Time
Additional Information
How Apache Starts
+
How Apache Starts
Errors During Start-up
Starting at Boot-Time
Additional Information
How Apache Starts
-
If the Listen +
If the Listen specified in the configuration file is default of 80 (or any other port below 1024), then it is necessary to have root privileges in order to start apache, so that it can bind to this privileged @@ -32,8 +34,8 @@ compile-time, but it is possible to specify its location at run time using the -f command-line option as in
-
/usr/local/apache/bin/httpd -f - /usr/local/apache/conf/httpd.conf
+
/usr/local/apache/bin/httpd -f + /usr/local/apache/conf/httpd.conf

As an alternative to invoking the httpd binary directly, a shell script called apachectl is provided which @@ -45,14 +47,14 @@ the terminal and the command prompt will return almost immediately. This indicates that the server is up and running. You can then use your browser to connect to the server and view - the test page in the DocumentRoot directory + the test page in the DocumentRoot directory and the local copy of the documentation linked from that page.
-
Errors During Start-up
+
Errors During Start-up

If Apache suffers a fatal problem during startup, it will write a message describing the problem either to the console or - to the ErrorLog before + to the ErrorLog before exiting. One of the most common error messages is "Unable to bind to Port ...". This message is usually caused by either:
@@ -68,7 +70,7 @@
For further trouble-shooting instructions, consult the Apache FAQ.
-
Starting at Boot-Time
+
Starting at Boot-Time

If you want your server to continue running after a system reboot, you should add a call to httpd or @@ -80,7 +82,7 @@ designed so that it can often be linked directly as an init script, but be sure to check the exact requirements of your system.
-
Additional Information
+
Additional Information

Additional information about the command-line options of httpd and apachectl as well as other support programs included with the server is available on the @@ -88,4 +90,4 @@ There is also documentation on all the modules included with the Apache distribution and the directives that they provide.
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/invoking.html.ja.jis b/docs/manual/invoking.html.ja.jis index 7a3b8a80b7..93750b3867 100644 --- a/docs/manual/invoking.html.ja.jis +++ b/docs/manual/invoking.html.ja.jis @@ -1,24 +1,26 @@ -Apache $B$N5/F0(B - Apache HTTP Server
Apache HTTP Server Version 2.0
Apache $B$N5/F0(B
-
Windows $B>e(B$B$G$O!"(BApache $B$ODL>o$O(B - Windows NT $B$G$O(B$B%5!<%S%9$H$7$F!"(BWindows 95 - $B$G$O%3%s%=!<%k%"(B$B%W%j%1!<%7%g%s$H$7$FApache $B$N5/F0(B - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Apache $B$N5/F0(B
+
Windows $B>e$G$O!"(BApache $B$ODL>o$O(B + Windows NT $B$G$O%5!<%S%9$H$7$F!"(BWindows 95 + $B$G$O%3%s%=!<%k%"%W%j%1!<%7%g%s$H$7$F\:Y$K4X$7$F$O!"!V(B Windows $B$G(B Apache $B$r$B!W$r$4Mw2<$5$$!#(B

Unix$B$G$O!"(B httpd $B%W%m%0%i%`$,!"%P%C%/%0%i%&%s%I$G>o$K%j%/%(%9%H=hM}$r9T$&(B $B%G!<%b%s$H$7$Fhttpd $B$r(B$B5/F0$9$k$+$K$D$$$F5-=R$7$F$$$^$9!#(B
-
Apache $B$N5/F0J}K!(B
$B5/F0;~$N%(%i!<(B
$B%V!<%H;~$N5/F0(B
$BDI2C>pJs(B
Apache $B$N5/F0J}K!(B
+ httpd $B$r5/F0$9$k$+$K$D$$$F5-=R$7$F$$$^$9!#(B
+
Apache $B$N5/F0J}K!(B
$B5/F0;~$N%(%i!<(B
$B%V!<%H;~$N5/F0(B
$BDI2C>pJs(B
Apache $B$N5/F0J}K!(B

$B$b$7!"@_Dj%U%!%$%kCf$G;XDj$5$l$F$$$k(B - Listen + Listen $B$,%G%U%)%k%H$N(B 80 ($B$b$7$/$O(B 1024 $B0J2<$NB>$N%]!<%H(B) - $B$G$"$k>l9g$O!"(BApache $B$r5/F0$9$k$?(B$B$a$K$O(B root + $B$G$"$k>l9g$O!"(BApache $B$r5/F0$9$k$?$a$K$O(B root $B8"8B$,I,MW$K$J$j$^$9$,!"(B $B$3$l$O$3$NFC8"%]!<%H$K%P%$%s%I$9$k$?$a$G$9!#(B $B5/F0$7$F!"0lEY%m%0%U%!%$%k$r3+$/$H$$$C$?=`Hw$N$?$a$N(B @@ -35,8 +37,8 @@ -f $B%3%^%s%I%i%$%s%*%W%7%g%s$r;H$C$F(B $B0LCV$r;XDj$9$k$3$H$b$G$-$^$9!#Nc$($P -
/usr/local/apache/bin/httpd -f - /usr/local/apache/conf/httpd.conf
+
/usr/local/apache/bin/httpd -f + /usr/local/apache/conf/httpd.conf

httpd $B$N%P%$%J%j$rD>@\5/F0$9$kBe$o$j$K!"(B apachectl @@ -45,18 +47,18 @@ $B$H$$$C$?4JC1$J%3%^%s%I$G!"(B $B%G!<%b%s%W%m%;%9$r@)8f$9$k$N$K;H$($^$9!#(B
-
$B%9%?(B$B!<%H%"%C%W$,K|;v>e$B%9%?!<%H%"%C%W$,K|;v>euBV$r<($7$F$$$^$9!#(B $B$=$N8e$O%V%i%&%6$G%5!<%P$K@\B3$7$F!"(B - DocumentRoot + DocumentRoot $B%G%#%l%/%H%j$N%F%9%H%Z!<%8$d$=$3$+$i%j%s%/$5$l$F$$$k(B $B%m!<%+%k$N%I%-%e%a%s%H$r8+$k$3$H$,$G$-$k$G$7$g$&!#(B
-
$B5/F0;~$N%(%i!<(B
+
$B5/F0;~$N%(%i!<(B

Apache $B$O!"5/F0;~$KCWL?E*$JLdBj$KAx6x$9$k$H!"(B $B=*N;$9$kA0$K!"%3%s%=!<%k$+(B - ErrorLog + ErrorLog $B$N$I$A$i$+$KLdBj$r5-=R$7$?%a%C%;!<%8$r=PNO$7$^$9!#(B $B:G$b$h$/$"$k%(%i!<%a%C%;!<%8$O(B $B!V(BUnable to bind to Port ...$B!W(B @@ -68,12 +70,12 @@
$BF1$8%]!<%H$K4{$K%P%$%s%I$5$l$F$$$k(B Apache $B$,$b$&0l$D$"$k$H$-$dB>$N%&%'%V%5!<%P$,B8:_$7$F$$$k;~$K!"(B - $B%5!<%P(B$B$r3+;O$7$h$&$H$7$?!#(B
+ $B%5!<%P$r3+;O$7$h$&$H$7$?!#(B
$B$h$jB?$/$NLdBj2r7h$NJ}:v$N@bL@$O!"(B Apache FAQ $B$r$4Mw2<$5$$!#(B
-
$B%V!<%H;~$N5/F0(B
+
$B%V!<%H;~$N5/F0(B

$B%7%9%F%`$,%j%V!<%H$7$?8e$G$b(B $B%5!<%P$,l9g$O!"(B @@ -87,15 +89,15 @@ apachectl $B%9%/%j%W%H$ODL>o$O!"(B init $B%9%/%j%W%H$H$7$FD>@\%j%s%/$G$-$k$h$&$K@_7W$5$l$F$$$^$9$,!"(B $BG0$N$?$a%7%9%F%`$NMW5a$K9gCW$7$F$$$k$3$H$r3NG'$7$F$/$@$5$$!#(B
-
$BDI2C>pJs(B
+
$BDI2C>pJs(B

httpd $B$d(B apachectl $B!"%5!<%P$K4^$^$l$F$$$?$=$NB>Jd=u%W%m%0%i%`$N!"(B $B%3%^%s%I%i%$%s%*%W%7%g%s$K4X$9$kDI2C>pJs$O!"(B - $B%5!<%P$HJd=u%W%m%0(B$B%i%`(B$B%Z!<%8$K(B + $B%5!<%P$HJd=u%W%m%0%i%`(B$B%Z!<%8$K(B $B5-:\$5$l$F$$$^$9!#(B Apache $BG[I[$K4^$^$l$F$$$kA4(B$B%b%8%e!<%k(B$B!"(B $B$=$l$K$h$C$FDs6!$5$l$k(B$B%G%#%l%/%F%#%V(B $B$N%I%-%e%a%s%H$b$"$j$^$9!#(B
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en index 49370295e0..5be2bf3970 100644 --- a/docs/manual/logs.html.en +++ b/docs/manual/logs.html.en @@ -1,8 +1,10 @@ -Log Files - Apache HTTP Server
Apache HTTP Server Version 2.0
Log Files
+ -->Log Files - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Log Files

In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring. The Apache @@ -10,7 +12,7 @@ capabilities. This document describes how to configure its logging capabilities, and how to understand what the logs contain.
-
Security Warning
Error Log
Access Log
Common Log Format
Combined Log Format
Multiple Access Logs
Conditional Logs
Rotation Logs
Piped Logs
Virtual Hosts
Other Log Files
PID File
Script Log
Rewrite Log
Security Warning
+
Security Warning
Error Log
Access Log
Rotation Logs
Piped Logs
Virtual Hosts
Other Log Files
Security Warning

Anyone who can write to the directory where Apache is @@ -26,13 +28,13 @@ possible for malicious clients to insert control-characters in the log files, so care must be taken in dealing with raw logs.
-
Error Log
+
Error Log
-
Related Modules

Related Directives

ErrorLog
LogLevel
+
Related Modules Related Directives
ErrorLog
LogLevel

The server error log, whose name and location is set by the - ErrorLog directive, is the + ErrorLog directive, is the most important log file. This is the place where Apache httpd will send diagnostic information and record any errors that it encounters in processing requests. It is the first place to @@ -52,15 +54,15 @@ in most error log entries. For example, here is a typical message.
-
+ [Wed Oct 11 14:32:52 2000] [error] [client 127.0.0.1] client denied by server configuration: /export/home/live/ap/htdocs/test -
+

The first item in the log entry is the date and time of the message. The second entry lists the severity of the error being - reported. The LogLevel + reported. The LogLevel directive is used to control the types of errors that are sent to the error log by restricting the severity level. The third entry gives the IP address of the client that generated the @@ -87,18 +89,18 @@ the error log for any problems. On unix systems, you can accomplish this using:
-
+ tail -f error_log -
-
Access Log
+
+
Access Log
-
Related Modules

mod_log_config
mod_setenvif
Related Directives

CustomLog
LogFormat
SetEnvIf
+
Related Modules Related Directives
mod_log_config
mod_setenvif
CustomLog
LogFormat
SetEnvIf

The server access log records all requests processed by the server. The location and content of the access log are - controlled by the CustomLog - directive. The LogFormat + controlled by the CustomLog + directive. The LogFormat directive can be used to simplify the selection of the contents of the logs. This section describes how to configure the server to record information in the access log.
@@ -116,26 +118,26 @@
Various versions of Apache httpd have used other modules and directives to control access logging, including mod_log_referer, mod_log_agent, and the - TransferLog directive. The CustomLog directive now subsumes + TransferLog directive. The CustomLog directive now subsumes the functionality of all the older directives.

The format of the access log is highly configurable. The - format is specified using a CustomLog that + format is specified using a CustomLog that looks much like a C-style printf(1) format string. Some examples are presented in the next sections. For a complete list of the possible contents of the format string, see the mod_log_config documentation.
-
Common Log Format
+
Common Log Format

A typical configuration for the access log might look as follows.
-
- LogFormat "%h %l %u %t \"%r\" %>s %b" common + + LogFormat "%h %l %u %t \"%r\" %>s %b" common CustomLog logs/access_log common -
+

This defines the nickname common and associates it with a particular log format string. The format @@ -149,10 +151,10 @@ control characters "\n" for new-line and "\t" for tab.
-
The CustomLog +
The CustomLog directive sets up a new log file using the defined nickname. The filename for the access log is relative to - the ServerRoot unless it + the ServerRoot unless it begins with a slash.

The above configuration will write log entries in a format @@ -161,10 +163,10 @@ analysis programs. The log file entries produced in CLF will look something like this:
-
+ 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 -
+

Each part of this log entry is described below.
@@ -172,7 +174,7 @@
127.0.0.1 (%h)

This is the IP address of the client (remote host) which - made the request to the server. If HostnameLookups is + made the request to the server. If HostnameLookups is set to On, then the server will try to determine the hostname and log it in place of the IP address. However, this configuration is not recommended since it can @@ -193,7 +195,7 @@ machine. This information is highly unreliable and should almost never be used except on tightly controlled internal networks. Apache httpd will not even attempt to determine - this information unless IdentityCheck is set + this information unless IdentityCheck is set to On.

frank (%u)
@@ -215,16 +217,16 @@ The time that the server finished processing the request. The format is: -
- [day/month/year:hour:minute:second zone] - day = 2*digit - month = 3*letter - year = 4*digit - hour = 2*digit - minute = 2*digit - second = 2*digit + + [day/month/year:hour:minute:second zone] + day = 2*digit + month = 3*letter + year = 4*digit + hour = 2*digit + minute = 2*digit + second = 2*digit zone = (`+' | `-') 4*digit -
+ It is possible to have the time displayed in another format by specifying %{format}t in the log format string, where format is as in @@ -266,17 +268,17 @@ - Combined Log Format + Combined Log Format Another commonly used format string is called the Combined Log Format. It can be used as follows. - + LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" - \"%{User-agent}i\"" combined + \"%{User-agent}i\"" combined CustomLog log/acces_log combined - +

This format is exactly the same as the Common Log Format, with the addition of two more fields. Each of the additional @@ -285,12 +287,12 @@ any HTTP request header. The access log under this format will look like:
-
+ 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 "http://www.example.com/start.html" "Mozilla/4.08 [en] (Win98; I ;Nav)" -
+

The additional fields are:
@@ -312,31 +314,31 @@ -
Multiple Access Logs
+
Multiple Access Logs

Multiple access logs can be created simply by specifying - multiple CustomLog + multiple CustomLog directives in the configuration file. For example, the following directives will create three access logs. The first contains the basic CLF information, while the second and third contain referer and browser - information. The last two CustomLog lines show how + information. The last two CustomLog lines show how to mimic the effects of the ReferLog and AgentLog directives.
-
- LogFormat "%h %l %u %t \"%r\" %>s %b" common - CustomLog logs/access_log common - CustomLog logs/referer_log "%{Referer}i -> %U" + + LogFormat "%h %l %u %t \"%r\" %>s %b" common + CustomLog logs/access_log common + CustomLog logs/referer_log "%{Referer}i -> %U" CustomLog logs/agent_log "%{User-agent}i" -
+

This example also shows that it is not necessary to define a - nickname with the LogFormat directive. Instead, - the log format can be specified directly in the CustomLog directive.
+ nickname with the LogFormat directive. Instead, + the log format can be specified directly in the CustomLog directive.
-
Conditional Logs
+
Conditional Logs

There are times when it is convenient to exclude certain @@ -344,29 +346,29 @@ client request. This is easily accomplished with the help of environment variables. First, an environment variable must be set to indicate that the request meets certain conditions. This is usually accomplished with - SetEnvIf. Then the - env= clause of the CustomLog directive is used to + SetEnvIf. Then the + env= clause of the CustomLog directive is used to include or exclude requests where the environment variable is set. Some examples:
-
- # Mark requests from the loop-back interface - SetEnvIf Remote_Addr "127\.0\.0\.1" dontlog - # Mark requests for the robots.txt file - SetEnvIf Request_URI "^/robots\.txt$" dontlog - # Log what remains + + # Mark requests from the loop-back interface + SetEnvIf Remote_Addr "127\.0\.0\.1" dontlog + # Mark requests for the robots.txt file + SetEnvIf Request_URI "^/robots\.txt$" dontlog + # Log what remains CustomLog logs/access_log common env=!dontlog -
+

As another example, consider logging requests from english-speakers to one log file, and non-english speakers to a different log file.
-
- SetEnvIf Accept-Language "en" english - CustomLog logs/english_log common env=english + + SetEnvIf Accept-Language "en" english + CustomLog logs/english_log common env=english CustomLog logs/non_english_log common env=!english -
+

Although we have just shown that conditional logging is very powerful and flexibly, it is not the only way to control the @@ -375,7 +377,7 @@ easier to simply post-process the log files to remove requests that you do not want to consider.
-
Rotation Logs
+
Rotation Logs

On even a moderately busy server, the quantity of @@ -398,17 +400,17 @@ scenario that simply rotates the logs and compresses the old logs to save space is:
-
- mv access_log access_log.old - mv error_log error_log.old - apachectl graceful - sleep 600 + + mv access_log access_log.old + mv error_log error_log.old + apachectl graceful + sleep 600 gzip access_log.old error_log.old -
+

Another way to perform log rotation is using piped logs as discussed in the next section.
-
Piped Logs
+
Piped Logs

Apache httpd is capable of writing error and access log @@ -430,14 +432,14 @@
Some simple examples using piped logs:
-
- # compressed logs + + # compressed logs CustomLog "|/usr/bin/gzip -c >> - /var/log/access_log.gz" common - # almost-real-time name resolution + /var/log/access_log.gz" common + # almost-real-time name resolution CustomLog "|/usr/local/apache/bin/logresolve >> /var/log/access_log" common -
+

Notice that quotes are used to enclose the entire command that will be called for the pipe. Although these examples are @@ -450,10 +452,10 @@ purpose. For example, to rotate the logs every 24 hours, you can use:
-
+ CustomLog "|/usr/local/apache/bin/rotatelogs /var/log/access_log 86400" common -
+

A similar, but much more flexible log rotation program called cronolog @@ -462,23 +464,23 @@
As with conditional logging, piped logs are a very powerful tool, but they should not be used where a simpler solution like off-line post-processing is available.
-
Virtual Hosts
+
Virtual Hosts

When running a server with many virtual hosts, there are several options for dealing with log files. First, it is possible to use logs exactly as in a single-host server. Simply by placing the logging directives - outside the <VirtualHost> sections in the + outside the <VirtualHost> sections in the main server context, it is possible to log all requests in the same access log and error log. This technique does not allow for easy collection of statistics on individual virtual hosts.
-
If CustomLog - or ErrorLog +
If CustomLog + or ErrorLog directives are placed inside a - <VirtualHost> + <VirtualHost> section, all requests or errors for that virtual host will be logged only to the specified file. Any virtual host which does not have logging directives will still have its requests sent @@ -494,27 +496,27 @@ later split the log into individual files. For example, consider the following directives.
-
+ LogFormat "%v %l %u %t \"%r\" %>s %b" - comonvhost + comonvhost CustomLog logs/access_log comonvhost -
+

The %v is used to log the name of the virtual host that is serving the request. Then a program like split-logfile can be used to post-process the access log in order to split it into one file per virtual host.
-
Other Log Files
+
Other Log Files
-
Related Modules

mod_cgi
mod_rewrite
Related Directives

PidFile
RewriteLog
RewriteLogLevel
ScriptLog
ScriptLogBuffer
ScriptLogLength
+
Related Modules Related Directives
mod_cgi
mod_rewrite
PidFile
RewriteLog
RewriteLogLevel
ScriptLog
ScriptLogBuffer
ScriptLogLength
-
PID File
+
PID File

On startup, Apache httpd saves the process id of the parent httpd process to the file logs/httpd.pid. This - filename can be changed with the PidFile directive. The + filename can be changed with the PidFile directive. The process-id is for use by the administrator in restarting and terminating the daemon by sending signals to the parent process; on Windows, use the -k command line option instead. @@ -522,23 +524,23 @@ and Restarting page.
-
Script Log
+
Script Log

In order to aid in debugging, the - ScriptLog directive + ScriptLog directive allows you to record the input to and output from CGI scripts. This should only be used in testing - not for live servers. More information is available in the mod_cgi documentation.
-
Rewrite Log
+
Rewrite Log

When using the powerful and complex features of mod_rewrite, it is almost - always necessary to use the RewriteLog to help + always necessary to use the RewriteLog to help in debugging. This log file produces a detailed analysis of how the rewriting engine transforms requests. The level of detail - is controlled by the RewriteLogLevel directive.
+ is controlled by the RewriteLogLevel directive.
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/logs.xml b/docs/manual/logs.xml index 3953251294..d6136915fe 100644 --- a/docs/manual/logs.xml +++ b/docs/manual/logs.xml @@ -250,7 +250,7 @@ The time that the server finished processing the request. The format is: -
+
[day/month/year:hour:minute:second zone] day = 2*digit month = 3*letter @@ -259,7 +259,7 @@ minute = 2*digit second = 2*digit zone = (`+' | `-') 4*digit -
+
It is possible to have the time displayed in another format by specifying %{format}t in the log format string, where format is as in diff --git a/docs/manual/mpm.html.en b/docs/manual/mpm.html.en index 72505f60d2..45275c9c0c 100644 --- a/docs/manual/mpm.html.en +++ b/docs/manual/mpm.html.en @@ -1,11 +1,13 @@ -Multi-Processing Modules (MPMs) - Apache HTTP Server
Apache HTTP Server Version 2.0
Multi-Processing Modules (MPMs)
+ -->Multi-Processing Modules (MPMs) - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Multi-Processing Modules (MPMs)

This document describes what a Multi-Processing Module is and how they are using by the Apache HTTP Server.
-
Introduction
Choosing an MPM
MPM Defaults
Introduction
+
Introduction
Choosing an MPM
MPM Defaults
Introduction

The Apache HTTP Server is designed to be a powerful and flexible web server that can work on a very wide variety of @@ -31,7 +33,7 @@ how they are using by the Apache HTTP Server.

Apache can more cleanly and efficiently support a wide variety of operating systems. In particular, the Windows version of Apache is now much more efficient, since - mpm_winnt can use native + mpm_winnt can use native networking features in place of the POSIX layer used in Apache 1.3. This benefit also extends to other operating systems that implement specialized MPMs.
@@ -39,11 +41,11 @@ how they are using by the Apache HTTP Server.

The server can be better customized for the needs of the particular site. For example, sites that need a great deal of scalability can choose to use a threaded MPM like - worker, while sites requiring + worker, while sites requiring stability or compatibility with older software can use a - prefork. In addition, + prefork. In addition, special features like serving different hosts under different - userids (perchild) can be + userids (perchild) can be provided.
@@ -52,7 +54,7 @@ how they are using by the Apache HTTP Server.
be loaded into the server at any time. The list of available MPMs appears on the module index page.
-
Choosing an MPM
+
Choosing an MPM

MPMs must be chosen during configuration, and compiled into the server. Compilers are capable of optimizing a lot of @@ -69,16 +71,16 @@ how they are using by the Apache HTTP Server.
determine which MPM was chosen by using ./httpd -l. This command will list every module that is compiled into the server, including the MPM.
-
MPM Defaults
+
MPM Defaults

The following table lists the default MPMs for various operating systems. This will be the MPM selected if you do not make another choice at compile-time.
- - - - + + + +
BeOS beos
OS/2 mpmt_os2
Unix prefork
Windows mpm_winnt
BeOS beos
OS/2 mpmt_os2
Unix prefork
Windows mpm_winnt

-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/mpm.html.ja.jis b/docs/manual/mpm.html.ja.jis index d90ec16a22..3bf3a410d7 100644 --- a/docs/manual/mpm.html.ja.jis +++ b/docs/manual/mpm.html.ja.jis @@ -1,26 +1,28 @@ -$B%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B (MPM) - Apache HTTP Server
Apache HTTP Server Version 2.0
$B%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B (MPM)
-
$B$3$N(B$BJ8=q$G$O%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k$,$I$N$h$&$J$b$N$G!"(B -Apache HTTP $B%5!<%P$G$I$N$h$&$K;HMQ$5$l$k$+$K$D$$$F2r@b$7(B$B$F$$$^$9!#(B
-
$B$O$8$a$K(B
MPM $B$rA*$V(B
MPM $B%G%U%)%k%HCM(B
$B$O$8$a$K(B
+ -->$B%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B (MPM) - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
$B%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B (MPM)
+
$B$3$NJ8=q$G$O%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k$,$I$N$h$&$J$b$N$G!"(B +Apache HTTP $B%5!<%P$G$I$N$h$&$K;HMQ$5$l$k$+$K$D$$$F2r@b$7$F$$$^$9!#(B
+
$B$O$8$a$K(B
MPM $B$rA*$V(B
MPM $B%G%U%)%k%HCM(B
$B$O$8$a$K(B
-
Apache HTTP $B%5!<(B$B%P$O0[$J$kI}9-$$4D6-!"B?Apache HTTP $B%5!<%P$O0[$J$kI}9-$$4D6-!"B? + $B$I$N5!G=$r%5!<%P$K
Apache 2.0 $B$G$O!"(B $B$3$N%b%8%e!<%k2=$5$l$?@_7W$r%5!<%P$N4pK\5!G=$K$^$G3HD%$7$^$7$?!#(B $B%5!<%P$K$O@:A*$5$l$?%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B (MPM) - $B$,IU$$$F$-$F!"$3$l$i(B$B$O%^%7%s$N%M%C%H%o!<%/%]!<%H$r%P%$%s%I$7$?$j!"(B + $B$,IU$$$F$-$F!"$3$l$i$O%^%7%s$N%M%C%H%o!<%/%]!<%H$r%P%$%s%I$7$?$j!"(B $B%j%/%(%9%H$r @@ -31,7 +33,7 @@ Apache HTTP $B%5!<%P$G$I$N$h$&$K;HMQ$5$l$k$+$K$D$$$F2r@b$7(B$B$F$$$^$9!#(BApache $B$OI}9-$$%*%Z%l!<%F%#%s%0%7%9%F%`$r(B $B$h$jH~$7$/8zN(E*$K%5%]!<%H$G$-$^$9!#(B $BFC$K(B Windows $BHG$N(B Apache $B$O?oJ,8zN(E*$K$J$j$^$7$?!#(B - $B$J$<$J$i(B mpm_winnt + $B$J$<$J$i(B mpm_winnt $B$K$h$C$F!"(BApache 1.3 $B$GMQ$$$i$l$F$$$?(B POSIX $B%l%$%d$NBe$o$j$K%M%$%F%#%V$N%M%C%H%o!<%/5!G=$r(B $BMxMQ$G$-$k$+$i$G$9!#(B @@ -41,12 +43,12 @@ Apache HTTP $B%5!<%P$G$I$N$h$&$K;HMQ$5$l$k$+$K$D$$$F2r@b$7(B$B$F$$$^$9!#(B$B%5!<%P$OFCDj$N%5%$%H8~$1$K!"$h$j>eo$KBg$-$J%9%1!<%i%S%j%F%#$rI,MW$H$9$k%5%$%H$G$O!"(B - worker $B$H$$$C$?%9%l%C%I2=(B$B$5$l$?(B + worker $B$H$$$C$?%9%l%C%I2=$5$l$?(B MPM $B$rMxMQ$G$-$k0lJ}$G!"0BDj@-$d8E$$%=%U%H%&%'%"$H$N8_49@-$r(B - $BI,MW$H$9$k%5%$%H$G$O(B prefork + $BI,MW$H$9$k%5%$%H$G$O(B prefork $B$,MxMQ$G$-$^$9!#$^$?!"(B $B0[$J$k%[%9%H$r0[$J$k%f!<%6(B ID $B$GF0:n$5$;$k(B - (perchild) $B$H$$$C$?(B + (perchild) $B$H$$$C$?(B $BFCJL$J5!G=$bDs6!$G$-$^$9!#(B @@ -57,7 +59,7 @@ Apache HTTP $B%5!<%P$G$I$N$h$&$K;HMQ$5$l$k$+$K$D$$$F2r@b$7(B$B$F$$$^$9!#(Bmodule $B%$%s%G%C%/%9(B$B$K$"$j$^$9!#(B
-
MPM $B$rA*$V(B
+
MPM $B$rA*$V(B

MPM $B$O@_DjCf$KA*Br$7$F!"%5!<%PFbIt$K%3%s%Q%$%k$5$l$J$1$l$P(B $B$J$j$^$;$s!#(B @@ -65,7 +67,7 @@ Apache HTTP $B%5!<%P$G$I$N$h$&$K;HMQ$5$l$k$+$K$D$$$F2r@b$7(B$B$F$$$^$9!#(Be$G%9%l%C%I$rMQ$$$k$b$N$d!"%9%l%C%I$r$^$C$?$/(B $B;H$o$J$$$b$N$,$"$k$N$G!"(B - Apache $B$O!"(BMPM $B$,(B$B@_DjCf$KA*Br$5$l$F(B Apache $BFbIt$KAH$_9~$^$l$?>l9g$NJ}$,(B + Apache $B$O!"(BMPM $B$,@_DjCf$KA*Br$5$l$F(B Apache $BFbIt$KAH$_9~$^$l$?>l9g$NJ}$,(B $B>o$K$h$jNI$$%Q%U%)!<%^%s%9$rH/4x$7$^$9!#(B

$BK>$_$N(B MPM $B$r -
MPM $B%G%U%)%k%HCM(B
+
MPM $B%G%U%)%k%HCM(B

$B$rA*Br$7$J$1$l$P!"<+F0E*$K$3$l$i$N(B MPM $B$,A*Br$5$l$^$9!#(B
- - - - + + + +
BeOS beos
OS/2 mpmt_os2
Unix prefork
Windows mpm_winnt
BeOS beos
OS/2 mpmt_os2
Unix prefork
Windows mpm_winnt

-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/new_features_2_0.html.de b/docs/manual/new_features_2_0.html.de index e595319e3b..6267d9a23d 100644 --- a/docs/manual/new_features_2_0.html.de +++ b/docs/manual/new_features_2_0.html.de @@ -1,100 +1,102 @@ -Übersicht der neuen Funktionen in Apache 2.0 - Apache HTTP Server
Apache HTTP Server Version 2.0
Übersicht der neuen Funktionen in Apache 2.0
+ -->Übersicht der neuen Funktionen in Apache 2.0 - Apache HTTP Server
Module | Direktiven | FAQ | Glossar | Seitenindex
Apache HTTP Server Version 2.0
Apache > HTTP-Server > Dokumentation > Version 2.0
Übersicht der neuen Funktionen in Apache 2.0

Erweiterungen:
-
Core-Erweiterungen
Modul-Erweiterungen
Core-Erweiterungen
+
Core-Erweiterungen
Modul-Erweiterungen
Core-Erweiterungen

Unix-Threading
-
Auf Unix-Systemen mit Unterstützung für POSIX-Threads, kann Apache +
Auf Unix-Systemen mit Unterstützung für POSIX-Threads, kann Apache jetzt in einem Multi-Process, Multi-Threaded Hybrid-Mode gestartet werden. Dies - verbessert die Skalierfähigkeit für viele, jedoch nicht unbedingt alle + verbessert die Skalierfähigkeit für viele, jedoch nicht unbedingt alle Konfigurationen.

Neues Build-System

Das Build-System wurde komplett auf der Basis von autoconf und libtool neu geschrieben. Dadurch wird das Apache-Konfigurationssystem dem vieler - anderer Packages ähnlicher.
+ anderer Packages ähnlicher. -
Multi-Protokoll-Unterstützung
+
Multi-Protokoll-Unterstützung
-
Apache stellt jetzt die notwendigen Grundfunktionalitäten bereit um mehrere - Protokolle unterstützen und verarbeiten zu können. - mod_echo wurde hierfür als Beispiel geschrieben.
+
Apache stellt jetzt die notwendigen Grundfunktionalitäten bereit um mehrere + Protokolle unterstützen und verarbeiten zu können. + mod_echo wurde hierfür als Beispiel geschrieben.
-
Bessere Unterstützung von Nicht-Unix-Plattformen
+
Bessere Unterstützung von Nicht-Unix-Plattformen

Apache 2.0 ist schneller und stabiler auf Nicht-Unix-Plattformen - wie BeOS, OS/2 und Windows. Mit der Einführung von Plattform-spezifischen + wie BeOS, OS/2 und Windows. Mit der Einführung von Plattform-spezifischen Multi-Processing Modulen (MPMs) und der Apache Portable Runtime (APR), sind diese Plattformen jetzt in ihrem nativen - API implementiert, wodurch die Verwendung der häufig fehlerbehafteten und + API implementiert, wodurch die Verwendung der häufig fehlerbehafteten und schlecht funktionierenden POSIX-Emulation-Layer vermieden wird.

Neues Apache API
-
Das API für Module hat sich in 2.0 stark verändert. - Die meisten der Sortierungs-/Prioritätsprobleme von Modulen bei 1.3 sollten nun - verschwunden sein. In 2.0 wird hiervon vieles automatisch durchgeführt. Die - Modulsortierung wird jetzt über einen pre-hook vorgenommen, um mehr Flexibilität - zu bieten. Außerdem wurden neue API-Calls hinzugefügt, die zusätzliche - Modulfähigkeiten zur Verfügung stellen, ohne den Apache-Kern anpassen - zu müssen.
+
Das API für Module hat sich in 2.0 stark verändert. + Die meisten der Sortierungs-/Prioritätsprobleme von Modulen bei 1.3 sollten nun + verschwunden sein. In 2.0 wird hiervon vieles automatisch durchgeführt. Die + Modulsortierung wird jetzt über einen pre-hook vorgenommen, um mehr Flexibilität + zu bieten. Außerdem wurden neue API-Calls hinzugefügt, die zusätzliche + Modulfähigkeiten zur Verfügung stellen, ohne den Apache-Kern anpassen + zu müssen.
-
IPv6-Unterstützung
+
IPv6-Unterstützung

Auf Systemen, bei denen die zugrundeliegende Apache Portable Runtime-Bibliothek - IPv6 unterstützt, bekommt Apache standarmäßig IPv6 Listening - Sockets. Zusätzlich unterstützen die Konfigurationsanweisungen Listen, NameVirtualHost und VirtualHost + IPv6 unterstützt, bekommt Apache standarmäßig IPv6 Listening + Sockets. Zusätzlich unterstützen die Konfigurationsanweisungen Listen, NameVirtualHost und VirtualHost numerische IPv6-Adressangaben (z.B., "Listen [fe80::1]:8080").

Filterung
-
Apache-Module können jetzt als Filter entwickelt und zur Filterung +
Apache-Module können jetzt als Filter entwickelt und zur Filterung des rein- und rausgehenden Datenstroms des Servers eingesetzt werden. Hierdurch kann beispielsweise die Ausgabe von CGI-Skripten durch den INCLUDES-Filter - von mod_include bearbeitet werden und so Server-Side Include-Anweisungen ausgeführt + von mod_include bearbeitet werden und so Server-Side Include-Anweisungen ausgeführt werden.

Mehrsprachige Fehlermeldungen

Fehlermeldungen die an den Browser rausgehen, stehen jetzt als SSI-Dokumente in - verschiedenen Sprachen zur Verfügung. Sie können bei Bedarf durch den + verschiedenen Sprachen zur Verfügung. Sie können bei Bedarf durch den Administrator angepasst werden, um ein einheitliches Design zu erreichen.

Vereinfachte Konfiguration

Viele der verwirrenden Konfigurationsanweisungen wurden vereinfacht. - Die oft für Verwirrung sorgenden Port- und BindAddress-Anweisungen wurden - entfernt. Ausschließlich die Listen-Anweisung wird nun zum Setzen von + Die oft für Verwirrung sorgenden Port- und BindAddress-Anweisungen wurden + entfernt. Ausschließlich die Listen-Anweisung wird nun zum Setzen von IP-Addressen und Portnummern benutzt. Der Servername und die Portnummer, die - für Weiterleitungen und zur Erkennung virtueller Server verwendet werden, - werden über die ServerName-Anweisung konfiguriert.
+ für Weiterleitungen und zur Erkennung virtueller Server verwendet werden, + werden über die ServerName-Anweisung konfiguriert. -
Native Windows NT Unicode-Unterstützung
+
Native Windows NT Unicode-Unterstützung
-
Apache 2.0 auf Windows NT benutzt jetzt utf-8 für alle +
Apache 2.0 auf Windows NT benutzt jetzt utf-8 für alle Dateinamen-Kodierungen. Diese werden direkt auf das zugrundeliegende - Unicode-Dateisystem abgebildet, wodurch Mehrsprach-Unterstützung - für alle Windows NT-basierten Installationen, inklusive Windows 2000 und - Windows XP, zur Verfügung gestellt wird. - Diese Unterstützung ist nicht auf Windows 95, 98 oder ME verfügbar. - Hier wird weiterhin die jeweils lokale Codepage des Rechners für den + Unicode-Dateisystem abgebildet, wodurch Mehrsprach-Unterstützung + für alle Windows NT-basierten Installationen, inklusive Windows 2000 und + Windows XP, zur Verfügung gestellt wird. + Diese Unterstützung ist nicht auf Windows 95, 98 oder ME verfügbar. + Hier wird weiterhin die jeweils lokale Codepage des Rechners für den Zugriff auf das Dateisystem verwendet.

-
Modul-Erweiterungen
+
Modul-Erweiterungen

mod_ssl

Neues Modul in Apache 2.0. Dieses Modul ist ein Interface - zu den von OpenSSL bereitgestellten SSL/TLS Verschlüsselungs-Protokollen.
+ zu den von OpenSSL bereitgestellten SSL/TLS Verschlüsselungs-Protokollen.
mod_dav
@@ -104,73 +106,73 @@
mod_auth_digest
-
Zusätzliche Unterstützung für prozessübergreifendes +
Zusätzliche Unterstützung für prozessübergreifendes Session-Caching mittels Shared-Memory.

mod_charset_lite

Neues Modul in Apache 2.0. - Dieses experimentelle Modul erlaubt Zeichensatz-Übersetzungen oder - -Umschlüsselung.
+ Dieses experimentelle Modul erlaubt Zeichensatz-Übersetzungen oder + -Umschlüsselung.
mod_file_cache
-
Neues Modul in Apache 2.0. Dieses Modul beinhaltet die Funktionalität +
Neues Modul in Apache 2.0. Dieses Modul beinhaltet die Funktionalität von mod_mmap_static aus Apache 1.3, plus einige weitere Caching-Funktionen.

mod_headers

Dieses Modul ist in Apache 2.0 deutlich flexibler geworden. Es kann jetzt - die von mod_proxy genutzten Request-Header manipulieren und es ist möglich - Response-Header auf Basis von definierten Bedingungen zu verändern.
+ die von mod_proxy genutzten Request-Header manipulieren und es ist möglich + Response-Header auf Basis von definierten Bedingungen zu verändern.
mod_proxy
-
Das Proxy Modul wurde komplett neu geschrieben um die Möglichkeiten der - neuen Filter-Funktionalität auszuschöpfen und um einen - zuverlässigen Proxy zu haben, der den HTTP/1.1-Spezifikationen +
Das Proxy Modul wurde komplett neu geschrieben um die Möglichkeiten der + neuen Filter-Funktionalität auszuschöpfen und um einen + zuverlässigen Proxy zu haben, der den HTTP/1.1-Spezifikationen entspricht.

mod_negotiation
-
Die neue Konfigurationsanweisung ForceLanguagePriority +
Die neue Konfigurationsanweisung ForceLanguagePriority kann benutzt werden, um sicherzustellen, dass ein Client auf jeden Fall ein einzelnes Dokument, anstatt einer NOT ACCEPTABLE- oder MULTIPLE CHOICES-Antwort, - bekommt. Zusätzlich wurden die Negotiation- und Multiview-Algorithmen - angepasst um einheitlichere Ergebnisse zu liefern. Außerdem wird eine + bekommt. Zusätzlich wurden die Negotiation- und Multiview-Algorithmen + angepasst um einheitlichere Ergebnisse zu liefern. Außerdem wird eine neue Form von Type-Maps bereitgestellt, die direkt den Inhalt von Dokumenten - umfassen können.
+ umfassen können.
mod_autoindex
-
Automatisch erzeugte Verzeichnisindizes können zur besseren - Übersichtlichkeit durch HTML-Tabellen dargestellt werden. +
Automatisch erzeugte Verzeichnisindizes können zur besseren + Übersichtlichkeit durch HTML-Tabellen dargestellt werden. Genauere Sortierungen, wie Sortierung nach Versionsnummer und - Wildcard-Filterung des Verzeichnisindizes werden unterstützt.
+ Wildcard-Filterung des Verzeichnisindizes werden unterstützt.
mod_include

Neue Anweisungen erlauben es, die Standard Start- und Endtags von - SSI-Elementen zu ändern. Zudem können die Default-Formate für + SSI-Elementen zu ändern. Zudem können die Default-Formate für Fehlermeldungen und Zeitangaben nun ebenfalls in der Serverkonfiguration vorgenommen werden. Auf die Ergebnisse der Auswertung und Gruppierung von - regulären Ausdrücken (jetzt auf Basis der Perl's Regular Expression - Syntax) kann über die mod_include Variablen $0 bis $9 zugegriffen werden.
+ regulären Ausdrücken (jetzt auf Basis der Perl's Regular Expression + Syntax) kann über die mod_include Variablen $0 bis $9 zugegriffen werden.
mod_auth_dbm
-
DBM-ähnliche Datenbanken werden jetzt durch die Konfigurationsaweisung - AuthDBMType - unterstützt.
+
DBM-ähnliche Datenbanken werden jetzt durch die Konfigurationsaweisung + AuthDBMType + unterstützt.

mod_proxy

Neue <Proxy>-Konfigurationssektionen bringen eine besser lesbare (und intern schnellere) Kontrolle der genutzten Websites. - Die überladene <Directory "proxy:...">-Anweisung wird nicht mehr - unterstützt. Das Modul wurde in mehrere Module aufgeteilt, die jeweils - ein bestimmtes Übertragungsprotokoll implementieren. Diese sind proxy_connect, + Die überladene <Directory "proxy:...">-Anweisung wird nicht mehr + unterstützt. Das Modul wurde in mehrere Module aufgeteilt, die jeweils + ein bestimmtes Übertragungsprotokoll implementieren. Diese sind proxy_connect, proxy_ftp und proxy_http.

-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Gepflegt durch das Apache HTTP Server Documentation Project
Module | Direktiven | FAQ | Glossar | Seitenindex
\ No newline at end of file diff --git a/docs/manual/new_features_2_0.html.en b/docs/manual/new_features_2_0.html.en index 0af3aa5072..4b7c567ad7 100644 --- a/docs/manual/new_features_2_0.html.en +++ b/docs/manual/new_features_2_0.html.en @@ -1,10 +1,12 @@ -Overview of new features in Apache 2.0 - Apache HTTP Server
Apache HTTP Server Version 2.0
Overview of new features in Apache 2.0
+ -->Overview of new features in Apache 2.0 - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Overview of new features in Apache 2.0

Enhancements:
-
Core Enhancements
Module Enhancements
Core Enhancements
+
Core Enhancements
Module Enhancements
Core Enhancements

@@ -50,7 +52,7 @@
On systems where IPv6 is supported by the underlying Apache Portable Runtime library, Apache gets IPv6 listening - sockets by default. Additionally, the Listen, NameVirtualHost, and VirtualHost directives support + sockets by default. Additionally, the Listen, NameVirtualHost, and VirtualHost directives support IPv6 numeric address strings (e.g., "Listen [fe80::1]:8080").
@@ -86,7 +88,7 @@ continue to use the machine's local codepage for filesystem access.
-
Module Enhancements
+
Module Enhancements

@@ -137,7 +139,7 @@
mod_negotiation
-
A new ForceLanguagePriority directive can be used to assure that +
A new ForceLanguagePriority directive can be used to assure that the client receives a single document in all cases, rather than NOT ACCEPTABLE or MULTIPLE CHOICES responses. In addition, the negotiation and MultiViews algorithms have been cleaned up to @@ -163,7 +165,7 @@
mod_auth_dbm

Now supports multiple types of DBM-like databases using the - AuthDBMType + AuthDBMType directive.

mod_auth_db
@@ -171,4 +173,4 @@
Has been removed in favor of mod_auth_dbm with the AuthDBMType directive.

-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/server-wide.html.en b/docs/manual/server-wide.html.en index 5b6511b2bc..a32bb6dfc0 100644 --- a/docs/manual/server-wide.html.en +++ b/docs/manual/server-wide.html.en @@ -1,47 +1,49 @@ -Server-Wide Configuration - Apache HTTP Server
Apache HTTP Server Version 2.0
Server-Wide Configuration
+ -->Server-Wide Configuration - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Server-Wide Configuration

This document explains some of the directives provided by -the core server which are used to configure +the core server which are used to configure the basic operations of the server.
-
Server Identification
File Locations
Limiting Resource Usage
Server Identification
+
Server Identification
File Locations
Limiting Resource Usage
Server Identification
-
Related Modules

Related Directives

ServerName
ServerAdmin
ServerSignature
ServerTokens
UseCanonicalName
+
Related Modules Related Directives
ServerName
ServerAdmin
ServerSignature
ServerTokens
UseCanonicalName
-
The ServerAdmin and - ServerTokens directives +
The ServerAdmin and + ServerTokens directives control what information about the server will be presented in server-generated documents such as error messages. The - ServerTokens directive + ServerTokens directive sets the value of the Server HTTP response header field.
-
The ServerName and - UseCanonicalName +
The ServerName and + UseCanonicalName directives are used by the server to determine how to construct self-referential URLs. For example, when a client requests a directory, but does not include the trailing slash in the directory name, Apache must redirect the client to the full name including the trailing slash so that the client will correctly resolve relative references in the document.
-
File Locations
+
File Locations
-
Related Modules

Related Directives

CoreDumpDirectory
DocumentRoot
ErrorLog
LockFile
PidFile
ScoreBoardFile
ServerRoot
+
Related Modules Related Directives
CoreDumpDirectory
DocumentRoot
ErrorLog
LockFile
PidFile
ScoreBoardFile
ServerRoot

These directives control the locations of the various files that Apache needs for proper operation. When the pathname used does not begin with a slash (/), the files are located relative - to the ServerRoot. Be careful + to the ServerRoot. Be careful about locating files in paths which are writable by non-root users. See the security tips documentation for more details.
-
Limiting Resource Usage
+
Limiting Resource Usage
-
Related Modules

Related Directives

LimitRequestBody
LimitRequestFields
LimitRequestFieldsize
LimitRequestLine
RLimitCPU
RLimitMEM
RLimitNPROC
ThreadStackSize
+
Related Modules Related Directives
LimitRequestBody
LimitRequestFields
LimitRequestFieldsize
LimitRequestLine
RLimitCPU
RLimitMEM
RLimitNPROC
ThreadStackSize

The LimitRequest* directives are used to place limits on the amount of resources @@ -55,6 +57,6 @@ the basic operations of the server.
this will control resources used by CGI scripts and SSI exec commands.
-
The ThreadStackSize directive +
The ThreadStackSize directive is used only on Netware to control the stack size.
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/stopping.html.en b/docs/manual/stopping.html.en index 0be9ccd371..3aa32b3923 100644 --- a/docs/manual/stopping.html.en +++ b/docs/manual/stopping.html.en @@ -1,16 +1,18 @@ -Stopping and Restarting - Apache HTTP Server
Apache HTTP Server Version 2.0
Stopping and Restarting
+ -->Stopping and Restarting - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Stopping and Restarting

This document covers stopping and restarting Apache on Unix-like systems. Windows users should see Signalling Apache when running.
-
Introduction
Stop Now
Graceful Restart
Restart Now
Appendix: signals and race conditions
Introduction
+
Introduction
Stop Now
Graceful Restart
Restart Now
Appendix: signals and race conditions
Introduction

You will notice many httpd executables running on your system, but you should not send signals to any of them except - the parent, whose pid is in the PidFile. That is to say you shouldn't ever + the parent, whose pid is in the PidFile. That is to say you shouldn't ever need to send signals to any process except the parent. There are three signals that you can send the parent: TERM, HUP, and USR1, which will be described @@ -19,18 +21,18 @@
To send a signal to the parent you should issue a command such as:
-
kill -TERM `cat /usr/local/apache/logs/httpd.pid`
+
kill -TERM `cat /usr/local/apache/logs/httpd.pid`

You can read about its progress by issuing:
-
tail -f /usr/local/apache/logs/error_log
+
tail -f /usr/local/apache/logs/error_log
-
Modify those examples to match your ServerRoot and PidFile settings.
+
Modify those examples to match your ServerRoot and PidFile settings.

A shell script called apachectl is provided which automates the processing of signalling Apache. For details about this script, see the documentation on starting Apache.
-
Stop Now
+
Stop Now

Signal: TERM

apachectl stop
@@ -41,7 +43,7 @@ take it several seconds to complete killing off its children. Then the parent itself exits. Any requests in progress are terminated, and no further requests are served.
-
Graceful Restart
+
Graceful Restart

Signal: USR1

apachectl graceful
@@ -56,23 +58,23 @@ the configuration, which begins serving new requests immediately.
-
On certain platforms that do not allow USR1 to be used for a +
On certain platforms that do not allow USR1 to be used for a graceful restart, an alternative signal may be used (such as WINCH). The command apachectl graceful will send the - right signal for your platform.
+ right signal for your platform.

This code is designed to always respect the process control directive of the MPMs, so the number of processes and threads available to serve clients will be maintained at the appropriate values throughout the restart process. Furthermore, it respects - StartServers in the - following manner: if after one second at least StartServers new children have not + StartServers in the + following manner: if after one second at least StartServers new children have not been created, then create enough to pick up the slack. Hence the code tries to maintain both the number of children appropriate for the current load on the server, and respect your wishes with the StartServers parameter.
-
Users of the mod_status +
Users of the mod_status will notice that the server statistics are not set to zero when a USR1 is sent. The code was written to both minimize the time in which the server is unable @@ -95,7 +97,7 @@ low bandwidth links then you could wait 15 minutes before doing anything with the old log.
-
If your configuration file has errors +
If your configuration file has errors in it when you issue a restart then your parent will not restart, it will exit with an error. In the case of graceful restarts it will also leave children running when it exits. @@ -112,8 +114,8 @@ because it's not root (or because the currently running httpd already has those ports bound). If it fails for any other reason then it's probably a config file error and the error - should be fixed before issuing the graceful restart.
-
Restart Now
+ should be fixed before issuing the graceful restart.
+
Restart Now

Signal: HUP

apachectl restart
@@ -125,14 +127,14 @@ re-opens any log files. Then it spawns a new set of children and continues serving hits.
-
Users of mod_status +
Users of mod_status will notice that the server statistics are set to zero when a HUP is sent.
-
If your configuration file has errors in it when you issue a +
If your configuration file has errors in it when you issue a restart then your parent will not restart, it will exit with an -error. See above for a method of avoiding this.
-
Appendix: signals and race conditions
+error. See above for a method of avoiding this.
+
Appendix: signals and race conditions

Prior to Apache 1.2b9 there were several race conditions involving the restart and die signals (a simple @@ -143,7 +145,7 @@ error. See above for a method of avoiding this.
be noted that there still do exist race conditions on certain architectures.
-
Architectures that use an on disk ScoreBoardFile have the potential +
Architectures that use an on disk ScoreBoardFile have the potential to corrupt their scoreboards. This can result in the "bind: Address already in use" (after HUP) or "long lost child came home!" (after USR1). The former is a fatal @@ -151,7 +153,7 @@ error. See above for a method of avoiding this. scoreboard slot. So it might be advisable to use graceful restarts, with an occasional hard restart. These problems are very difficult to work around, but fortunately most architectures do - not require a scoreboard file. See the ScoreBoardFile documentation for a + not require a scoreboard file. See the ScoreBoardFile documentation for a architecture uses it.

All architectures have a small race condition in each child @@ -165,4 +167,4 @@ error. See above for a method of avoiding this. -- in a test case the server was restarted twenty times per second and clients successfully browsed the site without getting broken images or empty documents.
-
Apache HTTP Server Version 2.0
\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file diff --git a/docs/manual/suexec.html.en b/docs/manual/suexec.html.en index a4f911199d..57dc5667dd 100644 --- a/docs/manual/suexec.html.en +++ b/docs/manual/suexec.html.en @@ -1,8 +1,10 @@ -suEXEC Support - Apache HTTP Server

Apache HTTP Server Version 2.0
suEXEC Support
+ -->suEXEC Support - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
suEXEC Support

The suEXEC feature provides Apache users the ability to run CGI and SSI programs @@ -18,10 +20,10 @@ you aren't familiar with managing setuid root programs and the security issues they present, we highly recommend that you not consider using suEXEC.
-
Before we begin
suEXEC Security Model
Configuring & Installing - suEXEC
Enabling & Disabling - suEXEC
Using suEXEC
Debugging suEXEC
Beware the Jabberwock: - Warnings & Examples
Before we begin
+
Before we begin
suEXEC Security Model
Configuring & Installing + suEXEC
Enabling & Disabling + suEXEC
Using suEXEC
Debugging suEXEC
Beware the Jabberwock: + Warnings & Examples
Before we begin

Before jumping head-first into this document, you should be aware of the assumptions made on the part of the @@ -67,7 +69,7 @@ enough to use it.

Still with us? Yes? Good. Let's move on!
-
suEXEC Security Model
+
suEXEC Security Model

Before we begin configuring and installing suEXEC, we will first discuss the security model you are about @@ -94,209 +96,209 @@ Was the wrapper called with the proper number of arguments? -
+
The wrapper will only execute if it is given the proper number of arguments. The proper argument format is known to the Apache web server. If the wrapper is not receiving the proper number of arguments, it is either being hacked, or there is something wrong with the suEXEC portion of your Apache binary. -
+

Is the user executing this wrapper a valid user of this system? -
+
This is to ensure that the user executing the wrapper is truly a user of the system. -
+

Is this valid user allowed to run the wrapper? -
+
Is this user the user allowed to run this wrapper? Only one user (the Apache user) is allowed to execute this program. -
+

Does the target program have an unsafe hierarchical reference? -
+
Does the target program contain a leading '/' or have a '..' backreference? These are not allowed; the target program must reside within the Apache webspace. -
+

Is the target user name valid? -
+
Does the target user exist? -
+

Is the target group name valid? -
+
Does the target group exist? -
+

Is the target user NOT superuser? -
+
Presently, suEXEC does not allow 'root' to execute CGI/SSI programs. -
+

Is the target userid ABOVE the minimum ID number? -
+
The minimum user ID number is specified during configuration. This allows you to set the lowest possible userid that will be allowed to execute CGI/SSI programs. This is useful to block out "system" accounts. -
+

Is the target group NOT the superuser group? -
+
Presently, suEXEC does not allow the 'root' group to execute CGI/SSI programs. -
+

Is the target groupid ABOVE the minimum ID number? -
+
The minimum group ID number is specified during configuration. This allows you to set the lowest possible groupid that will be allowed to execute CGI/SSI programs. This is useful to block out "system" groups. -
+

Can the wrapper successfully become the target user and group? -
+
Here is where the program becomes the target user and group via setuid and setgid calls. The group access list is also initialized with all of the groups of which the user is a member. -
+

Does the directory in which the program resides exist? -
+
If it doesn't exist, it can't very well contain files. -
+

Is the directory within the Apache webspace? -
+
If the request is for a regular portion of the server, is the requested directory within the server's document root? If the request is for a UserDir, is the requested directory within the user's document root? -
+

Is the directory NOT writable by anyone else? -
+
We don't want to open up the directory to others; only the owner user may be able to alter this directories contents. -
+

Does the target program exist? -
+
If it doesn't exists, it can't very well be executed. -
+

Is the target program NOT writable by anyone else? -
+
We don't want to give anyone other than the owner the ability to change the program. -
+

Is the target program NOT setuid or setgid? -
+
We do not want to execute programs that will then change our UID/GID again. -
+

Is the target user/group the same as the program's user/group? -
+
Is the user the owner of the file? -
+

Can we successfully clean the process environment to ensure safe operations? -
+
suEXEC cleans the process' environment by establishing a safe execution PATH (defined during configuration), as well as only passing through those variables whose names are listed in the safe environment list (also created during configuration). -
+

Can we successfully become the target program and execute? -
+
Here is where suEXEC ends and the target program begins. -
+

@@ -311,13 +313,13 @@ configuration, as well as what security risks can be avoided with a proper suEXEC setup, see the "Beware the Jabberwock" section of this document.
-
Configuring & Installing +
Configuring & Installing suEXEC

Here's where we begin the fun.

suEXEC configuration - options
+ options

@@ -353,7 +355,7 @@ work properly in cases where the UserDir directive points to a location that is not the same as the user's home directory as referenced in the passwd file. Default value is - "public_html".
+ "public_html".
If you have virtual hosts with a different UserDir for each, you will need to define them to all reside in one parent directory; then name that parent directory here. If @@ -398,41 +400,41 @@

Checking your suEXEC - setup
+ setup
Before you compile and install the suEXEC wrapper you can - check the configuration with the --layout option.
+ check the configuration with the --layout option.
Example output:
-
- suEXEC setup: - suexec binary: /usr/local/apache/sbin/suexec - document root: /usr/local/apache/share/htdocs - userdir suffix: public_html - logfile: /usr/local/apache/var/log/suexec_log - safe path: /usr/local/bin:/usr/bin:/bin - caller ID: www - minimum user ID: 100 - minimum group ID: 100 -
+
+ suEXEC setup: + suexec binary: /usr/local/apache/sbin/suexec + document root: /usr/local/apache/share/htdocs + userdir suffix: public_html + logfile: /usr/local/apache/var/log/suexec_log + safe path: /usr/local/bin:/usr/bin:/bin + caller ID: www + minimum user ID: 100 + minimum group ID: 100 +

Compiling and installing the suEXEC - wrapper
+ wrapper
If you have enabled the suEXEC feature with the --enable-suexec option the suexec binary (together with Apache itself) is automatically built if you execute the command - "make".
+ "make".
After all components have been built you can execute the command "make install" to install them. The binary image "suexec" is installed in the directory defined by the --sbindir option. Default location is - "/usr/local/apache/sbin/suexec".
+ "/usr/local/apache/sbin/suexec".
Please note that you need root privileges for the installation step. In order for the wrapper to set the user ID, it must be installed as owner root and must have the setuserid execution bit set for file modes.
-
Enabling & Disabling +
Enabling & Disabling suEXEC

Upon startup of Apache, it looks for the file @@ -440,9 +442,9 @@ "/usr/local/apache/sbin/suexec"). If Apache finds a properly configured suEXEC wrapper, it will print the following message to the error log:
-
+ [notice] suEXEC mechanism enabled (wrapper: /path/to/suexec) -
+

If you don't see this message at server startup, the server is most likely not finding the wrapper program where it expects it, or the executable is not installed setuid root.
@@ -453,18 +455,18 @@ will not be enough.

If you want to disable suEXEC you should kill and restart Apache after you have removed the "suexec" file.
-
Using suEXEC
+
Using suEXEC
-
Virtual Hosts:
One way to use the suEXEC - wrapper is through the SuexecUserGroup directive in - VirtualHost definitions. By +
Virtual Hosts:
One way to use the suEXEC + wrapper is through the SuexecUserGroup directive in + VirtualHost definitions. By setting this directive to values different from the main server user ID, all requests for CGI resources will be executed as the - User and Group defined for that <VirtualHost>. If this - directive is not specified for a <VirtualHost> then the main server userid + User and Group defined for that <VirtualHost>. If this + directive is not specified for a <VirtualHost> then the main server userid is assumed.
-
User directories:
+
User directories:
The suEXEC wrapper can also be used to execute CGI programs as the user to which the request is being directed. This is accomplished by using the "~" @@ -473,7 +475,7 @@ execution to be enabled for the user and that the script must meet the scrutiny of the security checks above.
-
Debugging suEXEC
+
Debugging suEXEC

The suEXEC wrapper will write log information to the file defined with the --with-suexec-logfile option as @@ -481,7 +483,7 @@ the wrapper properly, have a look at this log and the error_log for the server to see where you may have gone astray.
-
Beware the Jabberwock: +
Beware the Jabberwock: Warnings & Examples

NOTE! This section may not be @@ -499,7 +501,7 @@
Hierarchy limitations -
+
For security and efficiency reasons, all suexec requests must remain within either a top-level document root for virtual host requests, or one top-level personal document @@ -508,30 +510,30 @@ of your VHosts' document roots off of one main Apache document hierarchy to take advantage of suEXEC for VirtualHosts. (Example forthcoming.) -
+

suEXEC's PATH environment variable -
+
This can be a dangerous thing to change. Make certain every path you include in this define is a trusted directory. You don't want to open people up to having someone from across the world running a trojan horse on them. -
+

Altering the suEXEC code -
+
Again, this can cause Big Trouble if you try this without knowing what you are doing. Stay away from it if at all possible. -
+

-

Apache HTTP Server Version 2.0

\ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/suexec.xml b/docs/manual/suexec.xml index 8e6441637e..0d61c5128c 100644 --- a/docs/manual/suexec.xml +++ b/docs/manual/suexec.xml @@ -100,209 +100,209 @@ Was the wrapper called with the proper number of arguments? -

+
The wrapper will only execute if it is given the proper number of arguments. The proper argument format is known to the Apache web server. If the wrapper is not receiving the proper number of arguments, it is either being hacked, or there is something wrong with the suEXEC portion of your Apache binary. -

Is the user executing this wrapper a valid user of this system? -

+
This is to ensure that the user executing the wrapper is truly a user of the system. -

Is this valid user allowed to run the wrapper? -

+
Is this user the user allowed to run this wrapper? Only one user (the Apache user) is allowed to execute this program. -

Does the target program have an unsafe hierarchical reference? -

+
Does the target program contain a leading '/' or have a '..' backreference? These are not allowed; the target program must reside within the Apache webspace. -

Is the target user name valid? -

+
Does the target user exist? -

Is the target group name valid? -

+
Does the target group exist? -

Is the target user NOT superuser? -

+
Presently, suEXEC does not allow 'root' to execute CGI/SSI programs. -

Is the target userid ABOVE the minimum ID number? -

+
The minimum user ID number is specified during configuration. This allows you to set the lowest possible userid that will be allowed to execute CGI/SSI programs. This is useful to block out "system" accounts. -

Is the target group NOT the superuser group? -

+
Presently, suEXEC does not allow the 'root' group to execute CGI/SSI programs. -

Is the target groupid ABOVE the minimum ID number? -

+
The minimum group ID number is specified during configuration. This allows you to set the lowest possible groupid that will be allowed to execute CGI/SSI programs. This is useful to block out "system" groups. -

Can the wrapper successfully become the target user and group? -

+
Here is where the program becomes the target user and group via setuid and setgid calls. The group access list is also initialized with all of the groups of which the user is a member. -

Does the directory in which the program resides exist? -

+
If it doesn't exist, it can't very well contain files. -

Is the directory within the Apache webspace? -

+
If the request is for a regular portion of the server, is the requested directory within the server's document root? If the request is for a UserDir, is the requested directory within the user's document root? -

Is the directory NOT writable by anyone else? -

+
We don't want to open up the directory to others; only the owner user may be able to alter this directories contents. -

Does the target program exist? -

+
If it doesn't exists, it can't very well be executed. -

Is the target program NOT writable by anyone else? -

+
We don't want to give anyone other than the owner the ability to change the program. -

Is the target program NOT setuid or setgid? -

+
We do not want to execute programs that will then change our UID/GID again. -

Is the target user/group the same as the program's user/group? -

+
Is the user the owner of the file? -

Can we successfully clean the process environment to ensure safe operations? -

+
suEXEC cleans the process' environment by establishing a safe execution PATH (defined during configuration), as well as only passing through those variables whose names are listed in the safe environment list (also created during configuration). -

Can we successfully become the target program and execute? -

+
Here is where suEXEC ends and the target program begins. -

@@ -520,7 +520,7 @@

Hierarchy limitations -

+
For security and efficiency reasons, all suexec requests must remain within either a top-level document root for virtual host requests, or one top-level personal document @@ -529,29 +529,29 @@ of your VHosts' document roots off of one main Apache document hierarchy to take advantage of suEXEC for VirtualHosts. (Example forthcoming.) -

suEXEC's PATH environment variable -

+
This can be a dangerous thing to change. Make certain every path you include in this define is a trusted directory. You don't want to open people up to having someone from across the world running a trojan horse on them. -

Altering the suEXEC code -

+
Again, this can cause Big Trouble if you try this without knowing what you are doing. Stay away from it if at all possible. -

diff --git a/docs/manual/upgrading.html.de b/docs/manual/upgrading.html.de index 2ad594a08b..0ce5a7b285 100644 --- a/docs/manual/upgrading.html.de +++ b/docs/manual/upgrading.html.de @@ -1,138 +1,141 @@ -Upgrade von 1.3 auf 2.0 - Apache HTTP Server

Apache HTTP Server Version 2.0
Upgrade von 1.3 auf 2.0
-
Dieses Dokument dient der Unterstützung beim Upgrade. Es - enthält die entscheidenden Informationen für bisherige + -->Upgrade von 1.3 auf 2.0 - Apache HTTP Server
Module | Direktiven | FAQ | Glossar | Seitenindex
Apache HTTP Server Version 2.0
Apache > HTTP-Server > Dokumentation > Version 2.0
Upgrade von 1.3 auf 2.0
+
Dieses Dokument dient der Unterstützung beim Upgrade. Es + enthält die entscheidenden Informationen für bisherige Apache-Nutzer. Diese sind als kurze Anmerkungen gedacht. Weitere Informationen finden Sie entweder unter Neue Funktionen oder in den src/CHANGES-Dateien.
-
Änderungen der Konfiguration bei der Kompilierung
Änderungen der Laufzeit-Konfiguration
Sonstige Änderungen
Module von Drittanbietern
Änderungen der Konfiguration bei der Kompilierung
+
Änderungen der Konfiguration bei der Kompilierung
Änderungen der Laufzeit-Konfiguration
Sonstige Änderungen
Module von Drittanbietern
Änderungen der Konfiguration bei der Kompilierung

Der Apache benutzt jetzt ein autoconf- und libtool-System zur Konfiguration des Erstellungsverfahrens. Die Verwendung dieses Systems ist - ähnlich, aber nicht identisch mit dem APACI-System des + ähnlich, aber nicht identisch mit dem APACI-System des Apache 1.3.
-
Zusätzlich zu der üblichen Auswahl von Modulen, die +
Zusätzlich zu der üblichen Auswahl von Modulen, die kompiliert werden sollen, wurde der Hauptteil der Request-Verarbeitung im Apache 2.0 in die Multi-Processing-Module (MPMs) verschoben.

-
Änderungen der Laufzeit-Konfiguration
+
Änderungen der Laufzeit-Konfiguration

Viele Anweisungen aus dem Serverkern des Apache 1.3 sind jetzt in den MPMs enthalten. Wenn Sie ein Serververhalten - wünschen, das demjenigen des Apache 1.3 möglichst - ähnlich ist, sollten Sie das prefork-MPM - auswählen. Andere MPMs verwenden abweichende Anweisungen - für die Prozess-Erstellung und Request-Verarbeitung.
+ wünschen, das demjenigen des Apache 1.3 möglichst + ähnlich ist, sollten Sie das prefork-MPM + auswählen. Andere MPMs verwenden abweichende Anweisungen + für die Prozess-Erstellung und Request-Verarbeitung.
Das Proxy-Modul wurde umgearbeitet, um es auf den Stand von HTTP/1.1 zu bringen. Eine - der bedeutendsten Änderungen ist die Platzierung der + der bedeutendsten Änderungen ist die Platzierung der Proxy-Zugriffskontrolle innerhalb eines <Proxy>-Blocks, statt innerhalb eines <Directory proxy:>-Blocks.
-
Die Behandlung von PATH_INFO (hinter dem tatsächlichen - Dateinamen angefügte Pfadangaben) wurde für einige Module - geändert. Module, die bisher als Handler implementiert +
Die Behandlung von PATH_INFO (hinter dem tatsächlichen + Dateinamen angefügte Pfadangaben) wurde für einige Module + geändert. Module, die bisher als Handler implementiert waren, jetzt aber als Filter implementiert sind, akzeptieren - möglicherweise keine Requests mit PATH_INFO mehr. + möglicherweise keine Requests mit PATH_INFO mehr. Filter wie INCLUDES sind gleich oben im Core-Handler implementiert und weisen deshalb - Requests mit PATH_INFO ab. Sie können die AcceptPathInfo-Direktive + Requests mit PATH_INFO ab. Sie können die AcceptPathInfo-Direktive verwenden, um den Core-Handler zu zwingen, Requests mit - PATH_INFO zu akzeptieren, und dadurch die Fähigkeit + PATH_INFO zu akzeptieren, und dadurch die Fähigkeit wiederherstellen, PATH_INFO in Server Side Includes zu benutzen.
-
Die CacheNegotiatedDocs-Direktive +
Die CacheNegotiatedDocs-Direktive hat jetzt das Argument an (on) oder aus (off). Die vorhandenen Anweisungen CacheNegotiatedDocs sollten durch CacheNegotiatedDocs on ersetzt werden.

- Die ErrorDocument-Direktive - verwendet kein Anführungszeichen mehr am Anfang des + Die ErrorDocument-Direktive + verwendet kein Anführungszeichen mehr am Anfang des Arguments, um eine Textnachricht anzuzeigen. Stattdessen sollten Sie die - Nachricht in doppelte Anführungszeichen einschließen. + Nachricht in doppelte Anführungszeichen einschließen. Zum Beispiel sollten existierende Angaben wie -
- ErrorDocument 403 "Eine Nachricht -
+
+ ErrorDocument 403 "Eine Nachricht +
durch -
- ErrorDocument 403 "Eine Nachricht" -
+
+ ErrorDocument 403 "Eine Nachricht" +
+ ersetzt werden. - Solange das zweite Argument kein gültiger URL oder + Solange das zweite Argument kein gültiger URL oder Pfadname ist, wird es als Textnachricht behandelt.

Die Direktiven AccessConfig und ResourceConfig sind entfallen. - Diese Direktiven können durch die Include-Direktive - ersetzt werden, die eine äquivalente Funktionalität besitzt. + Diese Direktiven können durch die Include-Direktive + ersetzt werden, die eine äquivalente Funktionalität besitzt. Wenn Sie die Defaultwerte dieser Direktiven verwendet haben, - ohne sie in die Konfigurationsdateien einzufügen, müssen Sie - möglicherweise Include conf/access.conf und - Include conf/srm.conf zu Ihrer httpd.conf hinzufügen. - Um sicherzustellen, daß der Apache die Konfigurationsdateien in - der gleichen Reihenfolge liest, wie sie von den älteren Direktiven + ohne sie in die Konfigurationsdateien einzufügen, müssen Sie + möglicherweise Include conf/access.conf und + Include conf/srm.conf zu Ihrer httpd.conf hinzufügen. + Um sicherzustellen, daß der Apache die Konfigurationsdateien in + der gleichen Reihenfolge liest, wie sie von den älteren Direktiven impliziert wurde, sollten die Include-Direktiven ans - Ende der httpd.conf gestellt werden, wobei die Direktive für - srm.conf derjenigen für access.conf + Ende der httpd.conf gestellt werden, wobei die Direktive für + srm.conf derjenigen für access.conf vorangeht.

Die Direktiven BindAddress und Port - sind entfallen. Eine äquivalente Funktionalität wird von der - flexibleren Direktive Listen bereitgestellt.
+ sind entfallen. Eine äquivalente Funktionalität wird von der + flexibleren Direktive Listen bereitgestellt. -
Im Apache 1.3 wurde die Port-Direktive außerdem - dazu verwendet, die Portnummer für +
Im Apache 1.3 wurde die Port-Direktive außerdem + dazu verwendet, die Portnummer für selbstreferenzierende URLs festzulegen. - Die neue ServerName-Syntax - stellt das Apache-2.0-Äquivalent dar: - sie wurde dahingehend verändert, sowohl den Hostnamen - als auch die Portnummer für selbstreferenzierende URLs - in einer Direktive angeben zu können.
+ Die neue ServerName-Syntax + stellt das Apache-2.0-Äquivalent dar: + sie wurde dahingehend verändert, sowohl den Hostnamen + als auch die Portnummer für selbstreferenzierende URLs + in einer Direktive angeben zu können. -
Die ServerType-Direktive entfällt. +
Die ServerType-Direktive entfällt. Die Methode zum Bedienen der Requests wird nun durch die Auswahl - des MPM ermittelt. Derzeit ist kein MPM dafür bestimmt, von inetd + des MPM ermittelt. Derzeit ist kein MPM dafür bestimmt, von inetd gestartet zu werden.

Die Module mod_log_agent und mod_log_referer, welche die Direktiven AgentLog, RefererLog und RefererIgnore bereitgestellt hatten, wurden entfernt. - Durch Verwendung der Direktive CustomLog aus mod_log_config - sind die Agent- und Refererlogs auch weiterhin verfügbar.
+ Durch Verwendung der Direktive CustomLog aus mod_log_config + sind die Agent- und Refererlogs auch weiterhin verfügbar.
Die Direktiven AddModule und ClearModuleList sind entfallen. - Diese Direktiven wurden benutzt, um sicherzustellen, daß die - Module in der richtigen Reihenfolge aktiviert werden können. + Diese Direktiven wurden benutzt, um sicherzustellen, daß die + Module in der richtigen Reihenfolge aktiviert werden können. Die neue Apache 2.0 API erlaubt es Modulen, ihre Reihenfolge explizit anzugeben, und macht diese Direktiven damit - überflüssig.
+ überflüssig.
Die Direktive FancyIndexing wurde entfernt. - Die gleiche Funktionalität ist nun mit der Option - FancyIndexing der Direktive IndexOptions verfügbar.
+ Die gleiche Funktionalität ist nun mit der Option + FancyIndexing der Direktive IndexOptions verfügbar.
-
Sonstige Änderungen
+
Sonstige Änderungen

@@ -147,17 +150,17 @@
Das Modul mod_mmap_static, das im Apache 1.3 experimentellen Status hatte, wurde durch das Modul mod_file_cache ersetzt.
-
Die Distribution wurde komplett reorganisiert und enthält kein - unabhängiges src-Verzeichnis mehr. Stattdessen wurden +
Die Distribution wurde komplett reorganisiert und enthält kein + unabhängiges src-Verzeichnis mehr. Stattdessen wurden die Quellcodes logisch unterhalb des Hauptverzeichnisses der Distribution angeordnet. Installationen des kompilierten Servers sollten in ein separates Verzeichnis erfolgen.

-
Module von Drittanbietern
+
Module von Drittanbietern
-
An der API des Apache 2.0 wurden umfassende Änderungen - vorgenommen. Bestehende Module, die für die Apache 1.3 API +
An der API des Apache 2.0 wurden umfassende Änderungen + vorgenommen. Bestehende Module, die für die Apache 1.3 API entwickelt wurden, werden nicht ohne Modifikationen mit - der Version 2.0 des Apache zusammenarbeiten. Details sind in der Dokumentation für Entwickler beschrieben.
-

Apache HTTP Server Version 2.0

\ No newline at end of file + der Version 2.0 des Apache zusammenarbeiten. Details sind in der Dokumentation für Entwickler beschrieben.

+ \ No newline at end of file diff --git a/docs/manual/upgrading.html.en b/docs/manual/upgrading.html.en index dd6c1de067..1d242c3bb1 100644 --- a/docs/manual/upgrading.html.en +++ b/docs/manual/upgrading.html.en @@ -1,14 +1,16 @@ -Upgrading to 2.0 from 1.3 - Apache HTTP Server

Apache HTTP Server Version 2.0
Upgrading to 2.0 from 1.3
+ -->Upgrading to 2.0 from 1.3 - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Upgrading to 2.0 from 1.3

In order to assist folks upgrading, we maintain a document describing information critical to existing Apache users. These are intended to be brief notes, and you should be able to find more information in either the New Features document, or in the src/CHANGES file.
-
Compile-Time Configuration Changes
Run-Time Configuration Changes
Misc Changes
Third Party Modules
Compile-Time Configuration Changes
+
Compile-Time Configuration Changes
Run-Time Configuration Changes
Misc Changes
Third Party Modules
Compile-Time Configuration Changes

@@ -22,7 +24,7 @@ request processing into Multi-Processing Modules (MPMs).
-
Run-Time Configuration Changes
+
Run-Time Configuration Changes

@@ -44,32 +46,33 @@ implemented as a filter may no longer accept requests with PATH_INFO. Filters such as INCLUDES are implemented on top of the core handler, and therefore reject requests with - PATH_INFO. You can use the AcceptPathInfo directive to + PATH_INFO. You can use the AcceptPathInfo directive to force the core handler to accept requests with PATH_INFO and thereby restore the ability to use PATH_INFO in server-side includes. -
The CacheNegotiatedDocs +
The CacheNegotiatedDocs directive now takes the argument on or off. Existing instances of CacheNegotiatedDocs should be replaced with CacheNegotiatedDocs on.

- The ErrorDocument + The ErrorDocument directive no longer uses a quote at the beginning of the argument to indicate a text message. Instead, you should enclose the message in double quotes. For example, existing instances of -
- ErrorDocument 403 "Some Message -
+
+ ErrorDocument 403 "Some Message +
should be replaced with -
- ErrorDocument 403 "Some Message" -
+
+ ErrorDocument 403 "Some Message" +
+ As long as the second argument is not a valid URL or pathname, it will be treated as a text message.
@@ -77,7 +80,7 @@
The AccessConfig and ResourceConfig directives no longer exist. Existing instances of these directives can be replaced with - the Include + the Include directive which has equivalent functionality. If you were making use of the default values of these directives without including them in the configuration files, you may need to @@ -92,13 +95,13 @@
The BindAddress and Port directives no longer exist. Equivalent functionality is provided with the more flexible - Listen + Listen directive.

Another use of the Port directive in Apache-1.3 was setting the port number to be used in self-referential URL's. The Apache-2.0 equivalent is - the new ServerName + the new ServerName syntax: it has been changed to allow specifying both the hostname and the port number for self-referential URL's in one directive.
@@ -112,7 +115,7 @@ provided the AgentLog, RefererLog and RefererIgnore directives have been removed. Agent and referer logs are still available using the - CustomLog + CustomLog directive of mod_log_config.
The AddModule and @@ -124,10 +127,10 @@
The FancyIndexing directive has been removed. The same functionality is available through the - FancyIndexing option to the IndexOptions + FancyIndexing option to the IndexOptions directive.

-
Misc Changes
+
Misc Changes

@@ -149,7 +152,7 @@ compiled server should be directed to a separate directory.
-
Third Party Modules
+
Third Party Modules

Extensive changes were made to the server API in Apache 2.0. @@ -157,4 +160,4 @@ not work in Apache 2.0 without modification. Details are provided in the developer documentation.
-

Apache HTTP Server Version 2.0

\ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/upgrading.xml b/docs/manual/upgrading.xml index e6f19a2716..601ae0f38a 100644 --- a/docs/manual/upgrading.xml +++ b/docs/manual/upgrading.xml @@ -76,14 +76,15 @@ enclose the message in double quotes. For example, existing instances of -

- ErrorDocument 403 "Some Message -

+ + ErrorDocument 403 "Some Message + should be replaced with -

- ErrorDocument 403 "Some Message" -

+ + ErrorDocument 403 "Some Message" + + As long as the second argument is not a valid URL or pathname, it will be treated as a text message. diff --git a/docs/manual/upgrading.xml.de b/docs/manual/upgrading.xml.de index faf2c86883..22d0ebcd3a 100644 --- a/docs/manual/upgrading.xml.de +++ b/docs/manual/upgrading.xml.de @@ -80,14 +80,15 @@ Nachricht in doppelte Anführungszeichen einschließen. Zum Beispiel sollten existierende Angaben wie -

- ErrorDocument 403 "Eine Nachricht -

+ + ErrorDocument 403 "Eine Nachricht + durch -

- ErrorDocument 403 "Eine Nachricht" -

+ + ErrorDocument 403 "Eine Nachricht" + + ersetzt werden. Solange das zweite Argument kein gültiger URL oder Pfadname ist, wird es als Textnachricht behandelt. diff --git a/docs/manual/urlmapping.html.en b/docs/manual/urlmapping.html.en index 9ebdfad934..169e607b18 100755 --- a/docs/manual/urlmapping.html.en +++ b/docs/manual/urlmapping.html.en @@ -1,82 +1,84 @@ -Mapping URLs to Filesystem Locations - Apache HTTP Server

Apache HTTP Server Version 2.0
Mapping URLs to Filesystem Locations
+ -->Mapping URLs to Filesystem Locations - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Mapping URLs to Filesystem Locations

This document explains how Apache uses the URL of a request to determine the filesystem location from which to serve a file.
-
Related Modules and Directives
DocumentRoot
Files Outside the DocumentRoot
User Directories
URL Redirection
Reverse Proxy
Rewriting Engine
File Not Found
Related Modules and Directives
+
Related Modules and Directives
DocumentRoot
Files Outside the DocumentRoot
User Directories
URL Redirection
Reverse Proxy
Rewriting Engine
File Not Found
Related Modules and Directives
-
Related Modules

mod_alias
mod_proxy
mod_rewrite
mod_userdir
mod_speling
mod_vhost_alias
Related Directives

Alias
AliasMatch
CheckSpelling
DocumentRoot
ErrorDocument
Options
ProxyPass
ProxyPassReverse
Redirect
RedirectMatch
RewriteCond
RewriteMatch
ScriptAlias
ScriptAliasMatch
UserDir
-
DocumentRoot
+
Related Modules Related Directives
mod_alias
mod_proxy
mod_rewrite
mod_userdir
mod_speling
mod_vhost_alias
Alias
AliasMatch
CheckSpelling
DocumentRoot
ErrorDocument
Options
ProxyPass
ProxyPassReverse
Redirect
RedirectMatch
RewriteCond
RewriteMatch
ScriptAlias
ScriptAliasMatch
UserDir
+
DocumentRoot

In deciding what file to serve for a given request, Apache's default behavior is to take the URL-Path for the request (the part of the URL following the hostname and port) and add it to the end - of the DocumentRoot specified + of the DocumentRoot specified in your configuration files. Therefore, the files and directories - underneath the DocumentRoot + underneath the DocumentRoot make up the basic document tree which will be visible from the web.

Apache is also capable of Virtual Hosting, where the server receives requests for more than one - host. In this case, a different DocumentRoot can be specified for each + host. In this case, a different DocumentRoot can be specified for each virtual host, or alternatively, the directives provided by the - module mod_vhost_alias can + module mod_vhost_alias can be used to dynamically determine the appropriate place from which to serve content based on the requested IP address or hostname.
-
Files Outside the DocumentRoot
+
Files Outside the DocumentRoot

There are frequently circumstances where it is necessary to allow web access to parts of the filesystem that are not strictly - underneath the DocumentRoot. Apache offers several + underneath the DocumentRoot. Apache offers several different ways to accomplish this. On Unix systems, symbolic links - can bring other parts of the filesystem under the DocumentRoot. For security reasons, - Apache will follow symbolic links only if the Options setting for the relevant + can bring other parts of the filesystem under the DocumentRoot. For security reasons, + Apache will follow symbolic links only if the Options setting for the relevant directory includes FollowSymLinks or SymLinksIfOwnerMatch.
-
Alternatively, the Alias directive will map any part +
Alternatively, the Alias directive will map any part of the filesystem into the web space. For example, with
-
Alias /docs /var/web
+
Alias /docs /var/web

the URL http://www.example.com/docs/dir/file.html will be served from /var/web/dir/file.html. The - ScriptAlias directive + ScriptAlias directive works the same way, with the additional effect that all content located at the target path is treated as CGI scripts.

For situations where you require additional flexibility, you - can use the AliasMatch and - ScriptAliasMatch + can use the AliasMatch and + ScriptAliasMatch directives to do powerful regular-expression based matching and substitution. For example,
-
ScriptAliasMatch ^/~([a-zA-Z0-9]*)/cgi-bin/(.*) - /home/$1/cgi-bin/$2
+
ScriptAliasMatch ^/~([a-zA-Z0-9]*)/cgi-bin/(.*) + /home/$1/cgi-bin/$2

will map a request to http://example.com/~user/cgi-bin/script.cgi to the path /home/user/cgi-bin/script.cgi and will treat the resulting file as a CGI script.
-
User Directories
+
User Directories

Traditionally on Unix systems, the home directory of a particular user can be referred to as - ~user/. The module mod_userdir + ~user/. The module mod_userdir extends this idea to the web by allowing files under each user's home directory to be accessed using URLs such as the following.
-
http://www.example.com/~user/file.html
+
http://www.example.com/~user/file.html

For security reasons, it is inappropriate to give direct access to a user's home directory from the web. Therefore, the - UserDir directive + UserDir directive specifies a directory underneath the user's home directory where web files are located. Using the default setting of Userdir public_html, the above URL maps to a file @@ -95,15 +97,15 @@ alternate string to represent user directories. This functionality is not supported by mod_userdir. However, if users' home directories are structured in a regular way, then it is possible - to use the AliasMatch + to use the AliasMatch directive to achieve the desired effect. For example, to make http://www.example.com/upages/user/file.html map to /home/user/public_html/file.html, use the following AliasMatch directive:
-
AliasMatch ^/upages/([a-zA-Z0-9]*)/?(.*) - /home/$1/public_html/$2
-
URL Redirection
+
AliasMatch ^/upages/([a-zA-Z0-9]*)/?(.*) + /home/$1/public_html/$2
+
URL Redirection

The configuration directives discussed in the above sections tell Apache to get content from a specific place in the filesystem @@ -111,14 +113,14 @@ inform the client that the requested content is located at a different URL, and instruct the client to make a new request with the new URL. This is called redirection and is - implemented by the Redirect directive. For example, if + implemented by the Redirect directive. For example, if the contents of the directory /foo/ under the - DocumentRoot are moved + DocumentRoot are moved to the new directory /bar/, you can instruct clients to request the content at the new location as follows:
-
Redirect permanent /foo/ - http://www.example.com/bar/
+
Redirect permanent /foo/ + http://www.example.com/bar/

This will redirect any URL-Path starting in /foo/ to the same URL path on the @@ -126,20 +128,20 @@ substituted for /foo/. You can redirect clients to any server, not only the origin server.
-
Apache also provides a RedirectMatch directive for more +
Apache also provides a RedirectMatch directive for more complicated rewriting problems. For example, to redirect requests for the site home page to a different site, but leave all other requests alone, use the following configuration:
-
RedirectMatch permanent ^/$ - http://www.example.com/startpage.html
+
RedirectMatch permanent ^/$ + http://www.example.com/startpage.html

Alternatively, to temporarily redirect all pages on a site to one particular page, use the following:
-
RedirectMatch temp .* - http://www.example.com/startpage.html
-
Reverse Proxy
+
RedirectMatch temp .* + http://www.example.com/startpage.html
+
Reverse Proxy

Apache also allows you to bring remote documents into the URL space of the local server. This technique is called reverse @@ -154,14 +156,14 @@ the /bar/ directory on internal.example.com and returns them to the client as if they were from the local server.
-
-ProxyPass /foo/ http://internal.example.com/bar/ + +ProxyPass /foo/ http://internal.example.com/bar/ ProxyPassReverse /foo/ http://internal.example.com/bar/ -
+
-
The ProxyPass configures +
The ProxyPass configures the server to fetch the appropriate documents, while the -ProxyPassReverse +ProxyPassReverse directive rewrites redirects originating at internal.examle.com so that they target the appropriate directory on the local server. It is important to note, however, that @@ -169,10 +171,10 @@ links inside the documents will not be rewritten. So any absolute links on internal.example.com will result in the client breaking out of the proxy server and requesting directly from internal.example.com.
-
Rewriting Engine
+
Rewriting Engine

When even more powerful substitution is required, the rewriting - engine provided by mod_rewrite + engine provided by mod_rewrite can be useful. The directives provided by this module use characteristics of the request such as browser type or source IP address in deciding from where to serve content. In addition, @@ -182,7 +184,7 @@ breaking out of the proxy server and requesting directly from internal redirects (aliases), external redirects, and proxying. Many practical examples employing mod_rewrite are discussed in the URL Rewriting Guide.
-
File Not Found
+
File Not Found

Inevitably, URLs will be requested for which no matching file can be found in the filesystem. This can happen for @@ -196,7 +198,7 @@ breaking out of the proxy server and requesting directly from
Another common cause of "File Not Found" errors is accidental mistyping of URLs, either directly in the browser, or in HTML links. Apache provides the module - mod_speling (sic) to help with + mod_speling (sic) to help with this problem. When this module is activated, it will intercept "File Not Found" errors and look for a resource with a similar filename. If one such file is found, mod_speling will send an @@ -216,8 +218,8 @@ breaking out of the proxy server and requesting directly from
If all attempts to locate the content fail, Apache returns an error page with HTTP status code 404 (file not found). The appearance of this page is controlled with the - ErrorDocument directive + ErrorDocument directive and can be customized in a flexible manner as discussed in the Custom error responses and International Server Error Responses documents.
-

Apache HTTP Server Version 2.0

\ No newline at end of file +
Maintained by the Apache HTTP Server Documentation Project
Modules | Directives | FAQ | Glossary | Sitemap
\ No newline at end of file -- 2.50.1

$B%U%!%$%kL>(B	foo.html.en	foo +	foo foo.html	-	foo.html.en.gz	foo +	foo foo.html	foo.gz +	foo.gz foo.html.gz
foo.html - foo.html.gz +	foo.html + foo.html.gz foo.gz
foo.gz.html.en	foo - foo.gz +	foo + foo.gz foo.gz.html	foo.html	foo.html.gz.en	foo - foo.html +	foo + foo.html foo.html.gz	foo.gz

BeOS	`beos`
OS/2	`mpmt_os2`
Unix	`prefork`
Windows	`mpm_winnt`
BeOS	`beos`
OS/2	`mpmt_os2`
Unix	`prefork`
Windows	`mpm_winnt`

Apache HTTP Server Version 2.0

Binding

See also

Apache HTTP Server Version 2.0

Apache HTTP Server Version 2.0

$B%P%$%s%I(B

$B%P%$%s%I(B

$B;2>H(B

Apache HTTP Server Version 2.0

Apache HTTP Server Version 2.0

Configuration Files

Configuration Files

Apache HTTP Server Version 2.0

Apache HTTP Server Version 2.0

$B@_Dj%U%!%$%k(B

$B@_Dj%U%!%$%k(B

Apache HTTP Server Version 2.0

Apache HTTP Server Version 2.0

Content Negotiation

Content Negotiation

Apache HTTP Server Version 2.0

Apache HTTP Server Version 2.0

$B%3%s%F%s%H%M%4%7%(!<%7%g%s(B

$B%3%s%F%s%H%M%4%7%(!<%7%g%s(B

Apache HTTP Server Version 2.0

Apache HTTP Server Version 2.0

Dynamic Shared Object (DSO) Support

Dynamic Shared Object (DSO) Support

Apache HTTP Server Version 2.0

Apache HTTP Server Version 2.0

Environment Variables in Apache

Environment Variables in Apache

$B%P%$%s%I(B

$B%P%$%s%I(B

$B;2>H(B

$B@_Dj%U%!%$%k(B

$B@_Dj%U%!%$%k(B

$B%3%s%F%s%H%M%4%7%(!<%7%g%s(B

$B%3%s%F%s%H%M%4%7%(!<%7%g%s(B