0N/A<!
DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
0N/A<
TITLE>Access Control by URL</
TITLE>
0N/A<!-- Background white, links blue (unvisited), navy (visited), red (active) --> 0N/A<
H1 ALIGN="CENTER">Access Control by URL</
H1>
0N/A<
h2><
a name="location">The <
code><Location></
code> Directive</
a></
h2>
2365N/A<
strong>Syntax:</
strong> <Location <
em>URL prefix</
em>><
br>
2365N/A<
strong>Context:</
strong> server config, virtual host<
br>
0N/A<
strong>Status:</
strong> core<
br>
2365N/A<
p>The <Location> directive provides for access control by
URL. It is comparable to the <
ahref="mod/core.html#directory"><Directory></
a> directive, and
should be matched with a </Location> directive. Directives that
apply to the URL given should be listen
within. <
code><Location></
code> sections are processed in the
order they appear in the configuration file, after the
<Directory> sections and <
code>.htaccess</
code> files are
<
p>Note that, due to the way HTTP functions, <
em>URL prefix</
em>
should, save for proxy requests, be of the form <
code>/path/</
code>,
necessarily have to protect a directory (it can be an individual
file, or a number of files), and can include wild-cards. In a wild-card
string, `?' matches any single character, and `*' matches any
<
p>This functionality is especially useful when combined with the
directive. For example, to enable status requests, but allow them only
from browsers at
foo.com, you might use: