You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2006/04/12 18:43:20 UTC
[jira] Updated: (JCR-391) WebDAV method invocation trying to create
a new resource should fail with 409 (Conflict) if parent resource does not
exist
[ http://issues.apache.org/jira/browse/JCR-391?page=all ]
Julian Reschke updated JCR-391:
-------------------------------
Attachment: diff.txt
OK, as Angela pointed out, this is because Litmus is trying a shallow copy, which currently isn't implemented. Returning 403 in this case is correct.
However, there seems to be a very simple workaround which does not only make Litmus happy, but may also help in some real-world cases: only reject the request here if the source resource indeed is a collection (otherwise WebDAV semantics for Depth: 0 and Depth: Infinity are identical).
(attached)
> WebDAV method invocation trying to create a new resource should fail with 409 (Conflict) if parent resource does not exist
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-391
> URL: http://issues.apache.org/jira/browse/JCR-391
> Project: Jackrabbit
> Type: Bug
> Components: webdav
> Reporter: Julian Reschke
> Priority: Minor
> Attachments: diff.txt
>
> This is Litmus test case copy_nodestcoll. An attempt is made to COPY an existing resource to a new location, where the parent collection of the resource-to-be-created does not exist. RFC2518 asks for status code 409 (Conflict) instead of 403 (Forbidden) in this case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira