yap,
I use to observe the same (odd) behaviour with standard j2ee form login
configuration ... but with acegi you can alwaysUseDefaultTargetUrl to
avoid this (setting default target to /init.action or a like).
hih
On Mon, Apr 21, 2008 at 12:36 PM, Sorin Postelnicu [EMAIL PROTECTED]
wrote:
Hi
:)
Thanks for your reply.
It's a little more complicated than that :)
Our client has very complex requirements. I already created an
ExtendedAuthenticationProcessingFilter to handle some of these requirements :)
But the problem with POST is quite tricky.
I discovered its cause, which is as
