Binding

+ -->Binding - Apache HTTP Server

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

Overview

diff --git a/docs/manual/configuring.html.en b/docs/manual/configuring.html.en index 3d840d9bcb..adb4bf5c91 100644 --- a/docs/manual/configuring.html.en +++ b/docs/manual/configuring.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Configuration Files - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Configuration Files

+ -->Configuration Files - Apache HTTP Server

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

diff --git a/docs/manual/content-negotiation.html.en b/docs/manual/content-negotiation.html.en index 6cf4c01fc0..6e44104496 100644 --- a/docs/manual/content-negotiation.html.en +++ b/docs/manual/content-negotiation.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Content Negotiation - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Content Negotiation

+ -->Content Negotiation - Apache HTTP Server

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 diff --git a/docs/manual/dso.html.en b/docs/manual/dso.html.en index 8f537e788f..92e065510a 100644 --- a/docs/manual/dso.html.en +++ b/docs/manual/dso.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Dynamic Shared Object (DSO) Support - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Dynamic Shared Object (DSO) Support

+ -->Dynamic Shared Object (DSO) Support - Apache HTTP Server

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 diff --git a/docs/manual/env.html.en b/docs/manual/env.html.en index d34e6da803..a2dd69087a 100644 --- a/docs/manual/env.html.en +++ b/docs/manual/env.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Environment Variables in Apache - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Environment Variables in Apache

+ -->Environment Variables in Apache - Apache HTTP Server

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 diff --git a/docs/manual/filter.html.en b/docs/manual/filter.html.en index 8cbeb15c2b..1caec9a86d 100644 --- a/docs/manual/filter.html.en +++ b/docs/manual/filter.html.en @@ -1,12 +1,14 @@ -Filters - Apache HTTP Server

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

This document describes the use of filters in Apache.
-
Filters
+
Filters
-
Related Modules

mod_deflate
mod_ext_filter
mod_include
Related Directives

AddInputFilter
AddOutputFilter
RemoveInputFilter
RemoveOutputFilter
ExtFilterDefine
ExtFilterOptions
SetInputFilter
SetOutputFilter
+
Related Modules Related Directives
mod_deflate
mod_ext_filter
mod_include
AddInputFilter
AddOutputFilter
RemoveInputFilter
RemoveOutputFilter
ExtFilterDefine
ExtFilterOptions
SetInputFilter
SetOutputFilter

A filter is a process that is applied to data that is sent or received by the server. Data sent by clients to the @@ -20,12 +22,12 @@ can provide filters that are selectable using run-time configuration directives. The set of filters that apply to data can be manipulated with the - SetInputFilter, - SetOutputFilter, - AddInputFilter, - AddOutputFilter, - RemoveInputFilter, and - RemoveOutputFilter + SetInputFilter, + SetOutputFilter, + AddInputFilter, + AddOutputFilter, + RemoveInputFilter, and + RemoveOutputFilter directives.

The following user-selectable filters are currently provided @@ -33,13 +35,13 @@

INCLUDES
-
Server-Side Includes processing by mod_include
+
Server-Side Includes processing by mod_include

DEFLATE

Compress output before sending it to the client using - mod_deflate + mod_deflate

-
In addition, the module mod_ext_filter allows +
In addition, the module mod_ext_filter allows for external programs to be defined as filters.
-

Related Modules	Related Directives
`mod_deflate` `mod_ext_filter` `mod_include`	`AddInputFilter` `AddOutputFilter` `RemoveInputFilter` `RemoveOutputFilter` `ExtFilterDefine` `ExtFilterOptions` `SetInputFilter` `SetOutputFilter`

Apache HTTP Server Version 2.0

\ No newline at end of file +

\ No newline at end of file diff --git a/docs/manual/handler.html.en b/docs/manual/handler.html.en index ab5d3b7b59..e6ef2eafc4 100644 --- a/docs/manual/handler.html.en +++ b/docs/manual/handler.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Apache's Handler Use - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Apache's Handler Use

+ -->Apache's Handler Use - Apache HTTP Server

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
Programmer's Note

What is a Handler

diff --git a/docs/manual/howto/htaccess.html.en b/docs/manual/howto/htaccess.html.en index ce05e59ed8..00758d3d24 100644 --- a/docs/manual/howto/htaccess.html.en +++ b/docs/manual/howto/htaccess.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Apache Tutorial: .htaccess files - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Apache Tutorial: .htaccess files

