jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-391) WebDAV method invocation trying to create a new resource should fail with 409 (Conflict) if parent resource does not exist
Date Mon, 10 Apr 2006 10:49:00 GMT
    [ http://issues.apache.org/jira/browse/JCR-391?page=comments#action_12373837 ] 

angela commented on JCR-391:
----------------------------

hi julian

if i remember correctly, the reason for this is that JSR170 does not allow to perform a 'shallow'
copy.
the conflict would be detected by the javax.jcr.Workspace#copy therefore no additional check
for existing parent is performed.

If you think this is worth an extra check, i would add it to the AbstractWebdavServlet, where
some basic validation of the destination is done.

regards
angela

> 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

>
> 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


Mime
View raw message