dear colleagues,
i have noted that, when using form based security (tomcat 3.2.1), a kind of expiration
is on: if i connect to a secured page (actually a servlet) and stay inactive for a
while (not sure about the lapse) when i reload the page or try to connect to another
resource, i have to re
i have noted that, when using form based security (tomcat
3.2.1), a kind of expiration is on: if i connect to a secured
page (actually a servlet) and stay inactive for a while (not
sure about the lapse) when i reload the page or try to
connect to another resource, i have to re insert
At 09:05 3/28/01 -0500, you wrote:
i have noted that, when using form based security (tomcat
3.2.1), a kind of expiration is on: if i connect to a secured
page (actually a servlet) and stay inactive for a while (not
sure about the lapse) when i reload the page or try to
connect to
Hi,
One possibility: you can set a sesson timout value in the web.xml for your
application
!-- session timeout --
session-config
session-timeout30/session-timeout!-- 30 minutes --
/session-config
Don't know what default is if you don't
andrew
On Wed, 28 Mar 2001,
thanks for your reply, but i am not using sessions any way.
either this does not happen when i use simple basic authentication.
it seems that session management is turned on some way, when
i use form based sec.
any hint?
Not sure I understand what you mean by not using sessions? You mean
At 09:35 3/28/01 -0500, you wrote:
thanks for your reply, but i am not using sessions any way.
either this does not happen when i use simple basic authentication.
it seems that session management is turned on some way, when
i use form based sec.
any hint?
Not sure I understand what you