+ -->Apache Tutorial: .htaccess files - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Apache Tutorial: .htaccess files

.htaccess files provide a way to make configuration changes on a per-directory basis.

.htaccess files
What they are/How to use them
When (not) to use .htaccess files
How directives are applied
Authentication example
Server side includes example
CGI example
Troubleshooting

.htaccess files

diff --git a/docs/manual/howto/public_html.html.en b/docs/manual/howto/public_html.html.en index 2ccf4369d4..bf768889f4 100644 --- a/docs/manual/howto/public_html.html.en +++ b/docs/manual/howto/public_html.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Per-user web directories - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Per-user web directories

+ -->Per-user web directories - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Per-user web directories

On systems with multiple users, each user can be permitted to have a web site in their home directory using the UserDir directive. Visitors to a URL http://example.com/~username/ will get content diff --git a/docs/manual/install.html.en b/docs/manual/install.html.en index 4273d5e0ca..a8f7a78ace 100644 --- a/docs/manual/install.html.en +++ b/docs/manual/install.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Compiling and Installing - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Compiling and Installing

+ -->Compiling and Installing - Apache HTTP Server

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 diff --git a/docs/manual/invoking.html.en b/docs/manual/invoking.html.en index 074abe3705..7d592bdf92 100644 --- a/docs/manual/invoking.html.en +++ b/docs/manual/invoking.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Starting Apache - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Starting Apache

+ -->Starting Apache - Apache HTTP Server

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 diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en index 5be2bf3970..8b2b2272e0 100644 --- a/docs/manual/logs.html.en +++ b/docs/manual/logs.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Log Files - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Log Files

+ -->Log Files - Apache HTTP Server

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 diff --git a/docs/manual/misc/security_tips.html.en b/docs/manual/misc/security_tips.html.en index 05b4f86dbb..9f4623b903 100644 --- a/docs/manual/misc/security_tips.html.en +++ b/docs/manual/misc/security_tips.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Security Tips - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Security Tips

+ -->Security Tips - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Security Tips

Some hints and tips on security issues in setting up a web server. Some of the suggestions will be general, others specific to Apache.

Permissions on ServerRoot Directories
Server Side Includes
CGI in General
Non Script Aliased CGI
Script Aliased CGI
Protecting System Settings
Protect Server Files by Default
Watching Your Logs

Permissions on ServerRoot Directories

diff --git a/docs/manual/mpm.html.en b/docs/manual/mpm.html.en index 45275c9c0c..05c47947a0 100644 --- a/docs/manual/mpm.html.en +++ b/docs/manual/mpm.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Multi-Processing Modules (MPMs) - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Multi-Processing Modules (MPMs)

+ -->Multi-Processing Modules (MPMs) - Apache HTTP Server

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

diff --git a/docs/manual/new_features_2_0.html.en b/docs/manual/new_features_2_0.html.en index 4b7c567ad7..270621d5d4 100644 --- a/docs/manual/new_features_2_0.html.en +++ b/docs/manual/new_features_2_0.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Overview of new features in Apache 2.0 - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Overview of new features in Apache 2.0

+ -->Overview of new features in Apache 2.0 - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Overview of new features in Apache 2.0

Enhancements:

Core Enhancements
Module Enhancements

Core Enhancements

diff --git a/docs/manual/sections.html.en b/docs/manual/sections.html.en index fce7d18545..e1b7282af6 100644 --- a/docs/manual/sections.html.en +++ b/docs/manual/sections.html.en @@ -1,63 +1,65 @@ -Configuration Sections - Apache HTTP Server

Apache HTTP Server Version 2.0
Configuration Sections

Directives in the configuration files may apply to the + -->Configuration Sections - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
Configuration Sections

Directives in the configuration files may apply to the entire server, or they may be restricted to apply only to particular directories, files, hosts, or URLs. This document describes how to use configuration section containers or .htaccess files to change the scope of other configuration directives.
-
Types of Configuration Section Containers
Filesystem and Webspace
Filesystem Containers
Webspace Containers
Wildcards and Regular Expressions
What to use When
Virtual Hosts
Proxy
What Directives are Allowed?
How the sections are merged
Some Examples
Types of Configuration Section Containers
+
Types of Configuration Section Containers
Filesystem and Webspace
Virtual Hosts
Proxy
What Directives are Allowed?
How the sections are merged
Types of Configuration Section Containers
-
Related Modules

core
mod_proxy
Related Directives

<Directory>
<DirectoryMatch>
<Files>
<FilesMatch>
<IfDefine>
<IfModule>
<Location>
<LocationMatch>
<Proxy>
<ProxyMatch>
<VirtualHost>
+
Related Modules Related Directives
core
mod_proxy
<Directory>
<DirectoryMatch>
<Files>
<FilesMatch>
<IfDefine>
<IfModule>
<Location>
<LocationMatch>
<Proxy>
<ProxyMatch>
<VirtualHost>

There are two basic types of containers. Most containers are evaluated for each request. The enclosed directives are applied only -for those requests that match the containers. The <IfDefine> and <IfModule> containers, on the +for those requests that match the containers. The <IfDefine> and <IfModule> containers, on the other hand, are evaluated only at server startup and restart. If their conditions are true at startup, then the enclosed directives will apply to all requests. If the conditions are not true, the enclosed directives will be ignored.
-
The <IfDefine> directive +
The <IfDefine> directive encloses directives that will only be applied if an appropriate parameter is defined on the httpd command line. For example, with the following configuration, all requests will be redirected to another site only if the server is started using httpd -DClosedForNow:
-
-<IfDefine ClosedForNow> -Redirect / http://otherserver.example.com/ + +<IfDefine ClosedForNow> +Redirect / http://otherserver.example.com/ </IfDefine> -
+
-
The <IfModule> +
The <IfModule> directive is very similar, except it encloses directives that will only be applied if a particular module is available in the server. The module must either be statically compiled in the server, or it -must be dynamically compiled and its LoadModule line must be earlier in the +must be dynamically compiled and its LoadModule line must be earlier in the configuration file. This directive should only be used if you need your configuration file to work whether or not certain modules are installed. It should not be used to enclose directives that you want to work all the time, because it can suppress useful error messages about missing modules.
-
In the following example, the MimeMagicFiles directive will be -applied only if mod_mime_magic is available.
+
In the following example, the MimeMagicFiles directive will be +applied only if mod_mime_magic is available.
-
-<IfModule mod_mime_magic.c> -MimeMagicFile conf/magic + +<IfModule mod_mime_magic.c> +MimeMagicFile conf/magic </IfModule> -
+
-
Both <IfDefine> -and <IfModule> +
Both <IfDefine> +and <IfModule> can apply negative conditions by preceding their test with "!". Also, these sections can be nested to achieve more complex restrictions.
-
Filesystem and Webspace
+

Related Modules	Related Directives
`core` `mod_proxy`	`<Directory>` `<DirectoryMatch>` `<Files>` `<FilesMatch>` `<IfDefine>` `<IfModule>` `<Location>` `<LocationMatch>` `<Proxy>` `<ProxyMatch>` `<VirtualHost>`

Filesystem and Webspace

The most commonly used configuration section containers are the ones that change the configuration of particular places in the @@ -76,40 +78,40 @@ default Apache install on Unix. The webspace need not map directly to the filesystem, since webpages may be generated dynamically from databases or other locations.

Filesystem Containers

The <Directory> -and <Files> +

The <Directory> +and <Files> directives, along with their regex counterparts, apply directives to -parts of the filesystem. Directives enclosed in a <Directory> section apply to +parts of the filesystem. Directives enclosed in a <Directory> section apply to the named filesystem directory and all subdirectories of that directory. The same effect can be obtained using .htaccess files. For example, in the following configuration, directory indexes will be enabled for the /var/web/dir1 directory and all subdirectories.

-<Directory /var/web/dir1> -Options +Indexes + +<Directory /var/web/dir1> +Options +Indexes </Directory> -

Directives enclosed in a <Files> section apply to any file with +

Directives enclosed in a <Files> section apply to any file with the specified name, regardless of what directory it lies in. So for example, the following configuration directives will, when placed in the main section of the configuration file, deny access to any file named private.html regardless of where it is found.

-<Files private.html> -Order allow,deny -Deny from all + +<Files private.html> +Order allow,deny +Deny from all </Files> -

