There's no perfect solution. You should choose a first-win or last-win
strategy.
Paul
On 10/1/07, Anton Pussep <[EMAIL PROTECTED]> wrote:
>
> First of all thanks a lot for the fast reply.
>
> The problem with storing something in the session is it that if the user
> tried to access two different
First of all thanks a lot for the fast reply.
The problem with storing something in the session is it that if the user
tried to access two different pages at once in separate windows and had
to login in both, he will be forwarded in both to the last page he tried
to access. I think this is a quite
Anton,
Acegi Security does something similar. The original requests (yes -- the
actual request object) is stored in the session when the user's credentials
are challenged. If they then succeed at the login page, the original request
is taken from the session and forwarded along.
Paul
On 9/30/07,
I spent quite a few hours today trying to forward the user to his
original destination when he has to login in between.
I have an interceptor (Authentication) that is called before an action
and it forwards to Login.action if the user is not logged in. The
problem is that if Login.action returns S
4 matches
Mail list logo
