Home/ Questions/Q 8409543
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T23:56:24+00:00

Since moving to a new server, we’re getting a 404 error when logging in

  • 0

Since moving to a new server, we’re getting a 404 error when logging in to our web application. We’re using Spring Acegi for authentication, and the HTTP stream is rather typical:

Request:
GET /dev/secure/umblogin?j_username=myuer&j_password=XXXX&j_client=1

Response:
HTTP/1.1 302 Moved Temporarily
Set-Cookie: JSESSIONID=3DABF165D2E18094632EA1478EF67D8E; Path=/dev
Location: http://hurricane.umbrellanet.ch/dev/secure/umbrellanet.go;jsessionid=3DABF165D2E18094632EA1478EF67D8E

Request:
GET /dev/login.go;jsessionid=DA122287727B72CD3F1B77DBD799531F

Response:
HTTP/1.1 404 Not Found

The reason lies somewhere with the path parameter ‘;jsessionid=..’ where the semicolon gets encoded to %3b and the server then fails to find

/dev/login.go%3bjsessionid=DA122287727B72CD3F1B77DBD799531F

I’ sure this is not an uncommon problem, but I fail to find any good google hits. We’re using Apache Tomcat/6.0.35, the browser is an IE 9.

Thanks
Simon

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is essentially a duplicate of Is it possible to disable jsessionid in tomcat servlet?.

    (Since Tomcat 6.0.33, the path parameters are returned on Request.getRequestURI(). This is seen as a bug fix.)

    • 0