Httpd Location: Difference between revisions
No edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
* [[httpd Configuration#Directives]] | * [[httpd Configuration#Directives]] | ||
* [[httpd Directory | * [[httpd Directory|Directory]] | ||
=Overview= | |||
The <Location> directive limits the scope of the enclosed directives by URL. It is similar to the <Directory> directive, and starts a subsection which is terminated with a </Location> directive. | |||
<Location> sections are processed in the order they appear in the configuration file, ''after'' the <Directory> sections and .htaccess files are read, and after the <Files> sections. | |||
<Location> sections ''operate completely outside the filesystem''. This has several consequences. Most importantly, <Location> directives should not be used to control access to filesystem locations. Since several different URLs may map to the same filesystem location, such access controls may by circumvented. | |||
The enclosed directives will be applied to the request if the path component of the URL meets any of the following criteria: | |||
* 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). | |||
Latest revision as of 03:07, 10 January 2016
External
Internal
Overview
The <Location> directive limits the scope of the enclosed directives by URL. It is similar to the <Directory> directive, and starts a subsection which is terminated with a </Location> directive.
<Location> sections are processed in the order they appear in the configuration file, after the <Directory> sections and .htaccess files are read, and after the <Files> sections.
<Location> sections operate completely outside the filesystem. This has several consequences. Most importantly, <Location> directives should not be used to control access to filesystem locations. Since several different URLs may map to the same filesystem location, such access controls may by circumvented.
The enclosed directives will be applied to the request if the path component of the URL meets any of the following criteria:
- 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).