[ 
https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim Shepherd updated DS-768:
----------------------------

    Attachment: dspace-cocoon-servlet-service-impl-1.0.2.jar

I've attached an example of a fixed cocoon-servlet-service-impl (based on 
1.0.0).
This is returning proper 404, unlike the old 1.0.0 and dspace's 1.0.1 
customisation.

I'm 99% sure that it incorporates the fixes for DS-253 / COCOON-2217, as well 
as DS-768 / COCOON-2218, but I'd appreciate more eyes on it... the source for 
dspace-cocoon-servlet-service-impl-1.0.1 isn't available anywhere that I can 
find, but the patches listed in DS-253 certainly imply that I've applied the 
same fixes to 1.02.

So I think this will fix up our response codes in XMLUI once and for all :)

Would really appreciate testers, so I can be sure I'm not reintroducing old 
bugs.
A quick and dirty test is just to drop this jar into [ your deployed xmlui 
]/WEB-INF/lib and remove the old 1.0.1 version, clear tomcat cache, and restart.

> 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
>
>         Attachments: dspace-cocoon-servlet-service-impl-1.0.2.jar
>
>
> 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

        

------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to