You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2005/10/03 15:45:48 UTC

[jira] Closed: (JCR-179) PROPPATCH in simple webdav server failing with 403 Forbidden error

     [ http://issues.apache.org/jira/browse/JCR-179?page=all ]
     
angela closed JCR-179:
----------------------


> PROPPATCH in simple webdav server failing with 403 Forbidden error
> ------------------------------------------------------------------
>
>          Key: JCR-179
>          URL: http://issues.apache.org/jira/browse/JCR-179
>      Project: Jackrabbit
>         Type: Bug
>     Reporter: Brian Moseley
>     Assignee: angela

>
> i've configured the import-collection chain (called via MKCOL) to add nodes with the node type "dav:collection", which is defined as such:
> NodeTypeName
>   dav:collection
> SuperTypes
>   nt:folder
> IsMixin
>   false
> HasOrderableChildNodes
>   false
> PrimaryItemName
>   null
> PropertyDef
>   Name *
>   RequiredType UNDEFINED
>   DefaultValues null
>   AutoCreate false
>   Mandatory false
>   OnParentVersion COPY
>   Protected false
>   Multiple false
> PropertyDef
>   Name *
>   RequiredType UNDEFINED
>   DefaultValues null
>   AutoCreate false
>   Mandatory false
>   OnParentVersion COPY
>   Protected false
>   Multiple true
> the idea is that i should be able to set arbitrary webdav properties (single- or multi-value) on a webdav collection.
> when i use cadaver to mkcol a collection (creating a jcr node of type dav:collection) and then try to propset an arbitrary property on that collection (which as i understand it would set a jcr property of the same name on the dav:collection node), i get a 403 Forbidden error:
> dav:/home/> mkcol hi
> Creating `hi': succeeded.
> dav:/home/> propset hi hi hi
> Setting property on `hi': failed:
> 403 Forbidden
> it's not clear to me if i'm using cadaver incorrectly, misunderstanding the PROPPATCH implementation, or both :) 

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