Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.8.0
-
Fix Version/s: 1.8.0
-
Component/s: XMLUI
-
Labels:None
-
Attachments:
-
Comments:58
-
Documentation Status:Not Required
Description
In DSpace 1.7.0 RC1, the XMLUI "Page Not Found" page responds with a 200 OK, rather than the necessary 404 Not Found error.
For example:
http://demo.dspace.org/xmlui/NOTAVALIDPATH
I believe this used to function properly in 1.6.x, but it seems to be broken now.
Obviously, we want this to return a 404 Not Found, in order to ensure that search engines do not index "Page Not Found" responses.
Furthermore, it has been discovered that all other XMLUI Error pages (Cocoon Errors or Invalid Continuation errors) also respond with 200 OK. In addition, it seems this affects all 1.6.x versions of DSpace, as the same responses can be found on http://dspace.mit.edu (currently running 1.6.0 with patches), and http://researchspace.auckland.ac.nz (currently running 1.6.2 with patches).
Attachments
Issue Links
- is related to
-
DS-253 NullPointerException in HttpServletResponseBufferingWrapper (Cocoon bug?)
-
- Closed
-
-
DS-1347 Using an invalid identifier leads to an exception rather than the user-friendly invalid identifier page
-
- Closed
-
-
DS-1384 Very heavy error pages
-
- Closed
-
-
DS-754 Revisit Browse-By Responses for DSpace 1.8.0
-
- Closed
-
-
DS-1596 Page not found look and feel
-
- Closed
-