-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
None
-
None
-
None
This page:
http://extranet.atlassian.com/display/~mike/Coho+Purchase+Statistics
Was moved to this page:
http://extranet.atlassian.com/display/CHE/Coho+Purchase+Statistics
However, if you go to the first page, you get a 404, and not the 'page moved' screen that you should get.
- was cloned as
-
CONFSERVER-9027 Document that redirect feature for not-found pages might not work in older appservers
- Closed
Ah. Found it. It's the Servlet spec.
In the code for the redirect page, we send back a '404' response code to indicate the original page wasn't found (a must-have so we don't confuse bots) using setStatus().
In Servlet 2.4, sendError() redirects you to the container-defined <error-page> for that status code, while setStatus() still assumes you're going to handle the response yourself. In Servlet 2.3, sendError() and setStatus() are treated the same. Given that most of our supported appservers are on 2.4 now, I'm going to mark this as "won't fix", and file separate issues to (a) document that the auto-redirect stuff may not work on certain appservers, and (b) upgrade Extranet to Tomcat 5.5.