[
https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22785#comment-22785
]
Tim Donohue commented on DS-768:
--------------------------------
Hi Kim,
A little more info...it looks like in our SCM we just need to apply the Cocoon
r685544 patch that is supposed to fix *both* DS-253 / COCOON-2217, as well as
DS-768 / COCOON-2218.
So, I think the issue is that amongst all our hurrying to get this "fixed",
that full patch (to mainly the HttpServletResponseBufferWrapper) has not been
applied to our SCM.
Here's the specific changes that are not in our SCM:
* Full list of r685544 changes:
http://svn.apache.org/viewvc?view=revision&revision=685544
* Patch for HttpServletResponseBufferWrapper.java :
http://svn.apache.org/viewvc/cocoon/trunk/subprojects/cocoon-servlet-service/cocoon-servlet-service-impl/src/main/java/org/apache/cocoon/servletservice/HttpServletResponseBufferingWrapper.java?r1=685544&r2=685543&pathrev=685544&view=patch
* Patch for HttpServletResponseBufferWrapperTestCase.java :
http://svn.apache.org/viewvc/cocoon/trunk/subprojects/cocoon-servlet-service/cocoon-servlet-service-impl/src/test/java/org/apache/cocoon/servletservice/HttpServletResponseBufferingWrapperTestCase.java?r1=685544&r2=685543&pathrev=685544&view=patch
Assuming those patches apply cleanly to our SCM, I think they should resolve
our issues (or at least that seems to be the case, based on the comments on
both COCOON-2217 and COCOON-2218)
> 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, 1.8.0
> Reporter: Tim Donohue
> Assignee: Kim Shepherd
> Priority: Major
> Fix For: 1.8.0
>
> Attachments:
> add_ResourceNotFoundException_to_xmlui_transformers.patch,
> [DS-768]_add_ProcessingException_to_transformers,
> [DS-768]_dspace-cocoon-servlet-service-impl-1_0_2.patch,
> dspace-cocoon-servlet-service-impl-1.0.2.jar, Screen shot 2011-08-17 at
> 2.20.40 PM.png, Screenshot-Resource not found-Mozilla Firefox.png
>
>
> 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, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
