RFC Compliance/WebDAV ACL

From Davical
< RFC Compliance
Revision as of 12:00, 14 November 2009 by Karora (talk) (New page: Covering the {{WebDAV ACL RFC}} points in detail and listing where DAViCal is believed to be in compliance with the specification. == Overview == From Section 2 of the RFC: * {{MUST}} sup...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Covering the RFC3744{{#if:WebDAV Access Control Protocol|:  |}}WebDAV Access Control Protocol points in detail and listing where DAViCal is believed to be in compliance with the specification.

Overview

From Section 2 of the RFC:

In addition, a server:

  • SHOULD support the MKCALENDAR method defined in Section 5.3.1 of this document.

Details of Unsupported Features

Section Feature Requirement Status as at 0.9.8
2. expose principal resources at an http(s) URL, which is a privileged scheme that points to resources that have additional properties, as described in Section 4 MUST Supported
3. Ability to perform a given method on a resource MUST be controlled by one or more privileges. MUST Supported
3. A principal with no privileges to a resource MUST be denied any HTTP access to that resource, unless the principal matches an ACE constructed using the DAV:all, DAV:authenticated, or DAV:unauthenticated pseudo-principals (see Section 5.5.1). MUST Supported
3. Servers MUST report a 403 "Forbidden" error if access is denied, except in the case where the privilege restricts the ability to know the resource exists, in which case 404 "Not Found" may be returned. MUST Supported
3. Privilege containment loops are not allowed; therefore, a privilege MUST NOT contain itself. MUST Supported
3. Privileges defined by individual implementations MUST NOT use the DAV: namespace, and instead should use a namespace that they control, such as an http scheme URL. MUST NOT Supported
3.1. the read privilege MUST control the OPTIONS method. MUST :  |}})
3.5. Any privilege controlling access by non-lock owners to UNLOCK MUST be aggregated under DAV:unlock. MUST Supported
3.12. Aggregation of Predefined Privileges MUST Supported
4. A principal MUST have a non-empty DAV:displayname property, and a DAV:resourcetype property. Additionally, a principal MUST report the DAV:principal XML element in the value of the DAV:resourcetype property. MUST Supported
4.1. Support for the alternate-URI-set property is REQUIRED, and the value is empty if no alternate URI exists for the principal. MUST :  |}})
4.2. Support for the principal-URL property is REQUIRED. MUST Supported
4.3. A URL in the DAV:group-member-set for a principal MUST be the DAV:principal-URL of that principal. MUST Supported
4.4. Support for the group-membership property is REQUIRED. MUST Supported
5. HTTP resources that support the WebDAV Access Control Protocol MUST contain the following properties:
  • DAV:owner
  • DAV:group
  • DAV:supported-privilege-set
  • DAV:current-user-privilege-set
  • DAV:acl
  • DAV:acl-restrictions
  • DAV:inherited-acl-set
  • DAV:principal-collection-set

Null resources (described in RFC4918{{#if:WebDAV|:  |}}WebDAV) MUST NOT contain these properties.

MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported
. MUST Supported