198N/A<!
DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
198N/A<
TITLE>Access Control by URL</
TITLE>
198N/A<!-- Background white, links blue (unvisited), navy (visited), red (active) --> 198N/A<
H1 ALIGN="CENTER">Access Control by URL</
H1>
198N/A<
h2><
A name="location">The <
CODE><Location></
CODE> Directive</
A></
h2>
198N/A<
STRONG>Syntax:</
STRONG> <Location <
EM>URL prefix</
EM>><
BR>
198N/A<
STRONG>Context:</
STRONG> server config, virtual host<
BR>
198N/A<
STRONG>Status:</
STRONG> core<
BR>
198N/A<
P>The <Location> directive provides for access control by
198N/AURL. It is comparable to the <
A 198N/Ashould be matched with a </Location> directive. Directives that
198N/Aapply to the URL given should be listen
198N/Awithin. <
CODE><Location></
CODE> sections are processed in the
198N/Aorder they appear in the configuration file, after the
379N/A<Directory> sections and <
CODE>.htaccess</
CODE> files are
198N/A<
P>Note that, due to the way HTTP functions, <
EM>URL prefix</
EM>
379N/Ashould, save for proxy requests, be of the form <
CODE>/path/</
CODE>,
379N/Anecessarily have to protect a directory (it can be an individual
379N/Afile, or a number of files), and can include wild-cards. In a wild-card
379N/Astring, `?' matches any single character, and `*' matches any
198N/Asequences of characters.
198N/A<
P>This functionality is especially useful when combined with the
198N/Adirective. For example, to enable status requests, but allow them only
379N/A <Location /status>
379N/A SetHandler server-status