Difference between revisions of "Apache HTTP Server"
m (Added sections based off of official documentation)
m (Tweaked note re LDAP/nested groups)
|Line 5:||Line 5:|
Revision as of 10:36, 20 February 2015
- Prior to version 2.4 Apache did not support nested LDAP groups
Much of the following is lifted directly from the official documentation .
<Location>sections are processed in the order they appear in the configuration file, after the
.htaccessfiles are read, and after the
- The specified location matches exactly the path component of the URL.
- The specified location, which ends in a forward slash, is a prefix of the path component of the URL (treated as a context root).
- The specified location, with the addition of a trailing slash, is a prefix of the path component of the URL (also treated as a context root).
In the example below, where no trailing slash is used, requests to
/private1/file.txt will have the enclosed directives applied, but
/private1other would not.
<Location /private1> # ... </Location>
In the example below, where a trailing slash is used, requests to
/private2/file.txt will have the enclosed directives applied, but
/private2other would not.
<Location /private2/> # ... </Location>
When to use
<Location> to apply directives to content that lives outside the filesystem. For content that lives in the filesystem, use
<Files>. An exception is
<Location />, which is an easy way to apply a configuration to the entire server.