W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2002

RE: Preventing a resource from being written

From: Peter Raymond <Peter.Raymond@merant.com>
Date: Thu, 24 Jan 2002 14:47:21 -0000
Message-ID: <20CF1CE11441D411919C0008C7C5A13B03BF636D@stalmail.eu.merant.com>
To: Elodie Tasia <e.tasia@ever-team.com>, IETF DAV <ietf-dav-versioning@w3.org>
Hi,

The ACL specification defines a "pseudo-principal" called DAV:all this
represents
all users.  So you could set an ACL on all resources denying write to
DAV:all.
Something that contains an ACE like....

  <D:ace> 
    <D:principal> 
      <D:all/> 
    </D:principal> 
    <D:deny> 
    <D:privilege> <D:write/> </D:privilege>  
    </D:deny> 
  </D:ace> 

Regards,
-- 
Peter Raymond - MERANT 
Principal Architect (PVCS) 
Tel: +44 (0)1727 813362 
Fax: +44 (0)1727 869804 
mailto:Peter.Raymond@merant.com 
WWW: http://www.merant.com 
-----Original Message-----
From: Elodie Tasia [mailto:e.tasia@ever-team.com]
Sent: 24 January 2002 14:43
To: IETF DAV
Subject: Preventing a resource from being written


Hi,

Suppose that I want to prevent a resource from being modified, just read.
And I use only what Webdav or ACL offers, not DeltaV.
What can I do ?
I can't set a infinite lock on that resource : it's "dangerous" and not nice
;o)
I could use the access control protocol, maybe, but I don't know how to
proceed : must I create juste one principal, that represent anyone, and has
a "read-only" right ?
What would be a good solution ?

thanx
Received on Thursday, 24 January 2002 09:51:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:43 GMT