-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mitch,
On 8/12/2009 7:08 PM, Mitch Claborn wrote:
The answer is: yes, there are times when the response is already
committed, so the valve is not a foolproof solution.
If the Valve wraps the request with an object that intercepts the
addCookie
I played a bit with that approach, but couldn't figure out how to get my
valve early enough in the chain.
Mitch
Christopher Schultz wrote:
Mitch,
On 8/12/2009 7:08 PM, Mitch Claborn wrote:
The answer is: yes, there are times when the response is already
committed, so the valve is not a
To: users@tomcat.apache.org
Subject: JSESSIONID cookie permanent?
Is there a way to make the JSESSIONID cookie issued by Tomcat
permanent,
or at least significantly longer life than end of session ?
Mitch
Mitch Claborn wrote:
I was able to change the expiration on the cookie with a one line change
to org.apache.catalina.connector.Request and it works like I need it to.
What is the official way to request an enhancement to allow this to be
configurable?
The correct way is to open a bugzilla
@tomcat.apache.org
Subject: JSESSIONID cookie permanent?
Is there a way to make the JSESSIONID cookie issued by Tomcat permanent,
or at least significantly longer life than end of session ?
Mitch
-
To unsubscribe, e-mail: users-unsubscr
Is there a way to make the JSESSIONID cookie issued by Tomcat permanent,
or at least significantly longer life than end of session ?
Mitch
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands,
...@claborn.net
To: users@tomcat.apache.org
Subject: JSESSIONID cookie permanent?
Is there a way to make the JSESSIONID cookie issued by Tomcat permanent,
or at least significantly longer life than end of session ?
Mitch
-0500
From: mi...@claborn.net
To: users@tomcat.apache.org
Subject: JSESSIONID cookie permanent?
Is there a way to make the JSESSIONID cookie issued by Tomcat permanent,
or at least significantly longer life than end of session ?
Mitch
On Wed, Aug 12, 2009 at 11:35 AM, Mitch Clabornmi...@claborn.net wrote:
My usage is: I store the key to the user's shopping cart in the
session.
If I understand you correctly, then you would need to serialize the
session when it ended, to be able to resurrect it and retrieve that
key, or have
. Étant donné que les email
peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
aucune responsabilité pour le contenu fourni.
Date: Wed, 12 Aug 2009 12:43:11 -0500
From: mi...@claborn.net
To: users@tomcat.apache.org
Subject: JSESSIONID cookie permanent
I don't have any problem with the session contents (on the tomcat
server). I'm in a tomcat cluster and the sessions are replicated
between members of the cluster. As long as at least one member of the
cluster is running, then the sessions survive. I don't mind if the
sessions on the server
pour le contenu fourni.
Date: Wed, 12 Aug 2009 12:43:11 -0500
From: mi...@claborn.net
To: users@tomcat.apache.org
Subject: JSESSIONID cookie permanent?
Is there a way to make the JSESSIONID cookie issued by Tomcat permanent,
or at least significantly longer life than end
fourni.
Date: Wed, 12 Aug 2009 12:43:11 -0500
From: mi...@claborn.net
To: users@tomcat.apache.org
Subject: JSESSIONID cookie permanent?
Is there a way to make the JSESSIONID cookie issued by Tomcat permanent,
or at least significantly longer life than end of session
:43:11 -0500
From: mi...@claborn.net
To: users@tomcat.apache.org
Subject: JSESSIONID cookie permanent?
Is there a way to make the JSESSIONID cookie issued by Tomcat permanent,
or at least significantly longer life than end of session ?
Mitch
Subject: JSESSIONID cookie permanent?
Is there a way to make the JSESSIONID cookie issued by Tomcat permanent,
or at least significantly longer life than end of session ?
Mitch
-
To unsubscribe, e-mail: users-unsubscr
Haftung
fuer den Inhalt uebernehmen.
Date: Wed, 12 Aug 2009 18:08:43 -0500
From: mi...@claborn.net
To: users@tomcat.apache.org
Subject: Re: JSESSIONID cookie permanent?
The answer is: yes, there are times when the response is already
committed, so the valve is not a foolproof solution
The session data is stored on the server, so if the JSESSIONID lasted
longer
than the session on the server, it would simply map to an expired
session.
What would happen in this case is the server would have no session
mapping
to that ID and simply allocate a new session, with a new
17 matches
Mail list logo
