-
Type:
Defect
-
Resolution: Cannot Reproduce
-
Priority:
Major
-
Affects Version/s: None
-
Component/s: User Interface
-
None
We might want to consider overriding Tomcat's standard error pages with our own.
It is easy to point to a specific page in the web.xml file for each error, but my guess is that Spring MVC also has its own way of handeling the different http status codes.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
It is also important to consider that non-browser devices (wget, web services, etc...) will be accessing our application and it might be important to return just plain text instead of html markup.
It is easy to point to a specific page in the web.xml file for each error, but my guess is that Spring MVC also has its own way of handeling the different http status codes.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
It is also important to consider that non-browser devices (wget, web services, etc...) will be accessing our application and it might be important to return just plain text instead of html markup.