[
https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21964#comment-21964
]
Tim Donohue commented on DS-768:
--------------------------------
Ugh. I just verified this is the same thing that happens on Trunk code. :(
With dspace-cocoon-servlet-service-impl-1.0.1.jar (Old JAR), I get:
[14:45:13.278] GET http://localhost:8080/xmlui18/NOTVALID [HTTP/1.1 200 OK
126ms]
If I then replace it with dspace-cocoon-servlet-service-impl-1.0.2.jar (Kim's
new JAR), visiting the *SAME* bad URL still gives a 200:
[14:47:33.111] GET http://localhost:8080/xmlui18/NOTVALID [HTTP/1.1 200 OK 78ms]
But, if I visit a *NEW* bad URL, I get the proper 404:
[14:47:47.049] GET http://localhost:8080/xmlui18/NOTAVALIDURL [HTTP/1.1 404 Not
Found 156ms]
Unfortunately, refreshing the page & visiting that same bad URL a second time,
also gives a 200:
[14:47:53.771] GET http://localhost:8080/xmlui18/NOTAVALIDURL [HTTP/1.1 200 OK
53ms]
If I clear the Cocoon cache (from XMLUI Control Panel), each of the above bad
URLs will again throw a 404 on the first access, and then a 200 thereafter.
So, it's definitely a Cocoon caching issue. Though, maybe we can figure out a
way to tell Cocoon not to cache these pages?
Good find, Hardy.
> 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: [DS-768]_dspace-cocoon-servlet-service-impl-1_0_2.patch,
> 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, 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
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
