[ https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22758#comment-22758 ]
Kim Shepherd commented on DS-768: --------------------------------- OK, I can confirm that the source I committed to svn (modules/dspace-cocoon-servlet-service-impl) is the right stuff -- I just manually built it into a .jar, renamed to 1.0.2 and dropped it in after clearing cache etc., and it works. It's also the same filesize as the jar attached to this job, which is a good sign :) If anyone feels like doing a checkout on https://scm.dspace.org/svn/repo/modules/dspace-cocoon-servlet-service-impl/trunk/ and building it (it'll be named 1.0.3 in this case, i think.. don't worry about the version number it gets given), removing your existing dspace-servlet-service-impl, and dropping this into xmlui/WEB-INF/lib and testing, that'd be great, but i'm very confident that this is the right jar, and that my source is building the right jar. So we just have to sort out the maven/sonatype release stuff. Not sure on our sonatype procedure for modules but I'd like to try it straight from my computer here if that'd help.. Mark, is there any danger? > 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 Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel