We are getting a consistent 404 error during our first login.
it seems to be appending the jsessionid= param and wicket doesn't seem
to like it.
This usually happens on the first login of the day:
the app redirects to the login page with the session id appended:
Goto : http://localhost:8080/
Redirected to : http://localhost:8080/login;jsessionid=1b5axe9wb1o8k
Receive a 404 error:
HTTP ERROR: 404
NOT_FOUND
RequestURI=/login;jsessionid=1b5axe9wb1o8k
Powered by Jetty://
This is happening in your dev Jetty instance and on you production
Tomcat 6 instance.
It looks to me as if the login system (auth-roles) is getting the
session id from something other than the real session, and attempting
to use it, but it may also be WIcket not parsing the URI properly.
We're using Wicket 1.4 SNAPSHOT deps.
Does anyone have any idea how to resolve this?
- Brill Pappin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
