hey jacob,
i tried it on 5.0.16.
there is always a chance this was fixed since that version.
i didn't find anything about it in the bugzilla. that's why i posted
just to ask if someone already met this problem .
i posted another bug earlier (see my utf-8 problem posts) and got an
answer that this is not a bug, but the attached solution didn't solve my
problem.
when i reposted, the answer was that i should write to this board.
and please, leave the DUTIES stuff for other discussions.
asher.
----- Original Message -----
From: "Jacob Kjome" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Monday, July 05, 2004 8:53 PM
Subject: Re: session invalidation
> At 10:15 AM 7/5/2004 +0200, you wrote:
> >Hello Ashert,
> >
> >may be you ran into the same prob as me....
> >
> >i also had the problem, that URL-rewriting under Tomcat 5 did not work
> >although i explicitly used it. I found out, that URL-rewriting does only
> >work, if your application runs in the root context, looking like that in
> >server.xml:
> >
> ><Context path="" docBase="myWebapp" cookies="false" />
> >
> >I was running my app under a named context:
> >
> ><Context path="myWebapp" docBase="myWebapp" cookies="false" />
> >
> >After changing the context definition to the first sample, URL-rewriting
> >worked fine....
> >
> >hope this helps & best regards,
>
> Well, this helps very little. If you want to help, then provide the
> version of Tomcat5 you are working with. For all we know it is an old
> version with a quirky bug that has already been fixed in more recent
> versions. And if that is true, you are just adding to the confusion
saying
> it is broken when it isn't anymore. If it is still broken, however, it is
> your duty to report the bug so it can be fixed. Have you done that or
even
> checked if someone else reported it? The Tomcat developers are pretty
> responsive to fixing bugs. If you have the ability to describe and
> reproduce this bug and you neglect to do so, then you are doing a
> disservice to the Tomcat community. Some might disagree with the whole
"it
> is your duty" part. It is an unwritten rule that, if followed, will
> provide benefit to yourself and everyone else.
>
> Jake
>
>
> >Thilo
> >
> >>hello,
> >>
> >>1. a webapp has a filter, which filters all of the requests to
> >>application's servlets.
> >>2. the filter makes a simple check:
> >>if (session == null || session.getAttribute("abc") == null)
> >>//redirect the request to the login page;
> >>else
> >>//continue with it as it is
> >>3. if i invalidate the session, and then try to use back button of the
> >>browser the filter kicks me to the login page.
> >>on tomcat4 this works fine. at least i didn't see any problem ever.
> >>4. on tomcat 5 this logic works fine only with browser whith enabled
> >>cookies. using the session tracking with url rewriting doesn't
work.works
> >>the debugging shows that the flow runs into the code block that must
> >>invalidate the session, but it's not invalidated. i still can get
> >>back,see the pages and use the data stored in session!:(
> >>did u have any expirience with this stuff?
> >>thanks in advance.
> >>
> >>
> >>---------------------------------------------------------------------
> >>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]
>
>
> ---------------------------------------------------------------------
> 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]
