[
https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue reassigned DS-768:
------------------------------
Assignee: Kim Shepherd
This issue was discussed in the DSpace Developers Mtg on April 6, 2011:
[20:17] <tdonohue> Next up, is our much beloved DS-768.
[20:17] <kompewter> [ https://jira.duraspace.org/browse/DS-768 ] - [#DS-768]
All XMLUI Error Pages respond with 200 OK, instead of 404 Not Found - DuraSpace
JIRA
[20:17] <tdonohue> Ok. Ds-767 - assign to kshepherd
[20:17] <richardrodgers> agreed, sounds like nice to have if not too expensive
[20:17] <tdonohue> anyone do further research/investigation into Ds-768?
[20:18] <kshepherd> mdiggory asked a cocoon guy about the revision the patch
was committed
[20:18] <kshepherd> so we could try and track it down
[20:18] <kshepherd> i checked out the cocoon 2.2 source to try and track it
down via commit comments, but had no luck
[20:18] <tdonohue> +1 to tracking down this cocoon patch, if we can.
[20:18] <kshepherd> there's a reply in COCOON-2218 to mark's questoin
[20:18] <kshepherd> "Mark, I'm not entirely sure, but looking at the history I
think it could've been revision 685544. Can't easily test this at the moment
though..."
[20:19] <kshepherd> so that gives us a possible lead
[20:19] <kshepherd> i'll add to our comments
[20:19] <tdonohue> sounds good. volunteers to test this lead out? (or is
mdiggory planning on doing so?)
[20:20] <kshepherd> well i know mdiggory and i have it on our radars
[20:20] * tdonohue remembers mdiggory is out this week. so, he actually isn't
here today.
[20:20] <kshepherd> not sure if it needs assigning until we're closer to a
fix..?
[20:21] <tdonohue> ok. Ds-768: kshepherd will add updates. He and mdiggory have
this on their radars. One or both will bring it back to our attention as help
is necessary, etc
> 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
> Assignee: Kim Shepherd
> Priority: Major
> Fix For: 1.8.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
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
