[
https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-768:
---------------------------
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).
was:
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.
Affects Version/s: 1.6.0
1.6.1
1.6.2
Summary: All XMLUI Error Pages respond with 200 OK, instead of
404 Not Found (was: 1.7.0 XMLUI "Page Not Found" returns a 200 OK, instead of
404 Not Found)
Changed title and description above to detail that this invalid 200 OK response
seems to affect all 1.6.x versions of DSpace, and is returned for *all* errors
reported by XMLUI.
> All XMLUI Error Pages respond with 200 OK, instead of 404 Not Found
> -------------------------------------------------------------------
>
> Key: DS-768
> URL: https://jira.duraspace.org/browse/DS-768
> Project: DSpace
> Issue Type: Bug
> Components: XMLUI
> Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.7.0
> Reporter: Tim Donohue
> Priority: Major
> Fix For: 1.7.0
>
>
> 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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
