[jetty-users] IPAccessHandler logic conundrum: all for /*, only some for

[lamphus <perssond9@xxxxxxxxx>]

Hi, jetty newbie here, and if this has been covered elsewhere then a hint as
to where is much appreciated.

Running jetty8 as applications being run have proved a tad problematic in 9
(most likely because I don't know enough about how to configure them/jetty)
and
reading the docs for jetty8's IPAccessHandler I see that

-if any whitelist entry then everything else is blacklisted
-blacklist entries will override whitelist ones if concerning the same IP /
resource
-resource paths can end with /* , not just *

What I would to accomplish is:

1. A specific range of IPs should be able to access /webapp/*
2. All IPs should be able to access /webapp/call....
3. All IPs should not be able to access /webapp/a/* or /webapp/b/* (that is
to say, only the specific range in 1. should be able to)
4. All IPs should be able to access /webapp/c/*

If I whitelist <every IP>|/webapp/c/* and <every IP>|/webapp/* and <specific
range>|webapp/a/* and /b/* then every IP has access to everything: can't say
/webapp/firstbitofcall* .

Can't use blacklist <!=IP>|webapp/a/* because there isn't a "not" to use as
far as I can tell.  

Is there a way to say <specific range of IPs>|/webapp/a while at the same
time saying <all IPs>|/webapp/* and not having the second overriding the
first? Or equivalent?

Many thanks for any advice : ) 

(P.S, I really hope this wasn't mailed twice - the first attempt was not
accepted to the list because I hadn't registered for the specific jetty list
and I subsequently removed it)



--
View this message in context: http://jetty.4.x6.nabble.com/IPAccessHandler-logic-conundrum-all-for-only-some-for-a-tp4963393.html
Sent from the Jetty User mailing list archive at Nabble.com.