draft-ietf-webdav-rfc2518bis-10.txt   draft-ietf-webdav-rfc2518bis-11.txt 
WebDAV L. Dusseault WebDAV L. Dusseault
Internet-Draft OSAF Internet-Draft OSAF
Obsoletes: 2518 (if approved) December 30, 2005 Obsoletes: 2518 (if approved) January 22, 2006
Expires: July 3, 2006 Expires: July 26, 2006
HTTP Extensions for Distributed Authoring - WebDAV HTTP Extensions for Distributed Authoring - WebDAV
draft-ietf-webdav-rfc2518bis-10 draft-ietf-webdav-rfc2518bis-11
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 3, 2006. This Internet-Draft will expire on July 26, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
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, URL namespace creation and management of resource collections, URL namespace
manipulation, and resource locking (collision avoidance). manipulation, and resource locking (collision avoidance).
RFC2518 was published in February 1999, and this specification makes RFC2518 was published in February 1999, and this specification makes
minor revisions mostly due to interoperability experience. minor revisions mostly due to interoperability experience.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 7 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 7
2. Notational Conventions . . . . . . . . . . . . . . . . . . . 9 2. Notational Conventions . . . . . . . . . . . . . . . . . . . 9
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 10 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 10
4. Data Model for Resource Properties . . . . . . . . . . . . . 11 4. Data Model for Resource Properties . . . . . . . . . . . . . 11
4.1. The Resource Property Model . . . . . . . . . . . . . . 11 4.1. The Resource Property Model . . . . . . . . . . . . . . 11
4.2. Properties and HTTP Headers . . . . . . . . . . . . . . 11 4.2. Properties and HTTP Headers . . . . . . . . . . . . . . 11
4.3. XML Usage . . . . . . . . . . . . . . . . . . . . . . . 11 4.3. Property Values . . . . . . . . . . . . . . . . . . . . 11
4.4. Property Values . . . . . . . . . . . . . . . . . . . . 12 4.3.1. Example - Property with Mixed Content . . . . . . . 13
4.4.1. Example - Property with Mixed Content . . . . . . . 14 4.4. Property Names . . . . . . . . . . . . . . . . . . . . . 15
4.5. Property Names . . . . . . . . . . . . . . . . . . . . . 15 4.5. Source Resources and Output Resources . . . . . . . . . 15
4.6. Source Resources and Output Resources . . . . . . . . . 16 5. Collections of Web Resources . . . . . . . . . . . . . . . . 16
5. Collections of Web Resources . . . . . . . . . . . . . . . . 17 5.1. HTTP URL Namespace Model . . . . . . . . . . . . . . . . 16
5.1. HTTP URL Namespace Model . . . . . . . . . . . . . . . . 17 5.2. Collection Resources . . . . . . . . . . . . . . . . . . 16
5.2. Collection Resources . . . . . . . . . . . . . . . . . . 17 6. Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6. Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 6.1. Exclusive Vs. Shared Locks . . . . . . . . . . . . . . . 18
6.1. Exclusive Vs. Shared Locks . . . . . . . . . . . . . . . 19 6.2. Required Support . . . . . . . . . . . . . . . . . . . . 19
6.2. Required Support . . . . . . . . . . . . . . . . . . . . 20 6.3. Lock Creator . . . . . . . . . . . . . . . . . . . . . . 19
6.3. Lock Tokens . . . . . . . . . . . . . . . . . . . . . . 20 6.4. Lock Tokens . . . . . . . . . . . . . . . . . . . . . . 20
6.4. Lock Capability Discovery . . . . . . . . . . . . . . . 21 6.5. Lock Capability Discovery . . . . . . . . . . . . . . . 20
6.5. Active Lock Discovery . . . . . . . . . . . . . . . . . 21 6.6. Active Lock Discovery . . . . . . . . . . . . . . . . . 21
6.6. Locks and Multiple Bindings . . . . . . . . . . . . . . 22 6.7. Locks and Multiple Bindings . . . . . . . . . . . . . . 21
7. Write Lock . . . . . . . . . . . . . . . . . . . . . . . . . 23 7. Write Lock . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.1. Lock Owner . . . . . . . . . . . . . . . . . . . . . . . 23 7.1. Methods Restricted by Write Locks . . . . . . . . . . . 22
7.2. Methods Restricted by Write Locks . . . . . . . . . . . 23 7.2. Write Locks and Lock Tokens . . . . . . . . . . . . . . 22
7.3. Write Locks and Lock Tokens . . . . . . . . . . . . . . 24 7.3. Write Locks and Properties . . . . . . . . . . . . . . . 23
7.4. Write Locks and Properties . . . . . . . . . . . . . . . 24 7.4. Avoiding Lost Updates . . . . . . . . . . . . . . . . . 23
7.5. Avoiding Lost Updates . . . . . . . . . . . . . . . . . 24 7.5. Write Locks and Unmapped URLs . . . . . . . . . . . . . 24
7.6. Write Locks and Unmapped URLs . . . . . . . . . . . . . 25 7.6. Write Locks and Collections . . . . . . . . . . . . . . 26
7.7. Write Locks and Collections . . . . . . . . . . . . . . 27 7.7. Write Locks and the If Request Header . . . . . . . . . 27
7.8. Write Locks and the If Request Header . . . . . . . . . 29 7.7.1. Example - Write Lock and COPY . . . . . . . . . . . 28
7.8.1. Example - Write Lock . . . . . . . . . . . . . . . . 29 7.7.2. Example - Deleting a member of a locked collection . 28
7.9. Write Locks and COPY/MOVE . . . . . . . . . . . . . . . 30 7.8. Write Locks and COPY/MOVE . . . . . . . . . . . . . . . 29
7.10. Refreshing Write Locks . . . . . . . . . . . . . . . . . 30 7.9. Refreshing Write Locks . . . . . . . . . . . . . . . . . 30
8. HTTP Methods for Distributed Authoring . . . . . . . . . . . 31 8. HTTP Methods for Distributed Authoring . . . . . . . . . . . 31
8.1. General Request and Response Handling . . . . . . . . . 31 8.1. General Request and Response Handling . . . . . . . . . 31
8.1.1. Use of XML . . . . . . . . . . . . . . . . . . . . . 31 8.1.1. Use of XML . . . . . . . . . . . . . . . . . . . . . 31
8.1.2. Required Bodies in Requests . . . . . . . . . . . . 31 8.1.2. Required Bodies in Requests . . . . . . . . . . . . 31
8.1.3. HTTP Headers for use in WebDAV . . . . . . . . . . . 31 8.1.3. HTTP Headers for use in WebDAV . . . . . . . . . . . 31
8.1.4. ETag . . . . . . . . . . . . . . . . . . . . . . . . 31 8.1.4. ETag . . . . . . . . . . . . . . . . . . . . . . . . 32
8.1.5. Including error response bodies . . . . . . . . . . 32 8.1.5. Including error response bodies . . . . . . . . . . 32
8.2. PROPFIND . . . . . . . . . . . . . . . . . . . . . . . . 32 8.1.6. Impact of Namespace Operations on Cache Validators . 33
8.2.1. PROPFIND status codes . . . . . . . . . . . . . . . 34 8.2. PROPFIND Method . . . . . . . . . . . . . . . . . . . . 33
8.2.2. Status codes for use with 207 (Multi-Status) . . . . 34 8.2.1. PROPFIND status codes . . . . . . . . . . . . . . . 35
8.2.3. Example - Retrieving Named Properties . . . . . . . 35 8.2.2. Status codes for use with 207 (Multi-Status) . . . . 35
8.2.4. Example - Retrieving Named and Dead Properties . . . 37 8.2.3. Example - Retrieving Named Properties . . . . . . . 36
8.2.4. Example - Retrieving Named and Dead Properties . . . 38
8.2.5. Example - Using 'propname' to Retrieve all 8.2.5. Example - Using 'propname' to Retrieve all
Property Names . . . . . . . . . . . . . . . . . . . 37 Property Names . . . . . . . . . . . . . . . . . . . 38
8.2.6. Example - Using 'allprop' . . . . . . . . . . . . . 39 8.2.6. Example - Using 'allprop' . . . . . . . . . . . . . 40
8.3. PROPPATCH . . . . . . . . . . . . . . . . . . . . . . . 41 8.3. PROPPATCH Method . . . . . . . . . . . . . . . . . . . . 42
8.3.1. Status Codes for use in 207 (Multi-Status) . . . . . 42 8.3.1. Status Codes for use in 207 (Multi-Status) . . . . . 43
8.3.2. Example - PROPPATCH . . . . . . . . . . . . . . . . 43 8.3.2. Example - PROPPATCH . . . . . . . . . . . . . . . . 44
8.4. MKCOL Method . . . . . . . . . . . . . . . . . . . . . . 44 8.4. MKCOL Method . . . . . . . . . . . . . . . . . . . . . . 45
8.4.1. MKCOL Status Codes . . . . . . . . . . . . . . . . . 45 8.4.1. MKCOL Status Codes . . . . . . . . . . . . . . . . . 46
8.4.2. Example - MKCOL . . . . . . . . . . . . . . . . . . 45 8.4.2. Example - MKCOL . . . . . . . . . . . . . . . . . . 46
8.5. GET, HEAD for Collections . . . . . . . . . . . . . . . 46 8.5. GET, HEAD for Collections . . . . . . . . . . . . . . . 47
8.6. POST for Collections . . . . . . . . . . . . . . . . . . 46 8.6. POST for Collections . . . . . . . . . . . . . . . . . . 47
8.7. DELETE . . . . . . . . . . . . . . . . . . . . . . . . . 46 8.7. DELETE Requirements . . . . . . . . . . . . . . . . . . 47
8.7.1. DELETE for Collections . . . . . . . . . . . . . . . 47 8.7.1. DELETE for Collections . . . . . . . . . . . . . . . 48
8.7.2. Example - DELETE . . . . . . . . . . . . . . . . . . 47 8.7.2. Example - DELETE . . . . . . . . . . . . . . . . . . 48
8.8. PUT . . . . . . . . . . . . . . . . . . . . . . . . . . 48 8.8. PUT Requirements . . . . . . . . . . . . . . . . . . . . 49
8.8.1. PUT for Non-Collection Resources . . . . . . . . . . 48 8.8.1. PUT for Non-Collection Resources . . . . . . . . . . 49
8.8.2. PUT for Collections . . . . . . . . . . . . . . . . 48 8.8.2. PUT for Collections . . . . . . . . . . . . . . . . 50
8.9. COPY . . . . . . . . . . . . . . . . . . . . . . . . . . 49 8.9. COPY Method . . . . . . . . . . . . . . . . . . . . . . 50
8.9.1. COPY for Non-collection Resources . . . . . . . . . 49 8.9.1. COPY for Non-collection Resources . . . . . . . . . 50
8.9.2. COPY for Properties . . . . . . . . . . . . . . . . 49 8.9.2. COPY for Properties . . . . . . . . . . . . . . . . 51
8.9.3. COPY for Collections . . . . . . . . . . . . . . . . 50 8.9.3. COPY for Collections . . . . . . . . . . . . . . . . 51
8.9.4. COPY and Overwriting Destination Resources . . . . . 51 8.9.4. COPY and Overwriting Destination Resources . . . . . 52
8.9.5. Status Codes . . . . . . . . . . . . . . . . . . . . 51 8.9.5. Status Codes . . . . . . . . . . . . . . . . . . . . 53
8.9.6. Example - COPY with Overwrite . . . . . . . . . . . 52 8.9.6. Example - COPY with Overwrite . . . . . . . . . . . 54
8.9.7. Example - COPY with No Overwrite . . . . . . . . . . 53 8.9.7. Example - COPY with No Overwrite . . . . . . . . . . 54
8.9.8. Example - COPY of a Collection . . . . . . . . . . . 53 8.9.8. Example - COPY of a Collection . . . . . . . . . . . 55
8.10. MOVE . . . . . . . . . . . . . . . . . . . . . . . . . . 54 8.10. MOVE Method . . . . . . . . . . . . . . . . . . . . . . 55
8.10.1. MOVE for Properties . . . . . . . . . . . . . . . . 55 8.10.1. MOVE for Properties . . . . . . . . . . . . . . . . 56
8.10.2. MOVE for Collections . . . . . . . . . . . . . . . . 55 8.10.2. MOVE for Collections . . . . . . . . . . . . . . . . 56
8.10.3. MOVE and the Overwrite Header . . . . . . . . . . . 56 8.10.3. MOVE and the Overwrite Header . . . . . . . . . . . 57
8.10.4. Status Codes . . . . . . . . . . . . . . . . . . . . 56 8.10.4. Status Codes . . . . . . . . . . . . . . . . . . . . 57
8.10.5. Example - MOVE of a Non-Collection . . . . . . . . . 57 8.10.5. Example - MOVE of a Non-Collection . . . . . . . . . 58
8.10.6. Example - MOVE of a Collection . . . . . . . . . . . 58 8.10.6. Example - MOVE of a Collection . . . . . . . . . . . 59
8.11. LOCK Method . . . . . . . . . . . . . . . . . . . . . . 58 8.11. LOCK Method . . . . . . . . . . . . . . . . . . . . . . 59
8.11.1. Refreshing Locks . . . . . . . . . . . . . . . . . . 59 8.11.1. Refreshing Locks . . . . . . . . . . . . . . . . . . 60
8.11.2. Depth and Locking . . . . . . . . . . . . . . . . . 60 8.11.2. Depth and Locking . . . . . . . . . . . . . . . . . 61
8.11.3. Locking Unmapped URLs . . . . . . . . . . . . . . . 60 8.11.3. Locking Unmapped URLs . . . . . . . . . . . . . . . 61
8.11.4. Lock Compatibility Table . . . . . . . . . . . . . . 60 8.11.4. Lock Compatibility Table . . . . . . . . . . . . . . 62
8.11.5. LOCK Responses . . . . . . . . . . . . . . . . . . . 61 8.11.5. LOCK Responses . . . . . . . . . . . . . . . . . . . 62
8.11.6. Example - Simple Lock Request . . . . . . . . . . . 62 8.11.6. Example - Simple Lock Request . . . . . . . . . . . 63
8.11.7. Example - Refreshing a Write Lock . . . . . . . . . 64 8.11.7. Example - Refreshing a Write Lock . . . . . . . . . 65
8.11.8. Example - Multi-Resource Lock Request . . . . . . . 65 8.11.8. Example - Multi-Resource Lock Request . . . . . . . 66
8.12. UNLOCK Method . . . . . . . . . . . . . . . . . . . . . 66 8.12. UNLOCK Method . . . . . . . . . . . . . . . . . . . . . 67
8.12.1. Status Codes . . . . . . . . . . . . . . . . . . . . 66 8.12.1. Status Codes . . . . . . . . . . . . . . . . . . . . 67
8.12.2. Example - UNLOCK . . . . . . . . . . . . . . . . . . 67 8.12.2. Example - UNLOCK . . . . . . . . . . . . . . . . . . 68
9. HTTP Headers for Distributed Authoring . . . . . . . . . . . 68 9. HTTP Headers for Distributed Authoring . . . . . . . . . . . 69
9.1. DAV Header . . . . . . . . . . . . . . . . . . . . . . . 68 9.1. DAV Header . . . . . . . . . . . . . . . . . . . . . . . 69
9.2. Depth Header . . . . . . . . . . . . . . . . . . . . . . 68 9.2. Depth Header . . . . . . . . . . . . . . . . . . . . . . 69
9.3. Destination Header . . . . . . . . . . . . . . . . . . . 70 9.3. Destination Header . . . . . . . . . . . . . . . . . . . 71
9.4. If Header . . . . . . . . . . . . . . . . . . . . . . . 70 9.4. If Header . . . . . . . . . . . . . . . . . . . . . . . 71
9.4.1. No-tag-list Production . . . . . . . . . . . . . . . 71 9.4.1. No-tag-list Production . . . . . . . . . . . . . . . 72
9.4.2. Tagged-list Production . . . . . . . . . . . . . . . 71 9.4.2. Tagged-list Production . . . . . . . . . . . . . . . 72
9.4.3. Example - Tagged List If header in COPY . . . . . . 72 9.4.3. Example - Tagged List If header in COPY . . . . . . 73
9.4.4. Not Production . . . . . . . . . . . . . . . . . . . 72 9.4.4. Not Production . . . . . . . . . . . . . . . . . . . 73
9.4.5. Matching Function . . . . . . . . . . . . . . . . . 73 9.4.5. Matching Function . . . . . . . . . . . . . . . . . 74
9.4.6. If Header and Non-DAV Aware Proxies . . . . . . . . 73 9.4.6. If Header and Non-DAV Aware Proxies . . . . . . . . 74
9.5. Lock-Token Header . . . . . . . . . . . . . . . . . . . 74 9.5. Lock-Token Header . . . . . . . . . . . . . . . . . . . 75
9.6. Overwrite Header . . . . . . . . . . . . . . . . . . . . 74 9.6. Overwrite Header . . . . . . . . . . . . . . . . . . . . 75
9.7. Timeout Request Header . . . . . . . . . . . . . . . . . 74 9.7. Timeout Request Header . . . . . . . . . . . . . . . . . 75
10. Status Code Extensions to HTTP/1.1 . . . . . . . . . . . . . 76 10. Status Code Extensions to HTTP/1.1 . . . . . . . . . . . . . 77
10.1. 207 Multi-Status . . . . . . . . . . . . . . . . . . . . 76 10.1. 207 Multi-Status . . . . . . . . . . . . . . . . . . . . 77
10.2. 422 Unprocessable Entity . . . . . . . . . . . . . . . . 76 10.2. 422 Unprocessable Entity . . . . . . . . . . . . . . . . 77
10.3. 423 Locked . . . . . . . . . . . . . . . . . . . . . . . 76 10.3. 423 Locked . . . . . . . . . . . . . . . . . . . . . . . 77
10.4. 424 Failed Dependency . . . . . . . . . . . . . . . . . 76 10.4. 424 Failed Dependency . . . . . . . . . . . . . . . . . 77
10.5. 507 Insufficient Storage . . . . . . . . . . . . . . . . 76 10.5. 507 Insufficient Storage . . . . . . . . . . . . . . . . 77
11. Use of HTTP Status Codes . . . . . . . . . . . . . . . . . . 77 11. Use of HTTP Status Codes . . . . . . . . . . . . . . . . . . 78
11.1. 412 Precondition Failed . . . . . . . . . . . . . . . . 77 11.1. 412 Precondition Failed . . . . . . . . . . . . . . . . 78
11.2. 414 Request-URI Too Long . . . . . . . . . . . . . . . . 77 11.2. 414 Request-URI Too Long . . . . . . . . . . . . . . . . 78
12. Multi-Status Response . . . . . . . . . . . . . . . . . . . . 78 12. Multi-Status Response . . . . . . . . . . . . . . . . . . . . 79
12.1. Response headers . . . . . . . . . . . . . . . . . . . . 78 12.1. Response headers . . . . . . . . . . . . . . . . . . . . 79
12.2. URL Handling . . . . . . . . . . . . . . . . . . . . . . 78 12.2. URL Handling . . . . . . . . . . . . . . . . . . . . . . 79
12.3. Handling redirected child resources . . . . . . . . . . 79 12.3. Handling redirected child resources . . . . . . . . . . 80
12.4. Internal Status Codes . . . . . . . . . . . . . . . . . 79 12.4. Internal Status Codes . . . . . . . . . . . . . . . . . 80
13. XML Element Definitions . . . . . . . . . . . . . . . . . . . 80 13. XML Element Definitions . . . . . . . . . . . . . . . . . . . 81
13.1. activelock XML Element . . . . . . . . . . . . . . . . . 80 13.1. activelock XML Element . . . . . . . . . . . . . . . . . 81
13.2. allprop XML Element . . . . . . . . . . . . . . . . . . 80 13.2. allprop XML Element . . . . . . . . . . . . . . . . . . 81
13.3. collection XML Element . . . . . . . . . . . . . . . . . 80 13.3. collection XML Element . . . . . . . . . . . . . . . . . 81
13.4. dead-props XML Element . . . . . . . . . . . . . . . . . 81 13.4. depth XML Element . . . . . . . . . . . . . . . . . . . 82
13.5. depth XML Element . . . . . . . . . . . . . . . . . . . 81 13.5. error XML Element . . . . . . . . . . . . . . . . . . . 82
13.6. error XML Element . . . . . . . . . . . . . . . . . . . 81 13.6. exclusive XML Element . . . . . . . . . . . . . . . . . 82
13.7. exclusive XML Element . . . . . . . . . . . . . . . . . 82 13.7. href XML Element . . . . . . . . . . . . . . . . . . . . 82
13.8. href XML Element . . . . . . . . . . . . . . . . . . . . 82 13.8. include XML Element . . . . . . . . . . . . . . . . . . 83
13.9. location XML Element . . . . . . . . . . . . . . . . . . 82 13.9. location XML Element . . . . . . . . . . . . . . . . . . 83
13.10. lockentry XML Element . . . . . . . . . . . . . . . . . 83 13.10. lockentry XML Element . . . . . . . . . . . . . . . . . 83
13.11. lockinfo XML Element . . . . . . . . . . . . . . . . . . 83 13.11. lockinfo XML Element . . . . . . . . . . . . . . . . . . 83
13.12. lockroot XML Element . . . . . . . . . . . . . . . . . . 83 13.12. lockroot XML Element . . . . . . . . . . . . . . . . . . 84
13.13. lockscope XML Element . . . . . . . . . . . . . . . . . 84 13.13. lockscope XML Element . . . . . . . . . . . . . . . . . 84
13.14. locktoken XML Element . . . . . . . . . . . . . . . . . 84 13.14. locktoken XML Element . . . . . . . . . . . . . . . . . 84
13.15. locktype XML Element . . . . . . . . . . . . . . . . . . 84 13.15. locktype XML Element . . . . . . . . . . . . . . . . . . 84
13.16. multistatus XML Element . . . . . . . . . . . . . . . . 85 13.16. multistatus XML Element . . . . . . . . . . . . . . . . 85
13.17. owner XML Element . . . . . . . . . . . . . . . . . . . 85 13.17. prop XML element . . . . . . . . . . . . . . . . . . . . 85
13.18. prop XML element . . . . . . . . . . . . . . . . . . . . 85 13.18. propertyupdate XML element . . . . . . . . . . . . . . . 85
13.19. propertyupdate XML element . . . . . . . . . . . . . . . 86 13.19. propfind XML Element . . . . . . . . . . . . . . . . . . 86
13.20. propfind XML Element . . . . . . . . . . . . . . . . . . 86 13.20. propname XML Element . . . . . . . . . . . . . . . . . . 86
13.21. propname XML Element . . . . . . . . . . . . . . . . . . 86 13.21. propstat XML Element . . . . . . . . . . . . . . . . . . 86
13.22. propstat XML Element . . . . . . . . . . . . . . . . . . 87 13.22. remove XML element . . . . . . . . . . . . . . . . . . . 86
13.23. remove XML element . . . . . . . . . . . . . . . . . . . 87 13.23. response XML Element . . . . . . . . . . . . . . . . . . 87
13.24. response XML Element . . . . . . . . . . . . . . . . . . 87 13.24. responsedescription XML Element . . . . . . . . . . . . 87
13.25. responsedescription XML Element . . . . . . . . . . . . 88 13.25. set XML element . . . . . . . . . . . . . . . . . . . . 87
13.26. set XML element . . . . . . . . . . . . . . . . . . . . 88 13.26. shared XML Element . . . . . . . . . . . . . . . . . . . 88
13.27. shared XML Element . . . . . . . . . . . . . . . . . . . 89 13.27. status XML Element . . . . . . . . . . . . . . . . . . . 88
13.28. status XML Element . . . . . . . . . . . . . . . . . . . 89 13.28. timeout XML Element . . . . . . . . . . . . . . . . . . 88
13.29. timeout XML Element . . . . . . . . . . . . . . . . . . 89 13.29. write XML Element . . . . . . . . . . . . . . . . . . . 89
13.30. write XML Element . . . . . . . . . . . . . . . . . . . 90 14. DAV Properties . . . . . . . . . . . . . . . . . . . . . . . 90
14. DAV Properties . . . . . . . . . . . . . . . . . . . . . . . 91 14.1. creationdate Property . . . . . . . . . . . . . . . . . 90
14.1. creationdate Property . . . . . . . . . . . . . . . . . 91 14.2. displayname Property . . . . . . . . . . . . . . . . . . 91
14.2. displayname Property . . . . . . . . . . . . . . . . . . 92 14.3. getcontentlanguage Property . . . . . . . . . . . . . . 91
14.3. getcontentlanguage Property . . . . . . . . . . . . . . 92 14.4. getcontentlength Property . . . . . . . . . . . . . . . 92
14.4. getcontentlength Property . . . . . . . . . . . . . . . 93 14.5. getcontenttype Property . . . . . . . . . . . . . . . . 92
14.5. getcontenttype Property . . . . . . . . . . . . . . . . 94 14.6. getetag Property . . . . . . . . . . . . . . . . . . . . 93
14.6. getetag Property . . . . . . . . . . . . . . . . . . . . 94 14.7. getlastmodified Property . . . . . . . . . . . . . . . . 93
14.7. getlastmodified Property . . . . . . . . . . . . . . . . 95 14.8. lockdiscovery Property . . . . . . . . . . . . . . . . . 94
14.8. lockdiscovery Property . . . . . . . . . . . . . . . . . 95 14.8.1. Example - Retrieving DAV:lockdiscovery . . . . . . . 95
14.8.1. Example - Retrieving the lockdiscovery Property . . 96 14.9. resourcetype Property . . . . . . . . . . . . . . . . . 96
14.9. resourcetype Property . . . . . . . . . . . . . . . . . 97 14.10. supportedlock Property . . . . . . . . . . . . . . . . . 97
14.10. supportedlock Property . . . . . . . . . . . . . . . . . 98 14.10.1. Example - Retrieving DAV:supportedlock . . . . . . . 98
14.10.1. Example - Retrieving the DAV:supportedlock 15. Precondition/postcondition XML elements . . . . . . . . . . . 99
Property . . . . . . . . . . . . . . . . . . . . . . 99 16. XML Extensibility in DAV . . . . . . . . . . . . . . . . . . 103
15. Precondition/postcondition XML elements . . . . . . . . . . . 100 17. DAV Compliance Classes . . . . . . . . . . . . . . . . . . . 105
15.1. Example - Response with precondition code . . . . . . . 101 17.1. Class 1 . . . . . . . . . . . . . . . . . . . . . . . . 105
16. Instructions for Processing XML in DAV . . . . . . . . . . . 103 17.2. Class 2 . . . . . . . . . . . . . . . . . . . . . . . . 105
17. DAV Compliance Classes . . . . . . . . . . . . . . . . . . . 104 17.3. Class 'bis' . . . . . . . . . . . . . . . . . . . . . . 105
17.1. Class 1 . . . . . . . . . . . . . . . . . . . . . . . . 104 18. Internationalization Considerations . . . . . . . . . . . . . 106
17.2. Class 2 . . . . . . . . . . . . . . . . . . . . . . . . 104 19. Security Considerations . . . . . . . . . . . . . . . . . . . 108
17.3. Class 'bis' . . . . . . . . . . . . . . . . . . . . . . 104 19.1. Authentication of Clients . . . . . . . . . . . . . . . 108
18. Internationalization Considerations . . . . . . . . . . . . . 105 19.2. Denial of Service . . . . . . . . . . . . . . . . . . . 108
19. Security Considerations . . . . . . . . . . . . . . . . . . . 107 19.3. Security through Obscurity . . . . . . . . . . . . . . . 109
19.1. Authentication of Clients . . . . . . . . . . . . . . . 107 19.4. Privacy Issues Connected to Locks . . . . . . . . . . . 109
19.2. Denial of Service . . . . . . . . . . . . . . . . . . . 107 19.5. Privacy Issues Connected to Properties . . . . . . . . . 109
19.3. Security through Obscurity . . . . . . . . . . . . . . . 108 19.6. Implications of XML Entities . . . . . . . . . . . . . . 110
19.4. Privacy Issues Connected to Locks . . . . . . . . . . . 108 19.7. Risks Connected with Lock Tokens . . . . . . . . . . . . 111
19.5. Privacy Issues Connected to Properties . . . . . . . . . 108 19.8. Hosting malicious scripts executed on client machines . 111
19.6. Implications of XML Entities . . . . . . . . . . . . . . 109 20. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 113
19.7. Risks Connected with Lock Tokens . . . . . . . . . . . . 110 20.1. New URI Schemes . . . . . . . . . . . . . . . . . . . . 113
19.8. Hosting malicious scripts executed on client machines . 110 20.2. XML Namespaces . . . . . . . . . . . . . . . . . . . . . 113
20. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 112 20.3. Message Header Fields . . . . . . . . . . . . . . . . . 113
21. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 113 20.3.1. DAV . . . . . . . . . . . . . . . . . . . . . . . . 113
21.1. Previous Authors' Addresses . . . . . . . . . . . . . . 114 20.3.2. Depth . . . . . . . . . . . . . . . . . . . . . . . 113
22. References . . . . . . . . . . . . . . . . . . . . . . . . . 115 20.3.3. Destination . . . . . . . . . . . . . . . . . . . . 114
22.1. Normative References . . . . . . . . . . . . . . . . . . 115 20.3.4. If . . . . . . . . . . . . . . . . . . . . . . . . . 114
22.2. Informational References . . . . . . . . . . . . . . . . 115 20.3.5. Lock-Token . . . . . . . . . . . . . . . . . . . . . 114
Appendix A. Notes on Processing XML Elements . . . . . . . . . . 117 20.3.6. Overwrite . . . . . . . . . . . . . . . . . . . . . 114
A.1. Notes on Empty XML Elements . . . . . . . . . . . . . . 117 20.3.7. Timeout . . . . . . . . . . . . . . . . . . . . . . 115
A.2. Notes on Illegal XML Processing . . . . . . . . . . . . 117 21. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 116
A.3. Example - XML Syntax Error . . . . . . . . . . . . . . . 117 21.1. Previous Authors' Addresses . . . . . . . . . . . . . . 117
A.4. Example - Unknown XML Element . . . . . . . . . . . . . 118 22. References . . . . . . . . . . . . . . . . . . . . . . . . . 118
Appendix B. Notes on HTTP Client Compatibility . . . . . . . . . 119 22.1. Normative References . . . . . . . . . . . . . . . . . . 118
Appendix C. The opaquelocktoken scheme and URIs . . . . . . . . 120 22.2. Informational References . . . . . . . . . . . . . . . . 119
Appendix D. Guidance for Clients Desiring to Authenticate . . . 121 Appendix A. Notes on Processing XML Elements . . . . . . . . . . 120
Appendix E. Summary of changes from RFC2518 . . . . . . . . . . 123 A.1. Notes on Empty XML Elements . . . . . . . . . . . . . . 120
E.1. Changes Notable to Server Implementors . . . . . . . . . 123 A.2. Notes on Illegal XML Processing . . . . . . . . . . . . 120
E.2. Changes Notable to Client Implementors . . . . . . . . . 124 A.3. Example - XML Syntax Error . . . . . . . . . . . . . . . 120
A.4. Example - Unknown XML Element . . . . . . . . . . . . . 121
Appendix B. Notes on HTTP Client Compatibility . . . . . . . . . 122
Appendix C. The opaquelocktoken scheme and URIs . . . . . . . . 123
Appendix D. Guidance for Clients Desiring to Authenticate . . . 124
Appendix E. Summary of changes from RFC2518 . . . . . . . . . . 126
E.1. Changes Notable to Server Implementors . . . . . . . . . 126
E.2. Changes Notable to Client Implementors . . . . . . . . . 127
Appendix F. Change Log (to be removed by RFC Editor before Appendix F. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 126 publication) . . . . . . . . . . . . . . . . . . . . 129
F.1. Changes from -05 to -06 . . . . . . . . . . . . . . . . 126 F.1. Changes from -05 to -06 . . . . . . . . . . . . . . . . 129
F.2. Changes in -07 . . . . . . . . . . . . . . . . . . . . . 126 F.2. Changes in -07 . . . . . . . . . . . . . . . . . . . . . 129
F.3. Changes in -08 . . . . . . . . . . . . . . . . . . . . . 127 F.3. Changes in -08 . . . . . . . . . . . . . . . . . . . . . 130
F.4. Changes in -09 . . . . . . . . . . . . . . . . . . . . . 128 F.4. Changes in -09 . . . . . . . . . . . . . . . . . . . . . 131
F.5. Chandles in -10 . . . . . . . . . . . . . . . . . . . . 129 F.5. Changes in -10 . . . . . . . . . . . . . . . . . . . . . 132
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 130 F.6. Changes in -11 . . . . . . . . . . . . . . . . . . . . . 132
Intellectual Property and Copyright Statements . . . . . . . . . 131 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 133
Intellectual Property and Copyright Statements . . . . . . . . . 134
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 page 8, line 12 skipping to change at page 8, line 12
(Section 11) as used in WebDAV. Since some WebDAV methods may (Section 11) as used in WebDAV. Since some WebDAV methods may
operate over many resources, the Multi-Status response (Section 12) operate over many resources, the Multi-Status response (Section 12)
has been introduced to return status information for multiple has been introduced to return status information for multiple
resources. Finally, this version of WebDAV introduces precondition resources. Finally, this version of WebDAV introduces precondition
and postcondition (Section 15) XML elements in error response bodies. and postcondition (Section 15) XML elements in error response bodies.
WebDAV uses [XML] for property names and some values, and also uses WebDAV uses [XML] for property names and some values, and also uses
XML to marshal complicated request and response. This specification XML to marshal complicated request and response. This specification
contains DTD and text definitions of all all properties (Section 14) contains DTD and text definitions of all all properties (Section 14)
and all other XML elements (Section 13) used in marshalling. WebDAV and all other XML elements (Section 13) used in marshalling. WebDAV
includes a few special rules on how to process XML (Section 16) includes a few special rules on extending (Section 16) WebDAV XML
appearing in WebDAV so that it truly is extensible. marshalling in backwards-compatible ways.
Finishing off the specification are sections on what it means for a Finishing off the specification are sections on what it means for a
resource to be compliant with this specification (Section 17), on resource to be compliant with this specification (Section 17), on
internationalization support (Section 18), and on security internationalization support (Section 18), and on security
(Section 19). (Section 19).
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 elements protocol, the augmented BNF used herein to describe protocol elements
skipping to change at page 11, line 42 skipping to change at page 11, line 42
4.2. Properties and HTTP Headers 4.2. Properties and HTTP Headers
Properties already exist, in a limited sense, in HTTP message Properties already exist, in a limited sense, in HTTP message
headers. However, in distributed authoring environments a relatively headers. However, in distributed authoring environments a relatively
large number of properties are needed to describe the state of a large number of properties are needed to describe the state of a
resource, and setting/returning them all through HTTP headers is resource, and setting/returning them all through HTTP headers is
inefficient. Thus a mechanism is needed which allows a principal to inefficient. Thus a mechanism is needed which allows a principal to
identify a set of properties in which the principal is interested and identify a set of properties in which the principal is interested and
to set or retrieve just those properties. to set or retrieve just those properties.
4.3. XML Usage 4.3. Property Values
In HTTP/1.1, method parameter information was exclusively encoded in
HTTP headers. Unlike HTTP/1.1, WebDAV encodes method parameter
information either in an [XML] request entity body, or in an HTTP
header. The use of XML to encode method parameters was motivated by
the ability to add extra XML elements to existing structures,
providing extensibility; and by XML's ability to encode information
in ISO 10646 character sets, providing internationalization support.
In addition to encoding method parameters, XML is used in WebDAV to
encode the responses from methods, providing the extensibility and
internationalization advantages of XML for method output, as well as
input.
When XML is used for a request or response body, the MIME type SHOULD
be application/xml. Implementations MUST accept both text/xml and
application/xml in request and response bodies. Use of text/xml is
deprecated.
The XML namespace extension [W3C.REC-xml-names-19990114] is also used
in this specification in order to allow for new XML elements to be
added without fear of colliding with other element names. Although
WebDAV request and response bodies can be extended by arbitrary XML
elements, which can be ignored by the message recipient, an XML
element in the "DAV:" 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 WebDAV working group.
Note that "DAV:" uses a scheme name defined solely for the purpose of
creating this XML namespace. Defining new URI schemes for namespaces
is discouraged. "DAV:" was defined before standard best practices
emerged, and this namespace is still used only because of significant
existing deployments.
4.4. Property Values
The value of a property is always a (well-formed) XML fragment. The value of a property is always a (well-formed) 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 MUST ignore elements they do not in the original schema and MUST ignore elements they do not
skipping to change at page 13, line 5 skipping to change at page 12, line 18
user. XML's support for multiple human languages, using the "xml: user. XML's support for multiple human languages, using the "xml:
lang" attribute, handles cases where the same character set is lang" attribute, handles cases where the same character set is
employed by multiple human languages. Note that xml:lang scope is employed by multiple human languages. Note that xml:lang scope is
recursive, so a xml:lang attribute on any element containing a recursive, so a xml:lang attribute on any element containing a
property name element applies to the property value unless it has property name element applies to the property value unless it has
been overridden by a more locally scoped attribute. Note that a been overridden by a more locally scoped attribute. Note that a
property only has one value, in one language (or language MAY be left property only has one value, in one language (or language MAY be left
undefined), not multiple values in different languages or a single undefined), not multiple values in different languages or a single
value in multiple languages. value in multiple languages.
A property is always represented in XML with an XML element A property is always represented with an XML element consisting of
consisting of the property name, called the "property name element". the property name, called the "property name element". The simplest
The simplest example is an empty property, which is different from a example is an empty property, which is different from a property that
property that does not exist: 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 the property appears inside the property name element.
The value may be any kind of well-formed XML content, including both The value may be any kind of well-formed XML content, including both
text-only and mixed content. In the latter case, servers MUST text-only and mixed content. Servers MUST preserve the following XML
preserve certain aspects of the content (described using the Information Items (using the terminology from [W3C.REC-xml-infoset-
terminology from [W3C.REC-xml-infoset-20040204]). 20040204]) in storage and transmission of dead properties:
For the property name Element Information Item itself: For the property name Element Information Item itself:
[namespace name] [namespace name]
[local name] [local name]
[attributes] named "xml:lang" or any such attribute in scope [attributes] named "xml:lang" or any such attribute in scope
[children] of type element or character [children] of type element or character
On all Element Information Items in the value: On all Element Information Items in the property value:
[namespace name] [namespace name]
[local name] [local name]
[attributes] [attributes]
[children] of type element or character [children] of type element or character
On Attribute Information Items in the value: On Attribute Information Items in the property value:
[namespace name] [namespace name]
[local name] [local name]
[normalized value] [normalized value]
On Character Information Items in the value: On Character Information Items in the property value:
[character code] [character code]
Since prefixes are used in some XML query/handling tools, servers Since prefixes are used in some XML vocabularies (XPath and XML
SHOULD preserve, for any Information Item in the value: Schema, for example), servers SHOULD preserve, for any Information
[prefix]
In dead properties (considered as content, like document bodies)
servers are encouraged to (MAY) preserve, for any Comment Information
Item in the value: Item in the value:
[content] [prefix]
XML Infoset attributes not listed above MAY be preserved by the XML Infoset attributes not listed above MAY be preserved by the
server, but clients MUST NOT rely on them being preserved. server, but clients MUST NOT rely on them being preserved. The above
rules would also apply by default to live properties, unless defined
otherwise.
The XML attribute xml:space MUST NOT be used to change white space Servers MUST ignore the XML attribute xml:space if present and never
handling. White space in property values is significant. use it to change white space handling. White space in property
values is significant.
4.4.1. Example - Property with Mixed Content 4.3.1. Example - Property with Mixed Content
Consider a dead property 'author' created by the client as follows: Consider a dead property 'author' created by the client as follows:
<D:prop xml:lang="en"> <D:prop xml:lang="en" xmlns:D="DAV:">
<x:author xmlns:x='http://example.com/ns'> <x:author xmlns:x='http://example.com/ns'>
<x:name>Jane Doe</x:name> <x:name>Jane Doe</x:name>
<!-- Jane's contact info --> <!-- Jane's contact info -->
<x:uri type='email' <x:uri type='email'
added='2005-11-26'>mailto:jane.doe@example.com</x:uri> added='2005-11-26'>mailto:jane.doe@example.com</x:uri>
<x:uri type='web' <x:uri type='web'
added='2005-11-27'>http://www.example.com</x:uri> added='2005-11-27'>http://www.example.com</x:uri>
<x:notes xmlns:h='http://www.w3.org/1999/xhtml'> <x:notes xmlns:h='http://www.w3.org/1999/xhtml'>
Jane has been working way <h:em>too</h:em> long on the Jane has been working way <h:em>too</h:em> long on the
long-awaited revision of <![CDATA[<RFC2518>]]>. long-awaited revision of <![CDATA[<RFC2518>]]>.
</x:notes> </x:notes>
</x:author> </x:author>
</D:prop> </D:prop>
When this property is requested, a server might return: When this property is requested, a server might return:
<D:prop><author xmlns:x='http://example.com/ns' xml:lang="en" <D:prop xmlns:D='DAV:'><author
xml:lang='en'
xmlns:x='http://example.com/ns'
xmlns='http://example.com/ns' xmlns='http://example.com/ns'
xmlns:ns1='http://www.w3.org/1999/xhtml'> xmlns:h='http://www.w3.org/1999/xhtml'>
<x:name>Jane Doe</name> <x:name>Jane Doe</x:name>
<x:uri added="2005-11-26" type="email" <x:uri added="2005-11-26" type="email"
>mailto:jane.doe@example.com</x:uri> >mailto:jane.doe@example.com</x:uri>
<x:uri added="2005-11-27" type="web" <x:uri added="2005-11-27" type="web"
>http://www.example.com</x:uri> >http://www.example.com</x:uri>
<x:notes> <x:notes>
Jane has been working way <h:em>too</h:em> long on the Jane has been working way <h:em>too</h:em> long on the
long-awaited revision of &lt;RFC2518&gt;. long-awaited revision of &lt;RFC2518&gt;.
</x:notes> </x:notes>
</author> </author>
</D:prop> </D:prop>
Note in this example: Note in this example:
o The [prefix] for the property name itself was not preserved, being o The [prefix] for the property name itself was not preserved, being
non-significant non-significant, all other [prefix] values have been preserved,
o attribute values have been rewritten with double quotes instead of o attribute values have been rewritten with double quotes instead of
single quotes (quoting style is not significant), and attribute single quotes (quoting style is not significant), and attribute
order has not been preserved, order has not been preserved,
o the xml:lang attribute has been returned on the property name o the xml:lang attribute has been returned on the property name
element itself (it was in scope when the property was set, but the element itself (it was in scope when the property was set, but the
exact position in the response is not considered significant as exact position in the response is not considered significant as
long as it is in scope), long as it is in scope),
skipping to change at page 15, line 35 skipping to change at page 15, line 5
o the comment item was stripped (as would have been a processing o the comment item was stripped (as would have been a processing
instruction item). instruction item).
Implementation note: there are cases such as editing scenarios where Implementation note: there are cases such as editing scenarios where
clients may require that XML content is preserved character-by- clients may require that XML content is preserved character-by-
character (such as attribute ordering or quoting style). In this character (such as attribute ordering or quoting style). In this
case, clients should consider using a text-only property value by case, clients should consider using a text-only property value by
escaping all characters that have a special meaning in XML parsing. escaping all characters that have a special meaning in XML parsing.
4.5. Property Names 4.4. Property Names
A property name is a universally unique identifier that is associated A property name is a universally unique identifier that is associated
with a schema that provides information about the syntax and with a schema that provides information about the syntax and
semantics of the property. 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
resources, on the same and across different servers, so long as that resources, on the same and across different servers, so long as that
property is "live" on the resources in question, and the property is "live" on the resources in question, and the
implementation of the live property is faithful to its definition. implementation of the live property is faithful to its definition.
skipping to change at page 16, line 14 skipping to change at page 15, line 32
is explicitly recognized. Thus, if a property A and a property A/B is explicitly recognized. Thus, if a property A and a property A/B
exist on a resource, there is no recognition of any relationship exist on a resource, there is no recognition of any relationship
between the two properties. It is expected that a separate between the two properties. It is expected that a separate
specification will eventually be produced which will address issues specification will eventually be produced which will address issues
relating to hierarchical properties. relating to hierarchical properties.
Finally, it is not possible to define the same property twice on a Finally, it is not possible to define the same property twice on a
single resource, as this would cause a collision in the resource's single resource, as this would cause a collision in the resource's
property namespace. property namespace.
4.6. Source Resources and Output Resources 4.5. Source Resources and Output Resources
Some HTTP resources are dynamically generated by the server. For Some HTTP resources are dynamically generated by the server. For
these resources, there presumably exists source code somewhere these resources, there presumably exists source code somewhere
governing how that resource is generated. The relationship of source governing how that resource is generated. The relationship of source
files to output HTTP resources may be one to one, one to many, many files to output HTTP resources may be one to one, one to many, many
to one or many to many. There is no mechanism in HTTP to determine to one or many to many. There is no mechanism in HTTP to determine
whether a resource is even dynamic, let alone where its source files whether a resource is even dynamic, let alone where its source files
exist or how to author them. Although this problem would usefully be exist or how to author them. Although this problem would usefully be
solved, interoperable WebDAV implementations have been widely solved, interoperable WebDAV implementations have been widely
deployed without actually solving this problem, by dealing only with deployed without actually solving this problem, by dealing only with
skipping to change at page 19, line 24 skipping to change at page 18, line 24
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. Only one exclusive The most basic form of lock is an exclusive lock. Only one exclusive
lock may exist on any resource, whether it is directly or indirectly lock may exist on any resource, whether it is directly or indirectly
locked (Section 7.7). Exclusive locks avoid having to merge results, locked (Section 7.6). Exclusive locks avoid having to merge results,
without requiring any coordination other than the methods described without requiring any coordination other than the methods described
in this specification. 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
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 use the lock. principal with appropriate access can use the lock.
skipping to change at page 20, line 19 skipping to change at page 19, line 19
face interaction, written notes, post-it notes on the screen, face interaction, written notes, post-it notes on the screen,
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 creator 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 resource is not required to support locking in any A WebDAV compliant resource is not required to support locking in any
form. If the resource does support locking it may choose to support form. If the resource does support locking it may choose to support
any combination of exclusive and shared locks for any access types. any combination of exclusive and shared locks for any access types.
skipping to change at page 20, line 41 skipping to change at page 19, line 41
The reason for this flexibility is that locking policy strikes to the The reason for this flexibility is that locking policy strikes to the
very heart of the resource management and versioning systems employed very heart of the resource management and versioning systems employed
by various storage repositories. These repositories require control by various storage repositories. These repositories require control
over what sort of locking will be made available. For example, some over what sort of locking will be made available. For example, some
repositories only support shared write locks while others only repositories only support shared write locks while others only
provide support for exclusive write locks while yet others use no provide support for exclusive write locks while yet others use no
locking at all. As each system is sufficiently different to merit locking at all. As each system is sufficiently different to merit
exclusion of certain locking features, this specification leaves exclusion of certain locking features, this specification leaves
locking as the sole axis of negotiation within WebDAV. locking as the sole axis of negotiation within WebDAV.
6.3. Lock Tokens 6.3. Lock Creator
The creator of a lock has special privileges to use the locked
resource. The server MUST restrict the usage of a lock token to the
creator of the lock, both for shared and exclusive locks. For multi-
user shared lock cases, each authenticated principal MUST obtain its
own shared lock.
The server MAY allow privileged users other than the lock creator to
destroy a lock (for example, the resource owner or an administrator)
as a special case of lock usage.
If an anonymous user requests a lock, the server MAY refuse the
request.
6.4. 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. Each lock has exactly one unique lock identifies a particular lock. Each lock has exactly one unique lock
token generated by the server. Clients MUST NOT attempt to interpret token generated by the server. Clients MUST NOT attempt to interpret
lock tokens in any way. lock tokens in any way.
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. Since lock tokens resources and servers without fear of confusion. Since lock tokens
are unique, a client MAY submit a lock token in an If header on a are unique, a client MAY submit a lock token in an If header on a
skipping to change at page 21, line 33 skipping to change at page 20, line 49
This specification encourages servers to create UUIDs for lock This specification encourages servers to create UUIDs for lock
tokens, and to use the URI form defined by "A Universally Unique tokens, and to use the URI form defined by "A Universally Unique
Identifier (UUID) URN Namespace" ([RFC4122]). However servers are Identifier (UUID) URN Namespace" ([RFC4122]). However servers are
free to use any URI (e.g. from another scheme) so long as it meets free to use any URI (e.g. from another scheme) so long as it meets
the uniqueness requirements. For example, a valid lock token might the uniqueness requirements. For example, a valid lock token might
be constructed using the "opaquelocktoken" scheme defined in be constructed using the "opaquelocktoken" scheme defined in
Appendix C. Appendix C.
Example: "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6" Example: "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"
6.4. 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
resource on a server can either try the lock and hope for the best, resource on a server can either try the lock and hope for the best,
or perform some form of discovery to determine what lock capabilities or perform some form of discovery to determine what lock capabilities
the server supports. This is known as lock capability discovery. A the server supports. This is known as lock capability discovery. A
client can determine what lock types the server supports by client can determine what lock types the server supports by
retrieving the DAV:supportedlock property. retrieving the DAV:supportedlock property.
Any DAV compliant resource that supports the LOCK method MUST support Any DAV compliant resource that supports the LOCK method MUST support
the DAV:supportedlock property. the DAV:supportedlock property.
6.5. 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 DAV:lockdiscovery who the first principal is. For this purpose the DAV:lockdiscovery
property is provided. This property lists all outstanding locks, property is provided. This property lists all outstanding locks,
describes their type, and MAY even provide the lock tokens. describes their type, and MAY even provide the lock tokens.
Any DAV compliant resource that supports the LOCK method MUST support Any DAV compliant resource that supports the LOCK method MUST support
the DAV:lockdiscovery property. the DAV:lockdiscovery property.
6.6. Locks and Multiple Bindings 6.7. Locks and Multiple Bindings
A resource may be made available through more than one URI. A lock A resource may be made available through more than one URI. A lock
MUST cover the resource as well as the URI to which the LOCK request MUST cover the resource as well as the URI to which the LOCK request
was addressed. The lock MAY cover other URIs mapped to the same was addressed. The lock MAY cover other URIs mapped to the same
resource as well. resource as well.
7. Write Lock 7. Write Lock
This section describes the semantics specific to the write lock type. This section describes the semantics specific to the write lock type.
The write lock is a specific instance of a lock type, and is the only The write lock is a specific instance of a lock type, and is the only
skipping to change at page 23, line 29 skipping to change at page 22, line 29
o any live property defined to be lockable (all properties defined o any live property defined to be lockable (all properties defined
in this specification are lockable) in this specification are lockable)
o the direct membership of the resource, if it is a collection o the direct membership of the resource, if it is a collection
o the URL/location of a resource o the URL/location of a resource
The next few sections describe in more specific terms how write locks The next few sections describe in more specific terms how write locks
interact with various operations. interact with various operations.
7.1. Lock Owner 7.1. Methods Restricted by Write Locks
The creator of the lock is the lock owner. The server MUST restrict
the usage of the lock token to the lock owner (both for shared and
exclusive locks -- for multi-user shared lock cases, each
authenticated principal MUST obtain its own shared lock).
The server MAY allow privileged users other than the lock owner to
destroy a lock (for example, the resource owner or an administrator)
as a special case of lock usage.
If an anonymous user requests a lock, the server MAY refuse the
request.
7.2. Methods Restricted by Write Locks
A server MUST reject any write request that alters a write-locked A server MUST reject any write request that alters a write-locked
resource unless a valid lock token is provided. The write operations resource unless a valid lock token is provided. The write operations
defined in HTTP and WebDAV are PUT, POST, PROPPATCH, LOCK, UNLOCK, defined in HTTP and WebDAV are PUT, POST, PROPPATCH, LOCK, UNLOCK,
MOVE, COPY (for the destination resource), DELETE, and MKCOL. All MOVE, COPY (for the destination resource), DELETE, and MKCOL. All
other HTTP/WebDAV methods, GET in particular, function independently other HTTP/WebDAV methods, GET in particular, function independently
of the lock. A shared write lock prevents the same operations of the lock. A shared write lock prevents the same operations
(except additional requests for shared write locks), however it also (except additional requests for shared write locks), however it also
allows access by any principal that has a shared write lock on the allows access by any principal that has a shared write lock on the
same resource. same resource.
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.3. 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
requesting principal. Thus if five principals have a shared write requesting principal. Thus if five principals have a shared write
lock on the same resource there will be five lock tokens, one for lock on the same resource there will be five lock tokens, one for
each principal. each principal.
7.4. Write Locks and Properties 7.3. Write Locks and Properties
While those without a write lock may not alter a property on a While those without a write lock may not alter a property on a
resource it is still possible for the values of live properties to resource it is still possible for the values of live properties to
change, even while locked, due to the requirements of their schemas. change, even while locked, due to the requirements of their schemas.
Only dead properties and live properties defined to respect locks are Only dead properties and live properties defined to respect locks are
guaranteed not to change while write locked. guaranteed not to change while write locked.
7.5. Avoiding Lost Updates 7.4. Avoiding Lost Updates
Although the write locks provide some help in preventing lost Although the write locks provide some help in preventing lost
updates, they cannot guarantee that updates will never be lost. updates, they cannot guarantee that updates will never be lost.
Consider the following scenario: 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
skipping to change at page 25, line 23 skipping to change at page 24, line 10
they interact with a WebDAV server that supports locking. they interact with a WebDAV server that supports locking.
HTTP 1.1 clients can be good citizens, avoiding overwriting other HTTP 1.1 clients can be good citizens, avoiding overwriting other
clients' changes, by using entity tags in If-Match headers with any clients' changes, by using entity tags in If-Match headers with any
requests that would modify resources. requests that would modify resources.
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.6. Write Locks and Unmapped URLs 7.5. Write Locks and Unmapped URLs
WebDAV provides the ability to lock an unmapped URL in order to WebDAV provides the ability to lock an unmapped URL in order to
reserve the name for use. This is a simple way to avoid the lost- reserve the name for use. This is a simple way to avoid the lost-
update problem on the creation of a new resource (another way is to update problem on the creation of a new resource (another way is to
use If-None-Match header specified in HTTP 1.1). It has the side use If-None-Match header specified in HTTP 1.1). It has the side
benefit of locking the new resource immediately for use of the benefit of locking the new resource immediately for use of the
creator. creator.
Note that the lost-update problem is not an issue for collections Note that the lost-update problem is not an issue for collections
because MKCOL can only be used to create a collection, not to because MKCOL can only be used to create a collection, not to
overwrite an existing collection. When trying to lock a collection overwrite an existing collection. When trying to lock a collection
upon creation, clients may attempt to increase the likelihood of upon creation, clients may attempt to increase the likelihood of
getting the lock by pipelining the MKCOL and LOCK requests together getting the lock by pipelining the MKCOL and LOCK requests together
(but because this doesn't convert two separate operations into one (but because this doesn't convert two separate operations into one
atomic operation there's no guarantee this will work). atomic operation there's no guarantee this will work).
A successful lock request to an unmapped URL MUST result in the A successful lock request to an unmapped URL MUST result in the
creation of an locked resource with empty content. Subsequently, a creation of an locked resource with empty content. Subsequently, a
successful PUT request (with the correct lock token) provides the successful PUT request (with the correct lock token) provides the
content for the resource, and the server MUST also use the content- content for the resource, and a server that normally uses the client-
type and content-language information from this request. provided content-type MUST also use the content-type and content-
language information from this request.
The original WebDAV model for locking unmapped URLs created "lock- The original WebDAV model for locking unmapped URLs created "lock-
null resources". This model was over-complicated and some null resources". This model was over-complicated and some
interoperability and implementation problems were discovered. The interoperability and implementation problems were discovered. The
new WebDAV model for locking unmapped URLs creates "locked empty new WebDAV model for locking unmapped URLs creates "locked empty
resources". Servers MUST implement either lock-null resources or resources". Servers MUST implement either lock-null resources or
locked empty resources, but servers SHOULD implement locked empty locked empty resources, but servers SHOULD implement locked empty
resources. This section discusses the original model briefly and the resources. This section discusses the original model briefly and the
new model more completely, because clients MUST be able to handle new model more completely, because clients MUST be able to handle
either model. either model.
skipping to change at page 27, line 5 skipping to change at page 25, line 43
o SHOULD NOT disappear when its lock goes away (clients must o 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 or any non-empty resource) any other operation or any non-empty resource)
o SHOULD default to having no content type. o SHOULD default to having no content type.
o MAY NOT have values for properties like DAV:getcontentlanguage o MAY NOT have values for properties like DAV:getcontentlanguage
which haven't been specified yet by the client. which haven't been specified yet by the client.
o Can be updated (have content added) with a PUT request. The o Can be updated (have content added) with a PUT request.
server MUST be able to set the content type as specified in the
PUT request.
o MUST NOT be converted into a collection. The server MUST fail a o MUST NOT be converted into a collection. The server MUST fail a
MKCOL request (as it would with a MKCOL request to any existing MKCOL request (as it would with a MKCOL request to any existing
non-collection resource). non-collection resource).
o MUST have defined values for DAV:lockdiscovery and DAV: o MUST have defined values for DAV:lockdiscovery and DAV:
supportedlock properties. supportedlock properties.
o The response MUST indicate that a resource was created, by use of o 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 DAV:lockdiscovery property, as with a LOCK request to include the DAV:lockdiscovery property, as with a LOCK request to
an existing resource. an existing resource.
The client is expected to update the locked empty resource shortly The client is expected to update the locked empty resource shortly
after locking it, using PUT and possibly PROPPATCH. When the client after locking it, using PUT and possibly PROPPATCH. When the client
uses PUT to overwrite a locked empty resource the client MUST supply 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- a Content-Type if any is known.
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 Clients can easily interoperate both with servers that support the
old model "lock-null resources" and the recommended model of "locked old model "lock-null resources" and the recommended model of "locked
empty resources" by only attempting PUT after a LOCK to an unmapped empty resources" by only attempting PUT after a LOCK to an unmapped
URL, not MKCOL or GET. URL, not MKCOL or GET.
7.7. Write Locks and Collections 7.6. 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 URLs of the collection by non-lock owners. member URLs of the collection by principals other than the lock
creator.
A zero-depth lock on a collection affects changes to the direct A zero-depth lock on a collection affects changes to the direct
membership of that collection. When a principal issues a write membership of that collection. When a principal issues a write
request to create a new resource in a write locked collection, or request to create a new resource in a write locked collection, or
isses a DELETE, MOVE or other request that would remove an existing isses a DELETE, MOVE or other request that would remove an existing
internal member URL of a write locked collection or change the internal member URL of a write locked collection or change the
binding name, this request MUST fail if the principal does not binding name, this request MUST fail if the principal does not
provide the correct lock token for the locked collection. provide the correct lock token for the locked collection.
This means that if a collection is locked (depth 0 or infinity), its This means that if a collection is locked (depth 0 or infinity), its
skipping to change at page 28, line 41 skipping to change at page 27, line 26
o Any indirectly locked resource moved out of a locked source o Any indirectly locked resource moved out of a locked source
collection into a depth-infinity locked target collection remains collection into a depth-infinity locked target collection remains
indirectly locked but is now within the scope of the lock on the indirectly locked but is now within the scope of the lock on the
target collection (the target collection's lock token will target collection (the target collection's lock token will
thereafter be required to make further changes). thereafter be required to make further changes).
If a depth-infinity write LOCK request is issued to a collection If a depth-infinity write LOCK request is issued to a collection
containing member URLs identifying resources that are currently containing member URLs identifying resources that are currently
locked in a manner which conflicts with the write lock, the request locked in a manner which conflicts with the write lock, the request
MUST fail with a 423 (Locked) status code, and the response SHOULD MUST fail with a 423 (Locked) status code, and the response SHOULD
contain the 'lock-token-present' precondition. contain the 'no-conflicting-lock' precondition.
If a lock owner causes the URL of a resource to be added as an If a lock creator causes the URL of a resource to be added as an
internal member URL 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.8. Write Locks and the If Request Header 7.7. 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
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
skipping to change at page 29, line 30 skipping to change at page 28, line 13
same authorization. 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 for all locked resources that a method may by an authorized principal for all locked resources that a method may
change or the method MUST fail. A lock token is submitted when it change or the method MUST fail. A lock token is submitted when it
appears in an If header. For example, if a resource is to be moved appears in an If header. For example, if a resource is to be moved
and both the source and destination are locked then two lock tokens and both the source and destination are locked then two lock tokens
must be submitted in the if header, one for the source and the other must be submitted in the if header, one for the source and the other
for the destination. for the destination.
7.8.1. Example - Write Lock 7.7.1. Example - Write Lock and COPY
>>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>
(<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>) (<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>)
>>Response >>Response
skipping to change at page 30, line 5 skipping to change at page 28, line 35
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.9. Write Locks and COPY/MOVE 7.7.2. Example - Deleting a member of a locked collection
Consider a collection "/locked" exclusively write-locked with Depth:
Infinity, and an attempt to delete an internal member "/locked/
member":
>>Request
DELETE /locked/member HTTP/1.1
Host: example.com
>>Response
HTTP/1.1 423 Locked
Content-Type: application/xml; charset="utf-8"
Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?>
<D:error xmlns:D="DAV:">
<D:lock-token-present>
<D:href>/locked/</D:href>
</D:lock-token-present>
</D:error>
Thus the client would need to submit the lock token with the request
to make it succeed. To do that, various forms of the If header (see
Section 9.4) could be used.
"No-Tag-List" format:
If: (<urn:uuid:150852e2-3847-42d5-8cbe-0f4f296f26cf>)
"Tagged-List" format, for "http://example.com/locked/":
If: <http://example.com/locked/>
(<urn:uuid:150852e2-3847-42d5-8cbe-0f4f296f26cf>)
"Tagged-List" format, for "http://example.com/locked/member":
If: <http://example.com/locked/member>
(<urn:uuid:150852e2-3847-42d5-8cbe-0f4f296f26cf>)
Note that for the purpose of submitting the lock token the actual
form doesn't matter; what's relevant is that the lock token appears
in the If header, and that the If header itself evaluates to true.
7.8. Write Locks and COPY/MOVE
A COPY method invocation MUST NOT duplicate any write locks active on A COPY method invocation MUST NOT duplicate any write locks active on
the source. However, as previously noted, if the COPY copies the 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.
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, if there is an existing the write lock with the resource. However, if there is an existing
lock at the destination, the server MUST add the moved resource to lock at the destination, the server MUST add the moved resource to
the destination lock scope. For example, if the MOVE makes the the destination lock scope. For example, if the MOVE makes the
skipping to change at page 30, line 18 skipping to change at page 30, line 4
the source. However, as previously noted, if the COPY copies the 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.
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, if there is an existing the write lock with the resource. However, if there is an existing
lock at the destination, the server MUST add the moved resource to lock at the destination, the server MUST add the moved resource to
the destination lock scope. For example, if the MOVE makes the the destination lock scope. For example, if the MOVE makes the
resource a child of a collection that is locked with "Depth: resource a child of a collection that is locked with "Depth:
infinity", then the resource will be added to that collection's lock. infinity", then the resource will be added to that collection's lock.
Additionally, if a resource locked with "Depth: infinity" is moved to Additionally, if a resource locked with "Depth: infinity" is moved to
a destination that is within the scope of the same lock (e.g., within a destination that is within the scope of the same lock (e.g., within
the URL namespace tree covered by the lock), the moved resource will the URL namespace tree covered by the lock), the moved resource will
again be a added to the lock. In both these examples, as specified again be a added to the lock. In both these examples, as specified
in Section 7.8, an If header must be submitted containing a lock in Section 7.7, an If header must be submitted containing a lock
token for both the source and destination. token for both the source and destination.
7.10. Refreshing Write Locks 7.9. Refreshing Write Locks
A client MUST NOT submit the same write lock request twice. Note A client MUST NOT submit the same write lock request twice. Note
that a client is always aware it is resubmitting the same lock that a client is always aware it is resubmitting the same lock
request because it must include the lock token in the If header in request because it must include the lock token in the If header in
order to make the request for a resource that is already locked. order to make the request for a resource that is already locked.
However, a client may submit a LOCK method with an If header but However, a client may submit a LOCK method with an If header but
without a body. This form of LOCK MUST only be used to "refresh" a without a body. This form of LOCK MUST only be used to "refresh" a
lock. Meaning, at minimum, that any timers associated with the lock lock. Meaning, at minimum, that any timers associated with the lock
MUST be re-set. MUST be re-set.
skipping to change at page 31, line 11 skipping to change at page 31, line 11
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 MUST NOT assume that the lock was 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 In HTTP/1.1, method parameter information was exclusively encoded in
response format. All DAV compliant clients and resources MUST use HTTP headers. Unlike HTTP/1.1, WebDAV encodes method parameter
XML parsers that are compliant with [XML] and XML Namespaces information either in an [XML] request entity body, or in an HTTP
[W3C.REC-xml-names-19990114]. All XML used in either requests or header. The use of XML to encode method parameters was motivated by
responses MUST be, at minimum, well formed and use namespaces the ability to add extra XML elements to existing structures,
correctly. If a server receives XML that is not well-formed then the providing extensibility; and by XML's ability to encode information
server MUST reject the entire request with a 400 (Bad Request). If a in ISO 10646 character sets, providing internationalization support.
client receives XML that is not well-formed in a response then the
client MUST NOT assume anything about the outcome of the executed In addition to encoding method parameters, XML is used in WebDAV to
method and SHOULD treat the server as malfunctioning. encode the responses from methods, providing the extensibility and
internationalization advantages of XML for method output, as well as
input.
All DAV compliant clients and resources MUST use XML parsers that are
compliant with [XML] and XML Namespaces [W3C.REC-xml-names-19990114].
All XML used in either requests or responses MUST be, at minimum,
well formed and use namespaces correctly. If a server receives XML
that is not well-formed then the server MUST reject the entire
request with a 400 (Bad Request). If a client receives XML that is
not well-formed in a response then the client MUST NOT assume
anything about the outcome of the executed method and SHOULD treat
the server as malfunctioning.
Note that processing XML submitted by an untrusted source may cause Note that processing XML submitted by an untrusted source may cause
risks connected to privacy, security, and service quality (see risks connected to privacy, security, and service quality (see
Section 19). Servers MAY reject questionable requests (even though Section 19). Servers MAY reject questionable requests (even though
they consist of well-formed XML), for instance with a 400 (Bad they consist of well-formed XML), for instance with a 400 (Bad
Request) status code and an optional response body explaining the Request) status code and an optional response body explaining the
problem. problem.
8.1.2. Required Bodies in Requests 8.1.2. Required Bodies in Requests
skipping to change at page 32, line 40 skipping to change at page 33, line 5
machine-parsable information until DeltaV introduced a mechanism to machine-parsable information until DeltaV introduced a mechanism to
include more specific information in the body of an error response include more specific information in the body of an error response
(section 1.6 of [RFC3253]). The error body mechanism is appropriate (section 1.6 of [RFC3253]). The error body mechanism is appropriate
to use with any error response that may take a body but does not to use with any error response that may take a body but does not
already have a body defined. The mechanism is particularly already have a body defined. The mechanism is particularly
appropriate when a status code can mean many things (for example, 400 appropriate when a status code can mean many things (for example, 400
Bad Request can mean required headers are missing, headers are Bad Request can mean required headers are missing, headers are
incorrectly formatted, or much more). This error body mechanism is incorrectly formatted, or much more). This error body mechanism is
covered in Section 15 covered in Section 15
8.2. PROPFIND 8.1.6. Impact of Namespace Operations on Cache Validators
Note that the HTTP response headers "Etag" and "Last-Modified" (see
[RFC2616], Sections 14.19 and 14.29) are defined per URL (not per
resource), and are used by clients for caching. Therefore servers
must ensure that executing any operation that affects the URL
namespace (such as COPY, MOVE, DELETE, PUT or MKCOL) does preserve
their semantics, in particular:
For any given URL, the "Last-Modified" value MUST increment every
time the representation returned upon GET changes (within the
limits of timestamp resolution).
For any given URL, an "ETag" value MUST NOT be re-used for
different representations returned by GET.
In practice this means that servers
might have to increment "Last-Modified" timestamps for every
resource inside the destination namespace of a namespace operation
unless it can do so more selectively, and
similarily, might have to re-assign "ETag" values for these
resources (unless the server allocates entity tags in a way so
that they are unique across the whole URL namespace managed by the
server).
Note that these considerations also apply to specific use cases, such
as using PUT to create a new resource at a URL that has been mapped
before, but has been deleted since then.
Finally, WebDAV properties (such as DAV:getetag and DAV:
getlastmodified) that inherit their semantics from HTTP headers must
behave accordingly.
8.2. PROPFIND Method
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 collection and potentially its member resources, if the resource is a collection
that has internal member URLs. All DAV compliant resources MUST that has internal member URLs. All DAV compliant resources MUST
support the PROPFIND method and the propfind XML element support the PROPFIND method and the propfind XML element
(Section 13.20) along with all XML elements defined for use with that (Section 13.19) along with all XML elements defined for use with that
element. 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. Servers MUST "infinity" with a PROPFIND on a collection resource. Servers MUST
support the "0", "1" and "infinity" behaviors on WebDAV-compliant support "0" and "1" depth requests on WebDAV-compliant resources and
resources. By default, the PROPFIND method without a Depth header SHOULD support "infinity" requests in the absence of serious
MUST act as if a "Depth: infinity" header was included. performance issues. By default, the PROPFIND 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 is request method describing what information is being requested. It is
possible to: possible to:
o Request particular property values, by naming the properties o Request particular property values, by naming the properties
desired within the 'prop' element (the ordering of properties in desired within the 'prop' element (the ordering of properties in
here MAY be ignored by server) here MAY be ignored by server),
o Request all dead property values, by using 'dead-props' element.
This can be combined with retrieving specific live properties
named as above. Servers advertising support for this
specification MUST support this feature.
o Request property values for those properties defined in this o Request property values for those properties defined in this
specification plus dead properties, by using 'allprop' element specification plus dead properties, by using the 'allprop' element
(the 'include' element can be used with 'allprop' to instruct the
server to also include additional live properties that may not
have been returned otherwise),
o Request a list of names of all the properties defined on the o 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 live 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 [RFC3744]) and do not return all properties (see [RFC3253] and [RFC3744]) and do not return all
properties already. Instead, WebDAV clients can use propname properties already. Instead, WebDAV clients can use propname
requests to discover what live properties exist, and request named requests to discover what live properties exist, and request named
properties when retrieving values. A WebDAV server MAY omit certain properties when retrieving values. A WebDAV server MAY omit certain
live properties from other specifications when responding to an live properties from other specifications when responding to an
'allprop' request from an older client, and MAY return only custom 'allprop' request, and MAY return only custom (dead) properties and
(dead) properties and those defined in this specification. those defined in this specification.
All servers MUST support returning a response of content type text/ All servers MUST support returning a response of content type text/
xml or application/xml that contains a multistatus XML element that xml or application/xml that contains a multistatus XML element that
describes the results of the attempts to retrieve the various describes the results of the attempts to retrieve the various
properties. properties.
If there is an error retrieving a property then a proper error result If there is an error retrieving a property then a proper error result
MUST be included in the response. A request to retrieve the value of 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 noted, if the a property which does not exist is an error and MUST be noted, if the
response uses a 'multistatus' XML element, with a 'response' XML response uses a 'multistatus' XML element, with a 'response' XML
skipping to change at page 34, line 19 skipping to change at page 35, line 16
contains the URL of the resource on which the properties in the prop contains the URL of the resource on which the properties in the prop
XML element are defined. Results for a PROPFIND on a collection XML element are defined. Results for a PROPFIND on a collection
resource with internal member URLs 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.
Properties may be subject to access control. In the case of Properties may be subject to access control. In the case of
'allprop' and 'propname' requests, if a principal does not have the 'allprop' and 'propname' requests, if a principal does not have the
right to know whether a particular property exists then the property right to know whether a particular property exists then the property
MAY be silently excluded from the response. MAY be silently excluded from the response.
The results of this method SHOULD NOT be cached. Some PROPFIND results MAY be cached, with care as there is no cache
validation mechanism for most properties. This method is both safe
and idempotent (see section 9.1 of [RFC2616]).
8.2.1. PROPFIND status codes 8.2.1. PROPFIND status codes
This section, as with similar sections for other methods, provides This section, as with similar sections for other methods, provides
some guidance on error codes and preconditions or postconditions some guidance on error codes and preconditions or postconditions
(defined in Section 15) that might be particularly useful with (defined in Section 15) that might be particularly useful with
PROPFIND. PROPFIND.
403 Forbidden - A server MAY reject all PROPFIND requests on 403 Forbidden - A server MAY reject PROPFIND requests on collections
collections with depth header of "Infinity", in which case it SHOULD with depth header of "Infinity", in which case it SHOULD use this
use this error with the precondition code 'propfind-finite-depth' error with the precondition code 'propfind-finite-depth' inside the
inside the error body. error body.
8.2.2. Status codes for use with 207 (Multi-Status) 8.2.2. Status codes for use with 207 (Multi-Status)
The following status codes are defined for use within the PROPFIND The following are examples of response codes one would expect to be
Multi-Status response: used in a 207 (Multi-Status) response for this method. Note,
however, that unless explicitly prohibited any 2/3/4/5xx series
response code may be used in a 207 (Multi-Status) response.
200 OK - A property exists and/or its value is successfully 200 OK - A property exists and/or its value is successfully
returned. returned.
401 Unauthorized - The property cannot be viewed without 401 Unauthorized - The property cannot be viewed without
appropriate authorization. appropriate authorization.
403 Forbidden - The property cannot be viewed regardless of 403 Forbidden - The property cannot be viewed regardless of
authentication. authentication.
skipping to change at page 40, line 38 skipping to change at page 41, line 38
<D:propstat> <D:propstat>
<D:prop xmlns:R="http://www.foo.bar/boxschema/"> <D:prop xmlns:R="http://www.foo.bar/boxschema/">
<R:bigbox><R:BoxType>Box type B</R:BoxType> <R:bigbox><R:BoxType>Box type B</R:BoxType>
</R:bigbox> </R:bigbox>
<D:creationdate>1997-12-01T18:27:21-08:00</D:creationdate> <D:creationdate>1997-12-01T18:27:21-08:00</D:creationdate>
<D:displayname>Example HTML resource</D:displayname> <D:displayname>Example HTML resource</D:displayname>
<D:getcontentlength>4525</D:getcontentlength> <D:getcontentlength>4525</D:getcontentlength>
<D:getcontenttype>text/html</D:getcontenttype> <D:getcontenttype>text/html</D:getcontenttype>
<D:getetag>"zzyzx"</D:getetag> <D:getetag>"zzyzx"</D:getetag>
<D:getlastmodified <D:getlastmodified
>Monday, 12-Jan-98 09:25:56 GMT</D:getlastmodified> >Mon, 12 Jan 1998 09:25:56 GMT</D:getlastmodified>
<D:resourcetype/> <D:resourcetype/>
<D:supportedlock> <D:supportedlock>
<D:lockentry> <D:lockentry>
<D:lockscope><D:exclusive/></D:lockscope> <D:lockscope><D:exclusive/></D:lockscope>
<D:locktype><D:write/></D:locktype> <D:locktype><D:write/></D:locktype>
</D:lockentry> </D:lockentry>
<D:lockentry> <D:lockentry>
<D:lockscope><D:shared/></D:lockscope> <D:lockscope><D:shared/></D:lockscope>
<D:locktype><D:write/></D:locktype> <D:locktype><D:write/></D:locktype>
</D:lockentry> </D:lockentry>
skipping to change at page 41, line 49 skipping to change at page 42, line 49
The DAV-specific properties assert that "front.html" was created on The DAV-specific properties assert that "front.html" was created on
December 1, 1997, at 6:27:21PM, in a time zone 8 hours west of GMT December 1, 1997, at 6:27:21PM, in a time zone 8 hours west of GMT
(DAV:creationdate), has a name of "Example HTML resource" (DAV: (DAV:creationdate), has a name of "Example HTML resource" (DAV:
displayname), a content length of 4525 bytes (DAV:getcontentlength), displayname), a content length of 4525 bytes (DAV:getcontentlength),
a MIME type of "text/html" (DAV:getcontenttype), an entity tag of a MIME type of "text/html" (DAV:getcontenttype), an entity tag of
"zzyzx" (DAV:getetag), was last modified on Monday, January 12, 1998, "zzyzx" (DAV:getetag), was last modified on Monday, January 12, 1998,
at 09:25:56 GMT (DAV:getlastmodified), has an empty resource type, at 09:25:56 GMT (DAV:getlastmodified), has an empty resource type,
meaning that it is not a collection (DAV:resourcetype), and supports meaning that it is not a collection (DAV:resourcetype), and supports
both exclusive write and shared write locks (DAV:supportedlock). both exclusive write and shared write locks (DAV:supportedlock).
8.3. PROPPATCH 8.3. PROPPATCH Method
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. Execution of the propertyupdate, set, and remove XML elements. Execution of the
directives in this method is, of course, subject to access control directives in this method is, of course, subject to access control
constraints. DAV compliant resources SHOULD support the setting of constraints. DAV compliant resources SHOULD support 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. Clients SHOULD NOT alter the same
document order (an exception to the normal rule that ordering is property more than once in a single PROPPATCH request.
irrelevant). Instructions MUST either all be executed or none
executed. Thus if any error occurs during processing all executed Servers MUST process PROPPATCH instructions in document order (an
instructions MUST be undone and a proper error result returned. exception to the normal rule that ordering is irrelevant).
Instruction processing details can be found in the definition of the Instructions MUST either all be executed or none executed. Thus if
set and remove instructions in Section 13.23 and Section 13.26. any error occurs during processing all executed instructions MUST be
undone and a proper error result returned. Instruction processing
details can be found in the definition of the set and remove
instructions in Section 13.22 and Section 13.25.
This method is idempotent, but not safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached.
8.3.1. Status Codes for use in 207 (Multi-Status) 8.3.1. Status Codes for use in 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 property set or change succeeded. Note that if this 200 (OK) - The property set or change succeeded. Note that if this
appears for one property, it appears for every property in the appears for one property, it appears for every property in the
skipping to change at page 45, line 18 skipping to change at page 46, line 18
A MKCOL request message may contain a message body. The precise A MKCOL request message may contain a message body. The precise
behavior of a MKCOL request when the body is present is undefined, behavior of a MKCOL request when the body is present is undefined,
but limited to creating collections, members of a collection, bodies but limited to creating collections, members of a collection, bodies
of members and properties on the collections or members. If the of members and properties on the collections or members. If the
server receives a MKCOL request entity type it does not support or server receives a MKCOL request entity type it does not support or
understand it MUST respond with a 415 (Unsupported Media Type) status understand it MUST respond with a 415 (Unsupported Media Type) status
code. If the server decides to reject the request based on the code. If the server decides to reject the request based on the
presence of an entity or the type of an entity, it should use the 415 presence of an entity or the type of an entity, it should use the 415
(Unsupported Media Type) status code. (Unsupported Media Type) status code.
This method is idempotent, but not safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached.
8.4.1. MKCOL Status Codes 8.4.1. MKCOL Status Codes
Responses from a MKCOL request MUST NOT be cached as MKCOL has non- In addition to the general status codes possible, the following
idempotent semantics. In addition to the general status codes status codes have specific applicability to MKCOL:
possible, the following status codes have specific applicability to
MKCOL:
201 (Created) - The collection was created. 201 (Created) - The collection was created.
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 URL namespace, or 2) the parent collection of the location in its URL 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 an unmapped 405 (Method Not Allowed) - MKCOL can only be executed on an unmapped
URL. URL.
skipping to change at page 46, line 37 skipping to change at page 47, line 37
collection resources. collection resources.
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 Requirements
DELETE is defined in [RFC2616], section 9.7, to "delete the resource DELETE is defined in [RFC2616], section 9.7, to "delete the resource
identified by the Request-URI". However, WebDAV changes some DELETE identified by the Request-URI". However, WebDAV changes some DELETE
handling requirements. handling requirements.
A server processing a successful DELETE request: A server processing a successful DELETE request:
MUST destroy locks rooted on the deleted resource MUST destroy locks rooted on the deleted resource
MUST remove the mapping from the Request-URI to any resource. MUST remove the mapping from the Request-URI to any resource.
skipping to change at page 48, line 28 skipping to change at page 49, line 28
In this example the attempt to delete In this example the attempt to delete
http://www.example.com/container/resource3 failed because it is http://www.example.com/container/resource3 failed because it is
locked, and no lock token was submitted with the request. locked, and no lock token was submitted with the request.
Consequently, the attempt to delete http://www.example.com/container/ Consequently, the attempt to delete http://www.example.com/container/
also failed. Thus the client knows that the attempt to delete also failed. Thus the client knows that the attempt to delete
http://www.example.com/container/ must have also failed since the http://www.example.com/container/ must have also failed since the
parent can not be deleted unless its child has also been deleted. parent can not be deleted unless its child has also been deleted.
Even though a Depth header has not been included, a depth of infinity Even though a Depth header has not been included, a depth of infinity
is assumed because the method is on a collection. is assumed because the method is on a collection.
8.8. PUT 8.8. PUT Requirements
8.8.1. PUT for Non-Collection Resources 8.8.1. PUT for Non-Collection Resources
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. For recomputed during PUT processing but are not otherwise affected. For
example, if a server recognizes the content type of the request body, example, if a server recognizes the content type of the request body,
it may be able to automatically extract information that could be it may be able to automatically extract information that could be
profitably exposed as properties. 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).
A PUT request is the only way a client has to indicate to the server
what Content-Type a resource should have, and whether it should
change if the resource is overwritten. Thus, a client MUST provide a
Content-Type for a new resource if any is known, and a server SHOULD
use the Content-Type header value on any PUT request as the
resource's type (unless security concerns or policy dictates
otherwise).
Note that although a recipient should treat metadata supplied with an
HTTP request as authorative, in practice there's no guarantee that a
server will accept Content- headers. Many servers do not allow
configuring the Content-Type on a per-resource basis in the first
place. Thus, clients should not rely on the ability to directly
influence the content type by including a Content-Type request
header.
8.8.2. PUT for Collections 8.8.2. PUT for Collections
This specification does not define the behavior of the PUT method for This specification does not define the behavior of the PUT method for
existing collections. A PUT request to an existing collection MAY be existing collections. A PUT request to an existing collection MAY be
treated as an error (405 Method Not Allowed). treated as an error (405 Method Not Allowed).
The MKCOL method is defined to create collections. The MKCOL method is defined to create collections.
8.9. COPY 8.9. COPY Method
The COPY method creates a duplicate of the source resource identified The COPY method creates a duplicate of the source resource identified
by the Request-URI, in the destination resource identified by the URI by the Request-URI, in the destination resource identified by the URI
in the Destination header. The Destination header MUST be present. in the Destination header. The Destination header MUST be present.
The exact behavior of the COPY method depends on the type of the The exact behavior of the COPY method depends on the type of the
source resource. source resource.
All WebDAV compliant resources MUST support the COPY method. All WebDAV compliant resources MUST support the COPY method.
However, support for the COPY method does not guarantee the ability However, support for the COPY method does not guarantee the ability
to copy a resource. For example, separate programs may control to copy a resource. For example, separate programs may control
resources on the same server. As a result, it may not be possible to resources on the same server. As a result, it may not be possible to
copy a resource to a location that appears to be on the same server. copy a resource to a location that appears to be on the same server.
This method is idempotent, but not safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached.
8.9.1. COPY for Non-collection Resources 8.9.1. COPY for Non-collection Resources
When the source resource is not a collection the result of the COPY When the source resource is not a collection the result of the COPY
method is the creation of a new resource at the destination whose method is the creation of a new resource at the destination whose
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. Since the environment at the destination may be different possible. Since the environment at the destination may be different
than at the source due to factors outside the scope of control of the than at the source due to factors outside the scope of control of the
server, such as the absence of resources required for correct server, such as the absence of resources required for correct
operation, it may not be possible to completely duplicate the operation, it may not be possible to completely duplicate the
behavior of the resource at the destination. Subsequent alterations behavior of the resource at the destination. Subsequent alterations
skipping to change at page 54, line 28 skipping to change at page 55, line 38
The Depth header is unnecessary as the default behavior of COPY on a The Depth header is unnecessary as the default behavior of COPY on a
collection is to act as if a "Depth: infinity" header had been collection is to act as if a "Depth: infinity" header had been
submitted. In this example most of the resources, along with the submitted. In this example most of the resources, along with the
collection, were copied successfully. However the collection R2 collection, were copied successfully. However the collection R2
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 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
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 URLs 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
skipping to change at page 55, line 5 skipping to change at page 56, line 14
For example, separate programs may actually control different sets of For example, separate programs may actually control different sets of
resources on the same server. Therefore, it may not be possible to resources on the same server. Therefore, it may not be possible to
move a resource within a namespace that appears to belong to the same move a resource within a namespace that appears to belong to the same
server. 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.
This method is idempotent, but not safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached.
8.10.1. MOVE for Properties 8.10.1. MOVE for Properties
Live properties described in this document SHOULD be moved along with Live properties described in this document SHOULD 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. Note that some live properties are defined such that same values. Note that some live properties are defined such that
the absence of the property has a specific meaning (e.g. a flag with the absence of the property has a specific meaning (e.g. a flag with
one meaning if present and the opposite if absent), and in these one meaning if present and the opposite if absent), and in these
cases, a successful MOVE might result in the property being reported cases, a successful MOVE might result in the property being reported
as "Not Found" in subsequent requests. If the live properties will as "Not Found" in subsequent requests. If the live properties will
skipping to change at page 59, line 8 skipping to change at page 60, line 13
These sections on the LOCK method describe only those semantics that These sections on the LOCK method describe only those semantics that
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, support Any resource which supports the LOCK method MUST, at minimum, support
the XML request and response formats defined herein. the XML request and response formats defined herein.
A LOCK method invocation to an unlocked resource creates a lock on A LOCK method invocation to an unlocked resource creates a lock on
the resource identified by the Request-URI, which becomes the root of the resource identified by the Request-URI, which becomes the root of
the lock. Lock method requests to create a new lock MUST have a XML the lock. Lock method requests to create a new lock MUST have a XML
request body which contains an owner XML element and other request body which contains an 'owner' XML element and other
information for this lock request. The server MUST preserve the information 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 time, Clients MUST assume that locks may arbitrarily disappear at any time,
regardless of the value given in the Timeout header. The Timeout regardless of the value given in the Timeout header. The Timeout
header only indicates the behavior of the server if extraordinary header only indicates the behavior of the server if extraordinary
circumstances do not occur. For example, a sufficiently privileged circumstances do not occur. For example, a sufficiently privileged
user may remove a lock at any time or the system may crash in such a user may remove a lock at any time or the system may crash in such a
skipping to change at page 59, line 31 skipping to change at page 60, line 36
When a new lock is created, the LOCK response: When a new lock is created, the LOCK response:
o MUST contain a body with the value of the DAV:lockdiscovery o MUST contain a body with the value of the DAV:lockdiscovery
property in a prop XML element. This MUST contain the full property in a prop XML element. This MUST contain the full
information about the lock just granted, while information about information about the lock just granted, while information about
other (shared) locks is OPTIONAL. other (shared) locks is OPTIONAL.
o MUST include the Lock-Token response header with the token o MUST include the Lock-Token response header with the token
associated with the new lock. associated with the new lock.
This method is neither idempotent nor safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached.
8.11.1. Refreshing Locks 8.11.1. Refreshing Locks
A lock is refreshed by sending a LOCK request without a request body A lock is refreshed by sending a LOCK request without a request body
to the URL of a resource within the scope of the lock. This request to the URL of a resource within the scope of the lock. This request
MUST specify which lock to refresh by using the 'Lock-Token' header MUST 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). with a single lock token (only one lock may be refreshed at a time).
It MAY contain a Timeout header, which a server MAY accept to change It MAY contain a Timeout header, which a server MAY accept to change
the duration remaining on the lock to the new value. A server MUST the duration remaining on the lock to the new value. A server MUST
ignore the Depth header on a LOCK refresh. ignore the Depth header on a LOCK refresh.
skipping to change at page 60, line 29 skipping to change at page 61, line 38
locked. If an UNLOCK is successfully executed on this token, all locked. If an UNLOCK is successfully executed on this token, all
associated resources are unlocked. Hence, partial success is not an associated resources are unlocked. Hence, partial success is not an
option. Either the entire hierarchy is locked or no resources are option. Either the entire hierarchy is locked or no resources are
locked. locked.
If the lock cannot be granted to all resources, the server MUST If the lock cannot be granted to all resources, the server MUST
return a Multi-Status response with a 'response' element for at least return a Multi-Status response with a 'response' element for at least
one resource which prevented the lock from being granted, along with one resource which prevented the lock from being granted, along with
a suitable status code for that failure (e.g. 403 (Forbidden) or 423 a suitable status code for that failure (e.g. 403 (Forbidden) or 423
(Locked)). Additionally, if the resource causing the failure was not (Locked)). Additionally, if the resource causing the failure was not
the resource requested, then the server MUST include a 'response' the resource requested, then the server SHOULD include a 'response'
element for the Request-URI as well, with a 'status' element element for the Request-URI as well, with a 'status' element
containing 424 Failed Dependency. containing 424 Failed Dependency.
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.
8.11.3. Locking Unmapped URLs 8.11.3. 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
skipping to change at page 61, line 43 skipping to change at page 62, line 51
201 (Created) - The LOCK request was to an unmapped URL, the request 201 (Created) - The LOCK request was to an unmapped URL, the request
succeeded and resulted in the creation of a new resource, and the succeeded and resulted in the creation of a new resource, and the
value of the DAV:lockdiscovery property is included in the response value of the DAV:lockdiscovery property is included in the response
body. 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.
423 (Locked) - The resource is locked already. 423 (Locked), potentially with 'no-conflicting-lock' precondition
code - There is already a lock on the resource which is not
compatible with the requested lock (see lock compatibility table
above).
400 (Bad Request), with 'lock-token-matches-request-uri' precondition 400 (Bad Request), with 'lock-token-matches-request-uri' precondition
code - The LOCK request was made with a Lock-Token header, indicating code - The LOCK request was made with a Lock-Token header, indicating
that the client wishes to refresh the given lock. However, the that the client wishes to refresh the given lock. However, the
Request-URI did not fall within the scope of the lock identified by Request-URI did not fall within the scope of the lock identified by
the token. The lock may have a scope that does not include the the token. The lock may have a scope that does not include the
Request-URI, or the lock could have disappeared, or the token may be Request-URI, or the lock could have disappeared, or the token may be
invalid. invalid.
8.11.6. Example - Simple Lock Request 8.11.6. Example - Simple Lock Request
skipping to change at page 63, line 37 skipping to change at page 64, line 37
<D:href <D:href
>http://example.com/workspace/webdav/proposal.doc</D:href> >http://example.com/workspace/webdav/proposal.doc</D:href>
</D:lockroot> </D:lockroot>
</D:activelock> </D:activelock>
</D:lockdiscovery> </D:lockdiscovery>
</D:prop> </D:prop>
This example shows the successful creation of an exclusive write lock This example shows the successful creation of an exclusive write lock
on resource http://example.com/workspace/webdav/proposal.doc. The on resource http://example.com/workspace/webdav/proposal.doc. The
resource http://www.ics.uci.edu/~ejw/contact.html contains contact resource http://www.ics.uci.edu/~ejw/contact.html contains contact
information for the owner of the lock. The server has an activity- information for the creator of the lock. The server has an activity-
based timeout policy in place on this resource, which causes the lock based timeout policy in place on this resource, which causes the lock
to automatically be removed after 1 week (604800 seconds). Note that to automatically be removed after 1 week (604800 seconds). Note that
the nonce, response, and opaque fields have not been calculated in the nonce, response, and opaque fields have not been calculated in
the Authorization request header. the Authorization request header.
8.11.7. Example - Refreshing a Write Lock 8.11.7. Example - Refreshing a Write Lock
>>Request >>Request
LOCK /workspace/webdav/proposal.doc HTTP/1.1 LOCK /workspace/webdav/proposal.doc HTTP/1.1
skipping to change at page 66, line 41 skipping to change at page 67, line 41
If all resources which have been locked under the submitted lock If all resources which have been locked under the submitted lock
token can not be unlocked then the UNLOCK request MUST fail. 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 necessarily unlocked. It means that the specific lock resource is necessarily unlocked. It means that the specific lock
corresponding to the specified token no longer exists. 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.
This method is idempotent, but not safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached.
8.12.1. Status Codes 8.12.1. Status Codes
In addition to the general status codes possible, the following In addition to the general status codes possible, the following
status codes have specific applicability to UNLOCK: status codes have specific applicability to UNLOCK:
204 (No Content) - Normal success response (rather than 200 OK, since 204 (No Content) - Normal success response (rather than 200 OK, since
200 OK would imply a response body, and an UNLOCK success response 200 OK would imply a response body, and an UNLOCK success response
does not normally contain a body) does not normally contain a body)
400 (Bad Request) - No lock token was provided (see 'lock-token- 400 (Bad Request) - No lock token was provided (see 'lock-token-
present' precondition), or request was made to a Request-URI that was present' precondition), or request was made to a Request-URI that was
not within the scope of the lock (see 'lock-token-matches-request- not within the scope of the lock (see 'lock-token-matches-request-
uri' precondition). uri' precondition).
403 (Forbidden) - The currently authenticated principal does not have 403 (Forbidden) - The currently authenticated principal does not have
permission to remove the lock. permission to remove the lock.
409 (Conflict) - The resource was not locked and thus could not be 409 (Conflict) - The resource was not locked and thus could not be
unlocked. unlocked.
skipping to change at page 68, line 25 skipping to change at page 69, line 25
DAV = "DAV" ":" #( compliance-class ) DAV = "DAV" ":" #( compliance-class )
compliance-class = ( "1" | "2" | "bis" | extend ) compliance-class = ( "1" | "2" | "bis" | extend )
extend = Coded-URL | token extend = Coded-URL | token
Coded-URL = "<" absolute-URI ">" Coded-URL = "<" absolute-URI ">"
; No LWS allowed in Coded-URL ; No LWS allowed in Coded-URL
; absolute-URI is defined in RFC3986 ; absolute-URI is defined in RFC3986
This general-header appearing in the response indicates that the This general-header appearing in the response indicates that the
resource supports the DAV schema and protocol as specified. All DAV resource supports the DAV schema and protocol as specified. All DAV
compliant resources MUST return the DAV header with compliance-class compliant resources MUST return the DAV header with compliance-class
"1" on all OPTIONS responses. "1" on all OPTIONS responses. In cases where WebDAV is only
supported in part of the server namespace, an OPTIONS request to non-
WebDAV resources (including "/") SHOULD NOT advertise WebDAV support.
The value is a comma-separated list of all compliance class The value is a comma-separated list of all compliance class
identifiers that the resource supports. Class identifiers may be identifiers that the resource supports. Class identifiers may be
Coded-URLs or tokens (as defined by [RFC2616]). Identifiers can Coded-URLs or tokens (as defined by [RFC2616]). Identifiers can
appear in any order. Identifiers that are standardized through the appear in any order. Identifiers that are standardized through the
IETF RFC process are tokens, but other identifiers SHOULD be Coded- IETF RFC process are tokens, but other identifiers SHOULD be Coded-
URLs to encourage uniqueness. URLs to encourage uniqueness.
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 17 for more
details on compliance classes defined in this specification. details on compliance classes defined in this specification.
This header must also appear on responses to OPTIONS requests to the Note that many WebDAV servers do not advertise WebDAV support in
special '*' Request-URI as defined in HTTP/1.1. In this case it response to "OPTIONS *".
means that the repository supports the named features in at least
some internal URL namespaces.
As a request header, this header allows the client to advertise As a request header, this header allows the client to advertise
compliance with named features when the server needs that compliance with named features when the server needs that
information. Clients SHOULD NOT send this header unless a standards information. Clients SHOULD NOT send this header unless a standards
track specification requires it. Any extension that makes use of track specification requires it. Any extension that makes use of
this as a request header will need to carefully consider caching this as a request header will need to carefully consider caching
implications. implications.
9.2. Depth Header 9.2. Depth Header
Depth = "Depth" ":" ("0" | "1" | "infinity") Depth = "Depth" ":" ("0" | "1" | "infinity")
skipping to change at page 69, line 37 skipping to change at page 70, line 37
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.
Upon execution, a method with a Depth header will perform as much of Upon execution, a method with a Depth header will perform as much of
its assigned task as possible and then return a response specifying its assigned task as possible and then return a response specifying
what it was able to accomplish and what it failed to do. what it was able to accomplish and what it failed to do.
So, for example, an attempt to COPY a hierarchy may result in some of So, for example, an attempt to COPY a hierarchy may result in some of
the members being copied and some not. the members being copied and some not.
Any headers on a method that has a defined interaction with the Depth By default, the Depth header does not interact with other headers.
header MUST be applied to all resources in the scope of the method That is, each header on a request with a Depth header MUST be applied
except where alternative behavior is explicitly defined. For only to the Request-URI if it applies to any resource, unless
example, an If-Match header will have its value applied against every specific Depth behavior is defined for that header.
resource in the method's scope and will cause the method to fail if
the header fails to match.
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 header. resource MUST be submitted with the request in the If request 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.
skipping to change at page 70, line 21 skipping to change at page 71, line 19
9.3. Destination Header 9.3. Destination Header
Destination = "Destination" ":" ( absolute-URI ) Destination = "Destination" ":" ( absolute-URI )
The Destination request header specifies the URI which identifies a The Destination request 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 absolute-URI production is two URIs as parameters. Note that the absolute-URI production is
defined in [RFC3986]. defined in [RFC3986].
If the Destination value is an absolute URI, it may name a different Since the Destination value is an absolute URI, it may name a
server (or different port or scheme). If the source server cannot different server (or different port or scheme). If the source server
attempt a copy to the remote server, it MUST fail the request with a cannot attempt a copy to the remote server, it MUST fail the request
502 (Bad Gateway) response. with a 502 (Bad Gateway) response.
If the Destination value is too long or otherwise unacceptable, the
server SHOULD return 400 (Bad Request), ideally with helpful
information in an error body.
9.4. If Header 9.4. 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 "]")) ")"
; No LWS allowed between "[", entity-tag and "]" ; No LWS allowed between "[", entity-tag and "]"
State-token = Coded-URL State-token = Coded-URL
The If request header is intended to have similar functionality to The If request 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 the If 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 <DAV:no-lock> state token is an example of a state token that The <DAV:no-lock> state token is an example of a state token that
will never match an actual valid lock token. The purpose of this is will never match an actual valid lock token (not that it's special in
described in Section 9.4.4. this regard). The purpose of this is described in Section 9.4.4.
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 succeed. lists matches the state of the resource then the request may succeed.
The server MUST do authorization checks before checking this or any The server MUST do authorization checks before checking this or any
conditional header. Assuming no other errors, the server MUST parse conditional header. Assuming no other errors, the server MUST parse
the If header when it appears on any request, evaluate all the the If header when it appears on any request, evaluate all the
skipping to change at page 76, line 29 skipping to change at page 77, line 29
415(Unsupported Media Type) status code is inappropriate), and the 415(Unsupported Media Type) status code is inappropriate), and the
syntax of the request entity is correct (thus a 400 (Bad Request) syntax of the request entity is correct (thus a 400 (Bad Request)
status code is inappropriate) but was unable to process the contained status code is inappropriate) but was unable to process the contained
instructions. For example, this error condition may occur if an XML instructions. For example, this error condition may occur if an XML
request body contains well-formed (i.e., syntactically correct), but request body contains well-formed (i.e., syntactically correct), but
semantically erroneous XML instructions. semantically erroneous XML instructions.
10.3. 423 Locked 10.3. 423 Locked
The 423 (Locked) status code means the source or destination resource The 423 (Locked) status code means the source or destination resource
of a method is locked. This response SHOULD contain the 'lock-token- of a method is locked. This response SHOULD contain an appropriate
present' precondition element and corresponding 'href' in the error precondition or postcondition code, such as 'lock-token-present' or
body. 'no-conflicting-lock".
10.4. 424 Failed Dependency 10.4. 424 Failed Dependency
The 424 (Failed Dependency) status code means that the method could The 424 (Failed Dependency) status code means that the method could
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 a depended on another action and that action failed. For example, if a
command in a PROPPATCH method fails then, at minimum, the rest of the command in a PROPPATCH method fails then, at minimum, the rest of the
commands will also fail with 424 (Failed Dependency). commands will also fail with 424 (Failed Dependency).
10.5. 507 Insufficient Storage 10.5. 507 Insufficient Storage
skipping to change at page 77, line 20 skipping to change at page 78, line 20
cases described in this document. Note also that WebDAV servers are cases described in this document. Note also that WebDAV servers are
known to use 300-level redirect responses (and early interoperability known to use 300-level redirect responses (and early interoperability
tests found clients unprepared to see those responses). A 300-level tests found clients unprepared to see those responses). A 300-level
request MUST NOT be used when the server has created a new resource request MUST NOT be used when the server has created a new resource
in response to the request. in response to the request.
11.1. 412 Precondition Failed 11.1. 412 Precondition Failed
Any request can contain a conditional header defined in HTTP (If- Any request can contain a conditional header defined in HTTP (If-
Match, If-Modified-Since, etc.) or the "If" or "Overwrite" Match, If-Modified-Since, etc.) or the "If" or "Overwrite"
conditional headers defined in this specification. If the request conditional headers defined in this specification. If the server
contains a conditional header, and if that condition fails to hold, evaluates a conditional header, and if that condition fails to hold,
then this error code MUST be returned unless some other error is then this error code MUST be returned. On the other hand, if the
returned. On the other hand, if the client did not include a client did not include a conditional header in the request, then the
conditional header in the request, then the server MUST NOT use this server MUST NOT use this error.
error.
11.2. 414 Request-URI Too Long 11.2. 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, not URIs
full URIs aren't used in other headers. WebDAV specifies full URLs in other locations.
in other headers, therefore this error MAY be used if the URI is too
long in other locations as well.
12. Multi-Status Response 12. Multi-Status Response
A Multi-Status response contains one 'response' element for each A Multi-Status response contains one 'response' element for each
resource in the scope of the request (in no required order) or may be resource in the scope of the request (in no required order) or MAY be
empty if no resources match the request. The default 207 (Multi- empty if no resources match the request. The default 207 (Multi-
Status) response body is a text/xml or application/xml HTTP entity Status) response body is a text/xml or application/xml HTTP entity
that contains a single XML element called 'multistatus', which that contains a single XML element called 'multistatus', which
contains a set of XML elements called response which contain 200, contains a set of XML elements called response which contain 200,
300, 400, and 500 series status codes generated during the method 300, 400, and 500 series status codes generated during the method
invocation. 100 series status codes SHOULD NOT be recorded in a invocation. 100 series status codes SHOULD NOT be recorded in a
'response' XML element. The 207 status code itself MUST NOT be 'response' XML element. The 207 status code itself MUST NOT be
considered a success response, it is only completely successful if considered a success response, it is only completely successful if
all 'response' elements inside contain success status codes. all 'response' elements inside contain success status codes.
skipping to change at page 80, line 25 skipping to change at page 81, line 25
All of the elements defined here may be extended by the addition of All of the elements defined here may be extended by the addition of
attributes and child elements not defined in this specification. All attributes and child elements not defined in this specification. All
elements defined here are in the "DAV:" namespace. elements defined here are in the "DAV:" namespace.
13.1. activelock XML Element 13.1. activelock XML Element
Name: activelock Name: activelock
Purpose: Describes a lock on a resource. Purpose: Describes a lock on a resource.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT activelock (lockscope, locktype, depth, owner?, timeout?, <!ELEMENT activelock (lockscope, locktype, depth, owner?, timeout?,
locktoken?, lockroot)> locktoken?, lockroot)>
13.2. allprop XML Element 13.2. allprop XML Element
Name: allprop Name: allprop
Purpose: Specifies that all names and values of dead properties and Purpose: Specifies that all names and values of dead properties and
the live properties defined by this document existing on the the live properties defined by this document existing on the
resource are to be returned. resource are to be returned.
Extensibility: Normally empty, but MAY be extended with additional
child elements or attributes which SHOULD be ignored if not
recognized.
<!ELEMENT allprop EMPTY > <!ELEMENT allprop EMPTY >
13.3. collection XML Element 13.3. collection XML Element
Name: collection Name: collection
Purpose: Identifies the associated resource as a collection. The Purpose: Identifies the associated resource as a collection. The
DAV:resourcetype property of a collection resource MUST contain DAV:resourcetype property of a collection resource MUST contain
this element. It is normally empty but extensions may add sub- this element. It is normally empty but extensions may add sub-
elements. elements.
Extensibility: MAY be extended with child elements or attributes
which SHOULD be ignored if not recognized.
<!ELEMENT collection EMPTY > <!ELEMENT collection EMPTY >
13.4. dead-props XML Element 13.4. depth XML Element
Name: dead-props
Purpose: Specifies that all dead properties, names and values,
should be returned in the response.
Extensibility: Normally empty, but MAY be extended with additional
child elements or attributes which SHOULD be ignored if not
recognized.
<!ELEMENT dead-props EMPTY >
13.5. depth XML Element
Name: depth Name: depth
Purpose: The value of the Depth header. Purpose: The value of the Depth header.
Value: "0" | "1" | "infinity" Value: "0" | "1" | "infinity"
Extensibility: MAY be extended with attributes which SHOULD be
ignored.
<!ELEMENT depth (#PCDATA) > <!ELEMENT depth (#PCDATA) >
13.6. error XML Element 13.5. error XML Element
Name: error Name: error
Purpose: Error responses, particularly 403 Forbidden and 409 Purpose: Error responses, particularly 403 Forbidden and 409
Conflict, sometimes need more information to indicate what went Conflict, sometimes need more information to indicate what went
wrong. When an error response contains a body in WebDAV, the body wrong. When an error response contains a body in WebDAV, the body
is in XML with the root element 'error'. The 'error' element is in XML with the root element 'error'. The 'error' element
SHOULD include an XML element with the code of a failed SHOULD include an XML element with the code of a failed
precondition or postcondition. precondition or postcondition.
Description: Contains any XML element Description: Contains at least one XML element, and MUST NOT contain
text or mixed content. Any element that is a child of the 'error'
Extensibility: Fully extensible with additional child elements, element is considered to be a precondition or postcondition code.
attributes or text (possibly mixed content). Unrecognized Unrecognized elements SHOULD be ignored if not recognized.
information items SHOULD be ignored if not recognized.
<!ELEMENT error ANY > <!ELEMENT error ANY >
13.7. exclusive XML Element 13.6. exclusive XML Element
Name: exclusive Name: exclusive
Purpose: Specifies an exclusive lock Purpose: Specifies an exclusive lock
Extensibility: Normally empty, but MAY be extended with additional
child elements or attributes which SHOULD be ignored if not
recognized.
<!ELEMENT exclusive EMPTY > <!ELEMENT exclusive EMPTY >
13.8. href XML Element 13.7. href XML Element
Name: href Name: href
Purpose: Identifies the content of the element as a URI or a Purpose: Identifies the content of the element as a URI or a
relative reference. There may be limits on the value of 'href' relative reference. There may be limits on the value of 'href'
depending on the context of its use. Refer to the specification depending on the context of its use. Refer to the specification
text where 'href' is used to see what limitations apply in each text where 'href' is used to see what limitations apply in each
case. case.
Value: URI-reference (See section 4.1 of [RFC3986]) Value: URI-reference (See section 4.1 of [RFC3986])
Extensibility: MAY be extended with attributes which SHOULD be
ignored if not recognized.
<!ELEMENT href (#PCDATA)> <!ELEMENT href (#PCDATA)>
13.8. include XML Element
Name: include
Purpose: Any child element represents the name of a property to be
included in the PROPFIND response. All elements inside an
'include' XML element MUST define properties related to the
resource, although possible property names are in no way limited
to those property names defined in this document or other
standards. This element MUST NOT contain text or mixed content.
<!ELEMENT include ANY >
13.9. location XML Element 13.9. location XML Element
Name: location Name: location
Purpose: HTTP defines the "Location" header (see [RFC2616], section Purpose: HTTP defines the "Location" header (see [RFC2616], section
14.30) for use with some status codes (such as 201 and the 300 14.30) for use with some status codes (such as 201 and the 300
series codes). When these codes are used inside a Multi-Status series codes). When these codes are used inside a 'multistatus'
response, the 'location' element can be used to provide the element, the 'location' element can be used to provide the
accompanying 'Location' header. accompanying Location header value.
Description: Contains a single href element with the same value that Description: Contains a single href element with the same value that
would be used in a Location header. would be used in a Location header.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT location (href)> <!ELEMENT location (href)>
13.10. lockentry XML Element 13.10. lockentry XML Element
Name: lockentry Name: lockentry
Purpose: Defines the types of locks that can be used with the Purpose: Defines the types of locks that can be used with the
resource. resource.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT lockentry (lockscope, locktype) > <!ELEMENT lockentry (lockscope, locktype) >
13.11. lockinfo XML Element 13.11. lockinfo XML Element
Name: lockinfo Name: lockinfo
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.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT lockinfo (lockscope, locktype, owner?) > <!ELEMENT lockinfo (lockscope, locktype, owner?) >
13.12. lockroot XML Element 13.12. lockroot XML Element
Name: lockroot Name: lockroot
Purpose: Contains the root URL of the lock, which is the URL through Purpose: Contains the root URL of the lock, which is the URL through
which the resource was addressed in the LOCK request. which the resource was addressed in the LOCK request.
Description: The href contains a HTTP URL with the address of the Description: The href contains a HTTP URL with the address of the
root of the lock. The server SHOULD include this in all DAV: root of the lock. The server SHOULD include this in all DAV:
lockdiscovery property values and the response to LOCK requests. lockdiscovery property values and the response to LOCK requests.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT lockroot (href) > <!ELEMENT lockroot (href) >
13.13. lockscope XML Element 13.13. lockscope XML Element
Name: lockscope Name: lockscope
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.
Extensibility: SHOULD NOT be extended with child elements. MAY be
extended with attributes which SHOULD be ignored.
<!ELEMENT lockscope (exclusive | shared) > <!ELEMENT lockscope (exclusive | shared) >
13.14. locktoken XML Element 13.14. locktoken XML Element
Name: locktoken Name: locktoken
Purpose: The lock token associated with a lock. Purpose: The lock token associated with a lock.
Description: The href contains a single lock token URI which refers Description: The href contains a single lock token URI which refers
to the lock. to the lock.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT locktoken (href) > <!ELEMENT locktoken (href) >
13.15. locktype XML Element 13.15. locktype XML Element
Name: locktype Name: locktype
Purpose: Specifies the access type of a lock. At present, this Purpose: Specifies the access type of a lock. At present, this
specification only defines one lock type, the write lock. specification only defines one lock type, the write lock.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT locktype (write) > <!ELEMENT locktype (write) >
13.16. multistatus XML Element 13.16. multistatus XML Element
Name: multistatus Name: multistatus
Purpose: Contains multiple response messages. Purpose: Contains multiple response messages.
Description The 'responsedescription' element at the top level is Description: The 'responsedescription' element at the top level is
used to provide a general message describing the overarching used to provide a general message describing the overarching
nature of the response. If this value is available an application nature of the response. If this value is available an application
may use it instead of presenting the individual response may use it instead of presenting the individual response
descriptions contained within the responses. descriptions contained within the responses.
Extensibility: MAY be extended with additional child elements or <!ELEMENT multistatus (response*, responsedescription?) >
attributes which SHOULD be ignored if not recognized.
<!ELEMENT multistatus (response+, responsedescription?) >
13.17. owner XML Element
Name: owner
Purpose: Provides information about the principal taking out a lock.
Description Provides information sufficient for either directly
contacting a principal (such as a telephone number or Email URI),
or for discovering the principal (such as the URL of a homepage)
who owns a lock. This information is provided by the client, and
may only be altered by the server if the owner value provided by
the client is empty.
Extensibility MAY be extended with child elements, mixed content,
text content or attributes. Structured content, for example one
or more 'href' child elements containing URIs of any kind, is
RECOMMENDED.
<!ELEMENT owner ANY >
13.18. prop XML element 13.17. prop XML element
Name: prop Name: prop
Purpose: Contains properties related to a resource. Purpose: Contains properties related to a resource.
Description A generic container for properties defined on resources. Description: A generic container for properties defined on
All elements inside a 'prop' XML element MUST define properties resources. All elements inside a 'prop' XML element MUST define
related to the resource. No other elements may be used inside of properties related to the resource, although possible property
a 'prop' element. names are in no way limited to those property names defined in
this document or other standards. This element MUST NOT contain
Extensibility MAY be extended with attributes which SHOULD be ignored text or mixed content.
if not recognized. Any child element of this element must be
considered to be a property name, however these are not restricted
to the property names defined in this document or other standards.
<!ELEMENT prop ANY > <!ELEMENT prop ANY >
13.19. propertyupdate XML element 13.18. propertyupdate XML element
Name: propertyupdate Name: propertyupdate
Purpose: Contains a request to alter the properties on a resource. Purpose: Contains a request to alter the properties on a resource.
Description: This XML element is a container for the information Description: This XML element is a container for the information
required to modify the properties on the resource. This XML required to modify the properties on the resource. This XML
element is multi-valued. element is multi-valued.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT propertyupdate (remove | set)+ > <!ELEMENT propertyupdate (remove | set)+ >
13.20. propfind XML Element 13.19. propfind XML Element
Name: propfind Name: propfind
Purpose: Specifies the properties to be returned from a PROPFIND Purpose: Specifies the properties to be returned from a PROPFIND
method. Four special elements are specified for use with method. Four special elements are specified for use with
'propfind': 'prop', 'dead-props', 'allprop' and 'propname'. If 'propfind': 'prop', 'allprop', 'include' and 'propname'. If
'prop' is used inside 'propfind' it MUST NOT contain property 'prop' is used inside 'propfind' it MUST NOT contain property
values. values.
Extensibility: MAY be extended with additional child elements or <!ELEMENT propfind ( propname | (allprop, include?) | prop ) >
attributes which SHOULD be ignored if not recognized, as long as
it still contains one of the required elements.
<!ELEMENT propfind ( propname | allprop | (prop, dead-props?) ) > 13.20. propname XML Element
13.21. propname XML Element
Name: propname Name: propname
Purpose: Specifies that only a list of property names on the Purpose: Specifies that only a list of property names on the
resource is to be returned. resource is to be returned.
Extensibility: Normally empty, but MAY be extended with additional
child elements or attributes which SHOULD be ignored if not
recognized.
<!ELEMENT propname EMPTY > <!ELEMENT propname EMPTY >
13.22. propstat XML Element 13.21. propstat XML Element
Name: propstat Name: propstat
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 XML Description: The propstat XML element MUST contain one prop XML
element and one status XML element. The contents of the prop XML element and one status XML element. The contents of the prop XML
element MUST only list the names of properties to which the result element MUST only list the names of properties to which the result
in the status element applies. in the status element applies.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT propstat (prop, status, responsedescription?) > <!ELEMENT propstat (prop, status, responsedescription?) >
13.23. remove XML element 13.22. remove XML element
Name: remove Name: remove
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 in prop Description: Remove instructs that the properties specified in prop
should be removed. Specifying the removal of a property that does should be removed. Specifying the removal of a property that does
not exist is not an error. All the XML elements in a 'prop' XML not exist is not an error. All the XML elements in a 'prop' XML
element inside of a 'remove' XML element MUST be empty, as only element inside of a 'remove' XML element MUST be empty, as only
the names of properties to be removed are required. the names of properties to be removed are required.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT remove (prop) > <!ELEMENT remove (prop) >
13.24. response XML Element 13.23. response XML Element
Name: response Name: response
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: The 'href' element contains a HTTP URL pointing to a Description: The 'href' element contains a HTTP URL pointing to a
WebDAV resource when used in the 'response' container. A WebDAV resource when used in the 'response' container. A
particular 'href' value MUST NOT appear more than once as the particular 'href' value MUST NOT appear more than once as the
child of a 'response' XML element under a 'multistatus' XML child of a 'response' XML element under a 'multistatus' XML
element. This requirement is necessary in order to keep element. This requirement is necessary in order to keep
processing costs for a response to linear time. Essentially, this processing costs for a response to linear time. Essentially, this
prevents having to search in order to group together all the prevents having to search in order to group together all the
responses by 'href'. There are, however, no requirements responses by 'href'. There are, however, no requirements
regarding ordering based on 'href' values. regarding ordering based on 'href' values.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT response (href, ((href*, status)|(propstat+)), <!ELEMENT response (href, ((href*, status)|(propstat+)),
responsedescription? , location?) > responsedescription? , location?) >
13.25. responsedescription XML Element 13.24. responsedescription XML Element
Name: responsedescription Name: responsedescription
Purpose: Contains information about a status response within a Purpose: Contains information about a status response within a
Multi-Status. Multi-Status.
Description: This XML element provides either information suitable Description: Provides information suitable to be presented to a user
to be presented to a user (PCDATA) or a machine readable error (PCDATA) and/or condition name elements (in 'error').
code.
Extensibility: MAY be extended with additional attributes which
SHOULD be ignored if not recognized.
<!ELEMENT responsedescription (#PCDATA | error) >
13.26. set XML element <!ELEMENT responsedescription (#PCDATA | error)* >
13.25. set XML element
Name: set Name: set
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 inside element. The elements contained by the prop XML element inside
the 'set' XML element MUST specify the name and value of the 'set' XML element MUST specify the name and value of
properties that are set on the resource identified by Request-URI. properties that are set on the resource identified by Request-URI.
If a property already exists then its value is replaced. Language If a property already exists then its value is replaced. Language
tagging information appearing in the scope of the 'prop' element tagging information appearing in the scope of the 'prop' element
(in the "xml:lang" attribute, if present) MUST be persistently (in the "xml:lang" attribute, if present) MUST be persistently
stored along with the property, and MUST be subsequently stored along with the property, and MUST be subsequently
retrievable using PROPFIND. retrievable using PROPFIND.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT set (prop) > <!ELEMENT set (prop) >
13.27. shared XML Element 13.26. shared XML Element
Name: shared Name: shared
Purpose: Specifies a shared lock Purpose: Specifies a shared lock
Extensibility: Normally empty, but MAY be extended with additional
child elements or attributes which SHOULD be ignored if not
recognized.
<!ELEMENT shared EMPTY > <!ELEMENT shared EMPTY >
13.28. status XML Element 13.27. status XML Element
Name: status Name: status
Purpose: Holds a single HTTP status-line Purpose: Holds a single HTTP status-line
Value: status-line (status-line defined in Section 6.1 of [RFC2616]) Value: status-line (status-line defined in Section 6.1 of [RFC2616])
Extensibility: MAY be extended with attributes which SHOULD be
ignored.
<!ELEMENT status (#PCDATA) > <!ELEMENT status (#PCDATA) >
13.29. timeout XML Element 13.28. timeout XML Element
Name: timeout Name: timeout
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.7). Value: TimeType (defined in Section 9.7).
Extensibility: MAY be extended with attributes which SHOULD be
ignored.
<!ELEMENT timeout (#PCDATA) > <!ELEMENT timeout (#PCDATA) >
13.30. write XML Element 13.29. write XML Element
Name: write Name: write
Purpose: Specifies a write lock. Purpose: Specifies a write lock.
Extensibility: Normally empty, but MAY be extended with additional
child elements or attributes which SHOULD be ignored if not
recognized.
<!ELEMENT write EMPTY > <!ELEMENT write 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 [XML]. The "Value" field, declaration using the format defined in [XML]. The "Value" field,
where present, specifies further restrictions on the allowable where present, specifies further restrictions on the allowable
contents of the XML element using BNF (i.e., to further restrict the contents of the XML element using BNF (i.e., to further restrict the
values of a PCDATA element). Note that a resource may have only one values of a PCDATA element). Note that a resource may have only one
value for a property of a given name, so the property may only show value for a property of a given name, so the property may only show
up once in PROPFIND responses or PROPPATCH requests. up once in PROPFIND responses.
A protected property is one which cannot be changed with a PROPPATCH A protected property is one which cannot be changed with a PROPPATCH
request. There may be other requests which would result in a change request. There may be other requests which would result in a change
to a protected property (as when a PUT request to an existing to a protected property (as when a LOCK request affects the value of
resource causes DAV:contentlength to change to a new value). Note DAV:lockdiscovery). Note that a given property could be protected on
that a given property could be protected on one type of resource, but one type of resource, but not protected on another type of resource.
not protected on another type of resource.
A computed property is one with a value defined in terms of a A computed property is one with a value defined in terms of a
computation (based on the content and other properties of that computation (based on the content and other properties of that
resource, or even of some other resource). A computed property is resource, or even of some other resource). A computed property is
always a protected property. always a protected property.
COPY and MOVE behavior refers to local COPY and MOVE operations. COPY and MOVE behavior refers to local COPY and MOVE operations.
For properties defined based on HTTP GET response headers (DAV:get*), For properties defined based on HTTP GET response headers (DAV:get*),
the value could include LWS as defined in [RFC2616], section 4.2. the value could include LWS as defined in [RFC2616], section 4.2.
skipping to change at page 92, line 15 skipping to change at page 91, line 15
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 normally re-initialized when a resource is MOVE operation, but is normally re-initialized when a resource is
created with a COPY. It should not be set in a COPY. created with a COPY. It should not be set in a COPY.
Description: The DAV:creationdate property SHOULD be defined on all Description: The DAV:creationdate property SHOULD be defined on all
DAV compliant resources. If present, it contains a timestamp of DAV compliant resources. If present, it contains a timestamp of
the moment when the resource was created. Servers that are the moment when the resource was created. Servers that are
incapable of persistently recording the creation date SHOULD incapable of persistently recording the creation date SHOULD
instead leave it undefined (i.e. report "Not Found") instead leave it undefined (i.e. report "Not Found")
Extensibility: MAY contain attributes which SHOULD be ignored if not
recognized.
<!ELEMENT creationdate (#PCDATA) > <!ELEMENT creationdate (#PCDATA) >
14.2. displayname Property 14.2. displayname Property
Name: displayname Name: displayname
Purpose: Provides a name for the resource that is suitable for Purpose: Provides a name for the resource that is suitable for
presentation to a user. presentation to a user.
Value: Any text Value: Any text
skipping to change at page 92, line 44 skipping to change at page 91, line 41
and MOVE operations. and MOVE operations.
Description: The DAV:displayname property should be defined on all Description: The DAV:displayname property should be defined on all
DAV compliant resources. If present, the property contains a DAV compliant resources. If present, the property contains a
description of the resource that is suitable for presentation to a description of the resource that is suitable for presentation to a
user. This property is defined on the resource, and hence SHOULD user. This property is defined on the resource, and hence SHOULD
have the same value independent of the Request-URI used to have the same value independent of the Request-URI used to
retrieve it (thus computing this property based on the Request-URI retrieve it (thus computing this property based on the Request-URI
is deprecated). is deprecated).
Extensibility: MAY contain attributes which SHOULD be ignored if not
recognized.
<!ELEMENT displayname (#PCDATA) > <!ELEMENT displayname (#PCDATA) >
14.3. getcontentlanguage Property 14.3. getcontentlanguage Property
Name: getcontentlanguage Name: getcontentlanguage
Purpose: Contains the Content-Language header value (from section Purpose: Contains the Content-Language header value (from section
14.12 of [RFC2616]) as it would be returned by a GET without 14.12 of [RFC2616]) as it would be returned by a GET without
accept headers. accept headers.
Value: language-tag (language-tag is defined in section 3.10 of Value: language-tag (language-tag is defined in section 3.10 of
[RFC2616]). [RFC2616]).
Protected: SHOULD NOT be protected, so that clients can reset the Protected: SHOULD NOT be protected, so that clients can reset the
skipping to change at page 93, line 24 skipping to change at page 92, line 19
language. Note that servers implementing RFC2518 might have made language. Note that servers implementing RFC2518 might have made
this a protected property as this is a new requirement. this a protected property as this is a new requirement.
COPY/MOVE behaviour: This property value SHOULD be preserved in COPY COPY/MOVE behaviour: This property value SHOULD be preserved in COPY
and MOVE operations. and MOVE operations.
Description: The DAV:getcontentlanguage property MUST be defined on Description: The DAV:getcontentlanguage property MUST be defined on
any DAV compliant resource that returns the Content-Language any DAV compliant resource that returns the Content-Language
header on a GET. header on a GET.
Extensibility: MAY contain attributes which SHOULD be ignored if not
recognized.
<!ELEMENT getcontentlanguage (#PCDATA) > <!ELEMENT getcontentlanguage (#PCDATA) >
14.4. getcontentlength Property 14.4. getcontentlength Property
Name: getcontentlength Name: getcontentlength
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.
Value: See section 14.13 of [RFC2616]. Value: See section 14.13 of [RFC2616].
skipping to change at page 93, line 48 skipping to change at page 92, line 40
Protected: This property is computed, therefore protected. Protected: This property is computed, therefore protected.
Description: The DAV:getcontentlength property MUST be defined on Description: The DAV:getcontentlength property MUST be defined on
any DAV compliant resource that returns the Content-Length header any DAV compliant resource that returns the Content-Length header
in response to a GET. in response to a GET.
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 the destination resource, not the value of the property on the
source resource. source resource.
Extensibility: MAY contain attributes which SHOULD be ignored if not
recognized.
<!ELEMENT getcontentlength (#PCDATA) > <!ELEMENT getcontentlength (#PCDATA) >
14.5. getcontenttype Property 14.5. getcontenttype Property
Name: getcontenttype Name: getcontenttype
Purpose: Contains the Content-Type header value (from section 14.17 Purpose: Contains the Content-Type header value (from section 14.17
of [RFC2616]) as it would be returned by a GET without accept of [RFC2616]) as it would be returned by a GET without accept
headers. headers.
skipping to change at page 94, line 26 skipping to change at page 93, line 18
Note that servers implementing RFC2518 might have made this a Note that servers implementing RFC2518 might have made this a
protected property as this is a new requirement. protected property as this is a new requirement.
COPY/MOVE behaviour: This property value SHOULD be preserved in COPY COPY/MOVE behaviour: This property value SHOULD be preserved in COPY
and MOVE operations. and MOVE operations.
Description: This property MUST be defined on any DAV compliant Description: This property MUST be defined on any DAV compliant
resource that returns the Content-Type header in response to a resource that returns the Content-Type header in response to a
GET. GET.
Extensibility: MAY contain attributes which SHOULD be ignored if not
recognized.
<!ELEMENT getcontenttype (#PCDATA) > <!ELEMENT getcontenttype (#PCDATA) >
14.6. getetag Property 14.6. getetag Property
Name: getetag Name: getetag
Purpose: Contains the ETag header value (from section 14.19 of Purpose: Contains the ETag header value (from section 14.19 of
[RFC2616]) as it would be returned by a GET without accept [RFC2616]) as it would be returned by a GET without accept
headers. headers.
Value: entity-tag (defined in section 3.11 of [RFC2616]) Value: entity-tag (defined in section 3.11 of [RFC2616])
Protected: MUST be protected because this value is created and Protected: MUST be protected because this value is created and
controlled by the server. controlled by the server.
COPY/MOVE behaviour: This property value is dependent on the final COPY/MOVE behaviour: This property value is dependent on the final
state of the destination resource, not the value of the property state of the destination resource, not the value of the property
on the source resource. on the source resource. Also note the considerations in
Section 8.1.6.
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 RFC2616 compliant resource that returns the Etag header. Refer to RFC2616
for a complete definition of the semantics of an ETag. Note that for a complete definition of the semantics of an ETag. Note that
changes in properties or lock state MUST not cause a resource's changes in properties or lock state MUST not cause a resource's
ETag to change. ETag to change.
Extensibility: MAY contain attributes which SHOULD be ignored if not
recognized.
<!ELEMENT getetag (#PCDATA) > <!ELEMENT getetag (#PCDATA) >
14.7. getlastmodified Property 14.7. getlastmodified Property
Name: getlastmodified Name: getlastmodified
Purpose: Contains the Last-Modified header value (from section 14.29 Purpose: Contains the Last-Modified header value (from section 14.29
of [RFC2616]) as it would be returned by a GET method without of [RFC2616]) as it would be returned by a GET method without
accept headers. accept headers.
Value: rfc1123-date (defined in section 3.3.1 of [RFC2616]) Value: rfc1123-date (defined in section 3.3.1 of [RFC2616])
Protected: SHOULD be protected because some clients may rely on the Protected: SHOULD be protected because some clients may rely on the
value for appropriate caching behavior, or on the value of the value for appropriate caching behavior, or on the value of the
Last-Modified header to which this property is linked. Last-Modified header to which this property is linked.
skipping to change at page 95, line 28 skipping to change at page 94, line 18
Value: rfc1123-date (defined in section 3.3.1 of [RFC2616]) Value: rfc1123-date (defined in section 3.3.1 of [RFC2616])
Protected: SHOULD be protected because some clients may rely on the Protected: SHOULD be protected because some clients may rely on the
value for appropriate caching behavior, or on the value of the value for appropriate caching behavior, or on the value of the
Last-Modified header to which this property is linked. Last-Modified header to which this property is linked.
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 the modified date of the destination resource, not the value of the
property on the source resource. Note that some server property on the source resource. Note that some server
implementations use the file system date modified value for the implementations use the file system date modified value for the
DAV:getlastmodified value, and this is preserved in a MOVE even DAV:getlastmodified value, and this can be preserved in a MOVE
when the HTTP Last-Modified value SHOULD change. Thus, clients even when the HTTP Last-Modified value SHOULD change. Note that
cannot rely on this value for caching and SHOULD use ETags. since [RFC2616] requires clients to use ETags where provided, a
server implementing ETags can count on clients using a much better
mechanism that modification dates for offline synchronization or
cache control. Also note the considerations in Section 8.1.6.
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 only SHOULD NOT cause the last- resource. A change in a property only SHOULD NOT cause the last-
modified date to change, because clients MAY rely on the last- modified date to change, because clients MAY rely on the last-
modified date to know when to overwrite the existing body. The modified date to know when to overwrite the existing body. The
DAV:getlastmodified property MUST be defined on any DAV compliant DAV:getlastmodified property MUST be defined on any DAV compliant
resource that returns the Last-Modified header in response to a resource that returns the Last-Modified header in response to a
GET. GET.
Extensibility: MAY contain attributes which SHOULD be ignored if not
recognized.
<!ELEMENT getlastmodified (#PCDATA) > <!ELEMENT getlastmodified (#PCDATA) >
14.8. lockdiscovery Property 14.8. lockdiscovery Property
Name: lockdiscovery Name: lockdiscovery
Purpose: Describes the active locks on a resource Purpose: Describes the active locks on a resource
Protected: MUST be protected. Clients change the list of locks Protected: MUST be protected. Clients change the list of locks
through LOCK and UNLOCK, not through PROPPATCH. through LOCK and UNLOCK, not through PROPPATCH.
COPY/MOVE behaviour: The value of this property depends on the lock COPY/MOVE behaviour: The value of this property depends on the lock
state of the destination, not on the locks of the source resource. state of the destination, not on the locks of the source resource.
Recall that locks are not moved in a MOVE operation. Recall that locks are not moved in a MOVE operation.
Description: Returns a listing of who has a lock, what type of lock Description: Returns a listing of who has a lock, what type of lock
skipping to change at page 96, line 20 skipping to change at page 95, line 12
state of the destination, not on the locks of the source resource. state of the destination, not on the locks of the source resource.
Recall that locks are not moved in a MOVE operation. Recall that locks are not moved in a MOVE operation.
Description: Returns a listing of who has a lock, what type of lock Description: Returns a listing of who has a lock, what type of lock
he has, the timeout type and the time remaining on the timeout, he has, the timeout type and the time remaining on the timeout,
and the associated lock token. If there are no locks, but the and the associated lock token. If there are no locks, but the
server supports locks, the property will be present but contain server supports locks, the property will be present but contain
zero 'activelock' elements. If there is one or more lock, an zero '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.
Extensibility: MAY be extended with additional child elements or
attributes which SHOULD be ignored if not recognized.
<!ELEMENT lockdiscovery (activelock)* > <!ELEMENT lockdiscovery (activelock)* >
14.8.1. Example - Retrieving the lockdiscovery Property 14.8.1. Example - Retrieving DAV:lockdiscovery
>>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: application/xml; charset="utf-8" Content-Type: application/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:'>
skipping to change at page 98, line 16 skipping to change at page 97, line 16
the same type of resource at the destination. the same type of resource at the destination.
Description: MUST be defined on all DAV compliant resources. Each Description: MUST be defined on all DAV compliant resources. Each
child element identifies a specific type the resource belongs to, child element identifies a specific type the resource belongs to,
such as 'collection', which is the only resource type defined by such as 'collection', which is the only resource type defined by
this specification (see Section 13.3). If the element contains this specification (see Section 13.3). If the element contains
the 'collection' child element plus additional unrecognized the 'collection' child element plus additional unrecognized
elements, it should generally be treated as a collection. If the elements, it should generally be treated as a collection. If the
element contains no recognized child elements, it should be element contains no recognized child elements, it should be
treated as a non-collection resource. The default value is empty. treated as a non-collection resource. The default value is empty.
This element MUST NOT contain text or mixed content. Any custom
Extensibility: MAY be extended with any child elements or attributes child element is considered to be an identifier for a resource
which SHOULD be ignored if not recognized. type.
Example: (fictional example to show extensibility) Example: (fictional example to show extensibility)
<x:resourcetype xmlns:x="DAV:"> <x:resourcetype xmlns:x="DAV:">
<x:collection/> <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
skipping to change at page 98, line 49 skipping to change at page 97, line 49
property at the source resource. Servers attempting to COPY to a property at the source resource. Servers attempting to COPY to a
destination should not attempt to set this property at the destination should not attempt to set this property at the
destination. destination.
Description: Returns a listing of the combinations of scope and Description: Returns a listing of the combinations of scope and
access types which may be specified in a lock request on the access types which may be specified in a lock request on the
resource. Note that the actual contents are themselves controlled resource. Note that the actual contents are themselves controlled
by access controls so a server is not required to provide by access controls so a server is not required to provide
information the client is not authorized to see. information the client is not authorized to see.
Extensibility: MAY be extended with any child elements or attributes
which SHOULD be ignored if not recognized.
<!ELEMENT supportedlock (lockentry)* > <!ELEMENT supportedlock (lockentry)* >
14.10.1. Example - Retrieving the DAV:supportedlock Property 14.10.1. Example - Retrieving DAV:supportedlock
>>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: application/xml; charset="utf-8" Content-Type: application/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:">
skipping to change at page 100, line 29 skipping to change at page 99, line 29
associated with it. In a 207 Multi-Status response, the XML element associated with it. In a 207 Multi-Status response, the XML element
MUST appear inside a DAV:error element in the appropriate DAV: MUST appear inside a DAV:error element in the appropriate DAV:
responsedescription element. In all other error responses, the XML responsedescription element. In all other error responses, the XML
element MUST be returned as the child of a top-level DAV:error element MUST be returned as the child of a top-level DAV:error
element in the response body, unless otherwise negotiated by the element in the response body, unless otherwise negotiated by the
request, along with an appropriate response status. The most common request, along with an appropriate response status. The most common
response status codes are 403 (Forbidden) if the request should not response status codes are 403 (Forbidden) if the request should not
be repeated because it will always fail, and 409 (Conflict) if it is be repeated because it will always fail, and 409 (Conflict) if it is
expected that the user might be able to resolve the conflict and expected that the user might be able to resolve the conflict and
resubmit the request. The DAV:error element MAY contain child resubmit the request. The DAV:error element MAY contain child
elements with specific error information and MAY be extended with elements with specific error information and MAY be extended with any
custom child elements and text (mixed content). custom child elements.
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 always 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 the be able to take a reasonable course of action based only on the
numeric error. However, it does remove the need to define new numeric error. However, it does remove the need to define new
numeric error codes. The machine-readable codes used for this numeric error codes. The machine-readable codes used for this
purpose are XML elements classified as preconditions and purpose are XML elements classified as preconditions and
postconditions, so naturally any group defining a new error code can postconditions, so naturally any group defining a new error code can
use their own namespace. As always, the "DAV:" namespace is reserved use their own namespace. As always, the "DAV:" namespace is reserved
for use by IETF-chartered WebDAV working groups. for use by IETF-chartered WebDAV working groups.
A server supporting "bis" SHOULD use the XML error whenever a A server supporting "bis" SHOULD use the XML error whenever a
precondition or postcondition defined in this document is violated. precondition or postcondition defined in this document is violated.
For error conditions not specified in this document, the server MAY For error conditions not specified in this document, the server MAY
simply choose an appropriate numeric status and leave the response simply choose an appropriate numeric status and leave the response
body blank. However, a server MAY instead use a custom error code body blank. However, a server MAY instead use a custom error code
and other supporting text, because even when clients do not and other supporting text, because even when clients do not
automatically recognize error codes they can be quite useful in automatically recognize error codes they can be quite useful in
interoperability testing and debugging. interoperability testing and debugging.
15.1. Example - Response with precondition code Example - Response with precondition code"
>>Response >>Response
HTTP/1.1 423 Locked HTTP/1.1 423 Locked
Content-Type: application/xml; charset="utf-8" Content-Type: application/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:lock-token-present> <D:lock-token-present>
<D:href>/workspace/webdav/</D:href> <D:href>/workspace/webdav/</D:href>
skipping to change at page 101, line 30 skipping to change at page 100, line 27
In this example, a client unaware of a "Depth: infinity" lock on the In this example, a client unaware of a "Depth: infinity" lock on the
parent collection "/workspace/webdav/" attempted to modify the parent collection "/workspace/webdav/" attempted to modify the
collection member "/workspace/webdav/proposal.doc". collection member "/workspace/webdav/proposal.doc".
Some other useful preconditions and postconditions have been defined Some other useful preconditions and postconditions have been defined
in other specifications extending WebDAV, such as [RFC3744] (see in other specifications extending WebDAV, such as [RFC3744] (see
particularly section 7.1.1), [RFC3253], and [RFC3648]. particularly section 7.1.1), [RFC3253], and [RFC3648].
All these elements are in the "DAV:" namespace. All these elements are in the "DAV:" namespace.
Name: no-external-entities
Use with: 403 Forbidden
Purpose: (precondition) -- If the server rejects a client request
because the request body contains an external entity, the server
SHOULD use this error.
<!ELEMENT no-external-entities EMPTY >
Name: lock-token-matches-request-uri Name: lock-token-matches-request-uri
Use with: 400 Bad Request Use with: 400 Bad Request
Purpose: (precondition) -- A request may include a Lock-Token header Purpose: (precondition) -- A request may include a Lock-Token header
to identify a lock for the purposes of an operation such as to identify a lock for the purposes of an operation such as
refresh LOCK or UNLOCK. However, if the Request-URI doe not fall refresh LOCK or UNLOCK. However, if the Request-URI doe not fall
within the scope of the lock identified by the token, the server within the scope of the lock identified by the token, the server
SHOULD use this error. The lock may have a scope that does not SHOULD use this error. The lock may have a scope that does not
include the Request-URI, or the lock could have disappeared, or include the Request-URI, or the lock could have disappeared, or
the token may be invalid. the token may be invalid.
<!ELEMENT lock-token-matches-request-uri EMPTY > <!ELEMENT lock-token-matches-request-uri EMPTY >
Name: lock-token-submitted (precondition)
Use with: 4xx responses, e.g. 400 Bad Request or 423 Locked
Purpose: The request could not succeed because a lock token should
have been submitted. This element, if present, MUST contain at
least one URL of a locked resource that prevented the request. In
cases of MOVE, COPY and DELETE where collection locks are
involved, it can be difficult for the client to find out which
locked resource made the request fail -- but the server is only
resonsible for returning one such locked resource. The server MAY
return every locked resource that prevented the request from
succeeding if it knows them all.
<!ELEMENT lock-token-present (href+) >
Name: no-conflicting-lock (precondition)
Use with: Typically 423 Locked
Purpose: A LOCK request failed due the presence of an already
existing conflicting lock. Note that a lock can be in conflict
although the resource to which the request was directed is only
indirectly locked. In this case, the precondition code can be
used to inform the client about the resource which is the root of
the conflicting lock, avoiding a separate lookup of the
"lockdiscovery" property.
<!ELEMENT no-conflicting-lock (href)* >
Name: no-external-entities
Use with: 403 Forbidden
Purpose: (precondition) -- If the server rejects a client request
because the request body contains an external entity, the server
SHOULD use this error.
<!ELEMENT no-external-entities EMPTY >
Name: preserved-live-properties Name: preserved-live-properties
Use with: 409 Conflict Use with: 409 Conflict
Purpose: (postcondition) -- The server received an otherwise-valid Purpose: (postcondition) -- The server received an otherwise-valid
MOVE or COPY request, but cannot maintain the live properties with MOVE or COPY request, but cannot maintain the live properties with
the same behavior at the destination. It may be that the server the same behavior at the destination. It may be that the server
only supports some live properties in some parts of the only supports some live properties in some parts of the
repository, or simply has an internal error. repository, or simply has an internal error.
<!ELEMENT preserved-live-properties EMPTY > <!ELEMENT preserved-live-properties EMPTY >
Name: writable-property
Use with: 403 Forbidden
Purpose: (precondition) -- The client attempted to set a read-only
property in a PROPPATCH (such as DAV:getetag).
<!ELEMENT writable-property EMPTY >
Name: propfind-finite-depth Name: propfind-finite-depth
Use with: 403 Forbidden Use with: 403 Forbidden
Purpose: (precondition) -- This server does not allow infinite-depth Purpose: (precondition) -- This server does not allow infinite-depth
PROPFIND requests on collections. PROPFIND requests on collections.
<!ELEMENT propfind-finite-depth EMPTY > <!ELEMENT propfind-finite-depth EMPTY >
Name: lock-token-present Name: writable-property
Use with: 4xx responses, e.g. 400 Bad Request or 423 Locked Use with: 403 Forbidden
Purpose: (precondition) -- The request could not succeed because a Purpose: (precondition) -- The client attempted to set a read-only
lock token should have been provided. This element, if present, property in a PROPPATCH (such as DAV:getetag).
MUST contain at least one URL of a locked resource that prevented
the request. In cases of MOVE, COPY and DELETE where collection
locks are involved, it can be difficult for the client to find out
which locked resource made the request fail -- but the server is
only resonsible for returning one such locked resource. The
server MAY return every locked resource that prevented the request
from succeeding if it knows them all.
<!ELEMENT lock-token-present (href+) > <!ELEMENT writable-property EMPTY >
16. Instructions for Processing XML in DAV 16. XML Extensibility in DAV
All DAV compliant resources MUST ignore any unknown XML element and The XML namespace extension [W3C.REC-xml-names-19990114] is used in
all its children encountered while processing a DAV method that uses this specification in order to allow for new XML elements to be added
XML as its command language. without fear of colliding with other element names. Although WebDAV
request and response bodies can be extended by arbitrary XML
elements, which can be ignored by the message recipient, an XML
element in the "DAV:" 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 WebDAV working group.
Extensibility with backwards-compatibility requires that both clients
and servers behave appropriately when unrecognized command extensions
are received. For XML processing, this means that clients and
servers MUST process received XML documents as if unrecognized
elements (and all children) and unrecognized attributes were not
there. Ignoring custom elements for backwards-compatibility can of
course be consistent with logging all information or presenting for
debugging.
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 the This restriction does not apply to setting dead DAV properties on the
server where the server MUST record unknown XML elements. server where the server MUST record unknown XML elements.
Additionally, this restriction does not apply to the use of XML where Additionally, this restriction does not apply to the use of XML where
XML happens to be the content type of the entity body, for example, XML happens to be the content type of the entity body, for example,
when used as the body of a PUT. when used as the body of a PUT.
Since XML can be transported as text/xml or application/xml, a DAV When XML is used for a request or response body, the Content-Type
server MUST accept DAV method requests with XML parameters type SHOULD be application/xml. Implementations MUST accept both
transported as either text/xml or application/xml, and a DAV client text/xml and application/xml in request and response bodies. Use of
MUST accept XML responses using either text/xml or application/xml. text/xml is deprecated.
Processing instructions in XML SHOULD be ignored by recipients.
Thus, specifications extending WebDAV SHOULD NOT use processing
instructions to define normative behavior.
XML DTD fragments are included for all the XML elements defined in XML DTD fragments are included for all the XML elements defined in
this specification. However, legal XML may not be valid according to this specification. However, correct XML will not be valid according
any DTD due to namespace usage and extension rules, so the DTD is to any DTD due to namespace usage and extension rules. In
only informational. A recipient of a WebDAV message with an XML body particular:
MUST NOT validate the XML document according to any hard-coded or
dynamically-declared DTD. All elements defined in this specification use the "DAV:"
namespace,
Element ordering is irrelevant unless otherwise stated,
Extension attributes MAY be added,
For element type definitions of "ANY", the normative text
definition for that element defines what can be in it and what
that means.
For element type definitions of "#PCDATA", extension elements MUST
NOT be added.
For other element type definitions, including "EMPTY", extension
elements MAY be added.
Note that this means that elements containing elements cannot be
extended to contain text, and vice versa.
With DTD validation relaxed by the rules above, the constraints
described by the DTD fragments are normative (see for example
Appendix A A recipient of a WebDAV message with an XML body MUST NOT
validate the XML document according to any hard-coded or dynamically-
declared DTD.
Note that this section describes backwards-compatible extensibility
rules. There might also be times when an extension is designed not
to be backwards-compatible, for example defining an extension that
reuses an XML element defined in this document but omitting one of
the child elements required by the DTDs in this specification.
17. DAV Compliance Classes 17. DAV Compliance Classes
A DAV compliant resource can advertise several classes of compliance. A DAV compliant resource can advertise several classes of compliance.
A client can discover the compliance classes of a resource by A client can discover the compliance classes of a resource by
executing OPTIONS on the resource, and examining the "DAV" header executing OPTIONS on the resource, and examining the "DAV" header
which is returned. Note particularly that resources are spoken of as which is returned. Note particularly that resources are spoken of as
being compliant, rather than servers. That is because theoretically being compliant, rather than servers. That is because theoretically
some resources on a server could support different feature sets. some resources on a server could support different feature sets.
E.g. a server could have a sub-repository where an advanced feature E.g. a server could have a sub-repository where an advanced feature
skipping to change at page 104, line 39 skipping to change at page 105, line 39
Class 1 compliant resources MUST return, at minimum, the value "1" in Class 1 compliant resources MUST return, at minimum, the value "1" in
the DAV header on all responses to the OPTIONS method. the DAV header on all responses to the OPTIONS method.
17.2. Class 2 17.2. Class 2
A class 2 compliant resource MUST meet all class 1 requirements and A class 2 compliant resource MUST meet all class 1 requirements and
support the LOCK method, the DAV:supportedlock property, the DAV: support the LOCK method, the DAV:supportedlock property, the DAV:
lockdiscovery property, the Time-Out response header and the Lock- lockdiscovery property, the Time-Out response header and the Lock-
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.
17.3. Class 'bis' 17.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. Class 1 must be supported as well. RFC2518 made in this document. Class 1 must be supported as well.
Class 2 MAY be supported. Class 2 MAY be supported.
skipping to change at page 108, line 35 skipping to change at page 109, line 35
WebDAV provides, through the PROPFIND method, a mechanism for listing WebDAV provides, through the PROPFIND method, a mechanism for listing
the member resources of a collection. This greatly diminishes the the member resources of a collection. This greatly diminishes the
effectiveness of security or privacy techniques that rely only on the effectiveness of security or privacy techniques that rely only on the
difficulty of discovering the names of network resources. Users of difficulty of discovering the names of network resources. Users of
WebDAV servers are encouraged to use access control techniques to WebDAV servers are encouraged to use access control techniques to
prevent unwanted access to resources, rather than depending on the prevent unwanted access to resources, rather than depending on the
relative obscurity of their resource names. relative obscurity of their resource names.
19.4. Privacy Issues Connected to Locks 19.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
XML field giving contact information for the person taking out the 'owner' XML field giving contact information for the person taking
lock (for those cases where a person, rather than a robot, is taking out the lock (for those cases where a person, rather than a robot, is
out the lock). This contact information is stored in a DAV: taking out the lock). This contact information is stored in a DAV:
lockdiscovery property on the resource, and can be used by other lockdiscovery property on the resource, and can be used by other
collaborators to begin negotiation over access to the resource. collaborators to begin negotiation over access to the resource.
However, in many cases this contact information can be very private, However, in many cases this contact information can be very private,
and should not be widely disseminated. Servers SHOULD limit read and should not be widely disseminated. Servers SHOULD limit read
access to the DAV:lockdiscovery property as appropriate. access to the DAV:lockdiscovery property as appropriate.
Furthermore, user agents SHOULD provide control over whether contact Furthermore, user agents SHOULD provide control over whether contact
information is sent at all, and if contact information is sent, information is sent at all, and if contact information is sent,
control over exactly what information is sent. control over exactly what information is sent.
19.5. Privacy Issues Connected to Properties 19.5. Privacy Issues Connected to Properties
skipping to change at page 110, line 9 skipping to change at page 111, line 9
crafted request using nested internal entities may require enormous crafted request using nested internal entities may require enormous
amounts of memory and/or processing time to process. Server amounts of memory and/or processing time to process. Server
implementors should be aware of this risk and configure their XML implementors should be aware of this risk and configure their XML
parsers so that requests like these can be detected and rejected as parsers so that requests like these can be detected and rejected as
early as possible. early as possible.
19.7. Risks Connected with Lock Tokens 19.7. Risks Connected with Lock Tokens
This specification encourages the use of "A Universally Unique This specification encourages the use of "A Universally Unique
Identifier (UUID) URN Namespace" ([RFC4122]) for lock tokens Identifier (UUID) URN Namespace" ([RFC4122]) for lock tokens
Section 6.3, in order to guarantee their uniqueness across space and Section 6.4, in order to guarantee their uniqueness across space and
time. Variant 1 UUIDs (defined in section 4) MAY contain a "node" time. Version 1 UUIDs (defined in section 4) MAY contain a "node"
field that "consists of an IEEE 802 MAC address, usually the host field that "consists of an IEEE 802 MAC address, usually the host
address. For systems with multiple IEEE addresses, any available one address. For systems with multiple IEEE addresses, any available one
can be used". can be used". Since a WebDAV server will issue many locks over its
lifetime, the implication is that it may also be publicly exposing
its IEEE 802 address.
There are several risks associated with exposure of IEEE 802 There are several risks associated with exposure of IEEE 802
addresses. Using the IEEE 802 address: addresses. Using the IEEE 802 address:
o It is possible to track the movement of hardware from subnet to o It is possible to track the movement of hardware from subnet to
subnet. subnet.
o It may be possible to identify the manufacturer of the hardware o It may be possible to identify the manufacturer of the hardware
running a WebDAV server. running a WebDAV server.
skipping to change at page 110, line 45 skipping to change at page 111, line 47
machines. These scripts can be used to read another user's cookies machines. These scripts can be used to read another user's cookies
and therefore may provide an attacker the ability to use another and therefore may provide an attacker the ability to use another
user's session, assume their identity temporarily and gain access to user's session, assume their identity temporarily and gain access to
their resources. Other attacks are also possible with client- their resources. Other attacks are also possible with client-
executed scripts. executed scripts.
WebDAV may worsen this situation only by making it easier for a Web WebDAV may worsen this situation only by making it easier for a Web
server to host content provided by many different authors (making it server to host content provided by many different authors (making it
harder to trust the content providers) and to host content with harder to trust the content providers) and to host content with
restricted access alongside public pages (see particularly RFC3744). restricted access alongside public pages (see particularly RFC3744).
Note also that allowing clients to set the Content-Type might make it
possible for malevolent clients to bypass type checks in other user
agents.
HTTP servers may mitigate some of these threats by filtering content HTTP servers may mitigate some of these threats by filtering content
in areas where many authors contribute pages -- the server could, for in areas where many authors contribute pages -- the server could, for
example, remove script from HTML pages. example, remove script from HTML pages.
This vulnerability should provide yet another reason for server This vulnerability should provide yet another reason for server
implementors and administrators not to replace authentication implementors and administrators not to replace authentication
mechanisms with cookie-based session tokens if there's any sensitive mechanisms with cookie-based session tokens if there's any sensitive
information relying on the authenticated identity. information relying on the authenticated identity.
HTTP and WebDAV client implementors might consider locking down the HTTP and WebDAV client implementors might consider locking down the
use of scripts and cookies based on these considerations. use of scripts and cookies based on these considerations.
20. IANA Considerations 20. IANA Considerations
20.1. New URI Schemes
This specification defines two URI schemes: This specification defines two URI schemes:
1. the "opaquelocktoken" scheme defined in Appendix C, and 1. the "opaquelocktoken" scheme defined in Appendix C, and
2. the "DAV" URI scheme, which historically was used in RFC2518 to 2. the "DAV" URI scheme, which historically was used in RFC2518 to
disambiguate WebDAV property and XML element names and which disambiguate WebDAV property and XML element names and which
continues to be used for that purpose in this specification and continues to be used for that purpose in this specification and
others extending WebDAV. Creation of identifiers in the "DAV:" others extending WebDAV. Creation of identifiers in the "DAV:"
namespace is controlled by the IETF. namespace is controlled by the IETF.
Note that defining new URI schemes for XML namespaces is now
discouraged. "DAV:" was defined before standard best practices
emerged.
20.2. XML Namespaces
XML namespaces disambiguate WebDAV property names and XML elements. XML namespaces disambiguate WebDAV property names and XML elements.
Any WebDAV user or application can define a new namespace in order to Any WebDAV user or application can define a new namespace in order to
create custom properties or extend WebDAV XML syntax. IANA does not create custom properties or extend WebDAV XML syntax. IANA does not
need to manage such namespaces, property names or element names. need to manage such namespaces, property names or element names.
20.3. Message Header Fields
The message header fields below should be added to the permanent
registry (see [RFC3864]).
20.3.1. DAV
Header field name: DAV
Applicable protocol: http
Status: standard
Author/Change controller: IETF
Specification document: this specification (Section 9.1)
20.3.2. Depth
Header field name: Depth
Applicable protocol: http
Status: standard
Author/Change controller: IETF
Specification document: this specification (Section 9.2)
20.3.3. Destination
Header field name: Destination
Applicable protocol: http
Status: standard
Author/Change controller: IETF
Specification document: this specification (Section 9.3)
20.3.4. If
Header field name: If
Applicable protocol: http
Status: standard
Author/Change controller: IETF
Specification document: this specification (Section 9.4)
20.3.5. Lock-Token
Header field name: Lock-Token
Applicable protocol: http
Status: standard
Author/Change controller: IETF
Specification document: this specification (Section 9.5)
20.3.6. Overwrite
Header field name: Overwrite
Applicable protocol: http
Status: standard
Author/Change controller: IETF
Specification document: this specification (Section 9.6)
20.3.7. Timeout
Header field name: Timeout
Applicable protocol: http
Status: standard
Author/Change controller: IETF
Specification document: this specification (Section 9.7)
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 Contributors to RFC2518
Terry Allen, Harald Alvestrand, Jim Amsden, Becky Anderson, Alan Terry Allen, Harald Alvestrand, Jim Amsden, Becky Anderson, Alan
skipping to change at page 115, line 38 skipping to change at page 118, line 38
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, November 2003.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005. RFC 3986, January 2005.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, Unique IDentifier (UUID) URN Namespace", RFC 4122,
July 2005. July 2005.
[W3C.REC-xml-infoset-20040204]
Tobin, R. and J. Cowan, "XML Information Set (Second
Edition)", W3C REC REC-xml-infoset-20040204,
February 2004.
[W3C.REC-xml-names-19990114] [W3C.REC-xml-names-19990114]
Hollander, D., Bray, T., and A. Layman, "Namespaces in Hollander, D., Bray, T., and A. Layman, "Namespaces in
XML", W3C REC REC-xml-names-19990114, January 1999. XML", W3C REC REC-xml-names-19990114, January 1999.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third
Edition)", W3C REC-xml-20040204, February 2004, Edition)", W3C REC-xml-20040204, February 2004,
<http://www.w3.org/TR/2004/REC-xml-20040204>. <http://www.w3.org/TR/2004/REC-xml-20040204>.
22.2. Informational References 22.2. Informational References
skipping to change at page 116, line 25 skipping to change at page 119, line 31
March 2002. March 2002.
[RFC3648] Whitehead, J. and J. Reschke, Ed., "Web Distributed [RFC3648] Whitehead, J. and J. Reschke, Ed., "Web Distributed
Authoring and Versioning (WebDAV) Ordered Collections Authoring and Versioning (WebDAV) Ordered Collections
Protocol", RFC 3648, December 2003. Protocol", RFC 3648, December 2003.
[RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web [RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web
Distributed Authoring and Versioning (WebDAV) Access Distributed Authoring and Versioning (WebDAV) Access
Control Protocol", RFC 3744, May 2004. Control Protocol", RFC 3744, May 2004.
[W3C.REC-xml-infoset-20040204] [RFC3864] Klyne, G., Nottingham, M., and J. Mogul, "Registration
Tobin, R. and J. Cowan, "XML Information Set (Second Procedures for Message Header Fields", BCP 90, RFC 3864,
Edition)", W3C REC REC-xml-infoset-20040204, September 2004.
February 2004.
Appendix A. Notes on Processing XML Elements Appendix A. Notes on Processing XML Elements
A.1. Notes on Empty XML Elements A.1. Notes on Empty XML Elements
XML supports two mechanisms for indicating that an XML element does XML supports two mechanisms for indicating that an XML element does
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.
skipping to change at page 123, line 13 skipping to change at page 126, line 13
[body omitted] [body omitted]
Appendix E. Summary of changes from RFC2518 Appendix E. Summary of changes from RFC2518
This section describes changes that are likely to result in This section describes changes that are likely to result in
implementation changes due to tightened requirements or changed implementation changes due to tightened requirements or changed
behavior. behavior.
E.1. Changes Notable to Server Implementors E.1. Changes Notable to Server Implementors
Tightened requirements for storing property values (Section 4.4) when Tightened requirements for storing property values (Section 4.3) when
"xml:lang" appears and also when values are XML fragments "xml:lang" appears and also when values are XML fragments
(specifically on preserving prefixes, namespaces and whitespace.) (specifically on preserving prefixes, namespaces and whitespace.)
Changed meaning of PROPFIND 'allprop' so that it doesn't have to
return live properties not defined in this specification; added
'include' syntax so that clients can retrieve specific live
properties along with 'allprop' results.
Tightened requirements on which properties are protected and computed Tightened requirements on which properties are protected and computed
(Section 14). (Section 14).
Several tightened requirements for general response handling Several tightened requirements for general response handling
(Section 8.1), including response bodies for use with errors, ETag (Section 8.1), including ETag and Location header, and reminder to
and Location header, and reminder to use Date header. use Date header.
Defined response bodies for error responses, including several
machine-readable precondition or postcondition codes (Section 15) for
error detail.
Tightened requirements for URL construction in PROPFIND (Section 8.2) Tightened requirements for URL construction in PROPFIND (Section 8.2)
responses. responses.
Tightened requirements for checking identity of lock owners Tightened requirements for checking identity of lock creators
(Section 7.1) during operations affected by locks. (Section 6.3) during operations affected by locks.
Tightened requirements for copying properties (Section 8.9.2) and Tightened requirements for copying properties (Section 8.9.2) and
moving properties (Section 8.10.1). moving properties (Section 8.10.1).
Tightened requirements on preserving owner field in locks Tightened requirements on preserving 'owner' field in locks
(Section 8.11). Added "lockroot" element to lockdiscovery (Section 8.11). Added "lockroot" element to lockdiscovery
information. information.
New value for "DAV:" header (Section 9.1) to advertise support for New value for "DAV:" header (Section 9.1) to advertise support for
this specification. this specification.
Tightened requirement for "Destination:" header (Section 9.3) to work
with path values
Some changes for "If:" header (Section 9.4), including "DAV:no-lock" Some changes for "If:" header (Section 9.4), including "DAV:no-lock"
state token and requirement to evaluate entire header. state token and requirement to evaluate entire header.
Support for UTF-16 now required (ref (Section 18)). Support for UTF-16 now required (ref (Section 18)).
Removed definition of "source" property and special handling for Removed definition of "source" property and special handling for
dynamic resources dynamic resources
Replaced lock-null resources with simpler locked empty resources Replaced lock-null resources with simpler locked empty resources
(Section 7.6). Lock-null resources are now not compliant with the (Section 7.5). Lock-null resources are now not compliant with the
requirements in this specification. requirements in this specification.
Encouraged servers to change ETags (Section 8.1.4) only when body of Encouraged servers to change ETags (Section 8.1.4) only when body of
resource changes. resource changes.
The definition of the 102 Processing response was removed and servers The definition of the 102 Processing response was removed and servers
ought to stop sending that response when they implement this ought to stop sending that response when they implement this
specification. specification.
Previously, servers were encouraged to return 409 status code in Previously, servers were encouraged to return 409 status code in
response to a collection LOCK request if some resource could not be response to a collection LOCK request if some resource could not be
locked. Now servers should use 207 Multi-Status instead. locked. Now servers should use 207 Multi-Status instead.
New element 'location' defined for handling redirected resources in
Multi-Status.
Only 'rfc1123-date' productions are legal as values for DAV: Only 'rfc1123-date' productions are legal as values for DAV:
getlastmodified. getlastmodified.
New explicit requirement to do authorization checks before New explicit requirement to do authorization checks before
conditional checks (Section 8.1.3). conditional checks (Section 8.1.3).
Defined idempotence, safeness and cacheability for all new methods.
Depth: Infinity doesn't affect other headers; by default these
headers only apply to the Request-URI (Section 9.4).
E.2. Changes Notable to Client Implementors E.2. Changes Notable to Client Implementors
Tightened requirements for supporting WebDAV collections Tightened requirements for supporting WebDAV collections
(Section 5.2) within resources that do not support WebDAV (e.g. (Section 5.2) within resources that do not support WebDAV (e.g.
servlet containers). servlet containers).
Redefined 'allprop' PROPFIND requests so that the server does not Redefined 'allprop' PROPFIND requests so that the server does not
have to return all properties. have to return all properties.
Required to handle empty multistatus responses in PROPFIND responses Servers are no longer required to support all depth "infinity"
(Section 8.2) PROPFIND requests, so clients need to be able to handle that and do
multiple depth "1" requests instead.
No more "propertybehavior" specification allowed in MOVE and COPY No more "propertybehavior" specification allowed in MOVE and COPY
requests requests
The change in behavior of LOCK with an unmapped URL might affect The change in behavior of LOCK with an unmapped URL might affect
client implementations that counted on lock-null resources client implementations that counted on lock-null resources
disappearing when the lock expired. Clients can no longer rely on disappearing when the lock expired. Clients can no longer rely on
that cleanup happening. that cleanup happening.
Support for UTF-16 now required (ref (Section 18)). Support for UTF-16 now required (ref (Section 18)).
Removed definition of "source" property and special handling for Removed definition of "source" property and special handling for
dynamic resources. dynamic resources.
skipping to change at page 126, line 5 skipping to change at page 128, line 22
dynamic resources. dynamic resources.
The definition of the 102 Processing response was removed and clients The definition of the 102 Processing response was removed and clients
can safely remove code (if any) that deals with this. can safely remove code (if any) that deals with this.
Servers may now reject PROPFIND depth "infinity" requests. Servers may now reject PROPFIND depth "infinity" requests.
Clients use Lock-Token header, not the If header, to provide lock Clients use Lock-Token header, not the If header, to provide lock
token when renewing lock. Section 8.11.1 token when renewing lock. Section 8.11.1
Clients must refresh locks explicitly as this is now the only way to
renew timeout.
Appendix F. Change Log (to be removed by RFC Editor before publication) Appendix F. Change Log (to be removed by RFC Editor before publication)
F.1. Changes from -05 to -06 F.1. Changes from -05 to -06
Specified that a successful LOCK request to an unmapped URL creates a Specified that a successful LOCK request to an unmapped URL creates a
new, empty locked resource. new, empty locked resource.
Resolved UNLOCK_NEEDS_IF_HEADER by clarifying that only Lock-Token Resolved UNLOCK_NEEDS_IF_HEADER by clarifying that only Lock-Token
header is needed on UNLOCK. header is needed on UNLOCK.
skipping to change at page 129, line 8 skipping to change at page 132, line 8
Fix bug 46, 105, 107, 120, 140 and 201. Fix bug 46, 105, 107, 120, 140 and 201.
Another stab at bug 12 - relative v. absolute URLs in Multi-Status Another stab at bug 12 - relative v. absolute URLs in Multi-Status
response hrefs response hrefs
Fix bug 6, 11, 15, 16, 28, 32, 42, 51, 52, 53, 58, 60, 62, 186, 189, Fix bug 6, 11, 15, 16, 28, 32, 42, 51, 52, 53, 58, 60, 62, 186, 189,
191, 199, 200 191, 199, 200
Fix bug 96 Fix bug 96
F.5. Chandles in -10 F.5. Changes in -10
Clarify lock intro text on when a client might use another client's Clarify lock intro text on when a client might use another client's
lock token - suggestion by Geoff, Nov 15 lock token - suggestion by Geoff, Nov 15
Removed Force-Authenticate header and instead added an appendix Removed Force-Authenticate header and instead added an appendix
explaining how existing mechanisms might resolve the need of clients explaining how existing mechanisms might resolve the need of clients
to get an authentication challenge (bug 18). to get an authentication challenge (bug 18).
Bug 62, 113, 125, 131, 143, 144, 171, 193 Bug 62, 113, 125, 131, 143, 144, 171, 193
Bug 176, 177, 179, 181, 184, 206, 207, 208 Bug 176, 177, 179, 181, 184, 206, 207, 208
F.6. Changes in -11
Bug 10, 50, 92, 213, 214, 215
not recommend use of 414 for over-long Destination URI, bug 179
Changes for bug 10, 31, 42, 44, 46, 47, 80, 86, 99, 124, 132, 143,
147, 152, 166, 177, 188, 216, 218
Various changes discussed in conference call, including bug 10, 42,
44, 80, 97, 152.
Bugs 55, 85, 86
Author's Address Author's Address
Lisa Dusseault Lisa Dusseault
Open Source Application Foundation Open Source Application Foundation
2064 Edgewood Dr. 2064 Edgewood Dr.
Palo Alto, CA 94303 Palo Alto, CA 94303
US US
Email: lisa@osafoundation.org Email: lisa@osafoundation.org
skipping to change at page 131, line 41 skipping to change at page 134, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 207 change blocks. 
669 lines changed or deleted 833 lines changed or added

This html diff was produced by rfcdiff 1.28, available from http://www.levkowetz.com/ietf/tools/rfcdiff/