rkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> >
> >
> >
> >> Date: Fri, 4 Jun 2010 00:34:36 +0300
> >> Subject: Re: HTTP Status 400 - Invalid direct reference to form login
> pag
nen und entfaltet keine rechtliche
> Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen
> wir keine Haftung fuer den Inhalt uebernehmen.
>
>
>
>> Date: Fri, 4 Jun 2010 00:34:36 +0300
>> Subject: Re: HTTP Status 400 - Invalid direct refere
ng 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.
&g
> > Date: Fri, 4 Jun 2010 00:34:36 +0300
> > Subject: Re: HTTP Status 400 - Invalid direct reference to form login
> page!
> > From: george.pu...@gmail.com
> > To: users@tomcat.apache.org
> >
> > Hello Cris,
> >
> > *After you call session.inval
:34:36 +0300
> Subject: Re: HTTP Status 400 - Invalid direct reference to form login page!
> From: george.pu...@gmail.com
> To: users@tomcat.apache.org
>
> Hello Cris,
>
> *After you call session.invalidation(), what does your code do,
> specifically? If you do a "
Hello Cris,
*After you call session.invalidation(), what does your code do,
specifically? If you do a "forward" to a protected resource, strange
things may happen with cookie-passing.*
After the session get's invalidate(on the server side) my code send back a
request success to the UI and then th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gheorghe,
On 6/3/2010 2:18 PM, Gheorghe Pucea wrote:
> By "when I get back to the login page" I mean that I log out from my app and
> then I redirect my app to a restricted resource and when my login page
> appears I type my User/pass and the error oc
g mechanism keeping the session alive
> somehow?
>
>
> -Original Message-
> From: Gheorghe Pucea [mailto:george.pu...@gmail.com]
> Sent: Thursday, June 03, 2010 2:37 PM
> To: Tomcat Users List
> Subject: Re: HTTP Status 400 - Invalid direct reference to form login page!
&g
dated properly?
>
> -Original Message-
> From: Gheorghe Pucea [mailto:george.pu...@gmail.com]
> Sent: Thursday, June 03, 2010 1:13 PM
> To: Tomcat Users List
> Subject: Re: HTTP Status 400 - Invalid direct reference to form login page!
>
> Hello Barry,
>
>
>
>
operly?
>
> -Original Message-
> From: Gheorghe Pucea [mailto:george.pu...@gmail.com]
> Sent: Thursday, June 03, 2010 1:13 PM
> To: Tomcat Users List
> Subject: Re: HTTP Status 400 - Invalid direct reference to form login page!
>
> Hello Barry,
>
>
>
> Exac
Sounds like the session's not getting invalidated properly?
-Original Message-
From: Gheorghe Pucea [mailto:george.pu...@gmail.com]
Sent: Thursday, June 03, 2010 1:13 PM
To: Tomcat Users List
Subject: Re: HTTP Status 400 - Invalid direct reference to form login page!
Hello
Sorry Pid I didn't noticed your message.
By "when I get back to the login page" I mean that I log out from my app and
then I redirect my app to a restricted resource and when my login page
appears I type my User/pass and the error occurs.
I want to add something, when I log out and after I red
List
> Subject: Re: HTTP Status 400 - Invalid direct reference to form login page!
>
> On 03/06/2010 15:29, Gheorghe Pucea wrote:
> > Hello,
> >
> > I have a problem with my Tomcat instance, I'm using:
> >
> > Tomcat 6.0.26
> > Java jdk 1.5.
Yeah, I'd say he shouldn't be going "back to the login page" but rather to the
protected page.
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Thursday, June 03, 2010 12:11 PM
To: Tomcat Users List
Subject: Re: HTTP Status 400 - Invalid direct referenc
ed. If not, I'm not sure what to
tell you. Maybe some others on this forum would know better than I.
-Original Message-
From: Gheorghe Pucea [mailto:george.pu...@gmail.com]
Sent: Thursday, June 03, 2010 11:47 AM
To: Tomcat Users List
Subject: Re: HTTP Status 400 - Invalid direct re
On 03/06/2010 15:29, Gheorghe Pucea wrote:
> Hello,
>
> I have a problem with my Tomcat instance, I'm using:
>
> Tomcat 6.0.26
> Java jdk 1.5.0_17
> Windows XP SP3
>
>I have implemented a JAAS login module for my application and everything
> goes fine except from one thing.
>
> Here are th
Hello Barry,
Thank you very much for your quick respone, but I think that version of
Tomcat was very old compared to Tomcat 6.0.26 I think the problem should be
fix by now.
So you suggest that I manually should clear my browser's cache?And this
should fix my problem?
On Thu,
I had that happen periodically for years with my version of TC 4.1.31.
With some folks, we could get it to go away, by cleaning out browser cache.
With others, it was the same people that incurred it all the time. They could
access "other" protected areas, but not the one.
I ended up making a du
18 matches
Mail list logo
