-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
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?
mitch
Mitch Claborn wrote:
The answer is: yes, there are times
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
On 14/08/2009 19:32, 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?
Doesn't
anyone know if there is a use-case for sessionId surviving end-of-session?
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
My usage is: I store the key to the user's shopping cart in the
session. I'd like the user to be able to come back a few days from now
and still find the items they have placed in their shopping cart. (This
is mostly for anonymous users who don't sign in until checkout.)
Mitch
Martin Gainty
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
Your best bet is to assign your own cookie. Then on new session
creation, look for the cookie and repopulate the new session with
shopping cart data.
--David
Mitch Claborn wrote:
My usage is: I store the key to the user's shopping cart in the
session. I'd like the user to be able to come
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
If I can't find a another way that's what I'll have to do. I would be
surprised that this need doesn't come up more frequently.
Mitch
David Smith wrote:
Your best bet is to assign your own cookie. Then on new session
creation, look for the cookie and repopulate the new session with
shopping
It comes up all the time. The solution is typically to use a separate
cookie and *not* tie the persistent data to the browser session, since
the browser session is transient.
--
Len
On Wed, Aug 12, 2009 at 14:54, Mitch Claborn mi...@claborn.net wrote:
If I can't find a another way that's what
I was able to get the cookie permanent with a simple valve, code below.
Question: the new cookie will be ignored if the response has already
been committed (isCommitted()). In my brief testing, the new cookie
is being set, so the response must not be committed. Is it possible
that there might
The answer is: yes, there are times when the response is already
committed, so the valve is not a foolproof solution.
mitch
Mitch Claborn wrote:
I was able to get the cookie permanent with a simple valve, code below.
Question: the new cookie will be ignored if the response has already
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
16 matches
Mail list logo
