On Mon, Apr 19, 2010 at 4:22 PM, Nick Tkach <ntkach@xxxxxxxxxx> wrote: > Is it possible, for a given URL that's being directed to mod_jk, to lock it down so that you can only access it from a particular subnet? > > For example, let's say I have an app with JkMounts defined: > > JkMount /myapp worker1 > JkMount /myapp/sub worker2 > JkMount / worker3 > > Then I have a sub-directory, /admin that I want to restrict to being only available from 192.168.1.*. Is there some combination of JkMount and something like this that will get the desired effect or is this not possible with just mod_jk and Location? Do you *have* to do something with Java enterprise resources to lock it down? > > <Location /admin> > Order deny, allow > deny from all > allow from 192.168.1 > </Location> > I don't use mod_jk, but doesn't what you typed do exactly what you want? Have you tried it? The authnz layers in apache don't care where the actual content comes from*. Cheers Tom * For <Location> - obviously for <File> they do.. --------------------------------------------------------------------- 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
|