jsessionid 1.4-m1 vs 1.4-rc1

[Ryan McKinley]

Have there been any changes to how jsessionid might be handled in  
rc1?  I never seen this error before, but when I upgraded to rc1 I get  
it most of the time when starting a new session.

I'm using the HybridUrlCodingStrategy when I hit something that should  
be mapped, I get directed to:

http://localhost:8888/;jsessionid=a7m8jcgo54ae?wicket:interface=:1::::

and get a 404

any thoughts?

thanks
ryan