draft-ietf-webdav-rfc2518bis-03.txt   draft-ietf-webdav-rfc2518bis-04.txt 
Y. Goland, Microsoft Internet Draft L. Dusseault, Xythos
E. Whitehead, UCSC Document: draft-ietf-webdav-rfc2518bis-04.txt J. Crawford, IBM
Internet Draft A. Faizi, Netscape Expires: Oct 2003
Document: draft-ietf-webdav-rfc2518bis-03.txt S. Carter, Novell
Expires: Dec 2002 D. Jensen, Novell
L. Dusseault, Xythos
J. Crawford, IBM
HTTP Extensions for Distributed Authoring - WebDAV RFC2518 bis HTTP Extensions for Distributed Authoring - WebDAV RFC2518 bis
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026. with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at line 43 skipping to change at line 39
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Abstract Abstract
WebDAV consists of a set of methods, headers, and content-types WebDAV consists of a set of methods, headers, and content-types
ancillary to HTTP/1.1 for the management of resource properties, ancillary to HTTP/1.1 for the management of resource properties,
creation and management of resource collections, namespace creation and management of resource collections, namespace
manipulation, and resource locking (collision avoidance). manipulation, and resource locking (collision avoidance).
RFC2518 was published in February 1998, and this draft makes only RFC2518 was published in February 1998, and this draft makes minor
minor revisions mostly due to interoperability experience. revisions mostly due to interoperability experience.
Table of Contents Table of Contents
1 Introduction............................................6 1 Introduction...................................................6
2 Notational Conventions...................................7 2 Notational Conventions.........................................7
3 Terminology.............................................7 3 Terminology....................................................7
4 Data Model for Resource Properties.........................8 4 Data Model for Resource Properties.............................8
Expires Aug 2002 1 Expires Aug 2002 1
WebDAV (RFC2518) bis March 2003
4.1 The Resource Property Model..............................8 WebDAV (RFC2518) bis June 2003
4.2 Existing Metadata Proposals..............................8
4.3 Properties and HTTP Headers..............................9
4.4 Property Values........................................9
4.5 Property Names........................................ 11
5 Collections of Web Resources............................. 11
5.1 HTTP URL Namespace Model ............................... 11
5.2 Collection Resources................................... 12
5.3 Source Resources and Output Resources.................... 13
6 Locking ............................................... 14
6.1 Exclusive Vs. Shared Locks.............................. 14
6.2 Required Support...................................... 15
6.3 Lock Tokens........................................... 15
6.4 opaquelocktoken Lock Token URI Scheme.................... 16
6.5 Lock Capability Discovery............................... 16
6.6 Active Lock Discovery.................................. 16
6.7 Usage Considerations................................... 17
7 Write Lock............................................. 17
7.1 Methods Restricted by Write Locks........................ 18
7.2 Write Locks and Lock Tokens............................. 18
7.3 Write Locks and Properties.............................. 18
7.4 Write Locks and Unmapped URLs........................... 18
7.5 Write Locks and Collections............................. 19
7.6 Write Locks and the If Request Header.................... 20
7.7 Write Locks and COPY/MOVE............................... 21
7.8 Refreshing Write Locks................................. 21
8 HTTP Methods for Distributed Authoring .................... 21
8.1 General request and response handling.................... 21
8.2 PROPFIND............................................. 21
8.2.1 Example - Retrieving Named Properties................... 21
8.2.2 Example - Using propname to Retrieve all Property Names... 21
8.3 PROPPATCH ............................................ 21
8.3.1 Status Codes for use with 207 (Multi-Status)............. 21
8.3.2 Example - PROPPATCH................................... 21
8.4 MKCOL Method.......................................... 21
8.4.1 Example - MKCOL...................................... 21
8.5 GET, HEAD for Collections............................... 21
8.6 POST for Collections................................... 21
8.7 DELETE............................................... 21
8.7.1 Example - DELETE..................................... 21
8.8 PUT.................................................. 21
8.9 COPY Method........................................... 21
8.10 MOVE Method ......................................... 21
8.11 LOCK Method ......................................... 21
8.11.1 Example - Simple Lock Request......................... 21
8.11.2 Example - Refreshing a Write Lock..................... 21
8.11.3 Example - Multi-Resource Lock Request.................. 21
Expires Aug 2003 2 4.1 The Resource Property Model..................................8
WebDAV (RFC2518) bis March 2003 4.2 Existing Metadata Proposals..................................8
4.3 Properties and HTTP Headers..................................9
4.4 XML Usage....................................................9
4.5 Property Values.............................................10
4.6 Property Names..............................................11
5 Collections of Web Resources..................................11
5.1 HTTP URL Namespace Model....................................12
5.2 Collection Resources........................................12
5.3 Source Resources and Output Resources.......................13
6 Locking.......................................................14
6.1 Exclusive Vs. Shared Locks..................................14
6.2 Required Support............................................15
6.3 Lock Tokens.................................................16
6.4 opaquelocktoken Lock Token URI Scheme.......................16
6.5 Lock Capability Discovery...................................17
6.6 Active Lock Discovery.......................................17
6.7 Usage Considerations........................................17
7 Write Lock....................................................18
7.1 Methods Restricted by Write Locks...........................18
7.2 Write Locks and Lock Tokens.................................19
7.3 Write Locks and Properties..................................19
7.4 Write Locks and Unmapped URLs...............................19
7.5 Write Locks and Collections.................................21
7.6 Write Locks and the If Request Header.......................21
7.7 Write Locks and COPY/MOVE...................................22
7.8 Refreshing Write Locks......................................23
8 HTTP Methods for Distributed Authoring........................23
8.1 General request and response handling.......................23
8.1.1 Use of XML.................................................23
8.1.2 Required Bodies in Requests................................24
8.1.3 Use of Location header in responses........................24
8.1.4 Required Response Headers: Date............................24
8.1.5 ETag.......................................................24
8.1.6 Including error response bodies............................25
8.2 PROPFIND....................................................26
8.2.1 Example - Retrieving Named Properties......................28
8.2.2 Example - Retrieving Named and Dead Properties.............29
8.2.3 Example - Using propname to Retrieve all Property Names....30
8.2.4 PROPFIND Request Errors....................................31
8.3 PROPPATCH...................................................32
8.3.1 Status Codes for use with 207 (Multi-Status)...............32
8.3.2 Example - PROPPATCH........................................33
8.4 MKCOL Method................................................34
8.4.1 Example - MKCOL............................................35
8.12 UNLOCK Method........................................ 21 Expires Oct 2003 2
8.12.1 Example - UNLOCK.................................... 21
9 HTTP Headers for Distributed Authoring .................... 21
9.1 DAV Header............................................ 21
9.2 Depth Header.......................................... 21
9.3 Destination Header..................................... 21
9.4 Force-Authentication Header............................. 21
9.5 If Header ............................................ 21
9.6 Lock-Token Header ..................................... 21
9.7 Overwrite Header...................................... 21
9.8 Status-URI Response Header.............................. 21
9.9 Timeout Request Header................................. 21
10 Status Code Extensions to HTTP/1.1........................ 21
10.1 102 Processing....................................... 21
10.2 207 Multi-Status..................................... 21
10.3 422 Unprocessable Entity.............................. 21
10.4 423 Locked.......................................... 21
10.5 424 Failed Dependency................................. 21
10.6 507 Insufficient Storage.............................. 21
11 Use of HTTP Status Codes................................. 21
11.1 301 Moved Permanently................................. 21
11.2 302 Found........................................... 21
11.3 400 Bad Request...................................... 21
11.4 403 Forbidden........................................ 21
11.5 409 Conflict......................................... 21
11.6 414 Request-URI Too Long.............................. 21
12 Multi-Status Response................................... 21
12.1 302 and 303 in Multi-Status............................ 21
13 XML Element Definitions ................................. 21
13.1 activelock XML Element................................ 21
13.2 depth XML Element.................................... 21
13.3 locktoken XML Element................................. 21
13.4 lockroot XML Element.................................. 21
13.5 timeout XML Element................................... 21
13.6 collection XML Element................................ 21
13.7 href XML Element..................................... 21
13.8 lockentry XML Element................................. 21
13.9 lockinfo XML Element.................................. 21
13.10 lockscope XML Element................................. 21
13.11 exclusive XML Element................................. 21
13.12 shared XML Element ................................... 21
13.13 locktype XML Element.................................. 21
13.14 write XML Element.................................... 21
13.15 multistatus XML Element............................... 21
13.16 response XML Element.................................. 21
13.17 propstat XML Element.................................. 21
13.18 status XML Element ................................... 21
Expires Aug 2003 3 WebDAV (RFC2518) bis June 2003
WebDAV (RFC2518) bis March 2003
13.19 responsedescription XML Element........................ 21 8.5 GET, HEAD for Collections...................................35
13.20 owner XML Element.................................... 21 8.6 POST for Collections........................................36
13.21 prop XML element..................................... 21 8.7 DELETE......................................................36
13.22 propertyupdate XML element ............................ 21 8.7.1 Example - DELETE...........................................37
13.23 remove XML element ................................... 21 8.8 PUT.........................................................37
13.24 set XML element...................................... 21 8.9 COPY Method.................................................38
13.25 propfind XML Element.................................. 21 8.9.1 COPY for Collections.......................................39
13.26 allprop XML Element................................... 21 8.9.2 COPY and the Overwrite Header..............................40
13.27 propname XML Element.................................. 21 8.9.3 Status Codes...............................................40
14 DAV Properties......................................... 21 8.9.4 Example - COPY with Overwrite..............................41
14.1 creationdate Property................................. 21 8.10 MOVE Method................................................42
14.2 displayname Property.................................. 21 8.10.1 MOVE for Properties......................................43
14.3 getcontentlanguage Property............................ 21 8.10.2 MOVE for Collections.....................................43
14.4 getcontentlength Property............................. 21 8.10.3 MOVE and the Overwrite Header............................44
14.5 getcontenttype Property............................... 21 8.10.4 Status Codes.............................................44
14.6 getetag Property..................................... 21 8.10.5 Example - MOVE of a Non-Collection.......................45
14.7 getlastmodified Property.............................. 21 8.11 LOCK Method................................................46
14.8 lockdiscovery Property................................ 21 8.11.1 Example - Simple Lock Request............................50
14.8.1 Example - Retrieving the lockdiscovery Property......... 21 8.11.2 Example - Refreshing a Write Lock........................51
14.9 resourcetype Property................................. 21 8.11.3 Example - Multi-Resource Lock Request....................52
14.10 supportedlock Property................................ 21 8.12 UNLOCK Method..............................................54
14.10.1 Example - Retrieving the supportedlock Property ........ 21 8.12.1 Example - UNLOCK.........................................54
15 Instructions for Processing XML in DAV .................... 21 9 HTTP Headers for Distributed Authoring........................55
16 DAV Compliance Classes.................................. 21 9.1 DAV Header..................................................55
16.1 Class 1............................................. 21 9.2 Depth Header................................................55
16.2 Class 2............................................. 21 9.3 Destination Header..........................................57
16.3 Class "bis" ......................................... 21 9.4 Force-Authentication Header.................................57
17 Internationalization Considerations....................... 21 9.5 If Header...................................................57
18 Security Considerations ................................. 21 9.5.1 No-tag-list Production.....................................58
18.1 Authentication of Clients............................. 21 9.5.2 Example - No-tag-list If Header............................58
18.2 Denial of Service.................................... 21 9.5.3 Tagged-list Production.....................................59
18.3 Security through Obscurity ............................ 21 9.5.4 Example - Tagged List If header............................59
18.4 Privacy Issues Connected to Locks...................... 21 9.5.5 Not Production.............................................59
18.5 Privacy Issues Connected to Properties.................. 21 9.5.6 Matching Function..........................................60
18.6 Reduction of Security due to Source Link................ 21 9.5.7 If Header and Non-DAV Aware Proxies........................60
18.7 Implications of XML External Entities................... 21 9.6 Lock-Token Header...........................................60
18.8 Risks Connected with Lock Tokens....................... 21 9.7 Overwrite Header............................................60
19 IANA Considerations..................................... 21 9.8 Status-URI Response Header..................................61
20 Intellectual Property................................... 21 9.9 Timeout Request Header......................................61
21 Acknowledgements........................................ 21 10 Status Code Extensions to HTTP/1.1............................62
22 References............................................. 21 10.1 102 Processing.............................................62
22.1 Normative References.................................. 21 10.2 207 Multi-Status...........................................63
22.2 Informational References.............................. 21 10.3 422 Unprocessable Entity...................................63
23 Authors' Addresses...................................... 21 10.4 423 Locked.................................................63
24 Appendices............................................. 21 10.5 424 Failed Dependency......................................63
24.1 Appendix 1 - WebDAV Document Type Definition............. 21
24.2 Appendix 3 - Notes on Processing XML Elements............ 21
Expires Aug 2003 4 Expires Oct 2003 3
WebDAV (RFC2518) bis March 2003
24.2.1 Notes on Empty XML Elements.......................... 21 WebDAV (RFC2518) bis June 2003
24.2.2 Notes on Illegal XML Processing....................... 21
24.2.3 Example - XML Syntax Error........................... 21
24.2.4 Example - Unknown XML Element......................... 21
24.3 Appendix 4: UUID Node Generation....................... 21
25 Full Copyright Statement................................. 21
Expires Aug 2003 5 10.6 507 Insufficient Storage...................................63
WebDAV (RFC2518) bis March 2003 11 Use of HTTP Status Codes......................................63
11.1 301 Moved Permanently......................................63
11.2 302 Found..................................................64
11.3 400 Bad Request............................................64
11.4 403 Forbidden..............................................64
11.5 409 Conflict...............................................64
11.6 414 Request-URI Too Long...................................64
12 Multi-Status Response.........................................64
12.1 Responses requiring Location in Multi-Status...............65
13 XML Element Definitions.......................................65
13.1 activelock XML Element.....................................65
13.2 depth XML Element..........................................66
13.3 locktoken XML Element......................................66
13.4 lockroot XML Element.......................................66
13.5 timeout XML Element........................................66
13.6 collection XML Element.....................................67
13.7 href XML Element...........................................67
13.8 lockentry XML Element......................................67
13.9 lockinfo XML Element.......................................67
13.10 lockscope XML Element......................................67
13.11 exclusive XML Element......................................68
13.12 shared XML Element.........................................68
13.13 locktype XML Element.......................................68
13.14 write XML Element..........................................68
13.15 multistatus XML Element....................................68
13.16 response XML Element.......................................69
13.17 propstat XML Element.......................................69
13.18 status XML Element.........................................70
13.19 responsedescription XML Element............................70
13.20 owner XML Element..........................................70
13.21 prop XML element...........................................70
13.22 propertyupdate XML element.................................70
13.23 remove XML element.........................................71
13.24 set XML element............................................71
13.25 propfind XML Element.......................................71
13.26 allprop XML Element........................................72
13.27 propname XML Element.......................................72
13.28 deadprops XML Element......................................72
14 DAV Properties................................................72
14.1 creationdate Property......................................73
14.2 displayname Property.......................................73
14.3 getcontentlanguage Property................................74
14.4 getcontentlength Property..................................74
14.5 getcontenttype Property....................................74
Expires Oct 2003 4
WebDAV (RFC2518) bis June 2003
14.6 getetag Property...........................................75
14.7 getlastmodified Property...................................75
14.8 lockdiscovery Property.....................................76
14.8.1 Example - Retrieving the lockdiscovery Property..........76
14.9 resourcetype Property......................................77
14.10 supportedlock Property.....................................78
14.10.1 Example - Retrieving the supportedlock Property..........78
15 Instructions for Processing XML in DAV........................79
16 DAV Compliance Classes........................................80
16.1 Class 1....................................................80
16.2 Class 2....................................................80
16.3 Class "bis"................................................80
17 Internationalization Considerations...........................81
18 Security Considerations.......................................82
18.1 Authentication of Clients..................................82
18.2 Denial of Service..........................................83
18.3 Security through Obscurity.................................83
18.4 Privacy Issues Connected to Locks..........................83
18.5 Privacy Issues Connected to Properties.....................84
18.6 Implications of XML External Entities......................84
18.7 Risks Connected with Lock Tokens...........................85
19 IANA Considerations...........................................85
20 Intellectual Property.........................................86
21 Acknowledgements..............................................86
22 References....................................................88
22.1 Normative References.......................................88
22.2 Informational References...................................89
23 Authors' Addresses............................................90
24 Appendices....................................................91
24.1 Appendix 1 - WebDAV Document Type Definition...............91
24.2 Appendix 3 - Notes on Processing XML Elements..............92
24.2.1 Notes on Empty XML Elements..............................92
24.2.2 Notes on Illegal XML Processing..........................92
24.2.3 Example - XML Syntax Error...............................93
24.2.4 Example - Unknown XML Element............................93
24.3 Appendix 4: UUID Node Generation...........................94
25 Full Copyright Statement......................................96
Expires Oct 2003 5
WebDAV (RFC2518) bis June 2003
1 Introduction 1 Introduction
This document describes an extension to the HTTP/1.1 protocol that This document describes an extension to the HTTP/1.1 protocol that
allows clients to perform remote web content authoring operations. allows clients to perform remote web content authoring operations.
This extension provides a coherent set of methods, headers, request This extension provides a coherent set of methods, headers, request
entity body formats, and response entity body formats that provide entity body formats, and response entity body formats that provide
operations for: operations for:
Properties: The ability to create, remove, and query information Properties: The ability to create, remove, and query information
skipping to change at line 269 skipping to change at line 295
describe most error conditions encountered by WebDAV methods, there describe most error conditions encountered by WebDAV methods, there
are some errors that do not fall neatly into the existing are some errors that do not fall neatly into the existing
categories. New status codes developed for the WebDAV methods are categories. New status codes developed for the WebDAV methods are
defined in section 10, and existing HTTP status codes as used in defined in section 10, and existing HTTP status codes as used in
WebDAV are described in section Error! Reference source not found.. WebDAV are described in section Error! Reference source not found..
Since some WebDAV methods may operate over many resources, the Since some WebDAV methods may operate over many resources, the
Multi-Status response has been introduced to return status Multi-Status response has been introduced to return status
information for multiple resources. The Multi-Status response is information for multiple resources. The Multi-Status response is
described in section 12. described in section 12.
WebDAV uses XML to marshall complicated request and response Expires Oct 2003 6
information, as well as to express metadata. XML elements used in
this specification are defined in section 13. A DTD is provided in
Expires Aug 2003 6 WebDAV (RFC2518) bis June 2003
WebDAV (RFC2518) bis March 2003
Appendix 1. Section 15 explains how to process XML appearing in WebDAV uses XML to marshal complicated request and response
WebDAV so that it truly is extensible. information, as well as to express metadata. XML elements used in
this specification are defined in section 13. An informational DTD
is provided in Appendix 1. Section 15 explains how to process XML
appearing in WebDAV so that it truly is extensible.
WebDAV employs the property mechanism to store information about the WebDAV employs the property mechanism to store information about the
current state of the resource. For example, when a lock is taken current state of the resource. For example, when a lock is taken
out on a resource, a lock information property describes the current out on a resource, a lock information property describes the current
state of the lock. Section 14 defines the properties used within the state of the lock. Section 13.28 defines the properties used within
WebDAV specification. the WebDAV specification.
Finishing off the specification are sections on what it means to be Finishing off the specification are sections on what it means to be
compliant with this specification (section 16), on compliant with this specification (section 16), on
internationalization support (section 17), and on security (section internationalization support (section 17), and on security (section
18). 18).
2 Notational Conventions 2 Notational Conventions
Since this document describes a set of extensions to the HTTP/1.1 Since this document describes a set of extensions to the HTTP/1.1
protocol, the augmented BNF used herein to describe protocol protocol, the augmented BNF used herein to describe protocol
skipping to change at line 311 skipping to change at line 337
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC 2119 this document are to be interpreted as described in RFC 2119
[RFC2119]. [RFC2119].
3 Terminology 3 Terminology
URI/URL - A Uniform Resource Identifier and Uniform Resource URI/URL - A Uniform Resource Identifier and Uniform Resource
Locator, respectively. These terms (and the distinction between Locator, respectively. These terms (and the distinction between
them) are defined in [RFC2396]. them) are defined in [RFC2396].
Collection - A resource that contains a set of URIs, termed member Collection - A resource that contains a set of URLs, which identify
URIs, which identify member resources and meets the requirements in and locate member resources and which meet the requirements in
section 5 of this specification. section 5 of this specification.
Member URI - A URI which is a member of the set of URIs contained by Member URL - A URL which is a member of the set of URLs contained by
a collection. a collection.
Internal Member URI - A Member URI that is immediately relative to Internal Member URL - A Member URL that is immediately relative to
the URI of the collection (the definition of immediately relative is the URL of the collection (the definition of immediately relative is
given in section 5.2). given in section 5.2).
Expires Oct 2003 7
WebDAV (RFC2518) bis June 2003
Property - A name/value pair that contains descriptive information Property - A name/value pair that contains descriptive information
about a resource. about a resource.
Live Property - A property whose semantics and syntax are enforced Live Property - A property whose semantics and syntax are enforced
by the server. For example, the live "getcontentlength" property by the server. For example, the live "getcontentlength" property
Expires Aug 2003 7
WebDAV (RFC2518) bis March 2003
has its value, the length of the entity returned by a GET request, has its value, the length of the entity returned by a GET request,
automatically calculated by the server. automatically calculated by the server.
Dead Property - A property whose semantics and syntax are not Dead Property - A property whose semantics and syntax are not
enforced by the server. The server only records the value of a dead enforced by the server. The server only records the value of a dead
property; the client is responsible for maintaining the consistency property; the client is responsible for maintaining the consistency
of the syntax and semantics of a dead property. of the syntax and semantics of a dead property.
Null Resource - A resource which responds with a 404 (Not Found) to
any HTTP/1.1 or DAV method except for PUT, MKCOL, OPTIONS and LOCK.
A NULL resource MUST NOT appear as a member of its parent
collection.
4 Data Model for Resource Properties 4 Data Model for Resource Properties
4.1 The Resource Property Model 4.1 The Resource Property Model
Properties are pieces of data that describe the state of a resource. Properties are pieces of data that describe the state of a resource.
Properties are data about data. Properties are data about data.
Properties are used in distributed authoring environments to provide Properties are used in distributed authoring environments to provide
for efficient discovery and management of resources. For example, a for efficient discovery and management of resources. For example, a
'subject' property might allow for the indexing of all resources by 'subject' property might allow for the indexing of all resources by
skipping to change at line 380 skipping to change at line 401
4.2 Existing Metadata Proposals 4.2 Existing Metadata Proposals
Properties have long played an essential role in the maintenance of Properties have long played an essential role in the maintenance of
large document repositories, and many current proposals contain some large document repositories, and many current proposals contain some
notion of a property, or discuss web metadata more generally. These notion of a property, or discuss web metadata more generally. These
include PICS [REC-PICS], PICS-NG, XML, Web Collections, and several include PICS [REC-PICS], PICS-NG, XML, Web Collections, and several
proposals on representing relationships within HTML. Work on PICS-NG proposals on representing relationships within HTML. Work on PICS-NG
and Web Collections has been subsumed by the Resource Description and Web Collections has been subsumed by the Resource Description
Framework (RDF) metadata activity of the World Wide Web Consortium. Framework (RDF) metadata activity of the World Wide Web Consortium.
Expires Oct 2003 8
WebDAV (RFC2518) bis June 2003
RDF consists of a network-based data model and an XML representation RDF consists of a network-based data model and an XML representation
of that model. of that model.
Some proposals come from a digital library perspective. These Some proposals come from a digital library perspective. These
include the Dublin Core [RFC2413] metadata set and the Warwick include the Dublin Core [RFC2413] metadata set and the Warwick
Expires Aug 2003 8
WebDAV (RFC2518) bis March 2003
Framework [WF], a container architecture for different metadata Framework [WF], a container architecture for different metadata
schemas. The literature includes many examples of metadata, schemas. The literature includes many examples of metadata,
including MARC [USMARC], a bibliographic metadata format, and a including MARC [USMARC], a bibliographic metadata format, and a
technical report bibliographic format employed by the Dienst system technical report bibliographic format employed by the Dienst system
[RFC1807]. Additionally, the proceedings from the first IEEE [RFC1807]. Additionally, the proceedings from the first IEEE
Metadata conference describe many community-specific metadata sets. Metadata conference describe many community-specific metadata sets.
Participants of the 1996 Metadata II Workshop in Warwick, UK [WF], Participants of the 1996 Metadata II Workshop in Warwick, UK [WF],
noted that "new metadata sets will develop as the networked noted that "new metadata sets will develop as the networked
infrastructure matures" and "different communities will propose, infrastructure matures" and "different communities will propose,
skipping to change at line 436 skipping to change at line 458
parameters are encoded in XML entity bodies when they have unbounded parameters are encoded in XML entity bodies when they have unbounded
length, or when they may be shown to a human user and hence require length, or when they may be shown to a human user and hence require
encoding in an ISO 10646 character set. Otherwise, parameters are encoding in an ISO 10646 character set. Otherwise, parameters are
encoded within HTTP headers. encoded within HTTP headers.
In addition to encoding method parameters, XML is used in WebDAV to In addition to encoding method parameters, XML is used in WebDAV to
encode the responses from methods, providing the extensibility and encode the responses from methods, providing the extensibility and
internationalization advantages of XML for method output, as well as internationalization advantages of XML for method output, as well as
input. input.
Expires Oct 2003 9
WebDAV (RFC2518) bis June 2003
An XML DTD is included in an appendix for all the XML elements An XML DTD is included in an appendix for all the XML elements
defined in this specification. However, legal XML will not be valid defined in this specification. However, legal XML will not be valid
according to this DTD due to namespace usage and extension rules, so according to this DTD due to namespace usage and extension rules, so
the DTD is only informational. the DTD is only informational.
The XML namespace extension is also used in this specification in The XML namespace extension is also used in this specification in
order to allow for new XML elements to be added without fear of order to allow for new XML elements to be added without fear of
Expires Aug 2003 9
WebDAV (RFC2518) bis March 2003
colliding with other element names. Although WebDAV request and colliding with other element names. Although WebDAV request and
response bodies can be extended by arbitrary XML elements, which can response bodies can be extended by arbitrary XML elements, which can
be ignored by the message recipient, an XML element in the "DAV:" be ignored by the message recipient, an XML element in the "DAV:"
namespace SHOULD NOT be used in the request or response body unless namespace SHOULD NOT be used in the request or response body unless
that XML element is explicitly defined in an IETF RFC reviewed by a that XML element is explicitly defined in an IETF RFC reviewed by a
WebDAV working group. WebDAV working group.
Note that the use of a new top-level URI identifier as a namespace Note that ˘DAV:÷ is a top-level URI identifier that was defined
is considered by many to be a bad thing, and should not be emulated. solely to provide a namespace for WebDAV XML elements and property
However, "DAV:" was defined as the WebDAV namespace for property names. This practice is discouraged in part because registration of
names and XML elements before standard best practices emerged, and top-level URI identifiers is difficult. "DAV:" was defined as the
this namespace is kept and still used because of significant WebDAV namespace before standard best practices emerged, and this
existing deployments. namespace is kept and still used because of significant existing
deployments, but this should not be emulated.
4.5 Property Values 4.5 Property Values
The value of a property when expressed in XML MUST be well formed. The value of a property is always a (wellformed) XML fragment.
XML has been chosen because it is a flexible, self-describing, XML has been chosen because it is a flexible, self-describing,
structured data format that supports rich schema definitions, and structured data format that supports rich schema definitions, and
because of its support for multiple character sets. XML's self- because of its support for multiple character sets. XML's self-
describing nature allows any property's value to be extended by describing nature allows any property's value to be extended by
adding new elements. Older clients will not break when they adding new elements. Older clients will not break when they
encounter extensions because they will still have the data specified encounter extensions because they will still have the data specified
in the original schema and will ignore elements they do not in the original schema and will ignore elements they do not
understand. XML's support for multiple character sets allows any understand. XML's support for multiple character sets allows any
human-readable property to be encoded and read in a character set human-readable property to be encoded and read in a character set
skipping to change at line 488 skipping to change at line 511
containing a property name element applies to the property value containing a property name element applies to the property value
unless it has been overridden by a more locally scoped attribute. unless it has been overridden by a more locally scoped attribute.
A property is always represented in XML with an XML element A property is always represented in XML with an XML element
consisting of the property name. The simplest example is an empty consisting of the property name. The simplest example is an empty
property, which is different from a property that does not exist. property, which is different from a property that does not exist.
<R:title xmlns:R="http://www.example.com/ns/"></R:title> <R:title xmlns:R="http://www.example.com/ns/"></R:title>
The value of a property appears inside the property name element. The value of a property appears inside the property name element.
The value may be any text, including valid XML. When the value is The value may be any kind of well-formed XML content, including both
structured as XML, namespaces that are in scope for that part of the
XML document apply within the property value as well, and MUST be Expires Oct 2003 10
preserved in server storage for retransmission later. Namespace
WebDAV (RFC2518) bis June 2003
text-only and mixed content. When the property value contains
further XML elements, namespaces that are in scope for that part of
the XML document apply within the property value as well, and MUST
be preserved in server storage for retransmission later. Namespace
prefixes need not be preserved due to the rules of prefix prefixes need not be preserved due to the rules of prefix
declaration in XML. declaration in XML.
Attributes on the property name element may convey information about Attributes on the property name element may convey information about
the property, but are not considered part of the value. However, the property, but are not considered part of the value. However,
when language information appears in the 'xml:lang' attribute on the when language information appears in the 'xml:lang' attribute on the
property name element, the language information MUST be preserved in property name element, the language information MUST be preserved in
server storage for retransmission later. server storage for retransmission later.
Expires Aug 2003 10 The XML attribute xml:space MUST NOT be used to change white space
WebDAV (RFC2518) bis March 2003
The XML attribute xml:space MUST not be used to change white space
handling. White space in property values is significant. handling. White space in property values is significant.
4.6 Property Names 4.6 Property Names
A property name is a universally unique identifier that is A property name is a universally unique identifier that is
associated with a schema that provides information about the syntax associated with a schema that provides information about the syntax
and semantics of the property. and semantics of the property.
Because a property's name is universally unique, clients can depend Because a property's name is universally unique, clients can depend
upon consistent behavior for a particular property across multiple upon consistent behavior for a particular property across multiple
skipping to change at line 542 skipping to change at line 568
property namespace. property namespace.
5 Collections of Web Resources 5 Collections of Web Resources
This section provides a description of a new type of Web resource, This section provides a description of a new type of Web resource,
the collection, and discusses its interactions with the HTTP URL the collection, and discusses its interactions with the HTTP URL
namespace. The purpose of a collection resource is to model namespace. The purpose of a collection resource is to model
collection-like objects (e.g., file system directories) within a collection-like objects (e.g., file system directories) within a
server's namespace. server's namespace.
Expires Oct 2003 11
WebDAV (RFC2518) bis June 2003
All DAV compliant resources MUST support the HTTP URL namespace All DAV compliant resources MUST support the HTTP URL namespace
model specified herein. model specified herein.
5.1 HTTP URL Namespace Model 5.1 HTTP URL Namespace Model
The HTTP URL namespace is a hierarchical namespace where the The HTTP URL namespace is a hierarchical namespace where the
hierarchy is delimited with the "/" character. hierarchy is delimited with the "/" character.
An HTTP URL namespace is said to be consistent if it meets the An HTTP URL namespace is said to be consistent if it meets the
following conditions: for every URL in the HTTP hierarchy there following conditions: for every URL in the HTTP hierarchy there
exists a collection that contains that URL as an internal member. exists a collection that contains that URL as an internal member.
The root, or top-level collection of the namespace under The root, or top-level collection of the namespace under
consideration is exempt from the previous rule. consideration is exempt from the previous rule.
Expires Aug 2003 11
WebDAV (RFC2518) bis March 2003
Neither HTTP/1.1 nor WebDAV require that the entire HTTP URL Neither HTTP/1.1 nor WebDAV require that the entire HTTP URL
namespace be consistent. However, certain WebDAV methods are namespace be consistent. However, certain WebDAV methods are
prohibited from producing results that cause namespace prohibited from producing results that cause namespace
inconsistencies. inconsistencies.
Although implicit in [RFC2616] and [RFC2396], any resource, Although implicit in [RFC2616] and [RFC2396], any resource,
including collection resources, MAY be identified by more than one including collection resources, MAY be identified by more than one
URI. For example, a resource could be identified by multiple HTTP URI. For example, a resource could be identified by multiple HTTP
URLs. URLs.
5.2 Collection Resources 5.2 Collection Resources
A collection is a resource whose state consists of at least a list A collection is a resource whose state consists of at least a list
of internal member URIs and a set of properties, but which may have of internal member URLs and a set of properties, but which may have
additional state such as entity bodies returned by GET. An internal additional state such as entity bodies returned by GET. An internal
member URI MUST be immediately relative to a base URI of the member URL MUST be immediately relative to a base URL of the
collection. That is, the internal member URI is equal to a collection. That is, the internal member URL is equal to a
containing collection's URI plus an additional segment for non- containing collection's URL plus an additional segment for non-
collection resources, or additional segment plus trailing slash "/" collection resources, or additional segment plus trailing slash "/"
for collection resources, where segment is defined in section 3.3 of for collection resources, where segment is defined in section 3.3 of
[RFC2396]. [RFC2396].
Any given internal member URI MUST only belong to the collection Any given internal member URL MUST only belong to the collection
once, i.e., it is illegal to have multiple instances of the same URI once, i.e., it is illegal to have multiple instances of the same URL
in a collection. Properties defined on collections behave exactly in a collection. Properties defined on collections behave exactly
as do properties on non-collection resources. as do properties on non-collection resources.
For all WebDAV compliant resources A and B, identified by URIs U and For all WebDAV compliant resources A and B, identified by URLs U and
V, for which U is immediately relative to V, B MUST be a collection V, for which U is immediately relative to V, B MUST be a collection
that has U as an internal member URI. So, if the resource with URL that has U as an internal member URL. So, if the resource with URL
http://example.com/bar/blah is WebDAV compliant and if the resource http://example.com/bar/blah is WebDAV compliant and if the resource
with URL http://example.com/bar/ is WebDAV compliant then the with URL http://example.com/bar/ is WebDAV compliant then the
resource with URL http://example.com/bar/ must be a collection and resource with URL http://example.com/bar/ must be a collection and
must contain URL http://example.com/bar/blah as an internal member. must contain URL http://example.com/bar/blah as an internal member.
Expires Oct 2003 12
WebDAV (RFC2518) bis June 2003
Collection resources MAY list the URLs of non-WebDAV compliant Collection resources MAY list the URLs of non-WebDAV compliant
children in the HTTP URL namespace hierarchy as internal members but children in the HTTP URL namespace hierarchy as internal members but
are not required to do so. For example, if the resource with URL are not required to do so. For example, if the resource with URL
http://example.com/bar/blah is not WebDAV compliant and the URL http://example.com/bar/blah is not WebDAV compliant and the URL
http://example.com/bar/ identifies a collection then URL http://example.com/bar/ identifies a collection then URL
http://example.com/bar/blah may or may not be an internal member of http://example.com/bar/blah may or may not be an internal member of
the collection with URL http://example.com/bar/. the collection with URL http://example.com/bar/.
If a WebDAV compliant resource has no WebDAV compliant children in If a WebDAV compliant resource has no WebDAV compliant children in
the HTTP URL namespace hierarchy then the WebDAV compliant resource the HTTP URL namespace hierarchy then the WebDAV compliant resource
is not required to be a collection. is not required to be a collection.
There is a standing convention that when a collection is referred to There is a standing convention that when a collection is referred to
by its name without a trailing slash, the server MAY handle the by its name without a trailing slash, the server MAY handle the
request as if the trailing slash were present. In this case it request as if the trailing slash were present. In this case it
SHOULD return a Content-Location header in the response, pointing to SHOULD return a Content-Location header in the response, pointing to
the URI ending with the "/". For example, if a client invokes a the URL ending with the "/". For example, if a client invokes a
method on http://example.bar/blah (no trailing slash), the server method on http://example.bar/blah (no trailing slash), the server
may respond as if the operation were invoked on may respond as if the operation were invoked on
Expires Aug 2003 12
WebDAV (RFC2518) bis March 2003
http://example.com/blah/ (trailing slash), and should return a http://example.com/blah/ (trailing slash), and should return a
Content-Location header with the value http://example.bar/blah/. Content-Location header with the value http://example.bar/blah/.
Wherever a server produces a URL referring to a collection, the Wherever a server produces a URL referring to a collection, the
server MUST include the trailing slash. In general clients SHOULD server MUST include the trailing slash. In general clients SHOULD
use the "/" form of collection names. use the "/" form of collection names.
A resource MAY be a collection but not be WebDAV compliant. That A resource MAY be a collection but not be WebDAV compliant. That
is, the resource may comply with all the rules set out in this is, the resource may comply with all the rules set out in this
specification regarding how a collection is to behave without specification regarding how a collection is to behave without
necessarily supporting all methods that a WebDAV compliant resource necessarily supporting all methods that a WebDAV compliant resource
skipping to change at line 642 skipping to change at line 669
contained inside non-WebDAV resources. For example, if a OPTIONS contained inside non-WebDAV resources. For example, if a OPTIONS
response from "http://example.com/servlet/dav/collection" indicates response from "http://example.com/servlet/dav/collection" indicates
WebDAV support, the client cannot assume that WebDAV support, the client cannot assume that
"http://example.com/servlet/dav/" or its parent necessarily are "http://example.com/servlet/dav/" or its parent necessarily are
WebDAV collections. WebDAV collections.
5.3 Source Resources and Output Resources 5.3 Source Resources and Output Resources
For many resources, the entity returned by a GET method exactly For many resources, the entity returned by a GET method exactly
matches the persistent state of the resource, for example, a GIF matches the persistent state of the resource, for example, a GIF
file stored on a disk. For this simple case, the URI at which a file stored on a disk. For this simple case, the URL at which a
resource is accessed is identical to the URI at which the source resource is accessed is identical to the URL at which the source
(the persistent state) of the resource is accessed. This is also (the persistent state) of the resource is accessed. This is also
the case for HTML source files that are not processed by the server the case for HTML source files that are not processed by the server
prior to transmission. prior to transmission.
Expires Oct 2003 13
WebDAV (RFC2518) bis June 2003
However, the server can sometimes process HTML resources before they However, the server can sometimes process HTML resources before they
are transmitted as a return entity body. For example, a server- are transmitted as a return entity body. For example, a server-
side-include directive within an HTML file might instruct a server side-include directive within an HTML file might instruct a server
to replace the directive with another value, such as the current to replace the directive with another value, such as the current
date. In this case, what is returned by GET (HTML plus date) date. In this case, what is returned by GET (HTML plus date)
differs from the persistent state of the resource (HTML plus differs from the persistent state of the resource (HTML plus
directive). Typically there is no way to access the HTML resource directive). Typically there is no way to access the HTML resource
containing the unprocessed directive. containing the unprocessed directive.
Sometimes the entity returned by GET is the output of a data- Sometimes the entity returned by GET is the output of a data-
skipping to change at line 671 skipping to change at line 702
potentially large number of output resources. An example of this is potentially large number of output resources. An example of this is
a CGI script that describes a "finger" gateway process that maps a CGI script that describes a "finger" gateway process that maps
part of the namespace of a server into finger requests, such as part of the namespace of a server into finger requests, such as
http://finger.example.com/finger_gateway/user@host. http://finger.example.com/finger_gateway/user@host.
Although this problem would usefully be solved, interoperable WebDAV Although this problem would usefully be solved, interoperable WebDAV
implementations have been widely deployed without actually solving implementations have been widely deployed without actually solving
this problem. Thus, the source vs. output problem is not solved in this problem. Thus, the source vs. output problem is not solved in
this specification, and has been deferred to a separate document. this specification, and has been deferred to a separate document.
Expires Aug 2003 13
WebDAV (RFC2518) bis March 2003
6 Locking 6 Locking
The ability to lock a resource provides a mechanism for serializing The ability to lock a resource provides a mechanism for serializing
access to that resource. Using a lock, an authoring client can access to that resource. Using a lock, an authoring client can
provide a reasonable guarantee that another principal will not provide a reasonable guarantee that another principal will not
modify a resource while it is being edited. In this way, a client modify a resource while it is being edited. In this way, a client
can prevent the "lost update" problem. can prevent the "lost update" problem.
This specification allows locks to vary over two client-specified This specification allows locks to vary over two client-specified
parameters, the number of principals involved (exclusive vs. shared) parameters, the number of principals involved (exclusive vs. shared)
and the type of access to be granted. This document defines locking and the type of access to be granted. This document defines locking
for only one access type, write. However, the syntax is extensible, for only one access type, write. However, the syntax is extensible,
and permits the eventual specification of locking for other access and permits the eventual specification of locking for other access
types. types.
6.1 Exclusive Vs. Shared Locks 6.1 Exclusive Vs. Shared Locks
The most basic form of lock is an exclusive lock. This is a lock The most basic form of lock is an exclusive lock. Only one
where the access right in question is only granted to a single exclusive lock may exist on any resource, whether it is directly or
principal. The need for this arbitration results from a desire to indirectly locked (see 7.5). Exclusive locks avoid having to merge
avoid having to merge results. results, without requiring any coordination other than the methods
described in this specification.
However, there are times when the goal of a lock is not to exclude However, there are times when the goal of a lock is not to exclude
others from exercising an access right but rather to provide a others from exercising an access right but rather to provide a
mechanism for principals to indicate that they intend to exercise mechanism for principals to indicate that they intend to exercise
their access rights. Shared locks are provided for this case. A their access rights. Shared locks are provided for this case. A
Expires Oct 2003 14
WebDAV (RFC2518) bis June 2003
shared lock allows multiple principals to receive a lock. Hence any shared lock allows multiple principals to receive a lock. Hence any
principal with appropriate access can get the lock. principal with appropriate access can get the lock.
With shared locks there are two trust sets that affect a resource. With shared locks there are two trust sets that affect a resource.
The first trust set is created by access permissions. Principals The first trust set is created by access permissions. Principals
who are trusted, for example, may have permission to write to the who are trusted, for example, may have permission to write to the
resource. Among those who have access permission to write to the resource. Among those who have access permission to write to the
resource, the set of principals who have taken out a shared lock resource, the set of principals who have taken out a shared lock
also must trust each other, creating a (typically) smaller trust set also must trust each other, creating a (typically) smaller trust set
within the access permission write set. within the access permission write set.
skipping to change at line 726 skipping to change at line 760
decide they trust their collaborators will not overwrite their work decide they trust their collaborators will not overwrite their work
(the potential set of collaborators being the set of principals who (the potential set of collaborators being the set of principals who
have write permission) and use a shared lock, which informs their have write permission) and use a shared lock, which informs their
collaborators that a principal may be working on the resource. collaborators that a principal may be working on the resource.
The WebDAV extensions to HTTP do not need to provide all of the The WebDAV extensions to HTTP do not need to provide all of the
communications paths necessary for principals to coordinate their communications paths necessary for principals to coordinate their
activities. When using shared locks, principals may use any out of activities. When using shared locks, principals may use any out of
band communication channel to coordinate their work (e.g., face-to- band communication channel to coordinate their work (e.g., face-to-
face interaction, written notes, post-it notes on the screen, face interaction, written notes, post-it notes on the screen,
Expires Aug 2003 14
WebDAV (RFC2518) bis March 2003
telephone conversation, Email, etc.) The intent of a shared lock is telephone conversation, Email, etc.) The intent of a shared lock is
to let collaborators know who else may be working on a resource. to let collaborators know who else may be working on a resource.
Shared locks are included because experience from web distributed Shared locks are included because experience from web distributed
authoring systems has indicated that exclusive locks are often too authoring systems has indicated that exclusive locks are often too
rigid. An exclusive lock is used to enforce a particular editing rigid. An exclusive lock is used to enforce a particular editing
process: take out an exclusive lock, read the resource, perform process: take out an exclusive lock, read the resource, perform
edits, write the resource, release the lock. This editing process edits, write the resource, release the lock. This editing process
has the problem that locks are not always properly released, for has the problem that locks are not always properly released, for
example when a program crashes, or when a lock owner leaves without example when a program crashes, or when a lock owner leaves without
unlocking a resource. While both timeouts and administrative action unlocking a resource. While both timeouts and administrative action
can be used to remove an offending lock, neither mechanism may be can be used to remove an offending lock, neither mechanism may be
available when needed; the timeout may be long or the administrator available when needed; the timeout may be long or the administrator
may not be available. may not be available.
6.2 Required Support 6.2 Required Support
A WebDAV compliant server is not required to support locking in any A WebDAV compliant resource is not required to support locking in
form. If the server does support locking it may choose to support any form. If the resource does support locking it may choose to
any combination of exclusive and shared locks for any access types. support any combination of exclusive and shared locks for any access
types.
The reason for this flexibility is that locking policy strikes to The reason for this flexibility is that locking policy strikes to
the very heart of the resource management and versioning systems the very heart of the resource management and versioning systems
employed by various storage repositories. These repositories employed by various storage repositories. These repositories
Expires Oct 2003 15
WebDAV (RFC2518) bis June 2003
require control over what sort of locking will be made available. require control over what sort of locking will be made available.
For example, some repositories only support shared write locks while For example, some repositories only support shared write locks while
others only provide support for exclusive write locks while yet others only provide support for exclusive write locks while yet
others use no locking at all. As each system is sufficiently others use no locking at all. As each system is sufficiently
different to merit exclusion of certain locking features, this different to merit exclusion of certain locking features, this
specification leaves locking as the sole axis of negotiation within specification leaves locking as the sole axis of negotiation within
WebDAV. WebDAV.
6.3 Lock Tokens 6.3 Lock Tokens
A lock token is a type of state token, represented as a URI, which A lock token is a type of state token, represented as a URI, which
identifies a particular lock. A lock token is returned by every identifies a particular lock. A lock token is returned in the Lock-
successful LOCK operation in the lockdiscovery property in the Token header in the response to a successful LOCK operation. The
response body, and can also be found through lock discovery on a lock token also appears in the value of the lockdiscovery property,
resource. Each lock has only one unique lock token. the value of which is returned in the body of the response to a
successful LOCK operation (this property also includes the tokens of
other current locks on the resource). Finally, the lockdiscovery
property can be queried using PROPFIND and the token can be
discovered that way. Each lock has only one unique lock token.
Lock token URIs MUST be unique across all resources for all time. Lock token URIs MUST be unique across all resources for all time.
This uniqueness constraint allows lock tokens to be submitted across This uniqueness constraint allows lock tokens to be submitted across
resources and servers without fear of confusion. resources and servers without fear of confusion.
This specification provides a lock token URI scheme called This specification provides a lock token URI scheme called
opaquelocktoken that meets the uniqueness requirements. However opaquelocktoken that meets the uniqueness requirements. However
resources are free to return any URI scheme so long as it meets the resources are free to return any URI scheme so long as it meets the
uniqueness requirements. uniqueness requirements.
Having a lock token provides no special access rights. Anyone can Having a lock token provides no special access rights. Anyone can
find out anyone else's lock token by performing lock discovery. find out anyone else's lock token by performing lock discovery.
Locks MUST be enforced based upon whatever authentication mechanism Locks MUST be enforced based upon whatever authentication mechanism
is used by the server, not based on the secrecy of the token values. is used by the server, not based on the secrecy of the token values.
Expires Aug 2003 15
WebDAV (RFC2518) bis March 2003
6.4 opaquelocktoken Lock Token URI Scheme 6.4 opaquelocktoken Lock Token URI Scheme
The opaquelocktoken URI scheme is designed to be unique across all The opaquelocktoken URI scheme is designed to be unique across all
resources for all time. Due to this uniqueness quality, a client resources for all time. Due to this uniqueness quality, a client
may submit an opaque lock token in an If header on a resource other may submit an opaque lock token in an If header on a resource other
than the one that returned it. than the one that returned it.
All resources MUST recognize the opaquelocktoken scheme and, at
minimum, recognize that the lock token does not refer to an
outstanding lock on the resource.
In order to guarantee uniqueness across all resources for all time In order to guarantee uniqueness across all resources for all time
the opaquelocktoken requires the use of the Universal Unique the opaquelocktoken requires the use of the Universal Unique
Identifier (UUID) mechanism, as described in [ISO-11578]. Identifier (UUID) mechanism, as described in [ISO-11578].
Opaquelocktoken generators, however, have a choice of how they Opaquelocktoken generators, however, have a choice of how they
create these tokens. They can either generate a new UUID for every create these tokens. They can either generate a new UUID for every
lock token they create or they can create a single UUID and then lock token they create or they can create a single UUID and then
add extension characters. If the second method is selected then the add extension characters. If the second method is selected then the
program generating the extensions MUST guarantee that the same program generating the extensions MUST guarantee that the same
extension will never be used twice with the associated UUID. extension will never be used twice with the associated UUID.
Expires Oct 2003 16
WebDAV (RFC2518) bis June 2003
OpaqueLockToken-URI = "opaquelocktoken:" UUID [Extension] ; The OpaqueLockToken-URI = "opaquelocktoken:" UUID [Extension] ; The
UUID production is the string representation of a UUID, as defined UUID production is the string representation of a UUID, as defined
in [ISO-11578]. Note that white space (LWS) is not allowed between in [ISO-11578]. Note that white space (LWS) is not allowed between
elements of this production. elements of this production.
Extension = path ; path is defined in section 3.2.1 of [RFC2616] Extension = path ; path is defined in section 3.2.1 of [RFC2616]
6.5 Lock Capability Discovery 6.5 Lock Capability Discovery
Since server lock support is optional, a client trying to lock a Since server lock support is optional, a client trying to lock a
skipping to change at line 840 skipping to change at line 877
6.6 Active Lock Discovery 6.6 Active Lock Discovery
If another principal locks a resource that a principal wishes to If another principal locks a resource that a principal wishes to
access, it is useful for the second principal to be able to find out access, it is useful for the second principal to be able to find out
who the first principal is. For this purpose the lockdiscovery who the first principal is. For this purpose the lockdiscovery
property is provided. This property lists all outstanding locks, property is provided. This property lists all outstanding locks,
describes their type, and where available, provides their lock describes their type, and where available, provides their lock
token. token.
Expires Aug 2003 16
WebDAV (RFC2518) bis March 2003
Any DAV compliant resource that supports the LOCK method MUST Any DAV compliant resource that supports the LOCK method MUST
support the lockdiscovery property. support the lockdiscovery property.
6.7 Usage Considerations 6.7 Usage Considerations
Although the locking mechanisms specified here provide some help in Although the locking mechanisms specified here provide some help in
preventing lost updates, they cannot guarantee that updates will preventing lost updates, they cannot guarantee that updates will
never be lost. Consider the following scenario: never be lost. Consider the following scenario:
Two clients A and B are interested in editing the resource Two clients A and B are interested in editing the resource
'index.html'. Client A is an HTTP client rather than a WebDAV 'index.html'. Client A is an HTTP client rather than a WebDAV
client, and so does not know how to perform locking. client, and so does not know how to perform locking.
Client A doesn't lock the document, but does a GET and begins Client A doesn't lock the document, but does a GET and begins
editing. editing.
Client B does LOCK, performs a GET and begins editing. Client B does LOCK, performs a GET and begins editing.
Client B finishes editing, performs a PUT, then an UNLOCK. Client B finishes editing, performs a PUT, then an UNLOCK.
Client A performs a PUT, overwriting and losing all of B's changes. Client A performs a PUT, overwriting and losing all of B's changes.
WebDAV (RFC2518) bis June 2003
There are several reasons why the WebDAV protocol itself cannot There are several reasons why the WebDAV protocol itself cannot
prevent this situation. First, it cannot force all clients to use prevent this situation. First, it cannot force all clients to use
locking because it must be compatible with HTTP clients that do not locking because it must be compatible with HTTP clients that do not
comprehend locking. Second, it cannot require servers to support comprehend locking. Second, it cannot require servers to support
locking because of the variety of repository implementations, some locking because of the variety of repository implementations, some
of which rely on reservations and merging rather than on locking. of which rely on reservations and merging rather than on locking.
Finally, being stateless, it cannot enforce a sequence of operations Finally, being stateless, it cannot enforce a sequence of operations
like LOCK / GET / PUT / UNLOCK. like LOCK / GET / PUT / UNLOCK.
WebDAV servers that support locking can reduce the likelihood that WebDAV servers that support locking can reduce the likelihood that
skipping to change at line 895 skipping to change at line 931
Information managers may attempt to prevent overwrites by Information managers may attempt to prevent overwrites by
implementing client-side procedures requiring locking before implementing client-side procedures requiring locking before
modifying WebDAV resources. modifying WebDAV resources.
7 Write Lock 7 Write Lock
This section describes the semantics specific to the write lock This section describes the semantics specific to the write lock
type. The write lock is a specific instance of a lock type, and is type. The write lock is a specific instance of a lock type, and is
the only lock type described in this specification. the only lock type described in this specification.
Expires Aug 2003 17 Write locks prevent unauthorized changes to resources. In general
WebDAV (RFC2518) bis March 2003 terms, changes affected by write locks include changes to:
- the content of the resource
- any dead property of the resource
- any live property defined to be lockable (all properties defined
in this specification are lockable)
- the direct membership of the resource, if it is a collection
- the URL/location of a resource
The next few sections describe in more specific terms how write
locks interact with various operations.
7.1 Methods Restricted by Write Locks 7.1 Methods Restricted by Write Locks
A write lock MUST prevent a principal without the lock from A write lock MUST prevent a principal without the lock from
successfully executing a PUT, POST, PROPPATCH, LOCK, UNLOCK, MOVE, successfully executing a PUT, POST, PROPPATCH, LOCK, UNLOCK, MOVE,
Expires Oct 2003 18
WebDAV (RFC2518) bis June 2003
DELETE, or MKCOL on the locked resource. All other current methods, DELETE, or MKCOL on the locked resource. All other current methods,
GET in particular, function independently of the lock. GET in particular, function independently of the lock.
Note, however, that as new methods are created it will be necessary Note, however, that as new methods are created it will be necessary
to specify how they interact with a write lock. to specify how they interact with a write lock.
7.2 Write Locks and Lock Tokens 7.2 Write Locks and Lock Tokens
A successful request for an exclusive or shared write lock MUST A successful request for an exclusive or shared write lock MUST
result in the generation of a unique lock token associated with the result in the generation of a unique lock token associated with the
skipping to change at line 943 skipping to change at line 993
MKCOL can only be used to create a collection, not to overwrite an MKCOL can only be used to create a collection, not to overwrite an
existing collection. In order to immediately lock a collection upon existing collection. In order to immediately lock a collection upon
creation, clients may attempt to pipeline the MKCOL and LOCK creation, clients may attempt to pipeline the MKCOL and LOCK
requests together. requests together.
A lock request to an unmapped URL should result in the creation of a A lock request to an unmapped URL should result in the creation of a
resource that is locked. A subsequent PUT request with the correct resource that is locked. A subsequent PUT request with the correct
lock token should normally succeed, and provides the content, lock token should normally succeed, and provides the content,
content-type, content-language and other information as appropriate. content-type, content-language and other information as appropriate.
In this situation, WebDAV servers compliant with RFC2518 MAY create In this situation, a WebDAV server that was implemented from RFC2518
"lock-null" resources which are special and unusual resources. A MAY create "lock-null" resources which are special and unusual
lock-null resource: resources. Historically, a lock-null resource:
- Responds with a 404 or 405 to any DAV method except for PUT, - Responds with a 404 or 405 to any DAV method except for PUT,
MKCOL, OPTIONS, PROPFIND, LOCK, UNLOCK. MKCOL, OPTIONS, PROPFIND, LOCK, UNLOCK.
- Appears as a member of its parent collection. - Appears as a member of its parent collection.
Expires Aug 2003 18
WebDAV (RFC2518) bis March 2003
- Disappears (becomes once more an unmapped URL) if its lock goes - Disappears (becomes once more an unmapped URL) if its lock goes
away before it is converted to a regular resource. (This must away before it is converted to a regular resource. (This must
Expires Oct 2003 19
WebDAV (RFC2518) bis June 2003
also happen if it is renamed or moved, or if any parent collection also happen if it is renamed or moved, or if any parent collection
is renamed or moved, because locks are tied to URLs). is renamed or moved, because locks are tied to URLs).
- May be turned into a regular resource when a PUT request to the - May be turned into a regular resource when a PUT request to the
URL is successful. Ceases to be a lock-null resource. URL is successful. Ceases to be a lock-null resource.
- May be turned into a collection when a MKCOL request to the URL - May be turned into a collection when a MKCOL request to the URL
is successful. Ceases to be a lock-null resource is successful. Ceases to be a lock-null resource
- Has defined values for lockdiscovery and supportedlock - Has defined values for lockdiscovery and supportedlock
properties. properties.
However, interoperability and compliance problems have been found However, interoperability and compliance problems have been found
with lock-null resources. Therefore, they are deprecated. WebDAV with lock-null resources. Therefore, they are deprecated. WebDAV
servers compliant with this document SHOULD create regular locked servers SHOULD create regular locked empty resources, which are and
empty resources, which behave in every way as if they were a normal behave in every way as normal resources. A locked empty resource:
resource. A locked empty resource:
- Can be downloaded, deleted, moved, copied, and in all ways behave - Can be read, deleted, moved, copied, and in all ways behave as a
as a regular resource, not a lock-null resource. regular resource, not a lock-null resource.
- Appears as a member of its parent collection. - Appears as a member of its parent collection.
- SHOULD NOT disappear when its lock goes away (clients must - SHOULD NOT disappear when its lock goes away (clients must
therefore be responsible for cleaning up their own mess, as with therefore be responsible for cleaning up their own mess, as with
any other operation) any other operation)
- SHOULD default to a content-type of "application/octet-stream". - SHOULD default to having no content type.
- MAY NOT have values for properties like getcontentlanguage which - MAY NOT have values for properties like getcontentlanguage which
havenĂt been specified yet by the client. havenĂt been specified yet by the client.
- May have content added with a PUT request. MUST be able to - May have content added with a PUT request. MUST be able to
change content type. change content type.
- MUST NOT be turned into a collection. A MKCOL request must fail - MUST NOT be turned into a collection. A MKCOL request must fail
as it would to any existing resource. as it would to any existing resource.
- MUST have defined values for lockdiscovery and supportedlock - MUST have defined values for lockdiscovery and supportedlock
properties. properties.
- The response MUST indicate that a resource was created, by use of - The response MUST indicate that a resource was created, by use of
the "201 Created" response code (a LOCK request to an existing the "201 Created" response code (a LOCK request to an existing
resource instead will result in 200 OK). The body must still resource instead will result in 200 OK). The body must still
include the lockdiscovery property, as with a LOCK request to an include the lockdiscovery property, as with a LOCK request to an
existing resource. existing resource.
Clients can easily interoperate with either kind of server (both The client is expected to update the locked empty resource shortly
exist) by only attempting PUT after a LOCK to an unmapped URL, not after locking it, using PUT and possibly PROPPATCH. When the client
MKCOL or GET. uses PUT to overwrite a locked empty resource the client MUST supply
a Content-Type if any is known. If the client supplies a Content-
Type value the server MUST set that value (this requirement actually
applies to any resource that is overwritten but is particularly
necessary for locked empty resources which are initially created
with no Content-Type.
Clients can easily interoperate both with servers that support the
deprecated lock-null resources and servers that support simpler
Expires Oct 2003 20
WebDAV (RFC2518) bis June 2003
locked empty resources by only attempting PUT after a LOCK to an
unmapped URL, not MKCOL or GET.
7.5 Write Locks and Collections 7.5 Write Locks and Collections
A write lock on a collection, whether created by a "Depth: 0" or A write lock on a collection, whether created by a "Depth: 0" or
"Depth: infinity" lock request, prevents the addition or removal of "Depth: infinity" lock request, prevents the addition or removal of
member URIs of the collection by non-lock owners. As a consequence, member URLs of the collection by non-lock owners.
when a principal issues a PUT or POST request to create a new
resource under a URI which needs to be an internal member of a write
locked collection to maintain HTTP namespace consistency, or issues
Expires Aug 2003 19 A zero-depth lock on a collection affects changes to the direct
WebDAV (RFC2518) bis March 2003 membership of that collection. When a principal issues a PUT or
POST request to create a new resource in a write locked collection,
or issues a DELETE to remove a resource which has a URL which is an
existing internal member URL of a write locked collection, this
request MUST fail if the principal does not provide the correct lock
token for the locked collection.
a DELETE to remove a resource which has a URI which is an existing In addition, a depth-infinity lock affects all write operations to
internal member URI of a write locked collection, this request MUST all descendents of the locked collection. With a depth-infinity
fail if the principal does not have a write lock on the collection. lock, the root of the lock is directly locked, and all its
descendants are indirectly locked.
- Any new resource added as a descendent of a depth-infinity locked
collection becomes indirectly locked.
- Any indirectly locked resource moved out of the locked collection
into an unlocked collection is thereafter unlocked.
- Any indirectly locked resource moved out of a locked source
collection into a depth-infinity locked target collection remains
indirectly locked but is now within the scope of the lock on the
target collection (the target collection's lock token will
thereafter be required to make further changes).
However, if a depth-infinity write lock request is issued to a If a depth-infinity write LOCK request is issued to a collection
collection containing member URIs identifying resources that are containing member URLs identifying resources that are currently
currently locked in a manner which conflicts with the write lock, locked in a manner which conflicts with the write lock, the request
the request MUST fail with a 423 (Locked) status code. MUST fail with a 423 (Locked) status code.
If a lock owner causes the URI of a resource to be added as an If a lock owner causes the URL of a resource to be added as an
internal member URI of a depth-infinity locked collection then the internal member URL of a depth-infinity locked collection then the
new resource MUST be automatically added to the lock. This is the new resource MUST be automatically added to the lock. This is the
only mechanism that allows a resource to be added to a write lock. only mechanism that allows a resource to be added to a write lock.
Thus, for example, if the collection /a/b/ is write locked and the Thus, for example, if the collection /a/b/ is write locked and the
resource /c is moved to /a/b/c then resource /a/b/c will be added to resource /c is moved to /a/b/c then resource /a/b/c will be added to
the write lock. the write lock.
7.6 Write Locks and the If Request Header 7.6 Write Locks and the If Request Header
If a user agent is not required to have knowledge about a lock when If a user agent is not required to have knowledge about a lock when
requesting an operation on a locked resource, the following scenario requesting an operation on a locked resource, the following scenario
might occur. Program A, run by User A, takes out a write lock on a might occur. Program A, run by User A, takes out a write lock on a
resource. Program B, also run by User A, has no knowledge of the resource. Program B, also run by User A, has no knowledge of the
lock taken out by Program A, yet performs a PUT to the locked lock taken out by Program A, yet performs a PUT to the locked
Expires Oct 2003 21
WebDAV (RFC2518) bis June 2003
resource. In this scenario, the PUT succeeds because locks are resource. In this scenario, the PUT succeeds because locks are
associated with a principal, not a program, and thus program B, associated with a principal, not a program, and thus program B,
because it is acting with principal AĂs credential, is allowed to because it is acting with principal AĂs credential, is allowed to
perform the PUT. However, had program B known about the lock, it perform the PUT. However, had program B known about the lock, it
would not have overwritten the resource, preferring instead to would not have overwritten the resource, preferring instead to
present a dialog box describing the conflict to the user. Due to present a dialog box describing the conflict to the user. Due to
this scenario, a mechanism is needed to prevent different programs this scenario, a mechanism is needed to prevent different programs
from accidentally ignoring locks taken out by other programs with from accidentally ignoring locks taken out by other programs with
the same authorization. the same authorization.
In order to prevent these collisions a lock token MUST be submitted In order to prevent these collisions a lock token MUST be submitted
by an authorized principal in the If header for all locked resources by an authorized principal for all locked resources that a method
that a method may interact with or the method MUST fail. For may change or the method MUST fail. A lock token is submitted when
example, if a resource is to be moved and both the source and it appears in an If header. For example, if a resource is to be
destination are locked then two lock tokens must be submitted, one moved and both the source and destination are locked then two lock
for the source and the other for the destination. tokens must be submitted in the if header, one for the source and
the other for the destination.
Example - Write Lock Example - Write Lock
>>Request >>Request
COPY /~fielding/index.html HTTP/1.1 COPY /~fielding/index.html HTTP/1.1
Host: www.ics.uci.edu Host: www.ics.uci.edu
Destination: http://www.ics.uci.edu/users/f/fielding/index.html Destination: http://www.ics.uci.edu/users/f/fielding/index.html
If: <http://www.ics.uci.edu/users/f/fielding/index.html> If: <http://www.ics.uci.edu/users/f/fielding/index.html>
(<opaquelocktoken:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>) (<opaquelocktoken:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>)
>>Response >>Response
Expires Aug 2003 20
WebDAV (RFC2518) bis March 2003
HTTP/1.1 204 No Content HTTP/1.1 204 No Content
In this example, even though both the source and destination are In this example, even though both the source and destination are
locked, only one lock token must be submitted, for the lock on the locked, only one lock token must be submitted, for the lock on the
destination. This is because the source resource is not modified by destination. This is because the source resource is not modified by
a COPY, and hence unaffected by the write lock. In this example, a COPY, and hence unaffected by the write lock. In this example,
user agent authentication has previously occurred via a mechanism user agent authentication has previously occurred via a mechanism
outside the scope of the HTTP protocol, in the underlying transport outside the scope of the HTTP protocol, in the underlying transport
layer. layer.
7.7 Write Locks and COPY/MOVE 7.7 Write Locks and COPY/MOVE
A COPY method invocation MUST NOT duplicate any write locks active A COPY method invocation MUST NOT duplicate any write locks active
on the source. However, as previously noted, if the COPY copies the on the source. However, as previously noted, if the COPY copies the
resource into a collection that is locked with "Depth: infinity", resource into a collection that is locked with "Depth: infinity",
then the resource will be added to the lock. then the resource will be added to the lock.
Expires Oct 2003 22
WebDAV (RFC2518) bis June 2003
A successful MOVE request on a write locked resource MUST NOT move A successful MOVE request on a write locked resource MUST NOT move
the write lock with the resource. However, the resource is subject the write lock with the resource. However, the resource is subject
to being added to an existing lock at the destination, as specified to being added to an existing lock at the destination, as specified
in section 7.5. For example, if the MOVE makes the resource a child in section 7.5. For example, if the MOVE makes the resource a child
of a collection that is locked with "Depth: infinity", then the of a collection that is locked with "Depth: infinity", then the
resource will be added to that collection's lock. Additionally, if a resource will be added to that collection's lock. Additionally, if a
resource locked with "Depth: infinity" is moved to a destination resource locked with "Depth: infinity" is moved to a destination
that is within the scope of the same lock (e.g., within the that is within the scope of the same lock (e.g., within the
namespace tree covered by the lock), the moved resource will again namespace tree covered by the lock), the moved resource will again
be a added to the lock. In both these examples, as specified in be a added to the lock. In both these examples, as specified in
skipping to change at line 1114 skipping to change at line 1198
MUST be re-set. MUST be re-set.
A server may return a Timeout header with a lock refresh that is A server may return a Timeout header with a lock refresh that is
different than the Timeout header returned when the lock was different than the Timeout header returned when the lock was
originally requested. Additionally clients may submit Timeout originally requested. Additionally clients may submit Timeout
headers of arbitrary value with their lock refresh requests. headers of arbitrary value with their lock refresh requests.
Servers, as always, may ignore Timeout headers submitted by the Servers, as always, may ignore Timeout headers submitted by the
client. Note that timeout is measured in seconds remaining until client. Note that timeout is measured in seconds remaining until
expiration. expiration.
Expires Aug 2003 21
WebDAV (RFC2518) bis March 2003
If an error is received in response to a refresh LOCK request the If an error is received in response to a refresh LOCK request the
client SHOULD assume that the lock was not refreshed. client MUST NOT assume that the lock was refreshed.
8 HTTP Methods for Distributed Authoring 8 HTTP Methods for Distributed Authoring
8.1 General request and response handling 8.1 General request and response handling
8.1.1 Use of XML 8.1.1 Use of XML
Some of the following new HTTP methods use XML as a request and Some of the following new HTTP methods use XML as a request and
response format. All DAV compliant clients and resources MUST use response format. All DAV compliant clients and resources MUST use
XML parsers that are compliant with [REC-XML]. All XML used in XML parsers that are compliant with [REC-XML] and [REC-XMLNS]. All
either requests or responses MUST be, at minimum, well formed. If a XML used in either requests or responses MUST be, at minimum, well
server receives ill-formed XML in a request it MUST reject the formed and use namespaces correctly. If a server receives ill-
entire request with a 400 (Bad Request). If a client receives ill- formed XML in a request it MUST reject the entire request with a 400
formed XML in a response then it MUST NOT assume anything about the (Bad Request). If a client receives ill-formed XML in a response
outcome of the executed method and SHOULD treat the server as then it MUST NOT assume anything about the outcome of the executed
malfunctioning. method and SHOULD treat the server as malfunctioning.
Expires Oct 2003 23
WebDAV (RFC2518) bis June 2003
8.1.2 Required Bodies in Requests 8.1.2 Required Bodies in Requests
Some of these new methods do not define bodies. Servers MUST Some of these new methods do not define bodies. Servers MUST
examine all requests for a body, even when a body was not expected. examine all requests for a body, even when a body was not expected.
In cases where a request body is present but would be ignored by a In cases where a request body is present but would be ignored by a
server, the server MUST reject the request with 415 (Unsupported server, the server MUST reject the request with 415 (Unsupported
Media Type). This informs the client (which may have been Media Type). This informs the client (which may have been
attempting to use an extension) that the body could not be processed attempting to use an extension) that the body could not be processed
as they intended. as they intended.
8.1.3 Use of Location header in responses 8.1.3 Use of Location header in responses
When the Location header is used in a response, it is used by the When the Location header is used in a response, it is used by the
server to indicate the preferred address for the target resource of server to indicate the preferred address for the target resource of
the request. Whenever the server has a preferred address, it should the request. Whenever the server has a preferred address, it should
use that address consistently. This means that when a response use that address consistently. This means that when a response
contains a Location header, all the URLs in the response body (e.g. contains a Location header, all the URLs in the response body (e.g.
a Multi-Status) should be consistent. a Multi-Status) should be consistent (most importantly, should use
the same host and port).
8.1.4 Required Response Headers: Date 8.1.4 Required Response Headers: Date
Note that HTTP 1.1 requires the Date header in all responses. Note that HTTP 1.1 requires the Date header in all responses if
possible.
8.1.5 ETag 8.1.5 ETag
HTTP 1.1 suggests the use of the ETag header in responses to GET and HTTP 1.1 suggests the use of the ETag header in responses to GET and
PUT requests. Correct use of ETags is even more important in a PUT requests. Correct use of ETags is even more important in a
distributed authoring environment, because ETags are necessary along distributed authoring environment, because ETags are necessary along
with locks to avoid the lost-update problem. A client might fail to with locks to avoid the lost-update problem. A client might fail to
renew a lock, for example when the lock times out and the client is renew a lock, for example when the lock times out and the client is
accidentally offline or in the middle of a long upload. When a accidentally offline or in the middle of a long upload. When a
client fails to renew the lock, it's quite possible the resource can client fails to renew the lock, it's quite possible the resource can
still be relocked and the user can go on editing, as long as no still be relocked and the user can go on editing, as long as no
changes were made in the meantime. ETags are required for the client changes were made in the meantime. ETags are required for the client
to be able to distinguish this case. Otherwise, the client is forced to be able to distinguish this case. Otherwise, the client is forced
Expires Aug 2003 22
WebDAV (RFC2518) bis March 2003
to ask the user whether to overwrite the resource on the server to ask the user whether to overwrite the resource on the server
without even being able to tell the user whether it has changed. without even being able to tell the user whether it has changed.
Timestamps do not solve this problem nearly as well as ETags. Timestamps do not solve this problem nearly as well as ETags.
WebDAV servers SHOULD support strong ETags for all resources that WebDAV servers SHOULD support strong ETags for all resources that
may be PUT. If ETags are supported for a resource, the server MUST may be PUT. If ETags are supported for a resource, the server MUST
return the ETag header in all PUT and GET responses to that return the ETag header in all PUT and GET responses to that
resource, as well as provide the same value for the 'getetag' resource, as well as provide the same value for the 'getetag'
property. property.
Because clients may be forced to prompt users or throw away changed Because clients may be forced to prompt users or throw away changed
content if the ETag changes, a WebDAV server MUST not change the content if the ETag changes, a WebDAV server MUST not change the
ETag (or getlastmodified value) for a resource when only its ETag (or getlastmodified value) for a resource when only its
Expires Oct 2003 24
WebDAV (RFC2518) bis June 2003
property values change. The ETag represents the state of the body or property values change. The ETag represents the state of the body or
contents of the resource. There is no similar way to tell if contents of the resource. There is no similar way to tell if
properties have changed. properties have changed.
8.1.6 Including error response bodies 8.1.6 Including error response bodies
HTTP and WebDAV did not use the bodies of most error responses until HTTP and WebDAV did not use the bodies of most error responses for
DeltaV introduced a mechanism to include more specific information machine-parsable information until DeltaV introduced a mechanism to
in the body of an error response (section 1.6 of [RFC3253]). The include more specific information in the body of an error response
mechanism is appropriate to use with any error response that may (section 1.6 of [RFC3253]). The mechanism is appropriate to use with
take a body but does not already have a body defined. The mechanism any error response that may take a body but does not already have a
is particularly appropriate when a status code can mean many things body defined. The mechanism is particularly appropriate when a
(for example, 400 Bad Request can mean required headers are missing, status code can mean many things (for example, 400 Bad Request can
headers are incorrectly formatted, or much more). mean required headers are missing, headers are incorrectly
formatted, or much more).
This mechanism does not take the place of using a correct numeric This mechanism does not take the place of using a correct numeric
error code as defined here or in HTTP, because the client MUST error code as defined here or in HTTP, because the client MUST
always be able to take a reasonable course of action based only on always be able to take a reasonable course of action based only on
the numeric error. However, it does remove the need to define new the numeric error. However, it does remove the need to define new
numeric error codes, avoiding the confusion of who is allowed to numeric error codes, avoiding the confusion of who is allowed to
define such new codes. The codes used in this mechanism are XML define such new codes. The codes used in this mechanism are XML
elements in a namespace, so naturally any group defining a new error elements in a namespace, so naturally any group defining a new error
code can use their own namespace. As always, the "DAV:" namespace is code can use their own namespace. As always, the "DAV:" namespace is
reserved for use by IETF-chartered WebDAV working groups. reserved for use by IETF-chartered WebDAV working groups.
A server supporting "bis" SHOULD include a specific XML error code A server supporting "bis" SHOULD include a specific XML error code
in a "DAV:error" response body element, when a specific XML error in a "DAV:error" response body element, when a specific XML error
code is defined in this document. For error conditions not specified code is defined in this document. The ˘DAV:error÷ element may
in this document, the server MAY simply choose an appropriate contain multiple elements describing specific errors. For error
numeric status and leave the response body blank. conditions not specified in this document, the server MAY simply
choose an appropriate numeric status and leave the response body
blank.
HTTP/1.1 403 Conflict HTTP/1.1 403 Conflict
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:error xmlns:D="DAV:"> <D:error xmlns:D="DAV:">
<D:forbid-external-entities/> <D:forbid-external-entities/>
</D:error> </D:error>
Expires Aug 2003 23
WebDAV (RFC2518) bis March 2003
In this specification, both the numeric and the XML error code are In this specification, both the numeric and the XML error code are
defined for some failure situations, in which case the XML error defined for some failure situations, in which case the XML error
code must have the "DAV:" namespace, appear in the "error" root code must have the "DAV:" namespace, appear in the "error" root
element, and be returned in a body with the numeric error code element, and be returned in a body with the numeric error code
specified. specified.
Status codes are specified in this document with the convention of Status codes are specified in this document with the convention of
following the numeric error code with the XML error code. E.g. following the numeric error code with the XML error code. E.g.
Expires Oct 2003 25
WebDAV (RFC2518) bis June 2003
403/DAV:forbid-external-entities - response codes when the server 403/DAV:forbid-external-entities - response codes when the server
refuses to accept external XML entities in XML request bodies. refuses to accept external XML entities in XML request bodies.
8.2 PROPFIND 8.2 PROPFIND
The PROPFIND method retrieves properties defined on the resource The PROPFIND method retrieves properties defined on the resource
identified by the Request-URI, if the resource does not have any identified by the Request-URI, if the resource does not have any
internal members, or on the resource identified by the Request-URI internal members, or on the resource identified by the Request-URI
and potentially its member resources, if the resource is a and potentially its member resources, if the resource is a
collection that has internal member URIs. All DAV compliant collection that has internal member URLs. All DAV compliant
resources MUST support the PROPFIND method and the propfind XML resources MUST support the PROPFIND method and the propfind XML
element (section 13.25) along with all XML elements defined for use element (section 13.25) along with all XML elements defined for use
with that element. with that element.
A client may submit a Depth header with a value of "0", "1", or A client may submit a Depth header with a value of "0", "1", or
"infinity" with a PROPFIND on a collection resource with internal "infinity" with a PROPFIND on a collection resource with internal
member URIs. DAV compliant servers MUST support the "0", "1" and member URLs. Servers MUST support the "0", "1" and "infinity"
"infinity" behaviors. By default, the PROPFIND method without a behaviors on WebDAV-compliant resources. By default, the PROPFIND
Depth header MUST act as if a "Depth: infinity" header was included. method without a Depth header MUST act as if a "Depth: infinity"
header was included.
A client may submit a propfind XML element in the body of the A client may submit a propfind XML element in the body of the
request method describing what information is being requested. It request method describing what information is being requested. It
is possible to request: is possible to request:
- Request particular property values, by naming the properties - Request particular property values, by naming the properties
desired desired within the 'prop' element
- Request all dead property values, by using 'deadprops' element.
This can be combined with retrieving specific live properties
named as above. Servers advertising support for RFC2518bis MUST
support this feature.
- Request property values for those properties defined in this - Request property values for those properties defined in this
specification plus dead properties, by using ŠallpropĂ element specification plus dead properties, by using ŠallpropĂ element
- Request a list of names of all the properties defined on the - Request a list of names of all the properties defined on the
resource, by using the ŠpropnameĂ element. resource, by using the ŠpropnameĂ element.
A client may choose not to submit a request body. An empty PROPFIND A client may choose not to submit a request body. An empty PROPFIND
request body MUST be treated as if it were an ŠallpropĂ request. request body MUST be treated as if it were an ŠallpropĂ request.
Note that ŠallpropĂ does not return values for all properties. Note that ŠallpropĂ does not return values for all live properties.
WebDAV servers increasingly have expensively-calculated or lengthy WebDAV servers increasingly have expensively-calculated or lengthy
properties (see [RFC3253] and [TODO: ref ACL RFC when available]) properties (see [RFC3253] and [TODO: ref ACL RFC when available])
and do not return all properties already. Instead, WebDAV clients and do not return all properties already. Instead, WebDAV clients
can use propname requests to discover what live properties exist, can use propname requests to discover what live properties exist,
and request named properties when retrieving values. A WebDAV and request named properties when retrieving values. A WebDAV
server MAY omit certain live properties from other specifications server MAY omit certain live properties from other specifications
when responding to an allprop request from an older client, and MAY when responding to an allprop request from an older client, and MAY
Expires Oct 2003 26
WebDAV (RFC2518) bis June 2003
return only custom (dead) properties and those defined in this return only custom (dead) properties and those defined in this
specification. specification.
Expires Aug 2003 24
WebDAV (RFC2518) bis March 2003
All servers MUST support returning a response of content type All servers MUST support returning a response of content type
text/xml or application/xml that contains a multistatus XML element text/xml or application/xml that contains a multistatus XML element
that describes the results of the attempts to retrieve the various that describes the results of the attempts to retrieve the various
properties. properties.
If there is an error retrieving a property then a proper error If there is an error retrieving a property then a proper error
result MUST be included in the response. A request to retrieve the result MUST be included in the response. A request to retrieve the
value of a property which does not exist is an error and MUST be value of a property which does not exist is an error and MUST be
noted, if the response uses a multistatus XML element, with a noted, if the response uses a multistatus XML element, with a
response XML element which contains a 404 (Not Found) status value. response XML element which contains a 404 (Not Found) status value.
Consequently, the multistatus XML element for a collection resource Consequently, the multistatus XML element for a collection resource
with member URIs MUST include a response XML element for each member with member URLs MUST include a response XML element for each member
URI of the collection, to whatever depth was requested. Each URL of the collection, to whatever depth was requested. Each
response XML element MUST contain an href XML element that gives the response XML element MUST contain an href XML element that gives the
URI of the resource on which the properties in the prop XML element URL of the resource on which the properties in the prop XML element
are defined. URLs for collections appearing in the results MUST end are defined. URLs for collections appearing in the results MUST end
in a slash character. Results for a PROPFIND on a collection in a slash character. Results for a PROPFIND on a collection
resource with internal member URIs are returned as a flat list whose resource with internal member URLs are returned as a flat list whose
order of entries is not significant. order of entries is not significant.
A server enumerating the members of a collection using absolute URLs A server enumerating the members of a collection using absolute URLs
in a PROPFIND response MUST use a common prefix in those URLs, and in a PROPFIND response MUST use a common prefix in those URLs, and
that prefix MUST be the absolute URL used in the response to refer that prefix MUST be the absolute URL used in the response to refer
to the parent collection. to the parent collection.
Unless otherwise notified, clients may expect that the URL for the Unless otherwise notified, clients may expect that the URL for the
parent collection in the PROPFIND response will be the same URL that parent collection in the PROPFIND response will be the same URL that
was used to refer to the parent collection in the PROPFIND request. was used to refer to the parent collection in the PROPFIND request.
skipping to change at line 1333 skipping to change at line 1432
to have a common prefix which is the fully-qualified URL of the to have a common prefix which is the fully-qualified URL of the
parent collection itself. parent collection itself.
URLs in a PROPFIND response body MAY be represented as fully- URLs in a PROPFIND response body MAY be represented as fully-
qualified URLs, in which case they must all contain the full parent qualified URLs, in which case they must all contain the full parent
collection URL (scheme, host, port, and absolute path). collection URL (scheme, host, port, and absolute path).
Alternatively, these URLs MAY be absolute paths (not containing Alternatively, these URLs MAY be absolute paths (not containing
scheme, host or port), but in this case they must all still contain scheme, host or port), but in this case they must all still contain
the full parent collection path. the full parent collection path.
Note that URLs and URIs in XML must always be fully legal URIs. For If a server allows resource names to include characters that arenĂt
example, it is illegal to use a space character or double-quote in a legal in HTTP URL paths, these characters must be URI-escaped on the
URI [RFC2396]. URL-escaping is commonly used (e.g. replace a space
with a sequence such as %20). The URI must not appear in XML
"unescaped", it must be in its legal URI format.
Properties may be subject to access control. In the case of allprop Expires Oct 2003 27
and propname, if a principal does not have the right to know whether
Expires Aug 2003 25 WebDAV (RFC2518) bis June 2003
WebDAV (RFC2518) bis March 2003
wire. For example, it is illegal to use a space character or double-
quote in a URI [RFC2396]. URIs appearing in PROPFIND or PROPPATCH
XML bodies (or other XML marshalling defined in this specification)
must also be legal URIs.
Properties may be subject to access control. In the case of allprop
and propname, if a principal does not have the right to know whether
a particular property exists then the property should be silently a particular property exists then the property should be silently
excluded from the response. excluded from the response.
The results of this method SHOULD NOT be cached. The results of this method SHOULD NOT be cached.
8.2.1 Example - Retrieving Named Properties 8.2.1 Example - Retrieving Named Properties
>>Request >>Request
PROPFIND /file HTTP/1.1 PROPFIND /file HTTP/1.1
skipping to change at line 1385 skipping to change at line 1486
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response xmlns:R="http://www.example.com/boxschema/"> <D:response xmlns:R="http://www.example.com/boxschema/">
<D:href>http://www.example.com/file</D:href> <D:href>http://www.example.com/file</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<R:bigbox> <R:bigbox>
<R:BoxType>Box type A</R:BoxType> <R:BoxType>Box type A</R:BoxType>
</R:bigbox> </R:bigbox>
<R:author> <R:author>
Expires Oct 2003 28
WebDAV (RFC2518) bis June 2003
<R:Name>J.J. Johnson</R:Name> <R:Name>J.J. Johnson</R:Name>
</R:author> </R:author>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
<D:propstat> <D:propstat>
<D:prop><R:DingALing/><R:Random/></D:prop> <D:prop><R:DingALing/><R:Random/></D:prop>
<D:status>HTTP/1.1 403 Forbidden</D:status> <D:status>HTTP/1.1 403 Forbidden</D:status>
Expires Aug 2003 26
WebDAV (RFC2518) bis March 2003
<D:responsedescription> The user does not have access to the <D:responsedescription> The user does not have access to the
DingALing property. DingALing property.
</D:responsedescription> </D:responsedescription>
</D:propstat> </D:propstat>
</D:response> </D:response>
<D:responsedescription> There has been an access violation error. <D:responsedescription> There has been an access violation error.
</D:responsedescription> </D:responsedescription>
</D:multistatus> </D:multistatus>
In this example, PROPFIND is executed on a non-collection resource In this example, PROPFIND is executed on a non-collection resource
http://www.example.com/file. The propfind XML element specifies the http://www.example.com/file. The propfind XML element specifies the
name of four properties whose values are being requested. In this name of four properties whose values are being requested. In this
case only two properties were returned, since the principal issuing case only two properties were returned, since the principal issuing
the request did not have sufficient access rights to see the third the request did not have sufficient access rights to see the third
and fourth properties. and fourth properties.
8.2.2 Example - Using propname to Retrieve all Property Names 8.2.2 Example - Retrieving Named and Dead Properties
>>Request
PROPFIND /mycol/ HTTP/1.1
Host: www.example.com
Depth: 1
Content-type: text/xml; charset="utf-8"
Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:">
<D:prop>
<D:creationdate/>
<D:getlastmodified/>
</D:prop>
<D:deadprops/>
</D:propfind>
In this example, PROPFIND is executed on a collection resource
http://www.example.com/mycol/. The client requests the values of
Expires Oct 2003 29
WebDAV (RFC2518) bis June 2003
two specific live properties plus all dead properties (names and
values). The response is not shown.
8.2.3 Example - Using propname to Retrieve all Property Names
>>Request >>Request
PROPFIND /container/ HTTP/1.1 PROPFIND /container/ HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<propfind xmlns="DAV:"> <propfind xmlns="DAV:">
skipping to change at line 1446 skipping to change at line 1577
<href>http://www.example.com/container/</href> <href>http://www.example.com/container/</href>
<propstat> <propstat>
<prop xmlns:R="http://www.example.com/boxschema/"> <prop xmlns:R="http://www.example.com/boxschema/">
<R:bigbox/> <R:bigbox/>
<R:author/> <R:author/>
<creationdate/> <creationdate/>
<displayname/> <displayname/>
<resourcetype/> <resourcetype/>
<supportedlock/> <supportedlock/>
</prop> </prop>
Expires Aug 2003 27
WebDAV (RFC2518) bis March 2003
<status>HTTP/1.1 200 OK</status> <status>HTTP/1.1 200 OK</status>
</propstat> </propstat>
</response> </response>
<response> <response>
<href>http://www.example.com/container/front.html</href> <href>http://www.example.com/container/front.html</href>
<propstat> <propstat>
<prop xmlns:R="http://www.example.com/boxschema/"> <prop xmlns:R="http://www.example.com/boxschema/">
<R:bigbox/> <R:bigbox/>
<creationdate/> <creationdate/>
<displayname/> <displayname/>
Expires Oct 2003 30
WebDAV (RFC2518) bis June 2003
<getcontentlength/> <getcontentlength/>
<getcontenttype/> <getcontenttype/>
<getetag/> <getetag/>
<getlastmodified/> <getlastmodified/>
<resourcetype/> <resourcetype/>
<supportedlock/> <supportedlock/>
</prop> </prop>
<status>HTTP/1.1 200 OK</status> <status>HTTP/1.1 200 OK</status>
</propstat> </propstat>
</response> </response>
</multistatus> </multistatus>
In this example, PROPFIND is invoked on the collection resource In this example, PROPFIND is invoked on the collection resource
http://www.example.com/container/, with a propfind XML element http://www.example.com/container/, with a propfind XML element
containing the propname XML element, meaning the name of all containing the propname XML element, meaning the name of all
properties should be returned. Since no Depth header is present, it properties should be returned. Since no Depth header is present, it
assumes its default value of "infinity", meaning the name of the assumes its default value of "infinity", meaning the name of the
properties on the collection and all its progeny should be returned. properties on the collection and all its descendents should be
returned.
Consistent with the previous example, resource Consistent with the previous example, resource
http://www.example.com/container/ has six properties defined on it, http://www.example.com/container/ has six properties defined on it:
http://www.example.com/boxschema/bigbox, bigbox and author in the "http://www.example.com/boxschema/"
http://www.example.com/boxschema/author, DAV:creationdate, namespace, and creationdate, displayname, resourcetype, and
DAV:displayname, DAV:resourcetype, and DAV:supportedlock. supportedlock in the "DAV:" namespace.
The resource http://www.example.com/container/index.html, a member The resource http://www.example.com/container/index.html, a member
of the "container" collection, has nine properties defined on it, of the "container" collection, has nine properties defined on it,
http://www.example.com/boxschema/bigbox, DAV:creationdate, bigbox in the "http://www.example.com/boxschema/" namespace and,
DAV:displayname, DAV:getcontentlength, DAV:getcontenttype, creationdate, displayname, getcontentlength, getcontenttype,
DAV:getetag, DAV:getlastmodified, DAV:resourcetype, and getetag, getlastmodified, resourcetype, and supportedlock in the
DAV:supportedlock. "DAV:" namespace.
This example also demonstrates the use of XML namespace scoping, and This example also demonstrates the use of XML namespace scoping and
the default namespace. Since the "xmlns" attribute does not contain the default namespace. Since the "xmlns" attribute does not contain
an explicit "shorthand name" (prefix) letter, the namespace applies a prefix, the namespace applies by default to all enclosed elements.
by default to all enclosed elements. Hence, all elements which do Hence, all elements which do not explicitly state the namespace to
not explicitly state the namespace to which they belong are members which they belong are members of the "DAV:" namespace schema.
of the "DAV:" namespace schema.
Expires Aug 2003 28
WebDAV (RFC2518) bis March 2003
8.2.3 PROPFIND Request Errors 8.2.4 PROPFIND Request Errors
PROPFIND requests may also fail entirely, before the server even PROPFIND requests may also fail entirely, before the server even
gets a chance to evaluate individual properties. 404 (Not Found) and gets a chance to evaluate individual properties. 404 (Not Found) and
401 (Unauthorized) are possible as with every request. These are 401 (Unauthorized) are possible as with every request. These are
some other notable errors. some other notable errors.
Expires Oct 2003 31
WebDAV (RFC2518) bis June 2003
403/DAV:propfind-infinite-depth-forbidden - A server MAY reject all 403/DAV:propfind-infinite-depth-forbidden - A server MAY reject all
PROPFIND requests on collections with depth header of "Infinity", in PROPFIND requests on collections with depth header of "Infinity", in
which case it should use this error. which case it should use this error.
8.3 PROPPATCH 8.3 PROPPATCH
The PROPPATCH method processes instructions specified in the request The PROPPATCH method processes instructions specified in the request
body to set and/or remove properties defined on the resource body to set and/or remove properties defined on the resource
identified by the Request-URI. identified by the Request-URI.
All DAV compliant resources MUST support the PROPPATCH method and All DAV compliant resources MUST support the PROPPATCH method and
MUST process instructions that are specified using the MUST process instructions that are specified using the
propertyupdate, set, and remove XML elements of the DAV schema. propertyupdate, set, and remove XML elements. Execution of the
Execution of the directives in this method is, of course, subject to directives in this method is, of course, subject to access control
access control constraints. DAV compliant resources SHOULD support constraints. DAV compliant resources SHOULD support the setting of
the setting of arbitrary dead properties. arbitrary dead properties.
The request message body of a PROPPATCH method MUST contain the The request message body of a PROPPATCH method MUST contain the
propertyupdate XML element. Instruction processing MUST occur in propertyupdate XML element. Instruction processing MUST occur in
the order instructions are received (i.e., from top to bottom). document order. Instructions MUST either all be executed or none
Instructions MUST either all be executed or none executed. Thus if executed. Thus if any error occurs during processing all executed
any error occurs during processing all executed instructions MUST be instructions MUST be undone and a proper error result returned.
undone and a proper error result returned. Instruction processing Instruction processing details can be found in the definition of the
details can be found in the definition of the set and remove set and remove instructions in sections 13.23 and section 13.24.
instructions in sections 13.23 and section 13.24.
8.3.1 Status Codes for use with 207 (Multi-Status) 8.3.1 Status Codes for use with 207 (Multi-Status)
The following are examples of response codes one would expect to be The following are examples of response codes one would expect to be
used in a 207 (Multi-Status) response for this method. Note, used in a 207 (Multi-Status) response for this method. Note,
however, that unless explicitly prohibited any 2/3/4/5xx series however, that unless explicitly prohibited any 2/3/4/5xx series
response code may be used in a 207 (Multi-Status) response. response code may be used in a 207 (Multi-Status) response.
200 (OK) - The command succeeded. As there can be a mixture of sets 200 (OK) - The command succeeded. As there can be a mixture of sets
and removes in a body, a 201 (Created) seems inappropriate. and removes in a body, a 201 (Created) seems inappropriate.
403 (Forbidden) - The client, for reasons the server chooses not to 403 (Forbidden) - The client, for reasons the server chooses not to
specify, cannot alter one of the properties. specify, cannot alter one of the properties.
403/DAV:read-only-property: The client has attempted to set a read- 403/DAV:read-only-property: The client has attempted to set a read-
only property, such as getetag. only property, such as getetag.
409 (Conflict) - The client has provided a value whose semantics are 409 (Conflict) - The client has provided a value whose semantics are
not appropriate for the property. not appropriate for the property.
Expires Aug 2003 29
WebDAV (RFC2518) bis March 2003
423 (Locked) - The specified resource is locked and the client 423 (Locked) - The specified resource is locked and the client
either is not a lock owner or the lock type requires a lock token to either is not a lock owner or the lock type requires a lock token to
be submitted and the client did not submit it. be submitted and the client did not submit it.
507 (Insufficient Storage) - The server did not have sufficient 507 (Insufficient Storage) - The server did not have sufficient
space to record the property. space to record the property.
Expires Oct 2003 32
WebDAV (RFC2518) bis June 2003
8.3.2 Example - PROPPATCH 8.3.2 Example - PROPPATCH
>>Request >>Request
PROPPATCH /bar.html HTTP/1.1 PROPPATCH /bar.html HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
skipping to change at line 1606 skipping to change at line 1739
<D:multistatus xmlns:D="DAV:" <D:multistatus xmlns:D="DAV:"
xmlns:Z="http://www.w3.com/standards/z39.50"> xmlns:Z="http://www.w3.com/standards/z39.50">
<D:response> <D:response>
<D:href>http://www.example.com/bar.html</D:href> <D:href>http://www.example.com/bar.html</D:href>
<D:propstat> <D:propstat>
<D:prop><Z:Authors/></D:prop> <D:prop><Z:Authors/></D:prop>
<D:status>HTTP/1.1 424 Failed Dependency</D:status> <D:status>HTTP/1.1 424 Failed Dependency</D:status>
</D:propstat> </D:propstat>
<D:propstat> <D:propstat>
<D:prop><Z:Copyright-Owner/></D:prop> <D:prop><Z:Copyright-Owner/></D:prop>
Expires Aug 2003 30
WebDAV (RFC2518) bis March 2003
<D:status>HTTP/1.1 409 Conflict</D:status> <D:status>HTTP/1.1 409 Conflict</D:status>
</D:propstat> </D:propstat>
Expires Oct 2003 33
WebDAV (RFC2518) bis June 2003
<D:responsedescription> Copyright Owner can not be deleted or <D:responsedescription> Copyright Owner can not be deleted or
altered.</D:responsedescription> altered.</D:responsedescription>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
In this example, the client requests the server to set the value of In this example, the client requests the server to set the value of
the "Authors" property in the "http://www.w3.com/standards/z39.50/" the "Authors" property in the "http://www.w3.com/standards/z39.50/"
namespace, and to remove the property "Copyright-Owner" in the namespace, and to remove the property "Copyright-Owner" in the
"http://www.w3.com/standards/z39.50/" namespace. Since the "http://www.w3.com/standards/z39.50/" namespace. Since the
Copyright-Owner property could not be removed, no property Copyright-Owner property could not be removed, no property
modifications occur. The 424 (Failed Dependency) status code for modifications occur. The 424 (Failed Dependency) status code for
the Authors property indicates this action would have succeeded if the Authors property indicates this action would have succeeded if
it were not for the conflict with removing the Copyright-Owner it were not for the conflict with removing the Copyright-Owner
property. property.
8.4 MKCOL Method 8.4 MKCOL Method
The MKCOL method is used to create a new collection. All DAV The MKCOL method is used to create a new collection. All WebDAV
compliant resources MUST support the MKCOL method. compliant resources MUST support the MKCOL method.
MKCOL creates a new collection resource at the location specified by MKCOL creates a new collection resource at the location specified by
the Request-URI. If the resource identified by the Request-URI is the Request-URI. If the resource identified by the Request-URI is
non-null then the MKCOL MUST fail. During MKCOL processing, a non-null then the MKCOL MUST fail. During MKCOL processing, a
server MUST make the Request-URI a member of its parent collection, server MUST make the Request-URI a member of its parent collection,
unless the Request-URI is "/". If no such ancestor exists, the unless the Request-URI is "/". If no such ancestor exists, the
method MUST fail. When the MKCOL operation creates a new collection method MUST fail. When the MKCOL operation creates a new collection
resource, all ancestors MUST already exist, or the method MUST fail resource, all ancestors MUST already exist, or the method MUST fail
with a 409 (Conflict) status code. For example, if a request to with a 409 (Conflict) status code. For example, if a request to
skipping to change at line 1663 skipping to change at line 1797
entity or the type of an entity, it should use the 415 (Unsupported entity or the type of an entity, it should use the 415 (Unsupported
Media Type) status code. The exact behavior of MKCOL for various Media Type) status code. The exact behavior of MKCOL for various
request media types is undefined in this document, and will be request media types is undefined in this document, and will be
specified in separate documents. specified in separate documents.
Status Codes Status Codes
Responses from a MKCOL request MUST NOT be cached as MKCOL has non- Responses from a MKCOL request MUST NOT be cached as MKCOL has non-
idempotent semantics. idempotent semantics.
Expires Aug 2003 31 Expires Oct 2003 34
WebDAV (RFC2518) bis March 2003
WebDAV (RFC2518) bis June 2003
201 (Created) - The collection or structured resource was created in 201 (Created) - The collection or structured resource was created in
its entirety. its entirety.
403 (Forbidden) - This indicates at least one of two conditions: 1) 403 (Forbidden) - This indicates at least one of two conditions: 1)
the server does not allow the creation of collections at the given the server does not allow the creation of collections at the given
location in its namespace, or 2) the parent collection of the location in its namespace, or 2) the parent collection of the
Request-URI exists but cannot accept members. Request-URI exists but cannot accept members.
405 (Method Not Allowed) - MKCOL can only be executed on a 405 (Method Not Allowed) - MKCOL can only be executed on a
skipping to change at line 1713 skipping to change at line 1848
The semantics of GET are unchanged when applied to a collection, The semantics of GET are unchanged when applied to a collection,
since GET is defined as, "retrieve whatever information (in the form since GET is defined as, "retrieve whatever information (in the form
of an entity) is identified by the Request-URI" [RFC2616]. GET when of an entity) is identified by the Request-URI" [RFC2616]. GET when
applied to a collection may return the contents of an "index.html" applied to a collection may return the contents of an "index.html"
resource, a human-readable view of the contents of the collection, resource, a human-readable view of the contents of the collection,
or something else altogether. Hence it is possible that the result or something else altogether. Hence it is possible that the result
of a GET on a collection will bear no correlation to the membership of a GET on a collection will bear no correlation to the membership
of the collection. of the collection.
Expires Oct 2003 35
WebDAV (RFC2518) bis June 2003
Similarly, since the definition of HEAD is a GET without a response Similarly, since the definition of HEAD is a GET without a response
message body, the semantics of HEAD are unmodified when applied to message body, the semantics of HEAD are unmodified when applied to
collection resources. collection resources.
Expires Aug 2003 32
WebDAV (RFC2518) bis March 2003
8.6 POST for Collections 8.6 POST for Collections
Since by definition the actual function performed by POST is Since by definition the actual function performed by POST is
determined by the server and often depends on the particular determined by the server and often depends on the particular
resource, the behavior of POST when applied to collections cannot be resource, the behavior of POST when applied to collections cannot be
meaningfully modified because it is largely undefined. Thus the meaningfully modified because it is largely undefined. Thus the
semantics of POST are unmodified when applied to a collection. semantics of POST are unmodified when applied to a collection.
8.7 DELETE 8.7 DELETE
DELETE for Non-Collection Resources DELETE for Non-Collection Resources
If the DELETE method is issued to a non-collection resource whose When a client issues a DELETE request to a Request-URI mapping to a
URIs are an internal member of one or more collections, then during non-collection resource, if the operation is successful the server
DELETE processing a server MUST remove any URI for the resource MUST remove that mapping. Thus, after a successful DELETE operation
identified by the Request-URI from collections which contain it as a (and in the absence of other actions) a subsequent GET/HEAD/PROPFIND
member. request to the target Request-URI would return 404 (Not Found).
DELETE for Collections DELETE for Collections
The DELETE method on a collection MUST act as if a "Depth: infinity" The DELETE method on a collection MUST act as if a "Depth: infinity"
header was used on it. A client MUST NOT submit a Depth header with header was used on it. A client MUST NOT submit a Depth header with
a DELETE on a collection with any value but infinity. a DELETE on a collection with any value but infinity.
DELETE instructs that the collection specified in the Request-URI DELETE instructs that the collection specified in the Request-URI
and all resources identified by its internal member URIs are to be and all resources identified by its internal member URLs are to be
deleted. deleted.
If any resource identified by a member URI cannot be deleted then If any resource identified by a member URL cannot be deleted then
all of the member's ancestors MUST NOT be deleted, so as to maintain all of the member's ancestors MUST NOT be deleted, so as to maintain
namespace consistency. namespace consistency.
Any headers included with DELETE MUST be applied in processing every Any headers included with DELETE MUST be applied in processing every
resource to be deleted. resource to be deleted.
When the DELETE method has completed processing it MUST result in a When the DELETE method has completed processing it MUST result in a
consistent namespace. consistent namespace.
If an error occurs deleting an internal resource (a resource other If an error occurs deleting an internal resource (a resource other
than the resource identified in the Request-URI) then the response than the resource identified in the Request-URI) then the response
can be a 207 (Multi-Status). Multi-Status is used here to indicate can be a 207 (Multi-Status). Multi-Status is used here to indicate
which internal resources could NOT be deleted, including an error which internal resources could NOT be deleted, including an error
code which should help the client understand which resources caused code which should help the client understand which resources caused
the failure. For example, the Multi-Status body could include a the failure. For example, the Multi-Status body could include a
response with status 423 (Locked) if an internal resource was response with status 423 (Locked) if an internal resource was
locked. locked.
Expires Oct 2003 36
WebDAV (RFC2518) bis June 2003
The server MAY return a 4xx status response, rather than a Multi- The server MAY return a 4xx status response, rather than a Multi-
Status, if the entire DELETE request failed and it canĂt identify Status, if the entire DELETE request failed and it canĂt identify
the internal resources that caused the DELETE to fail. the internal resources that caused the DELETE to fail.
424 (Failed Dependency) errors SHOULD NOT be in the 207 (Multi- 424 (Failed Dependency) errors SHOULD NOT be in the 207 (Multi-
Status). They can be safely left out because the client will know Status). They can be safely left out because the client will know
Expires Aug 2003 33
WebDAV (RFC2518) bis March 2003
that the ancestors of a resource could not be deleted when the that the ancestors of a resource could not be deleted when the
client receives an error for the ancestor's progeny. Additionally client receives an error for the ancestor's progeny. Additionally
204 (No Content) errors SHOULD NOT be returned in the 207 (Multi- 204 (No Content) errors SHOULD NOT be returned in the 207 (Multi-
Status). The reason for this prohibition is that 204 (No Content) Status). The reason for this prohibition is that 204 (No Content)
is the default success code. is the default success code.
8.7.1 Example - DELETE 8.7.1 Example - DELETE
>>Request >>Request
skipping to change at line 1819 skipping to change at line 1955
that the attempt to delete http://www.example.com/container/ must that the attempt to delete http://www.example.com/container/ must
have also failed since the parent can not be deleted unless its have also failed since the parent can not be deleted unless its
child has also been deleted. Even though a Depth header has not child has also been deleted. Even though a Depth header has not
been included, a depth of infinity is assumed because the method is been included, a depth of infinity is assumed because the method is
on a collection. on a collection.
8.8 PUT 8.8 PUT
PUT for Non-Collection Resources PUT for Non-Collection Resources
Expires Oct 2003 37
WebDAV (RFC2518) bis June 2003
A PUT performed on an existing resource replaces the GET response A PUT performed on an existing resource replaces the GET response
entity of the resource. Properties defined on the resource may be entity of the resource. Properties defined on the resource may be
recomputed during PUT processing but are not otherwise affected. recomputed during PUT processing but are not otherwise affected.
For example, if a server recognizes the content type of the request For example, if a server recognizes the content type of the request
body, it may be able to automatically extract information that could body, it may be able to automatically extract information that could
be profitably exposed as properties. be profitably exposed as properties.
A PUT that would result in the creation of a resource without an A PUT that would result in the creation of a resource without an
appropriately scoped parent collection MUST fail with a 409 appropriately scoped parent collection MUST fail with a 409
(Conflict). (Conflict).
Expires Aug 2003 34
WebDAV (RFC2518) bis March 2003
PUT for Collections PUT for Collections
As defined in [RFC2616], the "PUT method requests that the enclosed As defined in [RFC2616], the "PUT method requests that the enclosed
entity be stored under the supplied Request-URI." Since submission entity be stored under the supplied Request-URI." Since submission
of an entity representing a collection would implicitly encode of an entity representing a collection would implicitly encode
creation and deletion of resources, this specification intentionally creation and deletion of resources, this specification intentionally
does not define a transmission format for creating a collection does not define a transmission format for creating a collection
using PUT. Instead, the MKCOL method is defined to create using PUT. Instead, the MKCOL method is defined to create
collections. collections.
skipping to change at line 1872 skipping to change at line 2009
state and behavior match that of the source resource as closely as state and behavior match that of the source resource as closely as
possible. After a successful COPY invocation, all properties on the possible. After a successful COPY invocation, all properties on the
source resource MUST be duplicated on the destination resource, source resource MUST be duplicated on the destination resource,
subject to modifying headers and XML elements, following the subject to modifying headers and XML elements, following the
definition for copying properties. Since the environment at the definition for copying properties. Since the environment at the
destination may be different than at the source due to factors destination may be different than at the source due to factors
outside the scope of control of the server, such as the absence of outside the scope of control of the server, such as the absence of
resources required for correct operation, it may not be possible to resources required for correct operation, it may not be possible to
completely duplicate the behavior of the resource at the completely duplicate the behavior of the resource at the
destination. Subsequent alterations to the destination resource will destination. Subsequent alterations to the destination resource will
Expires Oct 2003 38
WebDAV (RFC2518) bis June 2003
not modify the source resource. Subsequent alterations to the not modify the source resource. Subsequent alterations to the
source resource will not modify the destination resource. source resource will not modify the destination resource.
COPY for Properties COPY for Properties
Live properties described in this document SHOULD be duplicated as Live properties described in this document SHOULD be duplicated as
identically behaving live properties at the destination resource, identically behaving live properties at the destination resource,
but not necessarily with the same values. If a property cannot be but not necessarily with the same values. If a property cannot be
copied live, then its value MUST be duplicated, octet-for-octet, in copied live, then its value MUST be duplicated, octet-for-octet, in
an identically named, dead property on the destination resource. an identically named, dead property on the destination resource.
Expires Aug 2003 35
WebDAV (RFC2518) bis March 2003
A COPY operation creates a new resource, much like a PUT operation A COPY operation creates a new resource, much like a PUT operation
does. Live properties which are related to resource creation (such does. Live properties which are related to resource creation (such
as creationdate) should have their values set accordingly. as creationdate) should have their values set accordingly.
Dead properties must be duplicated exactly. Dead properties must be duplicated exactly.
8.9.1 COPY for Collections 8.9.1 COPY for Collections
The COPY method on a collection without a Depth header MUST act as The COPY method on a collection without a Depth header MUST act as
if a Depth header with value "infinity" was included. A client may if a Depth header with value "infinity" was included. A client may
submit a Depth header on a COPY on a collection with a value of "0" submit a Depth header on a COPY on a collection with a value of "0"
or "infinity". DAV compliant servers MUST support the "0" and or "infinity". Servers MUST support the "0" and "infinity" Depth
"infinity" Depth header behaviors. header behaviors on WebDAV-compliant resources.
A COPY of depth infinity instructs that the collection resource A COPY of depth infinity instructs that the collection resource
identified by the Request-URI is to be copied to the location identified by the Request-URI is to be copied to the location
identified by the URI in the Destination header, and all its identified by the URI in the Destination header, and all its
internal member resources are to be copied to a location relative to internal member resources are to be copied to a location relative to
it, recursively through all levels of the collection hierarchy. it, recursively through all levels of the collection hierarchy.
A COPY of "Depth: 0" only instructs that the collection and its A COPY of "Depth: 0" only instructs that the collection and its
properties but not resources identified by its internal member URIs, properties but not resources identified by its internal member URLs,
are to be copied. are to be copied.
Any headers included with a COPY MUST be applied in processing every Any headers included with a COPY MUST be applied in processing every
resource to be copied with the exception of the Destination header. resource to be copied with the exception of the Destination header.
The Destination header only specifies the destination URI for the The Destination header only specifies the destination URI for the
Request-URI. When applied to members of the collection identified by Request-URI. When applied to members of the collection identified by
the Request-URI the value of Destination is to be modified to the Request-URI the value of Destination is to be modified to
reflect the current location in the hierarchy. So, if the Request- reflect the current location in the hierarchy. So, if the Request-
URI is /a/ with Host header value http://fun.com/ and the URI is /a/ with Host header value http://fun.com/ and the
Destination is http://fun.com/b/ then when http://fun.com/a/c/d is Destination is http://fun.com/b/ then when http://fun.com/a/c/d is
processed it must use a Destination of http://fun.com/b/c/d. processed it must use a Destination of http://fun.com/b/c/d.
When the COPY method has completed processing it MUST have created a When the COPY method has completed processing it MUST have created a
consistent namespace at the destination (see section 5.1 for the consistent namespace at the destination (see section 5.1 for the
definition of namespace consistency). However, if an error occurs definition of namespace consistency). However, if an error occurs
while copying an internal collection, the server MUST NOT copy any while copying an internal collection, the server MUST NOT copy any
Expires Oct 2003 39
WebDAV (RFC2518) bis June 2003
resources identified by members of this collection (i.e., the server resources identified by members of this collection (i.e., the server
must skip this subtree), as this would create an inconsistent must skip this subtree), as this would create an inconsistent
namespace. After detecting an error, the COPY operation SHOULD try namespace. After detecting an error, the COPY operation SHOULD try
to finish as much of the original copy operation as possible (i.e., to finish as much of the original copy operation as possible (i.e.,
the server should still attempt to copy other subtrees and their the server should still attempt to copy other subtrees and their
members, that are not descendents of an error-causing collection). members, that are not descendents of an error-causing collection).
So, for example, if an infinite depth copy operation is performed on So, for example, if an infinite depth copy operation is performed on
collection /a/, which contains collections /a/b/ and /a/c/, and an collection /a/, which contains collections /a/b/ and /a/c/, and an
error occurs copying /a/b/, an attempt should still be made to copy error occurs copying /a/b/, an attempt should still be made to copy
/a/c/. Similarly, after encountering an error copying a non- /a/c/. Similarly, after encountering an error copying a non-
collection resource as part of an infinite depth copy, the server collection resource as part of an infinite depth copy, the server
SHOULD try to finish as much of the original copy operation as SHOULD try to finish as much of the original copy operation as
possible. possible.
Expires Aug 2003 36
WebDAV (RFC2518) bis March 2003
If an error in executing the COPY method occurs with a resource If an error in executing the COPY method occurs with a resource
other than the resource identified in the Request-URI then the other than the resource identified in the Request-URI then the
response MUST be a 207 (Multi-Status), and the errored resource's response MUST be a 207 (Multi-Status), and the URL of the resource
URL MUST appear with the specific error. causing the failure MUST appear with the specific error.
The 424 (Failed Dependency) status code SHOULD NOT be returned in The 424 (Failed Dependency) status code SHOULD NOT be returned in
the 207 (Multi-Status) response from a COPY method. These responses the 207 (Multi-Status) response from a COPY method. These responses
can be safely omitted because the client will know that the progeny can be safely omitted because the client will know that the progeny
of a resource could not be copied when the client receives an error of a resource could not be copied when the client receives an error
for the parent. Additionally 201 (Created)/204 (No Content) status for the parent. Additionally 201 (Created)/204 (No Content) status
codes SHOULD NOT be returned as values in 207 (Multi-Status) codes SHOULD NOT be returned as values in 207 (Multi-Status)
responses from COPY methods. They, too, can be safely omitted responses from COPY methods. They, too, can be safely omitted
because they are the default success codes. because they are the default success codes.
skipping to change at line 1979 skipping to change at line 2120
pre-existing destination resource. pre-existing destination resource.
207 (Multi-Status) - Multiple resources were to be affected by the 207 (Multi-Status) - Multiple resources were to be affected by the
COPY, but errors on some of them prevented the operation from taking COPY, but errors on some of them prevented the operation from taking
place. Specific error messages, together with the most appropriate place. Specific error messages, together with the most appropriate
of the source and destination URLs, appear in the body of the multi- of the source and destination URLs, appear in the body of the multi-
status response. E.g. if a destination resource was locked and could status response. E.g. if a destination resource was locked and could
not be overwritten, then the destination resource URL appears with not be overwritten, then the destination resource URL appears with
the 423 (Locked) status. the 423 (Locked) status.
Expires Oct 2003 40
WebDAV (RFC2518) bis June 2003
403 (Forbidden) - The operation is forbidden. Possibly this is 403 (Forbidden) - The operation is forbidden. Possibly this is
because the source and destination URIs are the same. because the source and destination resources are the same resource.
409 (Conflict) - A resource cannot be created at the destination 409 (Conflict) - A resource cannot be created at the destination
until one or more intermediate collections have been created. The until one or more intermediate collections have been created. The
server MUST NOT create those intermediate collections automatically. server MUST NOT create those intermediate collections automatically.
412 (Precondition Failed) - A precondition failed, e.g. the 412 (Precondition Failed) - A precondition failed, e.g. the
Overwrite header is "F" and the state of the destination resource is Overwrite header is "F" and the state of the destination resource is
non-null. non-null.
423 (Locked) - The destination resource was locked. 423 (Locked) - The destination resource was locked.
502 (Bad Gateway) - This may occur when the destination is on 502 (Bad Gateway) - This may occur when the destination is on
another server, repository or context. Either the source context another server, repository or context. Either the source context
does not support copying to the destination context, or the does not support copying to the destination context, or the
Expires Aug 2003 37
WebDAV (RFC2518) bis March 2003
destination context refuses to accept the resource. The client may destination context refuses to accept the resource. The client may
wish to try GET/PUT and PROPFIND/PROPPATCH instead. wish to try GET/PUT and PROPFIND/PROPPATCH instead.
507 (Insufficient Storage) - The destination resource does not have 507 (Insufficient Storage) - The destination resource does not have
sufficient space to record the state of the resource after the sufficient space to record the state of the resource after the
execution of this method. execution of this method.
8.9.4 Example - COPY with Overwrite 8.9.4 Example - COPY with Overwrite
This example shows resource This example shows resource
skipping to change at line 2033 skipping to change at line 2174
Example - COPY with No Overwrite Example - COPY with No Overwrite
The following example shows the same copy operation being performed, The following example shows the same copy operation being performed,
but with the Overwrite header set to "F." A response of 412 but with the Overwrite header set to "F." A response of 412
(Precondition Failed) is returned because the destination resource (Precondition Failed) is returned because the destination resource
has a non-null state. has a non-null state.
>>Request >>Request
Expires Oct 2003 41
WebDAV (RFC2518) bis June 2003
COPY /~fielding/index.html HTTP/1.1 COPY /~fielding/index.html HTTP/1.1
Host: www.ics.uci.edu Host: www.ics.uci.edu
Destination: http://www.ics.uci.edu/users/f/fielding/index.html Destination: http://www.ics.uci.edu/users/f/fielding/index.html
Overwrite: F Overwrite: F
>>Response >>Response
HTTP/1.1 412 Precondition Failed HTTP/1.1 412 Precondition Failed
Example - COPY of a Collection Example - COPY of a Collection
>>Request >>Request
COPY /container/ HTTP/1.1 COPY /container/ HTTP/1.1
Host: www.example.com Host: www.example.com
Destination: http://www.example.com/othercontainer/ Destination: http://www.example.com/othercontainer/
Depth: infinity Depth: infinity
Expires Aug 2003 38
WebDAV (RFC2518) bis March 2003
>>Response >>Response
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<d:multistatus xmlns:d="DAV:"> <d:multistatus xmlns:d="DAV:">
<d:response> <d:response>
skipping to change at line 2083 skipping to change at line 2225
failed because the destination R2 is locked. Because there was an failed because the destination R2 is locked. Because there was an
error copying R2, none of R2's members were copied. However no error copying R2, none of R2's members were copied. However no
errors were listed for those members due to the error minimization errors were listed for those members due to the error minimization
rules. rules.
8.10 MOVE Method 8.10 MOVE Method
The MOVE operation on a non-collection resource is the logical The MOVE operation on a non-collection resource is the logical
equivalent of a copy (COPY), followed by consistency maintenance equivalent of a copy (COPY), followed by consistency maintenance
processing, followed by a delete of the source, where all three processing, followed by a delete of the source, where all three
Expires Oct 2003 42
WebDAV (RFC2518) bis June 2003
actions are performed atomically. The consistency maintenance step actions are performed atomically. The consistency maintenance step
allows the server to perform updates caused by the move, such as allows the server to perform updates caused by the move, such as
updating all URIs other than the Request-URI which identify the updating all URLs other than the Request-URI which identify the
source resource, to point to the new destination resource. source resource, to point to the new destination resource.
Consequently, the Destination header MUST be present on all MOVE Consequently, the Destination header MUST be present on all MOVE
methods and MUST follow all COPY requirements for the COPY part of methods and MUST follow all COPY requirements for the COPY part of
the MOVE method. All DAV compliant resources MUST support the MOVE the MOVE method. All WebDAV compliant resources MUST support the
method. However, support for the MOVE method does not guarantee the MOVE method. However, support for the MOVE method does not
ability to move a resource to a particular destination. guarantee the ability to move a resource to a particular
destination.
For example, separate programs may actually control different sets For example, separate programs may actually control different sets
of resources on the same server. Therefore, it may not be possible of resources on the same server. Therefore, it may not be possible
to move a resource within a namespace that appears to belong to the to move a resource within a namespace that appears to belong to the
same server. same server.
If a resource exists at the destination, the destination resource If a resource exists at the destination, the destination resource
will be DELETEd as a side-effect of the MOVE operation, subject to will be DELETEd as a side-effect of the MOVE operation, subject to
the restrictions of the Overwrite header. the restrictions of the Overwrite header.
8.10.1 MOVE for Properties 8.10.1 MOVE for Properties
Expires Aug 2003 39
WebDAV (RFC2518) bis March 2003
Live properties described in this document MUST be moved along with Live properties described in this document MUST be moved along with
the resource, such that the resource has identically behaving live the resource, such that the resource has identically behaving live
properties at the destination resource, but not necessarily with the properties at the destination resource, but not necessarily with the
same values. If the live properties will not work the same way at same values. If the live properties will not work the same way at
the destination, the server MUST fail the request (the client can the destination, the server MUST fail the request (the client can
perform COPY then DELETE if it wants a MOVE to work that badly). perform COPY then DELETE if it wants a MOVE to work that badly).
This can mean that the server removes a live property if that's the This can mean that the server removes a live property if that's the
most appropriate behavior for that live property at the destination. most appropriate behavior for that live property at the destination.
A MOVE can be a rename operation, so it's not appropriate to reset A MOVE can be a rename operation, so it's not appropriate to reset
live properties which are set at resource creation. For example, the live properties which are set at resource creation. For example, the
creationdate property value SHOULD remain the same. creationdate property value SHOULD remain the same.
Dead properties must be moved along with the resource. Dead properties must be moved along with the resource.
. .
8.10.2 MOVE for Collections 8.10.2 MOVE for Collections
A MOVE with "Depth: infinity" instructs that the collection A MOVE with "Depth: infinity" instructs that the collection
identified by the Request-URI be moved to the URI specified in the identified by the Request-URI be moved to the address specified in
Destination header, and all resources identified by its internal the Destination header, and all resources identified by its internal
member URIs are to be moved to locations relative to it, recursively member URLs are to be moved to locations relative to it, recursively
through all levels of the collection hierarchy. through all levels of the collection hierarchy.
The MOVE method on a collection MUST act as if a "Depth: infinity" The MOVE method on a collection MUST act as if a "Depth: infinity"
header was used on it. A client MUST NOT submit a Depth header on a header was used on it. A client MUST NOT submit a Depth header on a
MOVE on a collection with any value but "infinity". MOVE on a collection with any value but "infinity".
Expires Oct 2003 43
WebDAV (RFC2518) bis June 2003
Any headers included with MOVE MUST be applied in processing every Any headers included with MOVE MUST be applied in processing every
resource to be moved with the exception of the Destination header. resource to be moved with the exception of the Destination header.
The behavior of the Destination header is the same as given for COPY The behavior of the Destination header is the same as given for COPY
on collections. on collections.
When the MOVE method has completed processing it MUST have created a When the MOVE method has completed processing it MUST have created a
consistent namespace at both the source and destination (see section consistent namespace at both the source and destination (see section
5.1 for the definition of namespace consistency). However, if an 5.1 for the definition of namespace consistency). However, if an
error occurs while moving an internal collection, the server MUST error occurs while moving an internal collection, the server MUST
skipping to change at line 2160 skipping to change at line 2309
attempt to move other subtrees and the resources identified by their attempt to move other subtrees and the resources identified by their
members, that are not descendents of an error-causing collection). members, that are not descendents of an error-causing collection).
So, for example, if an infinite depth move is performed on So, for example, if an infinite depth move is performed on
collection /a/, which contains collections /a/b/ and /a/c/, and an collection /a/, which contains collections /a/b/ and /a/c/, and an
error occurs moving /a/b/, an attempt should still be made to try error occurs moving /a/b/, an attempt should still be made to try
moving /a/c/. Similarly, after encountering an error moving a non- moving /a/c/. Similarly, after encountering an error moving a non-
collection resource as part of an infinite depth move, the server collection resource as part of an infinite depth move, the server
SHOULD try to finish as much of the original move operation as SHOULD try to finish as much of the original move operation as
possible. possible.
Expires Aug 2003 40
WebDAV (RFC2518) bis March 2003
If an error occurs with a resource other than the resource If an error occurs with a resource other than the resource
identified in the Request-URI then the response MUST be a 207 identified in the Request-URI then the response MUST be a 207
(Multi-Status), and the errored resource's URL MUST appear with the (Multi-Status), and the errored resource's URL MUST appear with the
specific error. specific error.
The 424 (Failed Dependency) status code SHOULD NOT be returned in The 424 (Failed Dependency) status code SHOULD NOT be returned in
the 207 (Multi-Status) response from a MOVE method. These errors the 207 (Multi-Status) response from a MOVE method. These errors
can be safely omitted because the client will know that the progeny can be safely omitted because the client will know that the progeny
of a resource could not be moved when the client receives an error of a resource could not be moved when the client receives an error
for the parent. Additionally 201 (Created)/204 (No Content) for the parent. Additionally 201 (Created)/204 (No Content)
skipping to change at line 2189 skipping to change at line 2335
If a resource exists at the destination and the Overwrite header is If a resource exists at the destination and the Overwrite header is
"T" then prior to performing the move the server MUST perform a "T" then prior to performing the move the server MUST perform a
DELETE with "Depth: infinity" on the destination resource. If the DELETE with "Depth: infinity" on the destination resource. If the
Overwrite header is set to "F" then the operation will fail. Overwrite header is set to "F" then the operation will fail.
8.10.4 Status Codes 8.10.4 Status Codes
201 (Created) - The source resource was successfully moved, and a 201 (Created) - The source resource was successfully moved, and a
new resource was created at the destination. new resource was created at the destination.
Expires Oct 2003 44
WebDAV (RFC2518) bis June 2003
204 (No Content) - The source resource was successfully moved to a 204 (No Content) - The source resource was successfully moved to a
pre-existing destination resource. pre-existing destination resource.
207 (Multi-Status) - Multiple resources were to be affected by the 207 (Multi-Status) - Multiple resources were to be affected by the
MOVE, but errors on some of them prevented the operation from taking MOVE, but errors on some of them prevented the operation from taking
place. Specific error messages, together with the most appropriate place. Specific error messages, together with the most appropriate
of the source and destination URLs, appear in the body of the multi- of the source and destination URLs, appear in the body of the multi-
status response. E.g. if a source resource was locked and could not status response. E.g. if a source resource was locked and could not
be moved, then the source resource URL appears with the 423 (Locked) be moved, then the source resource URL appears with the 423 (Locked)
status. status.
403 (Forbidden) ű The source and destination URIs are the same. 403 (Forbidden) ű The source and destination resources are the same.
409 (Conflict) ű A resource cannot be created at the destination 409 (Conflict) ű A resource cannot be created at the destination
until one or more intermediate collections have been created. The until one or more intermediate collections have been created. The
server MUST NOT create those intermediate collections automatically. server MUST NOT create those intermediate collections automatically.
412 (Precondition Failed) ű A condition failed, e.g. the Overwrite 412 (Precondition Failed) ű A condition failed, e.g. the Overwrite
header is "F" and the state of the destination resource is non-null. header is "F" and the state of the destination resource is non-null.
423 (Locked) - The source or the destination resource was locked. 423 (Locked) - The source or the destination resource was locked.
500/DAV:live-properties-not-preserved - The server was unable to 500/DAV:live-properties-not-preserved - The server was unable to
preserve the behavior of the live properties and still move the preserve the behavior of the live properties and still move the
resource to the destination. resource to the destination.
Expires Aug 2003 41
WebDAV (RFC2518) bis March 2003
502 (Bad Gateway) - This may occur when the destination is on 502 (Bad Gateway) - This may occur when the destination is on
another server and the destination server refuses to accept the another server and the destination server refuses to accept the
resource. resource.
8.10.5 Example - MOVE of a Non-Collection 8.10.5 Example - MOVE of a Non-Collection
This example shows resource This example shows resource
http://www.ics.uci.edu/~fielding/index.html being moved to the http://www.ics.uci.edu/~fielding/index.html being moved to the
location http://www.ics.uci.edu/users/f/fielding/index.html. The location http://www.ics.uci.edu/users/f/fielding/index.html. The
contents of the destination resource would have been overwritten if contents of the destination resource would have been overwritten if
skipping to change at line 2241 skipping to change at line 2388
>>Request >>Request
MOVE /~fielding/index.html HTTP/1.1 MOVE /~fielding/index.html HTTP/1.1
Host: www.ics.uci.edu Host: www.ics.uci.edu
Destination: http://www.ics.uci.edu/users/f/fielding/index.html Destination: http://www.ics.uci.edu/users/f/fielding/index.html
>>Response >>Response
HTTP/1.1 201 Created HTTP/1.1 201 Created
Expires Oct 2003 45
WebDAV (RFC2518) bis June 2003
Location: http://www.ics.uci.edu/users/f/fielding/index.html Location: http://www.ics.uci.edu/users/f/fielding/index.html
Example - MOVE of a Collection Example - MOVE of a Collection
>>Request >>Request
MOVE /container/ HTTP/1.1 MOVE /container/ HTTP/1.1
Host: www.example.com Host: www.example.com
Destination: http://www.example.com/othercontainer/ Destination: http://www.example.com/othercontainer/
Overwrite: F Overwrite: F
skipping to change at line 2266 skipping to change at line 2418
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<d:multistatus xmlns:d='DAV:'> <d:multistatus xmlns:d='DAV:'>
<d:response> <d:response>
<d:href>http://www.example.com/othercontainer/C2/</d:href> <d:href>http://www.example.com/othercontainer/C2/</d:href>
<d:status>HTTP/1.1 423 Locked</d:status> <d:status>HTTP/1.1 423 Locked</d:status>
</d:response> </d:response>
Expires Aug 2003 42
WebDAV (RFC2518) bis March 2003
</d:multistatus> </d:multistatus>
In this example the client has submitted a number of lock tokens In this example the client has submitted a number of lock tokens
with the request. A lock token will need to be submitted for every with the request. A lock token will need to be submitted for every
resource, both source and destination, anywhere in the scope of the resource, both source and destination, anywhere in the scope of the
method, that is locked. In this case the proper lock token was not method, that is locked. In this case the proper lock token was not
submitted for the destination submitted for the destination
http://www.example.com/othercontainer/C2/. This means that the http://www.example.com/othercontainer/C2/. This means that the
resource /container/C2/ could not be moved. Because there was an resource /container/C2/ could not be moved. Because there was an
error moving /container/C2/, none of /container/C2's members were error moving /container/C2/, none of /container/C2's members were
moved. However no errors were listed for those members due to the moved. However no errors were listed for those members due to the
error minimization rules. User agent authentication has previously error minimization rules. User agent authentication has previously
occurred via a mechanism outside the scope of the HTTP protocol, in occurred via a mechanism outside the scope of the HTTP protocol, in
an underlying transport layer. an underlying transport layer.
8.11 LOCK Method 8.11 LOCK Method
The following sections describe the LOCK method, which is used to The following sections describe the LOCK method, which is used to
take out a lock of any access type and to refresh an existing lock. take out a lock of any access type and to refresh an existing lock.
These sections on the LOCK method describe only those semantics that These sections on the LOCK method describe only those semantics that
Expires Oct 2003 46
WebDAV (RFC2518) bis June 2003
are specific to the LOCK method and are independent of the access are specific to the LOCK method and are independent of the access
type of the lock being requested. type of the lock being requested.
Any resource which supports the LOCK method MUST, at minimum, Any resource which supports the LOCK method MUST, at minimum,
support the XML request and response formats defined herein. support the XML request and response formats defined herein.
Operation Operation
A LOCK method invocation creates the lock specified by the lockinfo A LOCK method invocation creates the lock specified by the lockinfo
XML element on the resource indicated by the Request-URI, which XML element on the resource indicated by the Request-URI, which
becomes the root of the lock. Lock method requests to create a new becomes the root of the lock. Lock method requests to create a new
lock MUST have a XML request body which contains an owner XML lock MUST have a XML request body which contains an owner XML
element for this lock request. The server MUST preserve the element for this lock request. The server MUST preserve the
information provided by the client in the owner field when the lock information provided by the client in the owner field when the lock
information is requested. The LOCK request may have a Timeout information is requested. The LOCK request MAY have a Timeout
header. header.
Clients MUST assume that locks may arbitrarily disappear at any Clients MUST assume that locks may arbitrarily disappear at any
time, regardless of the value given in the Timeout header. The time, regardless of the value given in the Timeout header. The
Timeout header only indicates the behavior of the server if Timeout header only indicates the behavior of the server if
"extraordinary" circumstances do not occur. For example, a "extraordinary" circumstances do not occur. For example, a
sufficiently privileged user may remove a lock at any time or the sufficiently privileged user may remove a lock at any time or the
system may crash in such a way that it loses the record of the system may crash in such a way that it loses the record of the
lock's existence. The response MUST contain the value of the lock's existence. The response MUST contain the value of the
lockdiscovery property in a prop XML element. lockdiscovery property in a prop XML element.
In order to indicate the lock token associated with a newly created In order to indicate the lock token associated with a newly created
lock, a Lock-Token response header MUST be included in the response lock, a Lock-Token response header MUST be included in the response
for every successful LOCK request for a new lock. Note that the for every successful LOCK request for a new lock. Note that the
Lock-Token header would not be returned in the response for a Lock-Token header would not be returned in the response for a
successful refresh LOCK request because a new lock was not created. successful refresh LOCK request because a new lock was not created.
Refreshing Locks Refreshing Locks
Expires Aug 2003 43
WebDAV (RFC2518) bis March 2003
A lock is refreshed by sending a new LOCK request to the resource A lock is refreshed by sending a new LOCK request to the resource
which is the root of the lock. A LOCK request to refresh a lock must which is the root of the lock. A LOCK request to refresh a lock must
specify which lock to refresh by using the Lock-Token header with a specify which lock to refresh by using the Lock-Token header with a
single lock token (only one lock may be refreshed at a time). This single lock token (only one lock may be refreshed at a time). This
request does not contain a body, but it may contain a Timeout request does not contain a body, but it may contain a Timeout
header. A server MAY accept the Timeout header to change the header. A server MAY accept the Timeout header to change the
duration remaining on the lock to the new value. duration remaining on the lock to the new value.
If the resource has other (shared) locks, those locks are unaffected If the resource has other (shared) locks, those locks are unaffected
by a lock refresh. Additionally, those locks do not prevent the by a lock refresh. Additionally, those locks do not prevent the
named lock from being refreshed. named lock from being refreshed.
Note that in RFC2518, clients were indicated through the example in Note that in RFC2518, clients were indicated through the example in
the text to use the If header to specify what lock to refresh the text to use the If header to specify what lock to refresh
(rather than the Lock-Token header). Servers are encouraged to (rather than the Lock-Token header). Servers are encouraged to
continue to support this as well as the Lock-Token header. continue to support this as well as the Lock-Token header.
Expires Oct 2003 47
WebDAV (RFC2518) bis June 2003
The Effect of Locks on Properties and Collections The Effect of Locks on Properties and Collections
The scope of a lock is the entire state of the resource, including The scope of a lock is the entire state of the resource, including
its body and associated properties. As a result, a lock on a its body and associated properties. As a result, a lock on a
resource MUST also lock the resource's properties. resource MUST also lock the resource's properties.
For collections, a lock also affects the ability to add or remove For collections, a lock also affects the ability to add or remove
members. The nature of the effect depends upon the type of access members. The nature of the effect depends upon the type of access
control involved. This means that if a collection is locked, its control involved. This means that if a collection is locked, its
lock-token is required in all these cases: lock-token is required in all these cases:
skipping to change at line 2379 skipping to change at line 2533
resource MUST NOT succeed if can not be honored by all the URIs resource MUST NOT succeed if can not be honored by all the URIs
through which the resource is addressable. through which the resource is addressable.
Depth and Locking Depth and Locking
The Depth header may be used with the LOCK method. Values other The Depth header may be used with the LOCK method. Values other
than 0 or infinity MUST NOT be used with the Depth header on a LOCK than 0 or infinity MUST NOT be used with the Depth header on a LOCK
method. All resources that support the LOCK method MUST support the method. All resources that support the LOCK method MUST support the
Depth header. Depth header.
Expires Aug 2003 44
WebDAV (RFC2518) bis March 2003
A Depth header of value 0 means to just lock the resource specified A Depth header of value 0 means to just lock the resource specified
by the Request-URI. by the Request-URI.
If the Depth header is set to infinity then the resource specified If the Depth header is set to infinity then the resource specified
in the Request-URI along with all its internal members, all the way in the Request-URI along with all its internal members, all the way
down the hierarchy, are to be locked. A successful result MUST down the hierarchy, are to be locked. A successful result MUST
return a single lock token which represents all the resources that return a single lock token which represents all the resources that
have been locked. If an UNLOCK is successfully executed on this have been locked. If an UNLOCK is successfully executed on this
token, all associated resources are unlocked. If the lock cannot be token, all associated resources are unlocked. If the lock cannot be
granted to all resources, a 409 (Conflict) status code MUST be granted to all resources, a 409 (Conflict) status code MUST be
returned with a response entity body containing a multistatus XML returned with a response entity body containing a multistatus XML
element describing which resource(s) prevented the lock from being element describing which resource(s) prevented the lock from being
Expires Oct 2003 48
WebDAV (RFC2518) bis June 2003
granted. Hence, partial success is not an option. Either the granted. Hence, partial success is not an option. Either the
entire hierarchy is locked or no resources are locked. entire hierarchy is locked or no resources are locked.
If no Depth header is submitted on a LOCK request then the request If no Depth header is submitted on a LOCK request then the request
MUST act as if a "Depth:infinity" had been submitted. MUST act as if a "Depth:infinity" had been submitted.
Interaction with other Methods Interaction with other Methods
The interaction of a LOCK with various methods is dependent upon the The interaction of a LOCK with various methods is dependent upon the
lock type. However, independent of lock type, a successful DELETE lock type. However, independent of lock type, a successful DELETE
of a resource MUST cause all of its locks to be removed. of a resource MUST cause all of its direct locks to be removed.
Locking Unmapped URLs Locking Unmapped URLs
A successful LOCK method MUST result in the creation of an empty A successful LOCK method MUST result in the creation of an empty
resource which is locked (and which is not a collection), when a resource which is locked (and which is not a collection), when a
resource did not previously exist at that URL. Later on, the lock resource did not previously exist at that URL. Later on, the lock
may go away but the empty resource remains. Empty resources MUST may go away but the empty resource remains. Empty resources MUST
then appear in PROPFIND responses including that URL in the response then appear in PROPFIND responses including that URL in the response
scope. A server MUST respond successfully to a GET request to an scope. A server MUST respond successfully to a GET request to an
empty resource, either by using a 204 No Content response, or by empty resource, either by using a 204 No Content response, or by
using 200 OK with a Content-Length header indicating zero length and using 200 OK with a Content-Length header indicating zero length and
an server-determined Content-Type. no Content-Type.
Lock Compatibility Table Lock Compatibility Table
The table below describes the behavior that occurs when a lock The table below describes the behavior that occurs when a lock
request is made on a resource. request is made on a resource.
Current State Shared Lock Request Exclusive Lock Request Current State Shared Lock Request Exclusive Lock Request
-------------------------------------------------------------------- --------------------------------------------------------------------
None True True None True True
Shared Lock True False Shared Lock True False
Exclusive Lock False False* Exclusive Lock False False*
Legend: True = lock may be granted. False = lock MUST NOT be Legend: True = lock may be granted. False = lock MUST NOT be
granted. *=It is illegal for a principal to request the same lock granted. *=It is illegal for a principal to request the same lock
twice. twice.
Expires Aug 2003 45
WebDAV (RFC2518) bis March 2003
The current lock state of a resource is given in the leftmost The current lock state of a resource is given in the leftmost
column, and lock requests are listed in the first row. The column, and lock requests are listed in the first row. The
intersection of a row and column gives the result of a lock request. intersection of a row and column gives the result of a lock request.
For example, if a shared lock is held on a resource, and an For example, if a shared lock is held on a resource, and an
exclusive lock is requested, the table entry is "false", indicating exclusive lock is requested, the table entry is "false", indicating
the lock must not be granted. the lock must not be granted.
Status Codes Status Codes
Expires Oct 2003 49
WebDAV (RFC2518) bis June 2003
200 (OK) - The lock request succeeded and the value of the 200 (OK) - The lock request succeeded and the value of the
lockdiscovery property is included in the body. lockdiscovery property is included in the body.
409 (Conflict) ű A resource cannot be created at the destination 409 (Conflict) ű A resource cannot be created at the destination
until one or more intermediate collections have been created. The until one or more intermediate collections have been created. The
server MUST NOT create those intermediate collections automatically. server MUST NOT create those intermediate collections automatically.
412 (Precondition Failed) - The included lock token was not 412 (Precondition Failed) - The included lock token was not
enforceable on this resource or the server could not satisfy the enforceable on this resource or the server could not satisfy the
request in the lockinfo XML element. request in the lockinfo XML element.
skipping to change at line 2487 skipping to change at line 2644
<D:owner> <D:owner>
<D:href>http://www.ics.uci.edu/~ejw/contact.html</D:href> <D:href>http://www.ics.uci.edu/~ejw/contact.html</D:href>
</D:owner> </D:owner>
</D:lockinfo> </D:lockinfo>
>>Response >>Response
HTTP/1.1 200 OK HTTP/1.1 200 OK
Lock-Token: <opaquelocktoken:e71d4fae-5dec-22d6-fea5-00a0c91e6be4> Lock-Token: <opaquelocktoken:e71d4fae-5dec-22d6-fea5-00a0c91e6be4>
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Expires Aug 2003 46
WebDAV (RFC2518) bis March 2003
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:prop xmlns:D="DAV:"> <D:prop xmlns:D="DAV:">
<D:lockdiscovery> <D:lockdiscovery>
Expires Oct 2003 50
WebDAV (RFC2518) bis June 2003
<D:activelock> <D:activelock>
<D:locktype><D:write/></D:locktype> <D:locktype><D:write/></D:locktype>
<D:lockscope><D:exclusive/></D:lockscope> <D:lockscope><D:exclusive/></D:lockscope>
<D:depth>infinity</D:depth> <D:depth>infinity</D:depth>
<D:owner> <D:owner>
<D:href> <D:href>
http://www.ics.uci.edu/~ejw/contact.html http://www.ics.uci.edu/~ejw/contact.html
</D:href> </D:href>
</D:owner> </D:owner>
<D:timeout>Second-604800</D:timeout> <D:timeout>Second-604800</D:timeout>
skipping to change at line 2538 skipping to change at line 2696
any whitespace. The line return appearing in this document is only any whitespace. The line return appearing in this document is only
for formatting. for formatting.
8.11.2 Example - Refreshing a Write Lock 8.11.2 Example - Refreshing a Write Lock
>>Request >>Request
LOCK /workspace/webdav/proposal.doc HTTP/1.1 LOCK /workspace/webdav/proposal.doc HTTP/1.1
Host: example.com Host: example.com
Timeout: Infinite, Second-4100000000 Timeout: Infinite, Second-4100000000
Lock-Token: (<opaquelocktoken:e71d4fae-5dec-22d6-fea5- Lock-Token: <opaquelocktoken:e71d4fae-5dec-22d6-fea5-00a0c91e6be4>
00a0c91e6be4>)
Expires Aug 2003 47
WebDAV (RFC2518) bis March 2003
Authorization: Digest username="ejw", Authorization: Digest username="ejw",
realm="ejw@example.com", nonce="...", realm="ejw@example.com", nonce="...",
uri="/workspace/webdav/proposal.doc", uri="/workspace/webdav/proposal.doc",
response="...", opaque="..." response="...", opaque="..."
Expires Oct 2003 51
WebDAV (RFC2518) bis June 2003
>>Response >>Response
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:prop xmlns:D="DAV:"> <D:prop xmlns:D="DAV:">
<D:lockdiscovery> <D:lockdiscovery>
<D:activelock> <D:activelock>
skipping to change at line 2593 skipping to change at line 2750
ignore the request. In this example, the nonce, response, and opaque ignore the request. In this example, the nonce, response, and opaque
fields have not been calculated in the Authorization request header. fields have not been calculated in the Authorization request header.
8.11.3 Example - Multi-Resource Lock Request 8.11.3 Example - Multi-Resource Lock Request
>>Request >>Request
LOCK /webdav/ HTTP/1.1 LOCK /webdav/ HTTP/1.1
Host: example.com Host: example.com
Timeout: Infinite, Second-4100000000 Timeout: Infinite, Second-4100000000
Depth: infinity
Expires Aug 2003 48 Expires Oct 2003 52
WebDAV (RFC2518) bis March 2003
WebDAV (RFC2518) bis June 2003
Depth: infinity
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
Authorization: Digest username="ejw", Authorization: Digest username="ejw",
realm="ejw@example.com", nonce="...", realm="ejw@example.com", nonce="...",
uri="/workspace/webdav/proposal.doc", uri="/workspace/webdav/proposal.doc",
response="...", opaque="..." response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:lockinfo xmlns:D="DAV:"> <D:lockinfo xmlns:D="DAV:">
<D:locktype><D:write/></D:locktype> <D:locktype><D:write/></D:locktype>
skipping to change at line 2644 skipping to change at line 2802
This example shows a request for an exclusive write lock on a This example shows a request for an exclusive write lock on a
collection and all its children. In this request, the client has collection and all its children. In this request, the client has
specified that it desires an infinite length lock, if available, specified that it desires an infinite length lock, if available,
otherwise a timeout of 4.1 billion seconds, if available. The otherwise a timeout of 4.1 billion seconds, if available. The
request entity body contains the contact information for the request entity body contains the contact information for the
principal taking out the lock, in this case a web page URL. principal taking out the lock, in this case a web page URL.
The error is a 403 (Forbidden) response on the resource The error is a 403 (Forbidden) response on the resource
http://example.com/webdav/secret. Because this resource could not http://example.com/webdav/secret. Because this resource could not
be locked, none of the resources were locked. Note also that the
lockdiscovery property for the Request-URI has been included as
Expires Aug 2003 49 Expires Oct 2003 53
WebDAV (RFC2518) bis March 2003
WebDAV (RFC2518) bis June 2003
be locked, none of the resources were locked. Note also that the
lockdiscovery property for the Request-URI has been included as
required. In this example the lockdiscovery property is empty which required. In this example the lockdiscovery property is empty which
means that there are no outstanding locks on the resource. means that there are no outstanding locks on the resource.
In this example, the nonce, response, and opaque fields have not In this example, the nonce, response, and opaque fields have not
been calculated in the Authorization request header. been calculated in the Authorization request header.
8.12 UNLOCK Method 8.12 UNLOCK Method
The UNLOCK method removes the lock identified by the lock token in The UNLOCK method removes the lock identified by the lock token in
the Lock-Token request header from the Request-URI and all other the Lock-Token request header from the Request-URI and all other
resources included in the lock. Any locked resource may be resources included in the lock. The root of the lock MUST be named
addressed by UNLOCK, not just the resource that the LOCK method by the Request-URI, not any other resource within the scope of the
applied to. If all resources which have been locked under the lock. Servers SHOULD redirect the UNLOCK request to the lock root.
submitted lock token can not be unlocked then the UNLOCK request Failing that, servers MAY fail an UNLOCK request to a resource that
MUST fail. is not directly locked (not the root of the lock) with error code
400 (Bad Request).
If all resources which have been locked under the submitted lock
token can not be unlocked then the UNLOCK request MUST fail.
A successful response to an UNLOCK method does not mean that the A successful response to an UNLOCK method does not mean that the
resource is unlocked. At most, it means that the specified token no resource is necessarily unlocked. It means that the specific lock
longer identifies a lock on the resource. corresponding to the specified token no longer exists.
Any DAV compliant resource which supports the LOCK method MUST Any DAV compliant resource which supports the LOCK method MUST
support the UNLOCK method. support the UNLOCK method.
Status Codes Status Codes
204 (No Content) ű Normal success response 204 (No Content) ű Normal success response
400 (Bad Request) ű No lock token was provided. 400 (Bad Request) ű No lock token was provided, or request was not
made to lock root.
412 (Precondition Failed) - The resource was not locked. 412 (Precondition Failed) - The resource was not locked.
8.12.1 Example - UNLOCK 8.12.1 Example - UNLOCK
>>Request >>Request
UNLOCK /workspace/webdav/info.doc HTTP/1.1 UNLOCK /workspace/webdav/info.doc HTTP/1.1
Host: example.com Host: example.com
Lock-Token: <opaquelocktoken:a515cfa4-5da4-22e1-f5b5-00a0451e6bf7> Lock-Token: <opaquelocktoken:a515cfa4-5da4-22e1-f5b5-00a0451e6bf7>
Authorization: Digest username="ejw", Authorization: Digest username="ejw",
realm="ejw@example.com", nonce="...", realm="ejw@example.com", nonce="...",
uri="/workspace/webdav/proposal.doc", uri="/workspace/webdav/proposal.doc",
Expires Oct 2003 54
WebDAV (RFC2518) bis June 2003
response="...", opaque="..." response="...", opaque="..."
>>Response >>Response
HTTP/1.1 204 No Content HTTP/1.1 204 No Content
In this example, the lock identified by the lock token In this example, the lock identified by the lock token
"opaquelocktoken:a515cfa4-5da4-22e1-f5b5-00a0451e6bf7" is "opaquelocktoken:a515cfa4-5da4-22e1-f5b5-00a0451e6bf7" is
successfully removed from the resource successfully removed from the resource
Expires Aug 2003 50
WebDAV (RFC2518) bis March 2003
http://example.com/workspace/webdav/info.doc. If this lock included http://example.com/workspace/webdav/info.doc. If this lock included
more than just one resource, the lock is removed from all resources more than just one resource, the lock is removed from all resources
included in the lock. The 204 (No Content) status code is used included in the lock. The 204 (No Content) status code is used
instead of 200 (OK) because there is no response entity body. instead of 200 (OK) because there is no response entity body.
In this example, the nonce, response, and opaque fields have not In this example, the nonce, response, and opaque fields have not
been calculated in the Authorization request header. been calculated in the Authorization request header.
9 HTTP Headers for Distributed Authoring 9 HTTP Headers for Distributed Authoring
skipping to change at line 2741 skipping to change at line 2906
Coded-URLs or tokens (as defined by [RFC2616]). Identifiers can Coded-URLs or tokens (as defined by [RFC2616]). Identifiers can
appear in any order. appear in any order.
A resource must show class 1 compliance if it shows class 2 or "bis" A resource must show class 1 compliance if it shows class 2 or "bis"
compliance. In general, support for one compliance class does not compliance. In general, support for one compliance class does not
entail support for any other. Please refer to section 16 for more entail support for any other. Please refer to section 16 for more
details on compliance classes defined in this specification. details on compliance classes defined in this specification.
9.2 Depth Header 9.2 Depth Header
Expires Oct 2003 55
WebDAV (RFC2518) bis June 2003
Depth = "Depth" ":" ("0" | "1" | "infinity") Depth = "Depth" ":" ("0" | "1" | "infinity")
The Depth header is used with methods executed on resources which The Depth header is used with methods executed on resources which
could potentially have internal members to indicate whether the could potentially have internal members to indicate whether the
method is to be applied only to the resource ("Depth: 0"), to the method is to be applied only to the resource ("Depth: 0"), to the
resource and its immediate children, ("Depth: 1"), or the resource resource and its immediate children, ("Depth: 1"), or the resource
and all its progeny ("Depth: infinity"). and all its progeny ("Depth: infinity").
The Depth header is only supported if a method's definition The Depth header is only supported if a method's definition
explicitly provides for such support. explicitly provides for such support.
The following rules are the default behavior for any method that The following rules are the default behavior for any method that
supports the Depth header. A method may override these defaults by supports the Depth header. A method may override these defaults by
defining different behavior in its definition. defining different behavior in its definition.
Expires Aug 2003 51
WebDAV (RFC2518) bis March 2003
Methods which support the Depth header may choose not to support all Methods which support the Depth header may choose not to support all
of the header's values and may define, on a case by case basis, the of the header's values and may define, on a case by case basis, the
behavior of the method if a Depth header is not present. For behavior of the method if a Depth header is not present. For
example, the MOVE method only supports "Depth: infinity" and if a example, the MOVE method only supports "Depth: infinity" and if a
Depth header is not present will act as if a "Depth: infinity" Depth header is not present will act as if a "Depth: infinity"
header had been applied. header had been applied.
Clients MUST NOT rely upon methods executing on members of their Clients MUST NOT rely upon methods executing on members of their
hierarchies in any particular order or on the execution being atomic hierarchies in any particular order or on the execution being atomic
unless the particular method explicitly provides such guarantees. unless the particular method explicitly provides such guarantees.
skipping to change at line 2794 skipping to change at line 2960
If a resource, source or destination, within the scope of the method If a resource, source or destination, within the scope of the method
with a Depth header is locked in such a way as to prevent the with a Depth header is locked in such a way as to prevent the
successful execution of the method, then the lock token for that successful execution of the method, then the lock token for that
resource MUST be submitted with the request in the If request resource MUST be submitted with the request in the If request
header. header.
The Depth header only specifies the behavior of the method with The Depth header only specifies the behavior of the method with
regards to internal children. If a resource does not have internal regards to internal children. If a resource does not have internal
children then the Depth header MUST be ignored. children then the Depth header MUST be ignored.
Expires Oct 2003 56
WebDAV (RFC2518) bis June 2003
Please note, however, that it is always an error to submit a value Please note, however, that it is always an error to submit a value
for the Depth header that is not allowed by the method's definition. for the Depth header that is not allowed by the method's definition.
Thus submitting a "Depth: 1" on a COPY, even if the resource does Thus submitting a "Depth: 1" on a COPY, even if the resource does
not have internal members, will result in a 400 (Bad Request). The not have internal members, will result in a 400 (Bad Request). The
method should fail not because the resource doesn't have internal method should fail not because the resource doesn't have internal
members, but because of the illegal value in the header. members, but because of the illegal value in the header.
9.3 Destination Header 9.3 Destination Header
Destination = "Destination" ":" ( absoluteURI | abs_path ) Destination = "Destination" ":" ( absoluteURI | abs_path )
The Destination header specifies the URI which identifies a The Destination header specifies the URI which identifies a
destination resource for methods such as COPY and MOVE, which take destination resource for methods such as COPY and MOVE, which take
two URIs as parameters. Note that the absoluteURI and abs_path two URIs as parameters. Note that the absoluteURI and abs_path
production are defined in [RFC2396]. If abs_path is used, the production are defined in [RFC2396]. If abs_path is used, the
scheme, host and port of the destination are the same as those for scheme, host and port of the destination are the same as those for
Expires Aug 2003 52
WebDAV (RFC2518) bis March 2003
the Request-URI (note the Host header, which must be present on the Request-URI (note the Host header, which must be present on
requests, contains the host and port). requests, contains the host and port).
If the Destination value is an absolute URI, it may name a different If the Destination value is an absolute URI, it may name a different
server (or different port or scheme). If the source server cannot server (or different port or scheme). If the source server cannot
attempt a copy to the remote server, it MUST fail the request with a attempt a copy to the remote server, it MUST fail the request with a
502 (Bad Gateway) response. 502 (Bad Gateway) response.
9.4 Force-Authentication Header 9.4 Force-Authentication Header
Force-Authentication = "Force-Authentication" ":" Method Force-Authentication = "Force-Authentication" ":" Method
The Force-Authentication header is used with the OPTIONS method to The Force-Authentication header is used with the OPTIONS method to
specify that the client wants to be challenged for authentication specify that the client wants to be challenged for authentication
credentials to the resource identified by the Request-URI. If credentials to the resource identified by the Request-URI. If
present, a compliant DAV server MUST respond with either 401 present on a request to a WebDAV-compliant resource, the server MUST
(Unauthorized) or 501 (Not Implemented) status code. The Method respond with either 401 (Unauthorized) or 501 (Not Implemented)
value is used for the client to indicate what method it intends to status code. The Method value is used for the client to indicate
use first on the resource identified in the Request-URI. what method it intends to use first on the resource identified in
the Request-URI.
9.5 If Header 9.5 If Header
If = "If" ":" ( 1*No-tag-list | 1*Tagged-list) If = "If" ":" ( 1*No-tag-list | 1*Tagged-list)
No-tag-list = List No-tag-list = List
Tagged-list = Resource 1*List Tagged-list = Resource 1*List
Resource = Coded-URL Resource = Coded-URL
List = "(" 1*(["Not"](State-token | "[" entity-tag "]")) ")" List = "(" 1*(["Not"](State-token | "[" entity-tag "]")) ")"
State-token = Coded-URL | "<no-lock>" State-token = Coded-URL | "<DAV:no-lock>"
Coded-URL = "<" absoluteURI ">" Coded-URL = "<" absoluteURI ">"
Expires Oct 2003 57
WebDAV (RFC2518) bis June 2003
The If header is intended to have similar functionality to the If- The If header is intended to have similar functionality to the If-
Match header defined in section 14.24 of [RFC2616]. However the If Match header defined in section 14.24 of [RFC2616]. However the If
header is intended for use with any URI which represents state header is intended for use with any URI which represents state
information, referred to as a state token, about a resource as well information, referred to as a state token, about a resource as well
as ETags. A typical example of a state token is a lock token, and as ETags. A typical example of a state token is a lock token, and
lock tokens are the only state tokens defined in this specification. lock tokens are the only state tokens defined in this specification.
The <no-lock> state token is a token that must never match an actual The <DAV:no-lock> state token is a token that must never match an
valid lock token. The purpose of this is described in section 9.5.5. actual valid lock token. The purpose of this is described in section
9.5.5.
The If header's purpose is to describe a series of state lists. If The If header's purpose is to describe a series of state lists. If
the state of the resource to which the header is applied does not the state of the resource to which the header is applied does not
match any of the specified state lists then the request MUST fail match any of the specified state lists then the request MUST fail
with a 412 (Precondition Failed). If one of the described state with a 412 (Precondition Failed). If one of the described state
lists matches the state of the resource then the request may lists matches the state of the resource then the request may
succeed. succeed.
The server must parse the If header when it appears on any request, The server must parse the If header when it appears on any request,
evaluate all the clauses, and if the conditional evaluates to false, evaluate all the clauses, and if the conditional evaluates to false,
fail the request. fail the request.
Expires Aug 2003 53
WebDAV (RFC2518) bis March 2003
Note that the absoluteURI production is defined in [RFC2396]. Note that the absoluteURI production is defined in [RFC2396].
RFC2518 originally defined the If header without comma separators. RFC2518 originally defined the If header without comma separators.
This oversight meant that the If header couldn't be divided up among This oversight meant that the If header couldn't be divided up among
multiple lines according to the HTTP header manipulation rules. multiple lines according to the HTTP header manipulation rules.
Servers supporting "bis" MUST be able to accept commas in If header Servers supporting "bis" MUST be able to accept commas in If header
values. If the header has commas between tokens or clauses, the values. If the header has commas between tokens or clauses, the
header can be evaluated simply by removing the commas and proceeding header can be evaluated simply by removing the commas and proceeding
with the evaluation rules. with the evaluation rules.
9.5.1 No-tag-list Production 9.5.1 No-tag-list Production
The No-tag-list production describes a series of state tokens and The No-tag-list production describes a series of state tokens and
ETags. If multiple No-tag-list productions are used then one only ETags. If multiple No-tag-list productions are used then one only
needs to match the state of the resource for the method to be needs to match the state of the resource for the method to be
allowed to continue. All untagged tokens apply to the resource allowed to continue. All untagged tokens apply to the resource
identified in the Request-URI. identified in the Request-URI.
9.5.2 Example - No-tag-list If Header 9.5.2 Example - No-tag-list If Header
If: (<locktoken:a-write-lock-token> ["I am an ETag"]) (["I am If: (<opaquelocktoken:a-write-lock-token> ["I am an ETag"]), (["I
another ETag"]) am another ETag"])
The previous header would require that the resource identified in The previous header would require that the resource identified in
the Request-URI be locked with the specified lock token and in the the Request-URI be locked with the specified lock token and in the
state identified by the "I am an ETag" ETag or in the state state identified by the "I am an ETag" ETag or in the state
identified by the second ETag "I am another ETag". To put the identified by the second ETag "I am another ETag". To put the
matter more plainly one can think of the previous If header as being matter more plainly one can think of the previous If header as being
in the form (or (and <locktoken:a-write-lock-token> ["I am an
Expires Oct 2003 58
WebDAV (RFC2518) bis June 2003
in the form (or (and <opaquelocktoken:a-write-lock-token> ["I am an
ETag"]) (and ["I am another ETag"])). ETag"]) (and ["I am another ETag"])).
9.5.3 Tagged-list Production 9.5.3 Tagged-list Production
The tagged-list production scopes a list production. That is, it The tagged-list production scopes a list production. That is, it
specifies that the lists following the resource specification only specifies that the lists following the resource specification only
apply to the specified resource. The scope of the resource apply to the specified resource. The scope of the resource
production begins with the list production immediately following the production begins with the list production immediately following the
resource production and ends with the next resource production, if resource production and ends with the next resource production, if
any. All clauses must be evaluated. any. All clauses must be evaluated.
The same URI MUST NOT appear more than once in a resource production The same URI MUST NOT appear more than once in a resource production
in an If header. in an If header.
9.5.4 Example - Tagged List If header 9.5.4 Example - Tagged List If header
COPY /resource1 HTTP/1.1 COPY /resource1 HTTP/1.1
Host: www.example.com Host: www.example.com
Destination: http://www.example.com/resource2 Destination: http://www.example.com/resource2
If: <http://www.example.com/resource1> (<locktoken:a-write-lock- If: <http://www.example.com/resource1> (<locktoken:a-write-lock-
token> [W/"A weak ETag"]) (["strong ETag"]) token> [W/"A weak ETag"]), (["strong ETag"]),
<http://www.bar.bar/random>(["another strong ETag"]) <http://www.bar.bar/random>(["another strong ETag"])
Expires Aug 2003 54
WebDAV (RFC2518) bis March 2003
In this example http://www.example.com/resource1 is being copied to In this example http://www.example.com/resource1 is being copied to
http://www.example.com/resource2. When the method is first applied http://www.example.com/resource2. When the method is first applied
to http://www.example.com/resource1, resource1 must be in the state to http://www.example.com/resource1, resource1 must be in the state
specified by "(<locktoken:a-write-lock-token> [W/"A weak ETag"]) specified by "(<locktoken:a-write-lock-token> [W/"A weak ETag"])
(["strong ETag"])", that is, it either must be locked with a lock (["strong ETag"])", that is, it either must be locked with a lock
token of "locktoken:a-write-lock-token" and have a weak entity tag token of "locktoken:a-write-lock-token" and have a weak entity tag
W/"A weak ETag" or it must have a strong entity tag "strong ETag". W/"A weak ETag" or it must have a strong entity tag "strong ETag".
That is the only success condition since the resource That is the only success condition since the resource
http://www.bar.bar/random never has the method applied to it (the http://www.bar.bar/random never has the method applied to it (the
only other resource listed in the If header) and only other resource listed in the If header) and
http://www.example.com/resource2 is not listed in the If header. http://www.example.com/resource2 is not listed in the If header.
9.5.5 Not Production 9.5.5 Not Production
Every state token or ETag is either current, and hence describes the Every state token or ETag is either current, and hence describes the
state of a resource, or is not current, and does not describe the state of a resource, or is not current, and does not describe the
state of a resource. The boolean operation of matching a state token state of a resource. The boolean operation of matching a state token
or ETag to the current state of a resource thus resolves to a true or ETag to the current state of a resource thus resolves to a true
or false value. The not production is used to reverse that value. or false value. The ŠNotĂ production is used to reverse that value.
The scope of the not production is the state-token or entity-tag The scope of the not production is the state-token or entity-tag
immediately following it. immediately following it.
If: (Not <locktoken:write1> <locktoken:write2>) If: (Not <locktoken:write1> <locktoken:write2>)
Expires Oct 2003 59
WebDAV (RFC2518) bis June 2003
When submitted with a request, this If header requires that all When submitted with a request, this If header requires that all
operand resources must not be locked with locktoken:write1 and must operand resources must not be locked with locktoken:write1 and must
be locked with locktoken:write2. be locked with locktoken:write2.
The Not production is particularly useful with the "<no-lock>" state The Not production is particularly useful with the "<DAV:no-lock>"
token defined. The clause "Not <no-lock>" must evaluate to true. state token defined. The clause "Not <DAV:no-lock>" must evaluate to
Thus, any "OR" statement containing the clause "Not <no-lock> must true. Thus, any "OR" statement containing the clause "Not <DAV:no-
also evaluate to true. lock> must also evaluate to true.
9.5.6 Matching Function 9.5.6 Matching Function
When performing If header processing, the definition of a matching When performing If header processing, the definition of a matching
state token or entity tag is as follows. state token or entity tag is as follows.
Matching entity tag: Where the entity tag matches an entity tag Matching entity tag: Where the entity tag matches an entity tag
associated with that resource. associated with that resource.
Matching state token: Where there is an exact match between the Matching state token: Where there is an exact match between the
state token in the If header and any state token on the resource. state token in the If header and any state token on the resource.
9.5.7 If Header and Non-DAV Compliant Proxies 9.5.7 If Header and Non-DAV Aware Proxies
Non-DAV compliant proxies will not honor the If header, since they Non-DAV aware proxies will not honor the If header, since they will
will not understand the If header, and HTTP requires non-understood not understand the If header, and HTTP requires non-understood
headers to be ignored. When communicating with HTTP/1.1 proxies, headers to be ignored. When communicating with HTTP/1.1 proxies,
the "Cache-Control: no-cache" request header MUST be used so as to the "Cache-Control: no-cache" request header MUST be used so as to
prevent the proxy from improperly trying to service the request from prevent the proxy from improperly trying to service the request from
Expires Aug 2003 55
WebDAV (RFC2518) bis March 2003
its cache. When dealing with HTTP/1.0 proxies the "Pragma: no- its cache. When dealing with HTTP/1.0 proxies the "Pragma: no-
cache" request header MUST be used for the same reason. cache" request header MUST be used for the same reason.
9.6 Lock-Token Header 9.6 Lock-Token Header
Lock-Token = "Lock-Token" ":" Coded-URL Lock-Token = "Lock-Token" ":" Coded-URL
The Lock-Token request header is used with the UNLOCK method to The Lock-Token request header is used with the UNLOCK method to
identify the lock to be removed. The lock token in the Lock-Token identify the lock to be removed. The lock token in the Lock-Token
request header MUST identify a lock that contains the resource request header MUST identify a lock that contains the resource
skipping to change at line 3001 skipping to change at line 3172
indicate the lock token created as a result of a successful LOCK indicate the lock token created as a result of a successful LOCK
request to create a new lock. request to create a new lock.
9.7 Overwrite Header 9.7 Overwrite Header
Overwrite = "Overwrite" ":" ("T" | "F") Overwrite = "Overwrite" ":" ("T" | "F")
The Overwrite header specifies whether the server should overwrite The Overwrite header specifies whether the server should overwrite
the state of a non-null destination resource during a COPY or MOVE. the state of a non-null destination resource during a COPY or MOVE.
A value of "F" states that the server must not perform the COPY or A value of "F" states that the server must not perform the COPY or
Expires Oct 2003 60
WebDAV (RFC2518) bis June 2003
MOVE operation if the state of the destination resource is non-null. MOVE operation if the state of the destination resource is non-null.
If the overwrite header is not included in a COPY or MOVE request If the overwrite header is not included in a COPY or MOVE request
then the resource MUST treat the request as if it has an overwrite then the resource MUST treat the request as if it has an overwrite
header of value "T". While the Overwrite header appears to duplicate header of value "T". While the Overwrite header appears to duplicate
the functionality of the If-Match: * header of HTTP/1.1, If-Match the functionality of the If-Match: * header of HTTP/1.1, If-Match
applies only to the Request-URI, and not to the Destination of a applies only to the Request-URI, and not to the Destination of a
COPY or MOVE. COPY or MOVE.
If a COPY or MOVE is not performed due to the value of the Overwrite If a COPY or MOVE is not performed due to the value of the Overwrite
header, the method MUST fail with a 412 (Precondition Failed) status header, the method MUST fail with a 412 (Precondition Failed) status
skipping to change at line 3031 skipping to change at line 3207
is defined in 6.1.1 of [RFC2616] is defined in 6.1.1 of [RFC2616]
The URIs listed in the header are source resources which have been The URIs listed in the header are source resources which have been
affected by the outstanding method. The status code indicates the affected by the outstanding method. The status code indicates the
resolution of the method on the identified resource. So, for resolution of the method on the identified resource. So, for
example, if a MOVE method on a collection is outstanding and a 102 example, if a MOVE method on a collection is outstanding and a 102
(Processing) response with a Status-URI response header is returned, (Processing) response with a Status-URI response header is returned,
the included URIs will indicate resources that have had move the included URIs will indicate resources that have had move
attempted on them and what the result was. attempted on them and what the result was.
Expires Aug 2003 56
WebDAV (RFC2518) bis March 2003
9.9 Timeout Request Header 9.9 Timeout Request Header
TimeOut = "Timeout" ":" 1#TimeType TimeOut = "Timeout" ":" 1#TimeType
TimeType = ("Second-" DAVTimeOutVal | "Infinite") TimeType = ("Second-" DAVTimeOutVal | "Infinite")
DAVTimeOutVal = 1*digit DAVTimeOutVal = 1*digit
Clients may include Timeout headers in their LOCK requests. Clients may include Timeout headers in their LOCK requests.
However, the server is not required to honor or even consider these However, the server is not required to honor or even consider these
requests. Clients MUST NOT submit a Timeout request header with any requests. Clients MUST NOT submit a Timeout request header with any
method other than a LOCK method. method other than a LOCK method.
Timeout response values MUST use a Second value or Infinite. Timeout response values MUST use a Second value or Infinite.
The "Second" TimeType specifies the number of seconds that will The "Second" TimeType specifies the number of seconds that will
elapse between granting of the lock at the server, and the automatic elapse between granting of the lock at the server, and the automatic
removal of the lock. The timeout value for TimeType "Second" MUST removal of the lock. The timeout value for TimeType "Second" MUST
NOT be greater than 2^32-1. NOT be greater than 2^32-1.
Expires Oct 2003 61
WebDAV (RFC2518) bis June 2003
The timeout counter MUST be restarted if a refresh LOCK request is The timeout counter MUST be restarted if a refresh LOCK request is
successful. The timeout counter SHOULD NOT be restarted at any successful. The timeout counter SHOULD NOT be restarted at any
other time. other time.
If the timeout expires then the lock may be lost. Specifically, if If the timeout expires then the lock may be lost. Specifically, if
the server wishes to harvest the lock upon time-out, the server the server wishes to harvest the lock upon time-out, the server
SHOULD act as if an UNLOCK method was executed by the server on the SHOULD act as if an UNLOCK method was executed by the server on the
resource using the lock token of the timed-out lock, performed with resource using the lock token of the timed-out lock, performed with
its override authority. Thus logs should be updated with the its override authority. Thus logs should be updated with the
disposition of the lock, notifications should be sent, etc., just as disposition of the lock, notifications should be sent, etc., just as
skipping to change at line 3085 skipping to change at line 3262
A client MUST NOT assume that just because the time-out has expired A client MUST NOT assume that just because the time-out has expired
the lock has been lost. Likewise, a client MUST NOT assume that just the lock has been lost. Likewise, a client MUST NOT assume that just
because the time-out has not expired, the lock still exists (and for because the time-out has not expired, the lock still exists (and for
this reason, clients are strongly advised to use ETags as well). this reason, clients are strongly advised to use ETags as well).
10 Status Code Extensions to HTTP/1.1 10 Status Code Extensions to HTTP/1.1
The following status codes are added to those defined in HTTP/1.1 The following status codes are added to those defined in HTTP/1.1
[RFC2616]. [RFC2616].
Expires Aug 2003 57
WebDAV (RFC2518) bis March 2003
10.1 102 Processing 10.1 102 Processing
The 102 (Processing) status code is an interim response used to The 102 (Processing) status code is an interim response used to
inform the client that the server has accepted the complete request, inform the client that the server has accepted the complete request,
but has not yet completed it. This status code SHOULD only be sent but has not yet completed it. This status code SHOULD only be sent
when the server has a reasonable expectation that the request will when the server has a reasonable expectation that the request will
take significant time to complete. As guidance, if a method is take significant time to complete. As guidance, if a method is
taking longer than 20 seconds (a reasonable, but arbitrary value) to taking longer than 20 seconds (a reasonable, but arbitrary value) to
process the server SHOULD return a 102 (Processing) response. The process the server SHOULD return a 102 (Processing) response. The
server MUST send a final response after the request has been server MUST send a final response after the request has been
completed. completed.
Methods can potentially take a long period of time to process, Methods can potentially take a long period of time to process,
especially methods that support the Depth header. In such cases the especially methods that support the Depth header. In such cases the
client may time-out the connection while waiting for a response. To client may time-out the connection while waiting for a response. To
Expires Oct 2003 62
WebDAV (RFC2518) bis June 2003
prevent this the server may return a 102 (Processing) status code to prevent this the server may return a 102 (Processing) status code to
indicate to the client that the server is still processing the indicate to the client that the server is still processing the
method. method.
10.2 207 Multi-Status 10.2 207 Multi-Status
The 207 (Multi-Status) status code provides status for multiple The 207 (Multi-Status) status code provides status for multiple
independent operations (see section 12 for more information). independent operations (see section 12 for more information).
10.3 422 Unprocessable Entity 10.3 422 Unprocessable Entity
skipping to change at line 3141 skipping to change at line 3320
not be performed on the resource because the requested action not be performed on the resource because the requested action
depended on another action and that action failed. For example, if depended on another action and that action failed. For example, if
a command in a PROPPATCH method fails then, at minimum, the rest of a command in a PROPPATCH method fails then, at minimum, the rest of
the commands will also fail with 424 (Failed Dependency). the commands will also fail with 424 (Failed Dependency).
10.6 507 Insufficient Storage 10.6 507 Insufficient Storage
The 507 (Insufficient Storage) status code means the method could The 507 (Insufficient Storage) status code means the method could
not be performed on the resource because the server is unable to not be performed on the resource because the server is unable to
store the representation needed to successfully complete the store the representation needed to successfully complete the
Expires Aug 2003 58
WebDAV (RFC2518) bis March 2003
request. This condition is considered to be temporary. If the request. This condition is considered to be temporary. If the
request which received this status code was the result of a user request which received this status code was the result of a user
action, the request MUST NOT be repeated until it is requested by a action, the request MUST NOT be repeated until it is requested by a
separate user action. separate user action.
11 Use of HTTP Status Codes 11 Use of HTTP Status Codes
11.1 301 Moved Permanently 11.1 301 Moved Permanently
Any WebDAV request may be redirected using this status code. Any WebDAV request may be redirected using this status code.
Expires Oct 2003 63
WebDAV (RFC2518) bis June 2003
11.2 302 Found 11.2 302 Found
Any WebDAV request may be redirected using this status code. Any WebDAV request may be redirected using this status code.
11.3 400 Bad Request 11.3 400 Bad Request
This code may be used if: This code may be used if:
- the Host header is missing in any request - the Host header is missing in any request
- The protocol version is HTTP/1.0 - The protocol version is HTTP/1.0
- Any header is improperly formatted - Any header is improperly formatted
- The request method line is improperly formatted - The request method line is improperly formatted
11.4 403 Forbidden 11.4 403 Forbidden
Uses: Uses:
- The server does not ever accept this method on this kind of - The server does not ever accept this method on this kind of
resource. For example, a PUT is not accepted on a collection. resource. For example, if a PUT is not accepted on a collection.
11.5 409 Conflict 11.5 409 Conflict
The 409 Conflict is most typically returned when a method that The 409 Conflict is most typically returned when a method that
attempts to create a new resource must fail, because one of the attempts to create a new resource must fail, because one of the
collections that resource depends on does not exist. Therefore, collections that resource depends on does not exist. However, other
this can be returned in response to a PUT request as well as the types of conflicts are defined in specifications extending RFC2518.
WebDAV methods that create resources. Therefore, this can be returned in response to all methods.
11.6 414 Request-URI Too Long 11.6 414 Request-URI Too Long
This status code is used in HTTP 1.1 only for Request-URIs, because This status code is used in HTTP 1.1 only for Request-URIs, because
full URIs arenĂt used in other headers. WebDAV specifies full URLs full URIs arenĂt used in other headers. WebDAV specifies full URLs
in other headers, therefore this error may be used if the URI is too in other headers, therefore this error may be used if the URI is too
long in other locations as well. This status code may be used in long in other locations as well. This status code may be used in
response to any method in this specification. response to any method in this specification.
12 Multi-Status Response 12 Multi-Status Response
The default 207 (Multi-Status) response body is a text/xml or The default 207 (Multi-Status) response body is a text/xml or
application/xml HTTP entity that contains a single XML element application/xml HTTP entity that contains a single XML element
called multistatus, which contains a set of XML elements called called multistatus, which contains a set of XML elements called
Expires Aug 2003 59
WebDAV (RFC2518) bis March 2003
response which contain 200, 300, 400, and 500 series status codes response which contain 200, 300, 400, and 500 series status codes
generated during the method invocation. 100 series status codes generated during the method invocation. 100 series status codes
SHOULD NOT be recorded in a response XML element. The 207 status SHOULD NOT be recorded in a response XML element. The 207 status
code itself MUST NOT be considered a success response, it is only code itself MUST NOT be considered a success response, it is only
completely successful if all response elements inside contain completely successful if all response elements inside contain
success status codes. success status codes.
The body of a 207 Multi-Status response MUST contain a URL The body of a 207 Multi-Status response MUST contain a URL
associated with each specific status code, so that the client can associated with each specific status code, so that the client can
Expires Oct 2003 64
WebDAV (RFC2518) bis June 2003
tell whether the error occurred with the source resource, tell whether the error occurred with the source resource,
destination resource or some other resource in the scope of the destination resource or some other resource in the scope of the
request. URLs for collections appearing in the results SHOULD end in request. URLs for collections appearing in the results SHOULD end in
a Š/Ă character. a Š/Ă character.
When a Multi-Status response does not have a clear scope (e.g. in When a Multi-Status response does not have a clear scope (e.g. in
response to MOVE or COPY when the scope could be either the source response to MOVE or COPY when the scope could be either the source
or the destination), URLs appearing in the response body SHOULD be or the destination), URLs appearing in the response body SHOULD be
absolute and fully-qualified URLs. absolute and fully-qualified URLs.
When a Multi-Status response does have a clear scope, especially in When a Multi-Status response does have a clear scope, especially in
response to a PROPFIND request when all URLs appearing in the body response to a PROPFIND request when all URLs appearing in the body
must be inside the collection named in the request-URI, the URLs MAY must be inside the collection named in the request-URI, the URLs MAY
be absolute or MAY be relative. be absolute or MAY be relative.
- If the URLs are absolute, then the server MUST ensure that the - If the URLs are absolute, then the server MUST ensure that the
URLs have the same prefix (scheme, host, port, and path) as the URL URLs have the same prefix (scheme, host, port, and path) as the URL
of the requested collection (which may be the same as the Request- of the requested collection (which may be the same as the Request-
URI or may be the corrected in the response Location header). URI or may be the corrected in the response Location header).
- If the URLs are relative, they MUST contain only the elements of - If the URLs are relative, they MUST be resolved against the
the path that can be simply concatenated with the queried Location header, if present, or as second choice against the
collectionĂs correct URL in order to make a complete and correct Request-URI.
URL. The client MUST use the the Location header value as base URL
if present, otherwise the request-URI (of the requested collection).
12.1 302 and 303 in Multi-Status 12.1 Responses requiring Location in Multi-Status
When the 302 and 303 status codes are returned as the only status The 300-303, 305 and 307 responses defined in HTTP 1.1 normally take
code for a response, HTTP1.1 uses the Location response header to a Location header to indicate where the client should make the
indicate where the client should make the request. The Multi-Status request. The Multi-Status response syntax does not allow for the
response syntax does not allow for the Location header information Location header information to be included in an unambiguous way, so
to be included in an unambiguous way, so servers MAY choose not to servers MAY choose not to use these status codes in Multi-Status
use these status codes in Multi-Status responses. If a clients responses. If a clients receives this status code in Multi-Status,
receives this status code in Multi-Status, the client MAY reissue the client MAY reissue the request to the individual resource, so
the request to the individual resource, so that the server can issue that the server can issue a response with a Location header for each
a response with a Location header for each resource. resource.
13 XML Element Definitions 13 XML Element Definitions
In the section below, the final line of each section gives the In the section below, the final line of each section gives the
element type declaration using the format defined in [REC-XML]. The element type declaration using the format defined in [REC-XML]. The
"Value" field, where present, specifies further restrictions on the "Value" field, where present, specifies further restrictions on the
allowable contents of the XML element using BNF (i.e., to further allowable contents of the XML element using BNF (i.e., to further
restrict the values of a PCDATA element). restrict the values of a PCDATA element).
Expires Aug 2003 60 All of the elements defined here may be extended by the addition of
WebDAV (RFC2518) bis March 2003 attributes and child elements not defined in this specification.
13.1 activelock XML Element 13.1 activelock XML Element
Name: activelock Name: activelock
Namespace: DAV: Namespace: DAV:
Expires Oct 2003 65
WebDAV (RFC2518) bis June 2003
Purpose: Describes a lock on a resource. Purpose: Describes a lock on a resource.
<!ELEMENT activelock ANY> <!ELEMENT activelock ANY>
ANY value: Any number of elements, including one of each of ANY value: Any number of elements, including one of each of
(lockscope, locktype, depth, owner, timeout, locktoken, lockroot) (lockscope, locktype, depth, owner, timeout, locktoken, lockroot)
13.2 depth XML Element 13.2 depth XML Element
Name: depth Name: depth
Namespace: DAV: Namespace: DAV:
skipping to change at line 3303 skipping to change at line 3486
lockdiscovery property values and the response to LOCK lockdiscovery property values and the response to LOCK
requests. requests.
<!ELEMENT lockroot (href) > <!ELEMENT lockroot (href) >
13.5 timeout XML Element 13.5 timeout XML Element
Name: timeout Name: timeout
Namespace: DAV: Namespace: DAV:
Purpose: The number of seconds remaining before a lock expires. Purpose: The number of seconds remaining before a lock expires.
Value: TimeType ;Defined in section 9.9.
Expires Aug 2003 61 Expires Oct 2003 66
WebDAV (RFC2518) bis March 2003
Value: TimeType ;Defined in section 9.9. WebDAV (RFC2518) bis June 2003
<!ELEMENT timeout (#PCDATA) > <!ELEMENT timeout (#PCDATA) >
13.6 collection XML Element 13.6 collection XML Element
Name: collection Name: collection
Namespace: DAV: Namespace: DAV:
Purpose: Identifies the associated resource as a collection. The Purpose: Identifies the associated resource as a collection. The
resourcetype property of a collection resource MUST have resourcetype property of a collection resource MUST have
this value. It is normally empty but extensions may add this value. It is normally empty but extensions may add
skipping to change at line 3355 skipping to change at line 3538
Namespace: DAV: Namespace: DAV:
Purpose: The lockinfo XML element is used with a LOCK method to Purpose: The lockinfo XML element is used with a LOCK method to
specify the type of lock the client wishes to have created. specify the type of lock the client wishes to have created.
<!ELEMENT lockinfo ANY > <!ELEMENT lockinfo ANY >
ANY value: any number of elements, including one of each of ANY value: any number of elements, including one of each of
(lockscope, locktype), and optionally including the owner element. (lockscope, locktype), and optionally including the owner element.
13.10 lockscope XML Element 13.10 lockscope XML Element
Name: lockscope Expires Oct 2003 67
Expires Aug 2003 62 WebDAV (RFC2518) bis June 2003
WebDAV (RFC2518) bis March 2003
Name: lockscope
Namespace: DAV: Namespace: DAV:
Purpose: Specifies whether a lock is an exclusive lock, or a shared Purpose: Specifies whether a lock is an exclusive lock, or a shared
lock. lock.
<!ELEMENT lockscope (exclusive | shared) > <!ELEMENT lockscope (exclusive | shared) >
13.11 exclusive XML Element 13.11 exclusive XML Element
Name: exclusive Name: exclusive
Namespace: DAV: Namespace: DAV:
skipping to change at line 3406 skipping to change at line 3589
Namespace: DAV: Namespace: DAV:
Purpose: Specifies a write lock. Purpose: Specifies a write lock.
<!ELEMENT write EMPTY > <!ELEMENT write EMPTY >
13.15 multistatus XML Element 13.15 multistatus XML Element
Name: multistatus Name: multistatus
Namespace: DAV: Namespace: DAV:
Purpose: Contains multiple response messages. Purpose: Contains multiple response messages.
Expires Oct 2003 68
WebDAV (RFC2518) bis June 2003
Description: The responsedescription at the top level is Description: The responsedescription at the top level is
used to provide a general message describing the used to provide a general message describing the
overarching nature of the response. If this value is overarching nature of the response. If this value is
Expires Aug 2003 63
WebDAV (RFC2518) bis March 2003
available an application may use it instead of presenting available an application may use it instead of presenting
the individual response descriptions contained within the the individual response descriptions contained within the
responses. responses.
<!ELEMENT multistatus ANY > <!ELEMENT multistatus ANY >
ANY value: At least one response element, and zero or more ANY value: At least one response element, and zero or more
responsedescription elements, plus other elements not defined in responsedescription elements.
this document.
13.16 response XML Element 13.16 response XML Element
Name: response Name: response
Namespace: DAV: Namespace: DAV:
Purpose: Holds a single response describing the effect of a method Purpose: Holds a single response describing the effect of a method
on resource and/or its properties. on resource and/or its properties.
Description: A particular href MUST NOT appear more than Description: A particular href MUST NOT appear more than
once as the child of a response XML element under a once as the child of a response XML element under a
multistatus XML element. This requirement is necessary in multistatus XML element. This requirement is necessary in
order to keep processing costs for a response to linear order to keep processing costs for a response to linear
time. Essentially, this prevents having to search in order time. Essentially, this prevents having to search in order
to group together all the responses by href. There are, to group together all the responses by href. There are,
however, no requirements regarding ordering based on href however, no requirements regarding ordering based on href
values. values.
<!ELEMENT response ANY > <!ELEMENT response ANY >
ANY value: MUST contain an href element. MUST contain a status ANY value: MUST contain an href element. MUST contain a status
element or a propstat element. MAY contain a responsedescription element or a propstat element. MAY contain a responsedescription
element. May contain additional elements not defined in this element.
document.
13.17 propstat XML Element 13.17 propstat XML Element
Name: propstat Name: propstat
Namespace: DAV: Namespace: DAV:
Purpose: Groups together a prop and status element that is Purpose: Groups together a prop and status element that is
associated with a particular href element. associated with a particular href element.
Description: The propstat XML element MUST contain one prop Description: The propstat XML element MUST contain one prop
XML element and one status XML element. The contents of XML element and one status XML element. The contents of
the prop XML element MUST only list the names of properties the prop XML element MUST only list the names of properties
to which the result in the status element applies. to which the result in the status element applies.
<!ELEMENT propstat ANY > <!ELEMENT propstat ANY >
ANY value: Contains one of each of (prop, status) and may contain a ANY value: Contains one of each of (prop, status) and may contain a
responsedescription element. May also contain elements not defined responsedescription element.
in this document.
13.18 status XML Element Expires Oct 2003 69
Name: status WebDAV (RFC2518) bis June 2003
Expires Aug 2003 64 13.18 status XML Element
WebDAV (RFC2518) bis March 2003
Name: status
Namespace: DAV: Namespace: DAV:
Purpose: Holds a single HTTP status-line Purpose: Holds a single HTTP status-line
Value: status-line ;status-line defined in [RFC2616] Value: status-line ;status-line defined in [RFC2616]
<!ELEMENT status (#PCDATA) > <!ELEMENT status (#PCDATA) >
13.19 responsedescription XML Element 13.19 responsedescription XML Element
Name: responsedescription Name: responsedescription
Namespace: DAV: Namespace: DAV:
skipping to change at line 3510 skipping to change at line 3691
Description: The prop XML element is a generic container for Description: The prop XML element is a generic container for
properties defined on resources. All elements inside a properties defined on resources. All elements inside a
prop XML element MUST define properties related to the prop XML element MUST define properties related to the
resource. No other elements may be used inside of a prop resource. No other elements may be used inside of a prop
element. element.
<!ELEMENT prop ANY> <!ELEMENT prop ANY>
13.22 propertyupdate XML element 13.22 propertyupdate XML element
Expires Oct 2003 70
WebDAV (RFC2518) bis June 2003
Name: propertyupdate Name: propertyupdate
Namespace: DAV: Namespace: DAV:
Purpose: Contains a request to alter the properties on a resource. Purpose: Contains a request to alter the properties on a resource.
Expires Aug 2003 65
WebDAV (RFC2518) bis March 2003
Description: This XML element is a container for the Description: This XML element is a container for the
information required to modify the properties on the information required to modify the properties on the
resource. This XML element is multi-valued. resource. This XML element is multi-valued.
<!ELEMENT propertyupdate ANY > <!ELEMENT propertyupdate ANY >
ANY value: Must contain at least one remove or set element. May ANY value: Must contain at least one remove or set element. May
contain any number of remove and set elements. May contain contain any number of remove and set elements.
additional elements not defined in this document.
13.23 remove XML element 13.23 remove XML element
Name: remove Name: remove
Namespace: DAV: Namespace: DAV:
Purpose: Lists the DAV properties to be removed from a resource. Purpose: Lists the DAV properties to be removed from a resource.
Description: Remove instructs that the properties specified Description: Remove instructs that the properties specified
in prop should be removed. Specifying the removal of a in prop should be removed. Specifying the removal of a
property that does not exist is not an error. All the XML property that does not exist is not an error. All the XML
elements in a prop XML element inside of a remove XML elements in a prop XML element inside of a remove XML
skipping to change at line 3550 skipping to change at line 3730
13.24 set XML element 13.24 set XML element
Name: set Name: set
Namespace: DAV: Namespace: DAV:
Purpose: Lists the DAV property values to be set for a resource. Purpose: Lists the DAV property values to be set for a resource.
Description: The set XML element MUST contain only a prop XML Description: The set XML element MUST contain only a prop XML
element. The elements contained by the prop XML element element. The elements contained by the prop XML element
inside the set XML element MUST specify the name and value inside the set XML element MUST specify the name and value
of properties that are set on the resource identified by of properties that are set on the resource identified by
Request-URI. If a property already exists then its value Request-URI. If a property already exists then its value
is replaced. Language tagging information in the property's is replaced. Language tagging information appearing in the
value (in the "xml:lang" attribute, if present) MUST be scope of the prop element (in the "xml:lang" attribute, if
persistently stored along with the property, and MUST be present) MUST be persistently stored along with the
subsequently retrievable using PROPFIND. property, and MUST be subsequently retrievable using
PROPFIND.
<!ELEMENT set (prop) > <!ELEMENT set (prop) >
13.25 propfind XML Element 13.25 propfind XML Element
Name: propfind Name: propfind
Expires Oct 2003 71
WebDAV (RFC2518) bis June 2003
Namespace: DAV: Namespace: DAV:
Purpose: Specifies the properties to be returned from a PROPFIND Purpose: Specifies the properties to be returned from a PROPFIND
method. Two special elements are specified for use with method. Four special elements are specified for use with
propfind, allprop and propname. If prop is used inside propfind: prop, deadprops, allprop and propname. If prop
propfind it MUST only contain property names, not values. is used inside propfind it MUST NOT contain property
values.
Expires Aug 2003 66
WebDAV (RFC2518) bis March 2003
<!ELEMENT propfind ANY > <!ELEMENT propfind ANY >
ANY value: MUST contain one and only one of (allprop | propname | ANY value: MUST contain one and only one of (allprop | propname |
prop). MAY contain additional elements not defined in this prop).
document.
13.26 allprop XML Element 13.26 allprop XML Element
Name: allprop Name: allprop
Namespace: DAV: Namespace: DAV:
Purpose: The allprop XML element specifies that all property names Purpose: The allprop XML element specifies that all names and values
and values on the resource are to be returned. of dead properties and the live properties defined by this
document existing on the resource are to be returned.
<!ELEMENT allprop EMPTY > <!ELEMENT allprop EMPTY >
13.27 propname XML Element 13.27 propname XML Element
Name: propname Name: propname
Namespace: DAV: Namespace: DAV:
Purpose: The propname XML element specifies that only a list of Purpose: The propname XML element specifies that only a list of
property names on the resource is to be returned. property names on the resource is to be returned.
<!ELEMENT propname EMPTY > <!ELEMENT propname EMPTY >
13.28 deadprops XML Element
Name: deadprops
Namespace: DAV:
Purpose: The deadprops XML element specifies that all dead
properties, names and values, should be returned in the
response.
<!ELEMENT deadprops EMPTY >
14 DAV Properties 14 DAV Properties
For DAV properties, the name of the property is also the same as the For DAV properties, the name of the property is also the same as the
name of the XML element that contains its value. In the section name of the XML element that contains its value. In the section
below, the final line of each section gives the element type below, the final line of each section gives the element type
declaration using the format defined in [REC-XML]. The "Value" declaration using the format defined in [REC-XML]. The "Value"
field, where present, specifies further restrictions on the field, where present, specifies further restrictions on the
Expires Oct 2003 72
WebDAV (RFC2518) bis June 2003
allowable contents of the XML element using BNF (i.e., to further allowable contents of the XML element using BNF (i.e., to further
restrict the values of a PCDATA element). Note that a resource may restrict the values of a PCDATA element). Note that a resource may
have only one value for a property of a given name, so the property have only one value for a property of a given name, so the property
may only show up once in PROPFIND responses or PROPPATCH requests. may only show up once in PROPFIND responses or PROPPATCH requests.
The value of a protected property may not be changed even by a user The value of a protected property may not be changed even by a user
with permission to edit other properties. Some property values are with permission to edit other properties. Some property values are
calculated by the server and it is not appropriate to allow client calculated by the server and it is not appropriate to allow client
changes. This specification mentions which properties may be changes. This specification mentions which properties may be
protected in order to set client expectations. protected in order to set client expectations.
14.1 creationdate Property 14.1 creationdate Property
Name: creationdate Name: creationdate
Namespace: DAV: Namespace: DAV:
Purpose: Records the time and date the resource was created. Purpose: Records the time and date the resource was created.
Value: date-time Value: date-time
COPY/MOVE behaviour: This property value SHOULD be kept during a COPY/MOVE behaviour: This property value SHOULD be kept during a
MOVE operation, but is re-initialized when a resource is MOVE operation, but is re-initialized when a resource is
created with a COPY. It should not be set in a remote COPY. created with a COPY. It should not be set in a remote COPY.
Expires Aug 2003 67
WebDAV (RFC2518) bis March 2003
Description: The creationdate property should be defined on all DAV Description: The creationdate property should be defined on all DAV
compliant resources. If present, it contains a timestamp compliant resources. If present, it contains a timestamp
of the moment when the resource was created (i.e., the of the moment when the resource was created (i.e., the
moment it had non-null state). This property is live and moment it had non-null state). This property is live and
protected. The Internet date-time format is defined in protected. The Internet date-time format is defined in
[RFC3339], see the ABNF in section 5.6. [RFC3339], see the ABNF in section 5.6.
<!ELEMENT creationdate (#PCDATA) > <!ELEMENT creationdate (#PCDATA) >
14.2 displayname Property 14.2 displayname Property
skipping to change at line 3649 skipping to change at line 3844
local COPY and MOVE operations. It MAY be attempted to be local COPY and MOVE operations. It MAY be attempted to be
set in remote COPY operation. set in remote COPY operation.
Description: The displayname property should be defined on Description: The displayname property should be defined on
all DAV compliant resources. If present, the property all DAV compliant resources. If present, the property
contains a description of the resource that is suitable for contains a description of the resource that is suitable for
presentation to a user. This property is live and MAY be presentation to a user. This property is live and MAY be
protected. protected.
<!ELEMENT displayname (#PCDATA) > <!ELEMENT displayname (#PCDATA) >
Expires Oct 2003 73
WebDAV (RFC2518) bis June 2003
14.3 getcontentlanguage Property 14.3 getcontentlanguage Property
Name: getcontentlanguage Name: getcontentlanguage
Namespace: DAV: Namespace: DAV:
Purpose: Contains the Content-Language header returned by a GET Purpose: Contains the Content-Language header returned by a GET
without accept headers without accept headers
COPY/MOVE behaviour: This property value SHOULD be preserved in COPY/MOVE behaviour: This property value SHOULD be preserved in
local COPY and MOVE operations. It should be attempted to local COPY and MOVE operations. It should be attempted to
be set in remote COPY operation. be set in remote COPY operation.
Description: The getcontentlanguage property MUST be defined Description: The getcontentlanguage property MUST be defined
skipping to change at line 3671 skipping to change at line 3870
protected. protected.
Value: language-tag ;language-tag is defined in section 14.13 of Value: language-tag ;language-tag is defined in section 14.13 of
[RFC2616] [RFC2616]
<!ELEMENT getcontentlanguage (#PCDATA) > <!ELEMENT getcontentlanguage (#PCDATA) >
14.4 getcontentlength Property 14.4 getcontentlength Property
Name: getcontentlength Name: getcontentlength
Namespace: DAV: Namespace: DAV:
Expires Aug 2003 68
WebDAV (RFC2518) bis March 2003
Purpose: Contains the Content-Length header returned by a GET Purpose: Contains the Content-Length header returned by a GET
without accept headers. without accept headers.
Description: The getcontentlength property MUST be defined Description: The getcontentlength property MUST be defined
on any DAV compliant resource that returns the Content- on any DAV compliant resource that returns the Content-
Length header in response to a GET. This property is live Length header in response to a GET. This property is live
and protected. and protected.
COPY/MOVE behaviour: This property value is dependent on the size of COPY/MOVE behaviour: This property value is dependent on the size of
the destination resource, not the value of the property on the destination resource, not the value of the property on
the source resource. the source resource.
Value: content-length ; see section 14.14 of [RFC2616] Value: content-length ; see section 14.14 of [RFC2616]
skipping to change at line 3698 skipping to change at line 3893
14.5 getcontenttype Property 14.5 getcontenttype Property
Name: getcontenttype Name: getcontenttype
Namespace: DAV: Namespace: DAV:
Purpose: Contains the Content-Type header returned by a GET without Purpose: Contains the Content-Type header returned by a GET without
accept headers. accept headers.
COPY/MOVE behaviour: This property value SHOULD be preserved in COPY/MOVE behaviour: This property value SHOULD be preserved in
local COPY and MOVE operations. In a remote COPY operation local COPY and MOVE operations. In a remote COPY operation
that is implemented through a GET request, the GET request that is implemented through a GET request, the GET request
must have the appropriate Content-Type header. must have the appropriate Content-Type header.
Expires Oct 2003 74
WebDAV (RFC2518) bis June 2003
Description: This getcontenttype property MUST be defined on Description: This getcontenttype property MUST be defined on
any DAV compliant resource that returns the Content-Type any DAV compliant resource that returns the Content-Type
header in response to a GET. This property is live and MAY header in response to a GET. This property is live and MAY
be protected. be protected.
Value: media-type ; defined in section 3.7 of [RFC2616] Value: media-type ; defined in section 3.7 of [RFC2616]
<!ELEMENT getcontenttype (#PCDATA) > <!ELEMENT getcontenttype (#PCDATA) >
14.6 getetag Property 14.6 getetag Property
skipping to change at line 3724 skipping to change at line 3924
property on the source resource. It MUST NOT be set in property on the source resource. It MUST NOT be set in
PROPPATCH during a cross-server copy. PROPPATCH during a cross-server copy.
Description: The getetag property MUST be defined on any DAV Description: The getetag property MUST be defined on any DAV
compliant resource that returns the Etag header. Refer to compliant resource that returns the Etag header. Refer to
RFC2616 for a complete definition of the semantics of an RFC2616 for a complete definition of the semantics of an
ETag. Note that changes in properties or lock state MUST ETag. Note that changes in properties or lock state MUST
not cause a resourceĂs ETag to change This property is live not cause a resourceĂs ETag to change This property is live
and protected. and protected.
Value: entity-tag ; defined in section 3.11 of [RFC2616] Value: entity-tag ; defined in section 3.11 of [RFC2616]
Expires Aug 2003 69
WebDAV (RFC2518) bis March 2003
<!ELEMENT getetag (#PCDATA) > <!ELEMENT getetag (#PCDATA) >
14.7 getlastmodified Property 14.7 getlastmodified Property
Name: getlastmodified Name: getlastmodified
Namespace: DAV: Namespace: DAV:
Purpose: Contains the Last-Modified header returned by a GET method Purpose: Contains the Last-Modified header returned by a GET method
without accept headers. without accept headers.
COPY/MOVE behaviour: This property value is dependent on the last COPY/MOVE behaviour: This property value is dependent on the last
modified date of the destination resource, not the value of modified date of the destination resource, not the value of
the property on the source resource. the property on the source resource.
Description: Note that the last-modified date on a resource SHOULD Description: Note that the last-modified date on a resource SHOULD
only reflect changes in the body (the GET responses) of the only reflect changes in the body (the GET responses) of the
resource. A change in a property SHOULD NOT cause the resource. A change in a property SHOULD NOT cause the
last-modified date to change, because clients MAY rely on last-modified date to change, because clients MAY rely on
the last-modified date to know when to overwrite the the last-modified date to know when to overwrite the
existing body. The getlastmodified property MUST be defined existing body. The getlastmodified property MUST be defined
on any DAV compliant resource that returns the Last- on any DAV compliant resource that returns the Last-
Expires Oct 2003 75
WebDAV (RFC2518) bis June 2003
Modified header in response to a GET. This property is live Modified header in response to a GET. This property is live
and protected. and protected.
Value: HTTP-date ; defined in section 3.3.1 of [RFC2616] Value: HTTP-date ; defined in section 3.3.1 of [RFC2616]
<!ELEMENT getlastmodified (#PCDATA) > <!ELEMENT getlastmodified (#PCDATA) >
14.8 lockdiscovery Property 14.8 lockdiscovery Property
Name: lockdiscovery Name: lockdiscovery
Namespace: DAV: Namespace: DAV:
skipping to change at line 3775 skipping to change at line 3977
ŠactivelockĂ elements. If there is one or more lock, an ŠactivelockĂ elements. If there is one or more lock, an
ŠactivelockĂ element appears for each lock on the resource. ŠactivelockĂ element appears for each lock on the resource.
This property is live and protected. This property is live and protected.
<!ELEMENT lockdiscovery ANY > <!ELEMENT lockdiscovery ANY >
ANY value: MAY contain zero or more activelock elements. MAY contain ANY value: MAY contain zero or more activelock elements. MAY contain
additional elements not defined in this document. additional elements not defined in this document.
14.8.1 Example - Retrieving the lockdiscovery Property 14.8.1 Example - Retrieving the lockdiscovery Property
Expires Aug 2003 70
WebDAV (RFC2518) bis March 2003
>>Request >>Request
PROPFIND /container/ HTTP/1.1 PROPFIND /container/ HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Length: xxxx Content-Length: xxxx
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D='DAV:'> <D:propfind xmlns:D='DAV:'>
<D:prop><D:lockdiscovery/></D:prop> <D:prop><D:lockdiscovery/></D:prop>
</D:propfind> </D:propfind>
>>Response >>Response
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Expires Oct 2003 76
WebDAV (RFC2518) bis June 2003
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D='DAV:'> <D:multistatus xmlns:D='DAV:'>
<D:response> <D:response>
<D:href>http://www.example.com/container/</D:href> <D:href>http://www.example.com/container/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:lockdiscovery> <D:lockdiscovery>
<D:activelock> <D:activelock>
skipping to change at line 3827 skipping to change at line 4031
</D:lockdiscovery> </D:lockdiscovery>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
This resource has a single exclusive write lock on it, with an This resource has a single exclusive write lock on it, with an
infinite timeout. infinite timeout.
Expires Aug 2003 71
WebDAV (RFC2518) bis March 2003
14.9 resourcetype Property 14.9 resourcetype Property
Name: resourcetype Name: resourcetype
Namespace: DAV: Namespace: DAV:
Purpose: Specifies the nature of the resource. Purpose: Specifies the nature of the resource.
COPY/MOVE behaviour: Generally a COPY/MOVE of a resource results in COPY/MOVE behaviour: Generally a COPY/MOVE of a resource results in
the same type of resource at the destination. In a remote the same type of resource at the destination. In a remote
COPY, the source server SHOULD NOT attempt to set this COPY, the source server SHOULD NOT attempt to set this
property. property.
Description: The resourcetype property MUST be defined on Description: The resourcetype property MUST be defined on
all DAV compliant resources. The default value is empty. all DAV compliant resources. The default value is empty.
This property is live and protected. This property is live and protected.
Expires Oct 2003 77
WebDAV (RFC2518) bis June 2003
<!ELEMENT resourcetype ANY > <!ELEMENT resourcetype ANY >
Example: (fictional example to show extensibility) Example: (fictional example to show extensibility)
<x:resourcetype xmlns:x="DAV:"><x:collection/> <x:resourcetype xmlns:x="DAV:"><x:collection/>
<f:search-results xmlns:f="http://www.example.com/ns"/> <f:search-results xmlns:f="http://www.example.com/ns"/>
</x:resourcetype> </x:resourcetype>
14.10 supportedlock Property 14.10 supportedlock Property
Name: supportedlock Name: supportedlock
skipping to change at line 3879 skipping to change at line 4084
14.10.1 Example - Retrieving the supportedlock Property 14.10.1 Example - Retrieving the supportedlock Property
>>Request >>Request
PROPFIND /container/ HTTP/1.1 PROPFIND /container/ HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Length: xxxx Content-Length: xxxx
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Expires Aug 2003 72
WebDAV (RFC2518) bis March 2003
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop><D:supportedlock/></D:prop> <D:prop><D:supportedlock/></D:prop>
</D:propfind> </D:propfind>
>>Response >>Response
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Expires Oct 2003 78
WebDAV (RFC2518) bis June 2003
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.example.com/container/</D:href> <D:href>http://www.example.com/container/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:supportedlock> <D:supportedlock>
<D:lockentry> <D:lockentry>
skipping to change at line 3928 skipping to change at line 4135
all its children encountered while processing a DAV method that uses all its children encountered while processing a DAV method that uses
XML as its command language. XML as its command language.
This restriction also applies to the processing, by clients, of DAV This restriction also applies to the processing, by clients, of DAV
property values where unknown XML elements SHOULD be ignored unless property values where unknown XML elements SHOULD be ignored unless
the property's schema declares otherwise. the property's schema declares otherwise.
This restriction does not apply to setting dead DAV properties on This restriction does not apply to setting dead DAV properties on
the server where the server MUST record unknown XML elements. the server where the server MUST record unknown XML elements.
Expires Aug 2003 73
WebDAV (RFC2518) bis March 2003
Additionally, this restriction does not apply to the use of XML Additionally, this restriction does not apply to the use of XML
where XML happens to be the content type of the entity body, for where XML happens to be the content type of the entity body, for
example, when used as the body of a PUT. example, when used as the body of a PUT.
Since XML can be transported as text/xml or application/xml, a DAV Since XML can be transported as text/xml or application/xml, a DAV
server MUST accept DAV method requests with XML parameters server MUST accept DAV method requests with XML parameters
transported as either text/xml or application/xml, and DAV client transported as either text/xml or application/xml, and DAV client
MUST accept XML responses using either text/xml or application/xml. MUST accept XML responses using either text/xml or application/xml.
Expires Oct 2003 79
WebDAV (RFC2518) bis June 2003
16 DAV Compliance Classes 16 DAV Compliance Classes
A DAV compliant resource can advertise several classes of A DAV compliant resource can advertise several classes of
compliance. A client can discover the compliance classes of a compliance. A client can discover the compliance classes of a
resource by executing OPTIONS on the resource, and examining the resource by executing OPTIONS on the resource, and examining the
"DAV" header which is returned. Note particularly that resources "DAV" header which is returned. Note particularly that resources
are spoken of as being compliant, rather than servers. That is are spoken of as being compliant, rather than servers. That is
because theoretically some resources on a server could support because theoretically some resources on a server could support
different feature sets. E.g. a server could have a sub-repository different feature sets. E.g. a server could have a sub-repository
where an advanced feature like server was supported, even if that where an advanced feature like server was supported, even if that
skipping to change at line 3983 skipping to change at line 4191
Token request header. A class "2" compliant resource SHOULD also Token request header. A class "2" compliant resource SHOULD also
support the Time-Out request header and the owner XML element. support the Time-Out request header and the owner XML element.
Class 2 compliant resources MUST return, at minimum, the values "1" Class 2 compliant resources MUST return, at minimum, the values "1"
and "2" in the DAV header on all responses to the OPTIONS method. and "2" in the DAV header on all responses to the OPTIONS method.
16.3 Class "bis" 16.3 Class "bis"
A resource can explicitly advertise its support for the revisions to A resource can explicitly advertise its support for the revisions to
RFC2518 made in this document. In particular, this allows clients to RFC2518 made in this document. In particular, this allows clients to
Expires Aug 2003 74
WebDAV (RFC2518) bis March 2003
use the Force-Authentication header on requests. Class 1 must be use the Force-Authentication header on requests. Class 1 must be
supported as well. Class 2 MAY be supported. supported as well. Class 2 MAY be supported.
A resource that supports bis MUST support: A resource that supports bis MUST support:
- the Force-Authentication header. - the Force-Authentication header.
- Any behavior that it supports, in the manner specified in this - Any behavior that it supports, in the manner specified in this
document, rather than in the manner specified in RFC2518, for all document, rather than in the manner specified in RFC2518, for all
Expires Oct 2003 80
WebDAV (RFC2518) bis June 2003
client requests. A server MAY use an older behavior for specific client requests. A server MAY use an older behavior for specific
clients that are discovered to have interoperability problems with clients that are discovered to have interoperability problems with
the requirements of this specification, but MUST NOT use an older the requirements of this specification, but MUST NOT use an older
behavior indiscriminately. behavior indiscriminately.
Example: Example:
DAV: 1, bis DAV: 1, bis
17 Internationalization Considerations 17 Internationalization Considerations
In the realm of internationalization, this specification complies In the realm of internationalization, this specification complies
with the IETF Character Set Policy [RFC2277]. In this specification, with the IETF Character Set Policy [RFC2277]. In this specification,
human-readable fields can be found either in the value of a human-readable fields can be found either in the value of a
property, or in an error message returned in a response entity body. property, or in an error message returned in a response entity body.
In both cases, the human-readable content is encoded using XML, In both cases, the human-readable content is encoded using XML,
which has explicit provisions for character set tagging and which has explicit provisions for character set tagging and
encoding, and requires that XML processors read XML elements encoding, and requires that XML processors read XML elements
encoded, at minimum, using the UTF-8 [UTF-8] encoding of the ISO encoded, at minimum, using the UTF-8 [UTF-8] and UTF-16 encodings of
10646 multilingual plane. XML examples in this specification the ISO 10646 multilingual plane. XML examples in this
demonstrate use of the charset parameter of the Content-Type header, specification demonstrate use of the charset parameter of the
as defined in [RFC2376], as well as the XML declarations which Content-Type header, as defined in [RFC2376], as well as the XML
provide charset identification information for MIME and XML declarations which provide charset identification information for
processors. MIME and XML processors.
XML also provides a language tagging capability for specifying the XML also provides a language tagging capability for specifying the
language of the contents of a particular XML element. The language of the contents of a particular XML element. The
"xml:lang" attribute appears on an XML element to identify the "xml:lang" attribute appears on an XML element to identify the
language of its content and attributes. See [REC-XML] for language of its content and attributes. See [REC-XML] for
definitions of values and scoping. definitions of values and scoping.
WebDAV applications MUST support the character set tagging, WebDAV applications MUST support the character set tagging,
character set encoding, and the language tagging functionality of character set encoding, and the language tagging functionality of
the XML specification. Implementors of WebDAV applications are the XML specification. Implementors of WebDAV applications are
strongly encouraged to read "XML Media Types" [RFC2376] for strongly encouraged to read "XML Media Types" [RFC2376] for
instruction on which MIME media type to use for XML transport, and instruction on which MIME media type to use for XML transport, and
on use of the charset parameter of the Content-Type header. on use of the charset parameter of the Content-Type header.
Names used within this specification fall into three categories: Names used within this specification fall into three categories:
names of protocol elements such as methods and headers, names of XML names of protocol elements such as methods and headers, names of XML
elements, and names of properties. Naming of protocol elements elements, names of properties, and names of conditions. Naming of
follows the precedent of HTTP, using English names encoded in protocol elements follows the precedent of HTTP, using English names
USASCII for methods and headers. Since these protocol elements are encoded in USASCII for methods and headers. Since these protocol
not visible to users, and are simply long token identifiers, they do elements are not visible to users, and are simply long token
not need to support multiple languages. Similarly, the names of XML identifiers, they do not need to support multiple languages.
Similarly, the names of XML elements used in this specification are
not visible to the user and hence do not need to support multiple
languages.
Expires Aug 2003 75 Expires Oct 2003 81
WebDAV (RFC2518) bis March 2003
elements used in this specification are not visible to the user and WebDAV (RFC2518) bis June 2003
hence do not need to support multiple languages.
WebDAV property names are qualified XML names (pairs of XML WebDAV property names are qualified XML names (pairs of XML
namespace name and local name). Although some applications (e.g., a namespace name and local name). Although some applications (e.g., a
generic property viewer) will display property names directly to generic property viewer) will display property names directly to
their users, it is expected that the typical application will use a their users, it is expected that the typical application will use a
fixed set of properties, and will provide a mapping from the fixed set of properties, and will provide a mapping from the
property name URI to a human-readable field when displaying the property name URI to a human-readable field when displaying the
property name to a user. It is only in the case where the set of property name to a user. It is only in the case where the set of
properties is not known ahead of time that an application need properties is not known ahead of time that an application need
display a property name URI to a user. We recommend that display a property name URI to a user. We recommend that
skipping to change at line 4096 skipping to change at line 4306
the introduction of locking functionality requires support for the introduction of locking functionality requires support for
authentication. authentication.
A password sent in the clear over an insecure channel is an A password sent in the clear over an insecure channel is an
inadequate means for protecting the accessibility and integrity of a inadequate means for protecting the accessibility and integrity of a
resource as the password may be intercepted. Since Basic resource as the password may be intercepted. Since Basic
authentication for HTTP/1.1 performs essentially clear text authentication for HTTP/1.1 performs essentially clear text
transmission of a password, Basic authentication MUST NOT be used to transmission of a password, Basic authentication MUST NOT be used to
authenticate a WebDAV client to a server unless the connection is authenticate a WebDAV client to a server unless the connection is
Expires Aug 2003 76 Expires Oct 2003 82
WebDAV (RFC2518) bis March 2003
WebDAV (RFC2518) bis June 2003
secure. Furthermore, a WebDAV server MUST NOT send Basic secure. Furthermore, a WebDAV server MUST NOT send Basic
authentication credentials in a WWW-Authenticate header unless the authentication credentials in a WWW-Authenticate header unless the
connection is secure. Examples of secure connections include a connection is secure. Examples of secure connections include a
Transport Layer Security (TLS) connection employing a strong cipher Transport Layer Security (TLS) connection employing a strong cipher
suite with mutual authentication of client and server, or a suite with mutual authentication of client and server, or a
connection over a network which is physically secure, for example, connection over a network which is physically secure, for example,
an isolated network in a building with restricted access. an isolated network in a building with restricted access.
WebDAV applications MUST support the Digest authentication scheme WebDAV applications MUST support the Digest authentication scheme
skipping to change at line 4150 skipping to change at line 4361
control techniques to prevent unwanted access to resources, rather control techniques to prevent unwanted access to resources, rather
than depending on the relative obscurity of their resource names. than depending on the relative obscurity of their resource names.
18.4 Privacy Issues Connected to Locks 18.4 Privacy Issues Connected to Locks
When submitting a lock request a user agent may also submit an owner When submitting a lock request a user agent may also submit an owner
XML field giving contact information for the person taking out the XML field giving contact information for the person taking out the
lock (for those cases where a person, rather than a robot, is taking lock (for those cases where a person, rather than a robot, is taking
out the lock). This contact information is stored in a lockdiscovery out the lock). This contact information is stored in a lockdiscovery
property on the resource, and can be used by other collaborators to property on the resource, and can be used by other collaborators to
Expires Oct 2003 83
WebDAV (RFC2518) bis June 2003
begin negotiation over access to the resource. However, in many begin negotiation over access to the resource. However, in many
cases this contact information can be very private, and should not cases this contact information can be very private, and should not
be widely disseminated. Servers SHOULD limit read access to the be widely disseminated. Servers SHOULD limit read access to the
Expires Aug 2003 77
WebDAV (RFC2518) bis March 2003
lockdiscovery property as appropriate. Furthermore, user agents lockdiscovery property as appropriate. Furthermore, user agents
SHOULD provide control over whether contact information is sent at SHOULD provide control over whether contact information is sent at
all, and if contact information is sent, control over exactly what all, and if contact information is sent, control over exactly what
information is sent. information is sent.
18.5 Privacy Issues Connected to Properties 18.5 Privacy Issues Connected to Properties
Since property values are typically used to hold information such as Since property values are typically used to hold information such as
the author of a document, there is the possibility that privacy the author of a document, there is the possibility that privacy
concerns could arise stemming from widespread access to a resource's concerns could arise stemming from widespread access to a resource's
property data. To reduce the risk of inadvertent release of private property data. To reduce the risk of inadvertent release of private
information via properties, servers are encouraged to develop access information via properties, servers are encouraged to develop access
control mechanisms that separate read access to the resource body control mechanisms that separate read access to the resource body
and read access to the resource's properties. This allows a user to and read access to the resource's properties. This allows a user to
control the dissemination of their property data without overly control the dissemination of their property data without overly
restricting access to the resource's contents. restricting access to the resource's contents.
18.6 Reduction of Security due to Source Link 18.6 Implications of XML External Entities
HTTP/1.1 warns against providing read access to script code because
it may contain sensitive information. Yet WebDAV, via its source
link facility, can potentially provide a URI for script resources so
they may be authored. For HTTP/1.1, a server could reasonably
prevent access to source resources due to the predominance of read-
only access. WebDAV, with its emphasis on authoring, encourages
read and write access to source resources, and provides the source
link facility to identify the source. This reduces the security
benefits of eliminating access to source resources. Users and
administrators of WebDAV servers should be very cautious when
allowing remote authoring of scripts, limiting read and write access
to the source resources to authorized principals.
18.7 Implications of XML External Entities
XML supports a facility known as "external entities", defined in XML supports a facility known as "external entities", defined in
section 4.2.2 of [REC-XML], which instruct an XML processor to section 4.2.2 of [REC-XML], which instruct an XML processor to
retrieve and include additional XML. An external XML entity can be retrieve and include additional XML. An external XML entity can be
used to append or modify the document type declaration (DTD) used to append or modify the document type declaration (DTD)
associated with an XML document. An external XML entity can also be associated with an XML document. An external XML entity can also be
used to include XML within the content of an XML document. For non- used to include XML within the content of an XML document. For non-
validating XML, such as the XML used in this specification, validating XML, such as the XML used in this specification,
including an external XML entity is not required by [REC-XML]. including an external XML entity is not required by [REC-XML].
However, [REC-XML] does state that an XML processor may, at its However, [REC-XML] does state that an XML processor may, at its
skipping to change at line 4211 skipping to change at line 4408
External XML entities have no inherent trustworthiness and are External XML entities have no inherent trustworthiness and are
subject to all the attacks that are endemic to any HTTP GET request. subject to all the attacks that are endemic to any HTTP GET request.
Furthermore, it is possible for an external XML entity to modify the Furthermore, it is possible for an external XML entity to modify the
DTD, and hence affect the final form of an XML document, in the DTD, and hence affect the final form of an XML document, in the
worst case significantly modifying its semantics, or exposing the worst case significantly modifying its semantics, or exposing the
XML processor to the security risks discussed in [RFC2376]. XML processor to the security risks discussed in [RFC2376].
Therefore, implementers must be aware that external XML entities Therefore, implementers must be aware that external XML entities
should be treated as untrustworthy. If a server implementor chooses should be treated as untrustworthy. If a server implementor chooses
not to handle external XML entities, it SHOULD respond to requests not to handle external XML entities, it SHOULD respond to requests
Expires Aug 2003 78
WebDAV (RFC2518) bis March 2003
containing external entities with an error (403 Forbidden, with the containing external entities with an error (403 Forbidden, with the
'forbid-external-entities' element in the error body). 'forbid-external-entities' element in the error body).
There is also the scalability risk that would accompany a widely There is also the scalability risk that would accompany a widely
deployed application which made use of external XML entities. In deployed application which made use of external XML entities. In
this situation, it is possible that there would be significant this situation, it is possible that there would be significant
numbers of requests for one external XML entity, potentially numbers of requests for one external XML entity, potentially
Expires Oct 2003 84
WebDAV (RFC2518) bis June 2003
overloading any server which fields requests for the resource overloading any server which fields requests for the resource
containing the external XML entity. containing the external XML entity.
18.8 Risks Connected with Lock Tokens 18.7 Risks Connected with Lock Tokens
This specification, in section 6.4, requires the use of Universal This specification, in section 6.4, requires the use of Universal
Unique Identifiers (UUIDs) for lock tokens, in order to guarantee Unique Identifiers (UUIDs) for lock tokens, in order to guarantee
their uniqueness across space and time. UUIDs, as defined in [ISO- their uniqueness across space and time. UUIDs, as defined in [ISO-
11578], contain a "node" field which "consists of the IEEE address, 11578], contain a "node" field which "consists of the IEEE address,
usually the host address. For systems with multiple IEEE 802 nodes, usually the host address. For systems with multiple IEEE 802 nodes,
any available node address can be used." Since a WebDAV server will any available node address can be used." Since a WebDAV server will
issue many locks over its lifetime, the implication is that it will issue many locks over its lifetime, the implication is that it will
also be publicly exposing its IEEE 802 address. also be publicly exposing its IEEE 802 address.
skipping to change at line 4258 skipping to change at line 4456
for generating the "node" field of a UUID without using an IEEE 802 for generating the "node" field of a UUID without using an IEEE 802
address, which alleviates the risks associated with exposure of IEEE address, which alleviates the risks associated with exposure of IEEE
802 addresses by using an alternate source of uniqueness. 802 addresses by using an alternate source of uniqueness.
19 IANA Considerations 19 IANA Considerations
This document defines two namespaces, the namespace of property This document defines two namespaces, the namespace of property
names, and the namespace of WebDAV-specific XML elements used within names, and the namespace of WebDAV-specific XML elements used within
property values. property values.
URIs are used for both names, for several reasons. Assignment of a The use of XML namespaces means that unique WebDAV property names
URI does not require a request to a central naming authority, and and XML elements can be quickly defined by any WebDAV user or
hence allow WebDAV property names and XML elements to be quickly application, without requiring IANA action.
defined by any WebDAV user or application. URIs also provide a
unique address space, ensuring that the distributed users of WebDAV
will not have collisions among the property names and XML elements
they create.
This specification defines a distinguished set of property names and This specification defines a distinguished set of property names and
XML elements that are understood by all WebDAV applications. The XML elements that are understood by all WebDAV applications. The
property names and XML elements in this specification are all in the
Expires Aug 2003 79 "DAV:" namespace. In natural language, a property like the
WebDAV (RFC2518) bis March 2003 "creationdate" property in the "DAV:" namespace is sometimes
referred to as "DAV:creationdate" for brevity.
property names and XML elements in this specification are all
derived from the base URI DAV: by adding a suffix to this URI, for
example, DAV:creationdate for the "creationdate" property.
This specification also defines a URI scheme for the encoding of This specification also defines a URI scheme for the encoding of
lock tokens, the opaquelocktoken URI scheme described in section lock tokens, the opaquelocktoken URI scheme described in section
6.4. 6.4.
Expires Oct 2003 85
WebDAV (RFC2518) bis June 2003
To ensure correct interoperation based on this specification, IANA To ensure correct interoperation based on this specification, IANA
must reserve the URI namespaces starting with "DAV:" and with must reserve the URI namespaces starting with "DAV:" and with
"opaquelocktoken:" for use by this specification, its revisions, and "opaquelocktoken:" for use by this specification, its revisions, and
related WebDAV specifications. related WebDAV specifications.
20 Intellectual Property 20 Intellectual Property
The following notice is copied from RFC 2026 [RFC2026], section The following notice is copied from RFC 2026 [RFC2026], section
10.4, and describes the position of the IETF concerning intellectual 10.4, and describes the position of the IETF concerning intellectual
property claims made against this document. property claims made against this document.
skipping to change at line 4318 skipping to change at line 4513
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
21 Acknowledgements 21 Acknowledgements
A specification such as this thrives on piercing critical review and A specification such as this thrives on piercing critical review and
withers from apathetic neglect. The authors gratefully acknowledge withers from apathetic neglect. The authors gratefully acknowledge
the contributions of the following people, whose insights were so the contributions of the following people, whose insights were so
valuable at every stage of our work. valuable at every stage of our work.
Contributors to RFC2518
Terry Allen, Harald Alvestrand, Jim Amsden, Becky Anderson, Alan Terry Allen, Harald Alvestrand, Jim Amsden, Becky Anderson, Alan
Babich, Sanford Barr, Dylan Barrell, Bernard Chester, Tim Berners- Babich, Sanford Barr, Dylan Barrell, Bernard Chester, Tim Berners-
Lee, Dan Connolly, Jim Cunningham, Ron Daniel, Jr., Jim Davis, Keith Lee, Dan Connolly, Jim Cunningham, Ron Daniel, Jr., Jim Davis, Keith
Dawson, Mark Day, Brian Deen, Martin Duerst, David Durand, Lee Dawson, Mark Day, Brian Deen, Martin Duerst, David Durand, Lee
Farrell, Chuck Fay, Wesley Felter, Roy Fielding, Mark Fisher, Alan Farrell, Chuck Fay, Wesley Felter, Roy Fielding, Mark Fisher, Alan
Freier, George Florentine, Jim Gettys, Phill Hallam-Baker, Dennis Freier, George Florentine, Jim Gettys, Phill Hallam-Baker, Dennis
Expires Aug 2003 80
WebDAV (RFC2518) bis March 2003
Hamilton, Steve Henning, Mead Himelstein, Alex Hopmann, Andre van Hamilton, Steve Henning, Mead Himelstein, Alex Hopmann, Andre van
der Hoek, Ben Laurie, Paul Leach, Ora Lassila, Karen MacArthur, der Hoek, Ben Laurie, Paul Leach, Ora Lassila, Karen MacArthur,
Expires Oct 2003 86
WebDAV (RFC2518) bis June 2003
Steven Martin, Larry Masinter, Michael Mealling, Keith Moore, Thomas Steven Martin, Larry Masinter, Michael Mealling, Keith Moore, Thomas
Narten, Henrik Nielsen, Kenji Ota, Bob Parker, Glenn Peterson, Jon Narten, Henrik Nielsen, Kenji Ota, Bob Parker, Glenn Peterson, Jon
Radoff, Saveen Reddy, Henry Sanders, Christopher Seiwald, Judith Radoff, Saveen Reddy, Henry Sanders, Christopher Seiwald, Judith
Slein, Mike Spreitzer, Einar Stefferud, Greg Stein, Ralph Swick, Slein, Mike Spreitzer, Einar Stefferud, Greg Stein, Ralph Swick,
Kenji Takahashi, Richard N. Taylor, Robert Thau, John Turner, Sankar Kenji Takahashi, Richard N. Taylor, Robert Thau, John Turner, Sankar
Virdhagriswaran, Fabio Vitali, Gregory Woodhouse, and Lauren Wood. Virdhagriswaran, Fabio Vitali, Gregory Woodhouse, and Lauren Wood.
Two from this list deserve special mention. The contributions by Two from this list deserve special mention. The contributions by
Larry Masinter have been invaluable, both in helping the formation Larry Masinter have been invaluable, both in helping the formation
of the working group and in patiently coaching the authors along the of the working group and in patiently coaching the authors along the
way. In so many ways he has set high standards we have toiled to way. In so many ways he has set high standards we have toiled to
meet. The contributions of Judith Slein in clarifying the meet. The contributions of Judith Slein in clarifying the
requirements, and in patiently reviewing draft after draft, both requirements, and in patiently reviewing draft after draft, both
improved this specification and expanded our minds on document improved this specification and expanded our minds on document
management. management.
We would also like to thank John Turner for developing the XML DTD. We would also like to thank John Turner for developing the XML DTD.
The authors of RFC2518 were Yaron Goland, Jim Whitehead, A. Faizi,
Steve Carter and D. Jensen. Although their names had to be removed
due to IETF author count restrictions they can take credit for the
majority of the design of WebDAV.
Additional Contributors to This Specification
Valuable contributions to RFC2518 bis came from some already named. Valuable contributions to RFC2518 bis came from some already named.
New contributors must also be gratefully acknowledged. Julian New contributors must also be gratefully acknowledged. Julian
Reschke, Joel Soderberg, and Dan Brotsky hashed out specific text on Reschke, Geoff Clemm, Joel Soderberg, and Dan Brotsky hashed out
the list or in meetings. Ilya Kirnos supplied text for Force- specific text on the list or in meetings. Ilya Kirnos supplied text
Authentication header. for Force-Authentication header.
Expires Aug 2003 81 Expires Oct 2003 87
WebDAV (RFC2518) bis March 2003
WebDAV (RFC2518) bis June 2003
22 References 22 References
22.1 Normative References 22.1 Normative References
[RFC2277] H. T. Alvestrand, "IETF Policy on Character Sets and [RFC2277] H. T. Alvestrand, "IETF Policy on Character Sets and
Languages." RFC 2277, BCP 18, January 1998. Languages." RFC 2277, BCP 18, January 1998.
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels." RFC 2119, BCP 14, March 1997. Requirement Levels." RFC 2119, BCP 14, March 1997.
skipping to change at line 4400 skipping to change at line 4606
Interconnection - Remote Procedure Call (RPC)" Interconnection - Remote Procedure Call (RPC)"
[RFC2141] R. Moats, "URN Syntax." RFC 2141, May 1997. [RFC2141] R. Moats, "URN Syntax." RFC 2141, May 1997.
[RFC3339] G. Klyne, C. Newman, ˘Date and Time on the Internet: [RFC3339] G. Klyne, C. Newman, ˘Date and Time on the Internet:
Timestamps.÷ RFC3339, July 2002. Timestamps.÷ RFC3339, July 2002.
[UTF-8] F. Yergeau, "UTF-8, a transformation format of Unicode and [UTF-8] F. Yergeau, "UTF-8, a transformation format of Unicode and
ISO 10646." RFC 2279, January 1998. ISO 10646." RFC 2279, January 1998.
22.2 Informational References Expires Oct 2003 88
Expires Aug 2003 82 WebDAV (RFC2518) bis June 2003
WebDAV (RFC2518) bis March 2003
22.2 Informational References
[RFC2026] S. Bradner, "The Internet Standards Process - Revision 3." [RFC2026] S. Bradner, "The Internet Standards Process - Revision 3."
RFC 2026, BCP 9, October 1996. RFC 2026, BCP 9, October 1996.
[RFC1807] R. Lasher, D. Cohen, "A Format for Bibliographic Records," [RFC1807] R. Lasher, D. Cohen, "A Format for Bibliographic Records,"
RFC 1807, June 1995. RFC 1807, June 1995.
[WF] C. Lagoze, "The Warwick Framework: A Container Architecture [WF] C. Lagoze, "The Warwick Framework: A Container Architecture
for Diverse Sets of Metadata", D-Lib Magazine, July/August for Diverse Sets of Metadata", D-Lib Magazine, July/August
1996. http://www.dlib.org/dlib/july96/lagoze/07lagoze.html. 1996. http://www.dlib.org/dlib/july96/lagoze/07lagoze.html.
skipping to change at line 4439 skipping to change at line 4646
[RFC2413] S. Weibel, J. Kunze, C. Lagoze, M. Wolf, "Dublin Core [RFC2413] S. Weibel, J. Kunze, C. Lagoze, M. Wolf, "Dublin Core
Metadata for Resource Discovery." RFC 2413, September 1998. Metadata for Resource Discovery." RFC 2413, September 1998.
[RFC2376] E. Whitehead, M. Murata, "XML Media Types." RFC 2376, July [RFC2376] E. Whitehead, M. Murata, "XML Media Types." RFC 2376, July
1998. 1998.
[RFC3253] G. Clemm, J. Amsden, T. Ellison, C. Kaler, J. Whitehead, [RFC3253] G. Clemm, J. Amsden, T. Ellison, C. Kaler, J. Whitehead,
"Versioning Extensions to WebDAV (Web Distributed Authoring "Versioning Extensions to WebDAV (Web Distributed Authoring
and Versioning)", RFC 3253, March 2002. and Versioning)", RFC 3253, March 2002.
Expires Aug 2003 83 Expires Oct 2003 89
WebDAV (RFC2518) bis March 2003
WebDAV (RFC2518) bis June 2003
23 Authors' Addresses 23 Authors' Addresses
Editors of RFC2518
Y. Y. Goland Y. Y. Goland
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052-6399 Redmond, WA 98052-6399
Email: yarong@microsoft.com Email: yarong@microsoft.com
E. J. Whitehead, Jr. E. J. Whitehead, Jr.
Dept. Of Information and Computer Science Dept. Of Information and Computer Science
University of California, Irvine University of California, Irvine
Irvine, CA 92697-3425 Irvine, CA 92697-3425
skipping to change at line 4476 skipping to change at line 4686
Orem, UT 84097-2399 Orem, UT 84097-2399
Email: srcarter@novell.com Email: srcarter@novell.com
D. Jensen D. Jensen
Novell Novell
1555 N. Technology Way 1555 N. Technology Way
M/S ORM F111 M/S ORM F111
Orem, UT 84097-2399 Orem, UT 84097-2399
Email: dcjensen@novell.com Email: dcjensen@novell.com
Current Editors
L. Dusseault L. Dusseault
Xythos Software, Inc. Xythos Software, Inc.
25 Maiden Lane, 6th floor 25 Maiden Lane, 6th floor
San Francisco San Francisco
Email: lisa@xythos.com Email: lisa@xythos.com
Jason L Crawford Jason L Crawford
P.O.Box 704 P.O.Box 704
Yorktown Heights, NY 10598 Yorktown Heights, NY 10598
Phone: 914-784-7569 Phone: 914-784-7569
Email: nnjason8451@smallcue.com Email: nnjason8451@smallcue.com
Expires Aug 2003 84 Expires Oct 2003 90
WebDAV (RFC2518) bis March 2003
WebDAV (RFC2518) bis June 2003
24 Appendices 24 Appendices
24.1 Appendix 1 - WebDAV Document Type Definition 24.1 Appendix 1 - WebDAV Document Type Definition
This section provides a document type definition, following the This section provides a document type definition, following the
rules in [REC-XML], for the XML elements used in the protocol stream rules in [REC-XML], for the XML elements used in the protocol stream
and in the values of properties. It collects the element definitions and in the values of properties. It collects the element definitions
given in sections 13 and 14. given in sections 13 and 13.28.
The DTD is informational only, because legal XML in WebDAV bodies The DTD is informational only, because legal XML in WebDAV bodies
can not be validated according to this DTD. There are two reasons can not be validated according to this DTD. There are two reasons
for this: for this:
- the DTD syntax does not specify namespace usage - the DTD syntax does not specify namespace usage
- additional elements may appear according to the XML extensibility - additional elements may appear according to the XML extensibility
rules outlined in section 15. rules outlined in section 15.
<!DOCTYPE webdav-1.0 [ <!DOCTYPE webdav-1.0 [
skipping to change at line 4536 skipping to change at line 4749
<!ELEMENT depth (#PCDATA) > <!ELEMENT depth (#PCDATA) >
<!ELEMENT owner ANY > <!ELEMENT owner ANY >
<!ELEMENT timeout (#PCDATA) > <!ELEMENT timeout (#PCDATA) >
<!ELEMENT locktoken (href) > <!ELEMENT locktoken (href) >
<!ELEMENT lockroot (href) > <!ELEMENT lockroot (href) >
<!-- Multi-Status Response Body Elements --> <!-- Multi-Status Response Body Elements -->
<!ELEMENT multistatus ANY > <!ELEMENT multistatus ANY >
<!ELEMENT response ANY > <!ELEMENT response ANY >
Expires Oct 2003 91
WebDAV (RFC2518) bis June 2003
<!ELEMENT status (#PCDATA) > <!ELEMENT status (#PCDATA) >
<!ELEMENT propstat ANY > <!ELEMENT propstat ANY >
<!ELEMENT responsedescription (#PCDATA) > <!ELEMENT responsedescription (#PCDATA) >
Expires Aug 2003 85
WebDAV (RFC2518) bis March 2003
<!-- PROPPATCH Request Body Elements --> <!-- PROPPATCH Request Body Elements -->
<!ELEMENT propertyupdate ANY > <!ELEMENT propertyupdate ANY >
<!ELEMENT remove (prop) > <!ELEMENT remove (prop) >
<!ELEMENT set (prop) > <!ELEMENT set (prop) >
<!-- PROPFIND Request Body Elements --> <!-- PROPFIND Request Body Elements -->
<!ELEMENT propfind ANY > <!ELEMENT propfind ANY >
<!ELEMENT allprop EMPTY > <!ELEMENT allprop EMPTY >
<!ELEMENT propname EMPTY > <!ELEMENT propname EMPTY >
<!-- Property Elements for 'resourcetype' --> <!-- Property Elements for 'resourcetype' -->
<!ELEMENT collection EMPTY > <!ELEMENT collection EMPTY >
<!--========= Property Name Elements from Section 14 ============--> <!--========= Property Name Elements from Section 13.28
============-->
<!ELEMENT creationdate (#PCDATA) > <!ELEMENT creationdate (#PCDATA) >
<!ELEMENT displayname (#PCDATA) > <!ELEMENT displayname (#PCDATA) >
<!ELEMENT getcontentlanguage (#PCDATA) > <!ELEMENT getcontentlanguage (#PCDATA) >
<!ELEMENT getcontentlength (#PCDATA) > <!ELEMENT getcontentlength (#PCDATA) >
<!ELEMENT getcontenttype (#PCDATA) > <!ELEMENT getcontenttype (#PCDATA) >
<!ELEMENT getetag (#PCDATA) > <!ELEMENT getetag (#PCDATA) >
<!ELEMENT getlastmodified (#PCDATA) > <!ELEMENT getlastmodified (#PCDATA) >
<!ELEMENT lockdiscovery ANY > <!ELEMENT lockdiscovery ANY >
<!ELEMENT resourcetype ANY > <!ELEMENT resourcetype ANY >
<!ELEMENT supportedlock ANY > <!ELEMENT supportedlock ANY >
skipping to change at line 4584 skipping to change at line 4800
not have any content. The first is to declare an XML element of the not have any content. The first is to declare an XML element of the
form <A></A>. The second is to declare an XML element of the form form <A></A>. The second is to declare an XML element of the form
<A/>. The two XML elements are semantically identical. <A/>. The two XML elements are semantically identical.
24.2.2 Notes on Illegal XML Processing 24.2.2 Notes on Illegal XML Processing
XML is a flexible data format that makes it easy to submit data that XML is a flexible data format that makes it easy to submit data that
appears legal but in fact is not. The philosophy of "Be flexible in appears legal but in fact is not. The philosophy of "Be flexible in
what you accept and strict in what you send" still applies, but it what you accept and strict in what you send" still applies, but it
must not be applied inappropriately. XML is extremely flexible in must not be applied inappropriately. XML is extremely flexible in
Expires Oct 2003 92
WebDAV (RFC2518) bis June 2003
dealing with issues of white space, element ordering, inserting new dealing with issues of white space, element ordering, inserting new
elements, etc. This flexibility does not require extension, elements, etc. This flexibility does not require extension,
especially not in the area of the meaning of elements. especially not in the area of the meaning of elements.
There is no kindness in accepting illegal combinations of XML There is no kindness in accepting illegal combinations of XML
elements. At best it will cause an unwanted result and at worst it elements. At best it will cause an unwanted result and at worst it
can cause real damage. can cause real damage.
Expires Aug 2003 86
WebDAV (RFC2518) bis March 2003
24.2.3 Example - XML Syntax Error 24.2.3 Example - XML Syntax Error
The following request body for a PROPFIND method is illegal. The following request body for a PROPFIND method is illegal.
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:allprop/> <D:allprop/>
<D:propname/> <D:propname/>
</D:propfind> </D:propfind>
skipping to change at line 4631 skipping to change at line 4849
24.2.4 Example - Unknown XML Element 24.2.4 Example - Unknown XML Element
The previous example was illegal because it contained two elements The previous example was illegal because it contained two elements
that were explicitly banned from appearing together in the propfind that were explicitly banned from appearing together in the propfind
element. However, XML is an extensible language, so one can imagine element. However, XML is an extensible language, so one can imagine
new elements being defined for use with propfind. Below is the new elements being defined for use with propfind. Below is the
request body of a PROPFIND and, like the previous e