1 Dec 2007 23:32
Re: New draft: draft-daboo-webdav-mkcol-00.txt
Werner Baumann <werner.baumann <at> onlinehome.de>
2007-12-01 22:32:13 GMT
2007-12-01 22:32:13 GMT
Looking at RFC 4918, I found this: > A MKCOL request message may contain a message body. The precise > behaviour of a MKCOL request when the body is present is undefined, > but limited to creating collections, members of a collection, bodies > of members, and properties on the collections or members. So there is no need for an "extension". All we need is a substantiation of what is undefined and also one correction of what is wrong in RFC 4918. Here is a proposal: =================== 1. MKCOL request with a propertyupdate XML body ----------------------------------------------- When the body of a MKCOL request contains an propertyupdate XML element, the server must process it according to RFC 4918, 9.2 PROPPATCH Method. If this fails, the requests fails and the collection MUST NOT be created. The propertyupdate XML element may contain a set XML element for the resourcetype property. This MUST be the first set XML element. The resourcetype requested is a specialised type of a collection. The server MUST recognize this special type of collection and MUST be able to handle it; otherwise the request MUST fail. 2. Response to MKCOL with a propertyupdate XML body ---------------------------------------------------(Continue reading)
RSS Feed