To address files found in a particular part of the filesystem, the -<Files> and -<Directory> sections +<Files> and +<Directory> sections can be combined. For example, the following configuration will deny access to /var/web/dir1/private.html, /var/web/dir1/subdir2/private.html, @@ -117,19 +119,19 @@ access to /var/web/dir1/private.html, of private.html found under the /var/web/dir1/ directory.

-<Directory /var/web/dir1> -<Files private.html> -Order allow,deny -Deny from all -</Files> + +<Directory /var/web/dir1> +<Files private.html> +Order allow,deny +Deny from all +</Files> </Directory> -

Webspace Containers

The <Location> +

The <Location> directive and its regex counterpart, on the other hand, change the configuration for content in the webspace. For example, the following configuration prevents access to any URL-path that begins in /private. @@ -139,32 +141,32 @@ In particular, it will apply to requests for http://yoursite.example.com/private/dir/file.html as well as any other requests starting with the /private string.

-<Location /private> -Order Allow,Deny -Deny from all + +<Location /private> +Order Allow,Deny +Deny from all </Location> -

The <Location> +

The <Location> directive need not have anything to do with the filesystem. For example, the following example shows how to map a particular -URL to an internal Apache handler provided by mod_status. +URL to an internal Apache handler provided by mod_status. No file called server-status needs to exist in the filesystem.

-<Location /server-status> -SetHandler server-status + +<Location /server-status> +SetHandler server-status </Location> -

Wildcards and Regular Expressions

The <Directory>, -<Files>, and -<Location> +

The <Directory>, +<Files>, and +<Location> directives can each use shell-style wildcard characters as in fnmatch from the C standard library. The character "*" matches any sequence of characters, "?" matches any single character, @@ -173,7 +175,7 @@ character will not be matched by any wildcard; it must be specified explictly.

If even more flexible matching is required, each -container has a regular-expression (regex) counterpart <DirectoryMatch>, <FilesMatch>, and <LocationMatch> that allow +container has a regular-expression (regex) counterpart <DirectoryMatch>, <FilesMatch>, and <LocationMatch> that allow perl-compatible regular expressions to be used in choosing the matches. But see the section below on @@ -183,56 +185,56 @@ how directives are applied.

A non-regex wildcard section that changes the configuration of all user directories could look as follows:

-<Directory /home/*/public_html> -Options Indexes + +<Directory /home/*/public_html> +Options Indexes </Directory> -

Using regex sections, we can deny access to many types of image files at once:

-<FilesMatch \.(?i:gif|jpe?g|png)$> -Order allow,deny -Deny from all + +<FilesMatch \.(?i:gif|jpe?g|png)$> +Order allow,deny +Deny from all </FilesMatch> -

What to use When

Choosing between filesystem containers and webspace containers is actually quite easy. When applying directives to objects that reside -in the filesystem always use <Directory> or <Files>. When applying directives to objects +in the filesystem always use <Directory> or <Files>. When applying directives to objects that do not reside in the filesystem (such as a webpage generated from -a database), use <Location>.

+a database), use <Location>.

It is important to never use <Location> when trying to restrict +

It is important to never use <Location> when trying to restrict access to objects in the filesystem. This is because many different webspace locations (URLs) could map to the same filesystem location, allowing your restrictions to be circumvented. For example, consider the following configuration:

-<Location /dir/> -Order allow,deny -Deny from all + +<Location /dir/> +Order allow,deny +Deny from all </Location> -

This works fine if the request is for http://yoursite.example.com/dir/. But what if you are on a case-insensitive filesystem? Then your restriction could be easily circumvented by requesting -http://yoursite.example.com/DIR/. The <Directory> directive, in +http://yoursite.example.com/DIR/. The <Directory> directive, in contrast, will apply to any content served from that location, regardless of how it is called. (An exception is filesystem links. The same directory can be placed in more than one part of the -filesystem using symbolic links. The <Directory> directive will follow the symbolic +filesystem using symbolic links. The <Directory> directive will follow the symbolic link without resetting the pathname. Therefore, for the highest level of security, symbolic links should be disabled with the appropriate -Options directive.)

+Options directive.)

If you are, perhaps, thinking that none of this applies to you because you use a case-sensitive filesystem, remember that there are @@ -244,60 +246,60 @@ rule. Putting configuration restrictions in a <Location to all requests regardless of the specific URL.


 
 
