I admit not not looking at this in detail. But the lack or a 'return;'
statement after the jsp:forward is a major red flag.
Sundar Narasimhan [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Hi, I'm running out of options -- but is there a problem with
Hi, I'm running out of options -- but is there a problem with
getSession(false)?
Sigh. We used to have a piece of code included in our jsp's like so:
header-inc
% if (request.getSession(false) == null) { %
jsp:forward page=logout.jsp?TIMEOUT=60 /jsp:forward
% } %
jsp:useBean id=user
What used to worked? What behavior are you expecting that you no longer
observe?
If I was to guess at what you're expecting to happen... I would guess that
you are expecting that getSession(false) would equal null at some point and
that never happens? This causes the useBean directive to
On Tue, 4 Feb 2003, Sundar Narasimhan wrote:
Date: Tue, 4 Feb 2003 23:35:38 -0500
From: Sundar Narasimhan [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: session timeout not working anymore :(
Hi, I'm running out of options
