Thanks for the tip! The PathMatchingFilterChainResolver constructors just create an AntPathMatcher (this could actually be injected) anyway it is still possible to set the matcher. I've no idea how to do this in shiro.ini, but i'll check it out.
However this still feels like coupling SEO (the whole point of pretty urls) and security. I think i need to find a way to reset the ".FILTERED" parameter without interfering shiro internals? -- View this message in context: http://shiro-user.582556.n2.nabble.com/Using-urlrewritefilter-forward-with-Shiro-tp7578765p7578774.html Sent from the Shiro User mailing list archive at Nabble.com.
