Re: Question about the "EncodeUrlState" - option

I seem to recall that IE6 has some peculiar behavior with regards to
cookies.  I believe the discussion (unrelated to Enhydra) had something to
do with switching between http and https.  The author of the sample code had
to write some specific code to handle the IE6 behavior.  If it's important,
I can try to find it.

Regards,

Terry

----- Original Message -----
From: "Petr Stehlik" <pstehlik@xxxxxxxxxx>
To: <enhydra@xxxxxxxxxxx>
Sent: Tuesday, March 25, 2003 2:48 PM
Subject: Re: Enhydra: Question about the "EncodeUrlState" - option


> On Út, 2003-03-25 at 13:42, Thorsten Hilker wrote:
> > The first page I call with the browser is
> > generated with the "jsessionid" extension for
> > each link existing on the page.
> >
> > The second and any further page I call with the browser has
> > no "jsessionids" anymore.
> >
> > Is this normal? Shouldn't Enhydra realize
> > at the first page, that cookies can be used?
>
> I think it's logical and so normal. Enhydra does not know if cookie
> based session works or not until your IE6 returns to the Enhydra server
> for _second_ page. So the first page must come with the jsessionid and
> when the client browsers fetches second or subsequent pages with valid
> cookie then Enhydra stops generating the jsessionid.
>
> Petr
>
>
>
> _______________________________________________
> Enhydra mailing list
> Enhydra@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra