When BaseServlet senses that there is not a valid
session, it tries to do a res.sendRedirect and then
throws a ServletException. In my version of Tomcat
(4.1.27), the user does not get redirected.... the user
only gets the Tomcat error thrown on the screen.
It seems like writing the error to the logs, rather
than throwing it, makes more sense:
diff -r1.3 BaseServlet.java
92c92,93
< throw new ServletException("No
Authentication: redirected to " +loginUrl+currentRequest);
---
> // throw new ServletException("No
Authentication: redirected to " +loginUrl+currentRequest);
> errorLogger.warn("No Authentication:
redirected to " +loginUrl+currentRequest);
Or is this related more my Tomcat config?
Logged In: YES
user_id=550545
Lets write it too the logs, but I would like this investigated to
see if we can reproduce, becuase if it is a problem, then
everyone will eventially experience it.
Ian
Logged In: YES
user_id=562689
This can be investigated by logging into CourseWork,
deleting the session cookie, and then trying to access a
part of CourseWork (like "My Profile").