Since you're rewriting your CGI scripts as servlets, why not modify
them
to not expect the session-num parameter, and instead get the session ID
via normal java code (request.getSession().getId())? It's simpler,
standard, less code for you to write and test...
My problem is the client, which is
of some sort, and then from that point, the
legacy app appends it to any further queries?
-Original Message-
From: Sandy McArthur [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 07, 2004 10:21 AM
To: Tomcat Users List
Subject: Re: Custom session tracking method?
Since you're
: Sandy McArthur [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 07, 2004 10:21 AM
To: Tomcat Users List
Subject: Re: Custom session tracking method?
Since you're rewriting your CGI scripts as servlets, why not modify
them
to not expect the session-num parameter, and instead get
the session ID
via
-
From: Sandy McArthur [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 07, 2004 10:45 AM
To: Tomcat Users List
Subject: Re: Custom session tracking method?
The first request the legacy app makes is to /login which it
uses your
normal Basic authentication which is nice because I can
