Hmm I've seen the same a couple of times after restarting the server.
However it seems to "disapear" after the server is "warmed"...
It can also be a problem if you run apache http server in front and you
do not forward cookies etc... I wrote an example on this earlier in
some thread around here, theres also something on the wiki...
James Carman wrote:
Well, I know I've seen JSESSIONIDs appended to my wicket URLs and I do
have cookies enabled. So, apparently Jetty isn't doing that in my
case?
On Fri, Apr 25, 2008 at 10:12 AM, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
The server typically redirects to set the jsessionid iirc from the
previous discussion.
Martijn
On 4/25/08, James Carman <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 25, 2008 at 10:02 AM, Martijn Dashorst
> <[EMAIL PROTECTED]> wrote:
> > Yes, enable cookies in your browser.
>
>
> The JSESSIONID will still appear at least one time even if cookies are
> enabled, correct? Once a link/submit happens and the server sees that
> cookie come in, it knows not to append JSESSIONID anymore for that
> session.
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
