Well, I sent that too early. You could have mappings like this:
/discover/123/=anon /discover/**=authc In this case, /discover/123 would not get mapped to the authc. On the other hand, if the list of things like /discover/123 is long enough, this would become unmanageble pretty quickly. And, I take back my "no regex" - there is a org.apache.shiro.util.RegExPatternMatcher - you would need to set this on the PathMatchingFilterChainResolver - I'm not sure the easiest way to do that though. On Fri, May 24, 2013 at 8:52 AM, Jared Bunting <[email protected]>wrote: > I'm not aware of a regex mapping functionality, but shiro does follow a > "first-matched" rule. So, you could have mappings like this: > > > On Fri, May 24, 2013 at 5:50 AM, Onur Gunduru <[email protected]>wrote: > >> Unfortunately this is not the only url I'll have to duplicate rules for. >> Does >> the shiro filter provide regular expression mapping for rules? >> >> for example i also have a /discover/123/ url which is public? (Not my >> call). >> If i map /discover/** to authc then shiro will intercept it as well. >> >> BTW is it an expected behaviour for shiro not to intercept when a request >> is >> forwarded? After all, it's kind of another request and shiro has the >> dispatcher mapping for FORWARD? I'm open to any ideas? >> >> Thanks! >> >> >> >> -- >> View this message in context: >> http://shiro-user.582556.n2.nabble.com/Using-urlrewritefilter-forward-with-Shiro-tp7578765p7578769.html >> Sent from the Shiro User mailing list archive at Nabble.com. >> > >
