check ie.. it stores all cookies in a folder called cookies somewhere each
cookie in a seperate file.. however theres an index.dat .. no idea what this
does but you could delete it ( backup!! ) and all the cookies.. ( ??sorry??
but i've had this "general cookie issue" with netscrap and ie. )
chuck this in your code.. to test tomcat.
System.out.println ( this.getClass().getName() ) ;
System.out.println ("Path:" + request.getContextPath() + "
: info " + request.getPathInfo() );
for ( Enumeration headers= request.getHeaderNames();
headers.hasMoreElements() ; ) {
Object header = headers.nextElement();
if ( header !=null ) {
System.out.println ( "header :" + header.toString()
) ;
for ( Enumeration values = request.getHeaders(
header.toString() ); headers.hasMoreElements() ; ) {
if ( values .hasMoreElements() ) {
Object value = values.nextElement();
if ( value !=null )
System.out.println ( "-" + value.toString()
) ;
}else
break;
}
}else
break;
}
-----Original Message-----
From: Milt Epstein [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 4 April 2001 6:07 AM
To: [EMAIL PROTECTED]
Subject: Session problem -- sessions being recreated, browser related?
On a servlet-based application I have, I'm getting sporadic reports of
problems from users. The symptoms are similar to what happens when
cookies are disabled (but they aren't, because I had the users check).
Basically, they can't get past the front page of the application,
because it won't let them without a valid session (recall that session
access is handled via cookies -- I'm not using URL Rewriting). And
each time they try, Tomcat is creating a new session for them (and
giving them a new cookie). Apparently, it's not recognizing the
existing session.
Now, this is only happening to a small subset of the users. I haven't
isolated a pattern yet, but it may only be happening from certain
machines. And the couple of machines I have found the problem on so
far are both using Internet Explorer version 4.0. So that might be a
factor. (I don't have 4.0 myself, but I did find an old copy of 3.02,
and it works OK with that.)
Oh, a bit of background -- we switched over from using Netscape
Enterprise Server and ServletExec to Apache/Tomcat a couple of weeks
ago, and the problem seems to have only started occurring since then.
So it does appear to be something Apache/Tomcat-specific.
Thanks.
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
