-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Makaira,
On 2/17/2009 5:38 PM, makaira nigricans wrote:
> So after my all my dilemmas
> JSESSIONID is simple cookie!
Yes, containing only the id of the HttpSession living on the server. You
can look at this cookie's contents by watching the HTTP traf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jorge,
On 2/17/2009 3:57 PM, Jorge Medina wrote:
> My confusion came from the fact that through the HttpSession object,
> you can access the cookies with methods that names then Attributes
> (getAttribute/setAttribute). It was unclear -to me- that it
> From: makaira nigricans [mailto:liame.e...@yahoo.com]
> Subject: RE: Tomcat in-memory (session) cookie
>
> And is there in-memory cookie which generates on every get
> and post request?
First, let's do the terminology: there's no such thing as an "in-memory
cook
ssion" in it's name and through my
cookie-printing servlet I saw that JSESSIONID is cookie? And is there
in-memory cookie which generates on every get and post request?
I thought that this "Tomcat in-memory (session) cookie" which I am looking
for is JSESSIONID. I could print it
ssion" in it's name and through my
cookie-printing servlet I saw that JSESSIONID is cookie? And is there
in-memory cookie which generates on every get and post request?
I thought that this "Tomcat in-memory (session) cookie" which I am looking
for is JSESSIONID. I could
t memory.
-Jorge
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Tuesday, February 17, 2009 11:59 AM
To: Tomcat Users List
Subject: RE: Tomcat in-memory (session) cookie
> From: makaira nigricans [mailto:liame.e...@yahoo.com]
> Subject: Tomcat
> From: makaira nigricans [mailto:liame.e...@yahoo.com]
> Subject: Tomcat in-memory (session) cookie
>
> As I understood (maybe I understood wrongly)
You did.
> with every GET and POST request Tomcat "generates" cookie
> which it do not write on hard drive (so it
Hello...
As I understood (maybe I understood wrongly) with every GET and POST request
Tomcat "generates" cookie which it do not write on hard drive (so it cannot
be seen in browser cookie manager). It is some kind of in-memory (session)
cookie which is "active" only while browser's page is opened