-Virtual Hosts
+

`Virtual Hosts`


 
-The <VirtualHost>
+
The <VirtualHost>
 container encloses directives that apply to specific hosts.
 This is useful when serving multiple hosts from the same machine
 with a different configuration for each.  For more information,
 see the Virtual Host Documentation.
-Proxy
+

`Proxy`


 
-The <Proxy>
-and <ProxyMatch>
+
The <Proxy>
+and <ProxyMatch>
 containers apply enclosed configuration directives only
-to sites accessed through mod_proxy's proxy server
+to sites accessed through mod_proxy's proxy server
 that match the specified URL.  For example, the following configuration
 will prevent the proxy server from being used to access the
 cnn.com website.
 
-
-<Proxy http://cnn.com/*>

-Order allow,deny

-Deny from all

+
+<Proxy http://cnn.com/*>

+Order allow,deny

+Deny from all

 </Proxy>
-
-What Directives are Allowed?
+

What Directives are Allowed?

To find out what directives are allowed in what types of configuration sections, check the Context of the directive. Everything that is allowed in -<Directory> +<Directory> sections is also syntactically allowed in -<DirectoryMatch>, -<Files>, -<FilesMatch>, -<Location>, -<LocationMatch>, -<Proxy>, -and <ProxyMatch> +<DirectoryMatch>, +<Files>, +<FilesMatch>, +<Location>, +<LocationMatch>, +<Proxy>, +and <ProxyMatch> sections. There are some exceptions, however.

The AllowOverride directive -works only in <Directory> +
The AllowOverride directive +works only in <Directory> sections.
The FollowSymLinks and -SymLinksIfOwnerMatch Options work only in <Directory> sections or +SymLinksIfOwnerMatch Options work only in <Directory> sections or .htaccess files.
The Options directive cannot -be used in <Files> -and <FilesMatch> +
The Options directive cannot +be used in <Files> +and <FilesMatch> sections.

How the sections are merged

How the sections are merged

The configuration sections are applied in a very particular order. Since this can have important effects on how configuration directives @@ -306,39 +308,39 @@ are interpreted, it is important to understand how this works.

The order of merging is:

<Directory> (except regular expressions) +
<Directory> (except regular expressions) and .htaccess done simultaneously (with .htaccess, if allowed, - overriding <Directory>)

<Directory>

<DirectoryMatch> +
<DirectoryMatch> (and <Directory ~>)
<Files> and <FilesMatch> done +
<Files> and <FilesMatch> done simultaneously
<Location> - and <LocationMatch> done simultaneously
<Location> + and <LocationMatch> done simultaneously

Apart from <Directory>, each group is processed in - the order that they appear in the configuration files. <Directory> (group 1 above) +

Apart from <Directory>, each group is processed in + the order that they appear in the configuration files. <Directory> (group 1 above) is processed in the order shortest directory component to longest. So for example, <Directory /var/web/dir> will be processed before <Directory - /var/web/dir/subdir>. If multiple <Directory> sections apply + /var/web/dir/subdir>. If multiple <Directory> sections apply to the same directory they are processed in the configuration file - order. Configurations included via the Include directive will be treated as if + order. Configurations included via the Include directive will be treated as if they were inside the including file at the location of the - Include directive.

+ Include directive.

Sections inside <VirtualHost> sections +

Sections inside <VirtualHost> sections are applied after the corresponding sections outside the virtual host definition. This allows virtual hosts to override the main server configuration.

Later sections override earlier ones.

Technical Note
+
Technical Note
There is actually a <Location>/<LocationMatch> sequence performed just before the name translation phase @@ -346,59 +348,59 @@ are interpreted, it is important to understand how this works.
are used to map URLs to filenames). The results of this sequence are completely thrown away after the translation has completed. -

Some Examples

Below is an artificial example to show the order of merging. Assuming they all apply to the request, the directives in this example will be applied in the order A > B > C > D > E.

-<Location /> -E -</Location> - -<Files f.html> -D -</Files> - -<VirtualHost *> -<Directory /a/b> -B -</Directory> -</VirtualHost> - -<DirectoryMatch "^.*b$"> -C -</DirectoryMatch> - -<Directory /a/b> -A -</Directory> - -

