It's not an error.

p

On 22 Oct 2010, at 13:51, Martin Gainty <[email protected]> wrote:

>
> can you verify this error is corrected with TC 7.0.5?
>
> thanks,
> Martin
> ______________________________________________
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
> sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
> oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich 
> dem Austausch von Informationen und entfaltet keine rechtliche 
> Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen 
> wir keine Haftung fuer den Inhalt uebernehmen.
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
> destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
> l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci 
> est interdite. Ce message sert à l'information seulement et n'aura pas 
> n'importe quel effet légalement obligatoire. Étant donné que les email 
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter 
> aucune responsabilité pour le contenu fourni.
>
>
>
>
>> Date: Fri, 22 Oct 2010 05:16:07 -0700
>> Subject: Re: Login page timeout
>> From: [email protected]
>> To: [email protected]
>>
>> Top result doing google search
>> http://www.mindspill.org/kiwiThread$msgnum=207
>>
>> See Mark's response bottom of page:
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=3839#c14
>>
>>
>>
>>
>> On Fri, Oct 22, 2010 at 3:15 AM, Gabriele Bulfon <[email protected]>wrote:
>>
>>> Hello, I'm trying to figure out how to solve a very stupid problem.
>>> I have a solution, but I want to know if there is some other better ways.
>>>
>>> I have a webapp configured with jaas security.
>>> The login form page is configured and the security check works perfectly.
>>> But, if a user starts the browser and goes to the login page, then leaves
>>> the browser there
>>> for some reason, when he/she gets back later and try to login, it's like
>>> the login form has expired,
>>> and TomCat fails with the "Invalid direct reference to form login page".
>>> The only way I've seen so far to avoid this, is to have a javascript
>>> function to reload the login form
>>> every n seconds if the user does not enter.
>>> It's as if TomCat creates a session for the login form, and this session
>>> expires.
>>>
>>> How can I avoid this?
>>> Gabriele.
>>>
>>> -= Mail sent through WebTop2 =-
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to