Hello Shiro Users:

I have an issue with a custom authentication filter (implements
javax.servlet.Filter) I've written being used in the
1.2.0<http://search.maven.org/#artifactdetails%7Corg.apache.shiro.tools%7Cshiro-tools%7C1.2.0%7Cpom>
shiro
release (from maven). I've got the app configured using spring and am using
the filterChainDefinitions property in the ShiroFilterFactoryBean:

/profile = myAuthFilter
/pathOther/** myAuthFilter

when I attempt to access any of the protected url's with myAuthFilter, if
the url has a query string parameter

https://myserver.com/profile?param=val

It reaches my authentication filter as

https://myserver.com/profile?param=val?param=val (twice)

If I unconfigure the filter from shiro and just wire the filter url mapping
in web.xml,  my filter request appears correctly

https://myserver.com/profile?param=val

I think this may be a misconfiguration on my part or possible a real bug,
but am looking for where I might start debugging the source to follow the
ServletRequest path through shiro from the request in the browser to my
auth filter.

Does someone on the list here know where I can start?  I've tried looking
in a couple of files referenced in the Spring configuration, but the API is
pretty big and I'd like to narrow down to a more focused package.

Thanks for your help.
Bill.

Reply via email to