Re: jsesionid written into url when using tomcat behind apache & mod_j

[Igor Vaynberg <ig...@gmail.com>]

this has been asked a ton of times already...so do search the lists
next time. just to reiterate, servlet container always does this on
first request because it doesnt know if the cookies are enabled or not
until the second request. if cookies are enabled jsessionid will go
away on second request.

-igor


On Wed, Jun 4, 2008 at 9:45 AM, Joel Halbert <jo...@hotmail.com> wrote:
> Hi,
>
> This is probably not a wicket related query as such (so apologies) but just in case here goes....
>
> I have placed our tomcat server behind apache and we are using mod_jk.
> When I do this we see the jsessionid being written out in the url for the very first request response to the user (so we see something like www.dummydomain.com/list;jsessionid=899F7C88CDA2E8A0508651AA89484C6C)
>
> However, I have checked that cookies are being written correctly, and they are. Is this something anyone else has seen. Are there any other reasons that the cookie might be url encoded on the first request?
>
> Joel
>
> (I also found this post : http://www.nabble.com/Re%3A-how-to-resolve-jsessionid-for-the-first-time-in-the-url-ts16347213.html  but there was no resolution)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org