+<Location /> +E +</Location> + +<Files f.html> +D +</Files> + +<VirtualHost *> +<Directory /a/b> +B +</Directory> +</VirtualHost> + +<DirectoryMatch "^.*b$"> +C +</DirectoryMatch> + +<Directory /a/b> +A +</Directory> + +

For a more concrete example, consider the following. Regardless of -any access restrictions placed in <Directory> sections, the <Location> section will be +any access restrictions placed in <Directory> sections, the <Location> section will be evaluated last and will allow unrestricted access to the server. In other words, order of merging is important, so be careful!

-<Location /> -Order deny,allow -Allow from all -</Location> - -# Woops! This <Directory> section will have no effect -<Directory /> -Order allow,deny -Allow from all -Deny from badguy.example.com + +<Location /> +Order deny,allow +Allow from all +</Location> + +# Woops! This <Directory> section will have no effect +<Directory /> +Order allow,deny +Allow from all +Deny from badguy.example.com </Directory> -

Apache HTTP Server Version 2.0

\ No newline at end of file +

\ No newline at end of file diff --git a/docs/manual/server-wide.html.en b/docs/manual/server-wide.html.en index a32bb6dfc0..6e6b5950f7 100644 --- a/docs/manual/server-wide.html.en +++ b/docs/manual/server-wide.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Server-Wide Configuration - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Server-Wide Configuration

+ -->Server-Wide Configuration - Apache HTTP Server

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 basic operations of the server.

diff --git a/docs/manual/stopping.html.en b/docs/manual/stopping.html.en index 3aa32b3923..4a976d073f 100644 --- a/docs/manual/stopping.html.en +++ b/docs/manual/stopping.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Stopping and Restarting - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Stopping and Restarting

+ -->Stopping and Restarting - Apache HTTP Server

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.

diff --git a/docs/manual/suexec.html.en b/docs/manual/suexec.html.en index 57dc5667dd..a946accc54 100644 --- a/docs/manual/suexec.html.en +++ b/docs/manual/suexec.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->suEXEC Support - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

suEXEC Support

+ -->suEXEC Support - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

suEXEC Support

The suEXEC feature provides Apache users the ability to run CGI and SSI programs diff --git a/docs/manual/upgrading.html.en b/docs/manual/upgrading.html.en index 1d242c3bb1..28c3f7115f 100644 --- a/docs/manual/upgrading.html.en +++ b/docs/manual/upgrading.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Upgrading to 2.0 from 1.3 - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Upgrading to 2.0 from 1.3

+ -->Upgrading to 2.0 from 1.3 - Apache HTTP Server

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 diff --git a/docs/manual/urlmapping.html.en b/docs/manual/urlmapping.html.en index 169e607b18..e9b74a41f8 100755 --- a/docs/manual/urlmapping.html.en +++ b/docs/manual/urlmapping.html.en @@ -4,7 +4,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->Mapping URLs to Filesystem Locations - Apache HTTP Server

Apache > HTTP Server > Documentation > Version 2.0

Mapping URLs to Filesystem Locations

+ -->Mapping URLs to Filesystem Locations - Apache HTTP Server

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.

Binding

Binding

See also

Configuration Files

Configuration Files

Content Negotiation

Content Negotiation

Dynamic Shared Object (DSO) Support

Dynamic Shared Object (DSO) Support

Environment Variables in Apache

Environment Variables in Apache

Apache HTTP Server Version 2.0

Filters

Filters

Apache HTTP Server Version 2.0

Apache's Handler Use

Apache's Handler Use

Apache Tutorial: .htaccess files

Apache Tutorial: .htaccess files

Per-user web directories

Per-user web directories

Compiling and Installing

Compiling and Installing

Starting Apache

Starting Apache

Log Files

Log Files

Security Tips

Security Tips

Multi-Processing Modules (MPMs)

Multi-Processing Modules (MPMs)

Overview of new features in Apache 2.0

Overview of new features in Apache 2.0

Apache HTTP Server Version 2.0

Configuration Sections

Configuration Sections

Technical Note

Apache HTTP Server Version 2.0

Server-Wide Configuration

Server-Wide Configuration

Stopping and Restarting

Stopping and Restarting

suEXEC Support

suEXEC Support

Upgrading to 2.0 from 1.3

Upgrading to 2.0 from 1.3

Mapping URLs to Filesystem Locations

Mapping URLs to Filesystem Locations