After reverting to jdk 1.2.2, I still get the same problem: the
session.encodeURL function at some point ends up losing the session ID in
JRUN3.0.
So, does anybody have another idea what the solution could be?
Thank you for you help,
Pascal BLANC.
In a message dated 11/27/00 10:01:08 AM Eastern Standard Time,
[EMAIL PROTECTED] writes:
--part1_f9.4f8aa12.2753d0ee_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Adam,
Thank you very much for your help.
I indeed upgraded to jdk1.3 last week before I put the authentication into
place.
I reverted to 1.2 this morning and so far it seems to be working.
Thank you once again,
Pascal BLANC.
In a message dated 11/27/00 6:39:11 AM Eastern Standard Time,
[EMAIL PROTECTED] writes:
> What JVM are you running? I have heard of other people having problems
> similar to this when they were running JRE1.3 from Sun. In order to fix
> the problem they went back to JRE1.2.2.
>
> Adam
>
>
>
>
> AtaturkTheGre
>
> [EMAIL PROTECTED] To: JRun-Talk <
> [EMAIL PROTECTED]>
> cc:
>
> 11/26/00 Subject: response.encodeURL
>
> 07:47 PM
>
> Please
>
> respond to
>
> jrun-talk
>
>
>
>
>
>
>
>
>
>
> --part1_75.ca90590.27531739_boundary
> Content-Type: text/plain; charset="US-ASCII"
> Content-Transfer-Encoding: 7bit
>
> Hi all !
>
> I have a problem with response.encodeURL. All my pages uses it but, after
a
> little while, generally 1 or 2 mns, the same pages that were working now
do
> not retain the jsessionid and of course I get kicked out of my site
because
> the user authentication test fails.
>
> Did anybody have the same problem and if yes, what did you do to fix it?
>
> I'm using JRun 3.0 on NT6a.
>
> You help will be greatly appreciated.
>
> Pascal BLANC.
