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.
Best, Les On Wed, Dec 16, 2009 at 12:18 PM, Peter Ledbrook <[email protected]> wrote: >> Is there a reason it must come after the CharEncodingFilter? Do we >> have a choice, or does Grails force this? > > I don't recollect what the problem was, but I think encoding breaks > for some reason if the Shiro filter comes before the character > encoding one. Without knowing what the problem actually was, it's > difficult to say whether it's been fixed or not. > > Cheers, > > Peter >
