Re: Question about the "EncodeUrlState" - option

Thorsten,

I believe there was some discussion earlier in this list on this topic.  I
don't exactly know where it is.  However as I recall the standard way that
Enhydra tries to link with the Servlet container's jsessionid (using
pathinfo) creates some problems.

Myself, I modified the Enhydra code so it would handle the creation of the
session id directly and leave me free to use pathinfo as I wanted.

HTH,

Terry

----- Original Message -----
From: "Thorsten Hilker" <t_hilker@xxxxxxxxx>
To: "Enhydra" <enhydra@xxxxxxxxxxx>
Sent: Tuesday, March 25, 2003 7:42 AM
Subject: Enhydra: Question about the "EncodeUrlState" - option


> Hi!
>
> When I switch the "EncodeUrlState" - option in
> the application configuration file to "auto",
> I get the following behaviour:
> (Cookies are activated in the browser)
>
> 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'm using Enhydra 3.1b2 and IE6 here.
>
> TIA
>
> Thorsten
>
> _______________________________________________
> Enhydra mailing list
> Enhydra@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra
>