If it's a bug, is it possible to change the inheritance setting on the fly ? ie, change it to be "path" just before creating the new collection, and then change it back after ? Nick
-----Original Message----- From: James Mason [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 18, 2005 6:26 PM To: Slide Users Mailing List Subject: Re: MKCOL method when using acl_inheritance=none - fails (403) This could be a bug. Since you have inheritance off you don't have "write" access to the new node you're creating. I think I remember seeing something similar awhile ago. I don't know if it was fixed. -James On Tue, 2005-01-18 at 16:49 -0500, Nick Longinow wrote: > Hi > > I've got my acl inheritance set to none, and am explicitly setting acls on > nodes as needed. I find that when I switched to doing this from having > inheritance set to 'path', I now get a 403 (forbidden) when I attempt a > mkcolmethod to create a collection under the /files node (programmatically), > even though I do it in the credentials of the root, who should have "all" > permissions to that /files node. > The DAV spec says that mkcol just requires having dav:bind on the parent > node, which I believe I have set (by setting "all" for the principal > "/users/root" on the "/files" node. > Any ideas why this is occurring ? > Nick > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
