So according to this part: " <Location> and <LocationMatch> done simultaneously Apart from <Directory>, each group is processed in the order that they appear in the configuration files." I at least logically approached it correctly. Dunno. Perhaps it is something else. I have ruled out everything else and all roads lead back to this . . . the Apache location directives. I'll just keep looking at it. Thanks for the reference. -----Original Message----- From: Eric Covener [mailto:covener@xxxxxxxxx] Sent: Thursday, June 02, 2011 9:15 AM To: users@xxxxxxxxxxxxxxxx Subject: Re: how many <Location> directives can you have? On Wed, Jun 1, 2011 at 9:53 PM, Tommy Peterson <Tommy.Peterson@xxxxxxxxxxxxx> wrote: > I think I am confused about the <Location> directive. How many can you have? Can you list 4 or 5, for example, and they are all acted upon? Or does Apached just start with the first and stop there. Sorry for such a basic question but I ran into an issue. > > I used such a directive to lock down a particular directory. All was good. Then I decided that I only wanted part of the directory (web app) to be locked down. So I added several such Location directives. While it appeared to work . . . well without going into too much detail the application didn't require authentication. So I thought it was my application until I changed the directives back to one for the entire directory/application and it started working again as it should. > Generally, the contents of the matching sections are merged together. How this works for specific directives sometimes takes experimenting. http://httpd.apache.org/docs/current/sections.html#mergin Be aware also that location /foo includes anything under /foo. If you want more control, use LocationMatch. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx This message contains Devin Group confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail in error and delete this e-mail from your system. E-mail transmissions cannot be guaranteed secure, error-free and information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or contain viruses. The sender therefore does not accept liability for errors or omissions in the contents of this message which may arise as result of transmission. If verification is required please request hard-copy version. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|