I just looked at the Spring 2.5.6 CharacterEncodingFilter source and I don't see anything that would conflict at all - and we don't alter a Response's characterEncoding anywhere in Shiro. It doesn't use the HttpSession either. It should work perfectly fine either in front of or behind the ShiroFilter.
Until I we see exceptions or a test case, I don't think there is anything to do - it should work fine. Something else must be causing problems (if there are even still problems). - Les On Fri, Dec 18, 2009 at 1:29 AM, Peter Ledbrook <[email protected]> wrote: >> If you have a chance to test it out again, please share the results. >> I'd like to see if there is anything we need to do to change our >> implementation. We haven't heard about problems with other filter >> ordering issues, so maybe this is related just to the Spring filter, >> and if so, maybe we could contribute a fix back. In either case, I'd >> be happy to help to try and resolve it once we know why the problem >> occurs. > > Here's the original issue: > > http://jira.codehaus.org/browse/GRAILSPLUGINS-338 > > Perhaps it is/was a problem with the request wrapper? Not sure how to > test it to be honest, even after reading the problem description. > > Cheers, > > Peter >
