I had a quick question about this. For a session to be
refreshed by being
accessed, does this count only direct calls to the specific
URI's, or if I
do a forward from another servlet context into it, will this count as
access as well.
I'd have *expected* any access to the session
At 09:40 AM 01/29/2002 +, you wrote:
Is there a way to configure
Tomcat to check the expire time against last access time and not
creation time?
Sessions *are* invalidated when the timeout period has passed without
access. *Not* when the timeout period has passed from creation.
I had
On Wed, 30 Jan 2002, Mario Felarca wrote:
Date: Wed, 30 Jan 2002 12:03:56 -0600
From: Mario Felarca [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: Sessions Timeout
At 09:40 AM 01/29/2002 +, you wrote
Hi Jason,
the session method getMaxInactiveInterval() gives you the time-value, after
that your inactive session is killed. You can change this value in the
web.xml file.
Anja
--
To unsubscribe: mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the
Is there a way to configure
Tomcat to check the expire time against last access time and not
creation time?
Sessions *are* invalidated when the timeout period has passed without
access. *Not* when the timeout period has passed from creation.
Justin.
--
You're only jealous cos the little
the session method getMaxInactiveInterval() gives you the
time-value, after
that your inactive session is killed. You can change this value in the
web.xml file.
Or in the jsp - request.getSession.setMaxInactiveInterval(time in
seconds).
J.
--
You're only jealous cos the little penguins
