problem with caching?

[lordi <lo...@gmx.de>]

hi,
i have written a servlet, which is supposed to logout a user by invalidating
his servlet session. it works fine, when i invoke the servlet the first time,
but if i invoke it again, the session is not invalidated anymore.
i think it has something to do with the caching system of either the servlet
engine or velocity. can anybody please tell me, how i can prevent this
behaviour?

best regards,
Lordi




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: problem with caching?

[lordi <lo...@gmx.de>]

I have found out, that it is somehow a browser dependent problem. it works fine
with IE, but Opera (my standard browser) seems to cache the page, so that
the session will not be invalidated when i login and logout a 2nd time.

>
>> hi,
>> i have written a servlet, which is supposed to logout a user by invalidating
>> his servlet session. it works fine, when i invoke the servlet the first time,
>> but if i invoke it again, the session is not invalidated anymore.
>> i think it has something to do with the caching system of either the servlet
>> engine or velocity. can anybody please tell me, how i can prevent this
>> behaviour?
>
>Well, I think we'll need a little more detail, but Velocity's caching is
>limited only to templates - that means that with the right settings,
>Velocity will load the templates you ask for and keep them loaded in a
>parsed state, for faster access if you ask for it again.
>
>It's very unlikely, given what you describe, that Velocity has anything to
>do with it.
>
>
>How do you invalidate the servlet session?




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: problem with caching?

["Geir Magnusson Jr." <ge...@adeptra.com>]

On 7/3/02 3:17 AM, "lordi" <lo...@gmx.de> wrote:

> hi,
> i have written a servlet, which is supposed to logout a user by invalidating
> his servlet session. it works fine, when i invoke the servlet the first time,
> but if i invoke it again, the session is not invalidated anymore.
> i think it has something to do with the caching system of either the servlet
> engine or velocity. can anybody please tell me, how i can prevent this
> behaviour?

Well, I think we'll need a little more detail, but Velocity's caching is
limited only to templates - that means that with the right settings,
Velocity will load the templates you ask for and keep them loaded in a
parsed state, for faster access if you ask for it again.

It's very unlikely, given what you describe, that Velocity has anything to
do with it.


How do you invalidate the servlet session?

-- 
Geir Magnusson Jr. 
Research & Development, Adeptra Inc.
geirm@adeptra.com
+1-203-247-1713



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>