On May 9, 2011 9:21 , Eric Covener <covener@xxxxxxxxx> wrote:
On Mon, May 9, 2011 at 9:13 AM, Sébastien Moretti <sebastien.moretti@xxxxxxx> wrote:I run several servers and sometimes for some of them, directives in FilesMatch seem never to be executed. Problems come when apache is the frontend of other servers such as tomcat or play framework, through mod_jk or mod_proxy.In Apache terms, these requests don't match any Directory or Files containers because they're not mapped to any Directory or file. Pieces of the URL aren't files. Use Location/LocationMatch.I should use LocationMatch everywhere, it will be less ambiguous for my mind.FWIW -- The manual cautions against this, since you might accidentally expose a resource on a 2nd URL (or via some 'equivalent URL?') and have access control mis-applied.
Or to put this another way... Location and LocationMatch don't really control access to resources, they control access via specific resource names; they leave resources accessible via other names / means. Directory and DirectoryMatch, on the other hand, protect the actual filesystem resources.
-- Mark Montague mark@xxxxxxxxxxx --------------------------------------------------------------------- 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
|