You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Frauenberger Christopher <f_...@gmx.net> on 2000/02/10 15:35:05 UTC
mod_jserv/5737: cant get sessions - each getSession() creates a new one
>Number: 5737
>Category: mod_jserv
>Synopsis: cant get sessions - each getSession() creates a new one
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: jserv
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Thu Feb 10 06:40:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator: f_chris@gmx.net
>Release: 1.3.11
>Organization:
apache
>Environment:
IRIX 6.5
Netscape 4.61
JServ 1.1
TomCat 3.1 Milestone M1
JSDK2.0
JDK 1.2.1 (SGI)
>Description:
This code :
HttpSession session = req.getSession(false);
if (session == null)
session = req.getSession(true);
produces new SessionIDs every time
The funny thing is that I also tried encodeUrl(..) with
"Dont accept cookies" in Netscape, but it doesnt encode the SessionId in the URL.
If I contact tomcat directly (via 8080 port) it works with cookies but not with
encodeUrl(..)
We have compiled mod_jserv.so and placed it in the libexec/ (Apache 1.3.11 with DSO)
and everything else works fine.
>How-To-Repeat:
see code and enviroment
>Fix:
I've heard that under linux this problem disapears with the precompiled mod_jserv
but i havent found one for SGI/IRIX 6.5.5
>Release-Note:
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or ]
["Re: general/1098:"). If the subject doesn't match this ]
[pattern, your message will be misfiled and ignored. The ]
["apbugs" address is not added to the Cc line of messages from ]
[the database automatically because of the potential for mail ]
[loops. If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request from a ]
[developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]