draft-ietf-webdav-rfc2518bis-11.txt   draft-ietf-webdav-rfc2518bis-12.txt 
WebDAV L. Dusseault WebDAV L. Dusseault, Ed.
Internet-Draft OSAF Internet-Draft OSAF
Obsoletes: 2518 (if approved) January 22, 2006 Obsoletes: 2518 (if approved) February 5, 2006
Expires: July 26, 2006 Expires: August 9, 2006
HTTP Extensions for Distributed Authoring - WebDAV HTTP Extensions for Distributed Authoring - WebDAV
draft-ietf-webdav-rfc2518bis-11 draft-ietf-webdav-rfc2518bis-12
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 26, 2006. This Internet-Draft will expire on August 9, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). 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
skipping to change at page 2, line 21 skipping to change at page 2, line 21
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. Property Values . . . . . . . . . . . . . . . . . . . . 11 4.3. Property Values . . . . . . . . . . . . . . . . . . . . 11
4.3.1. Example - Property with Mixed Content . . . . . . . 13 4.3.1. Example - Property with Mixed Content . . . . . . . 13
4.4. Property Names . . . . . . . . . . . . . . . . . . . . . 15 4.4. Property Names . . . . . . . . . . . . . . . . . . . . . 15
4.5. Source Resources and Output Resources . . . . . . . . . 15 4.5. Source Resources and Output Resources . . . . . . . . . 15
5. Collections of Web Resources . . . . . . . . . . . . . . . . 16 5. Collections of Web Resources . . . . . . . . . . . . . . . . 16
5.1. HTTP URL Namespace Model . . . . . . . . . . . . . . . . 16 5.1. HTTP URL Namespace Model . . . . . . . . . . . . . . . . 16
5.2. Collection Resources . . . . . . . . . . . . . . . . . . 16 5.2. Collection Resources . . . . . . . . . . . . . . . . . . 16
6. Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6. Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.1. Exclusive Vs. Shared Locks . . . . . . . . . . . . . . . 18 6.1. Lock Model . . . . . . . . . . . . . . . . . . . . . . . 18
6.2. Required Support . . . . . . . . . . . . . . . . . . . . 19 6.2. Exclusive Vs. Shared Locks . . . . . . . . . . . . . . . 19
6.3. Lock Creator . . . . . . . . . . . . . . . . . . . . . . 19 6.3. Required Support . . . . . . . . . . . . . . . . . . . . 20
6.4. Lock Tokens . . . . . . . . . . . . . . . . . . . . . . 20 6.4. Lock Creator . . . . . . . . . . . . . . . . . . . . . . 20
6.5. Lock Capability Discovery . . . . . . . . . . . . . . . 20 6.5. Lock Tokens . . . . . . . . . . . . . . . . . . . . . . 21
6.6. Active Lock Discovery . . . . . . . . . . . . . . . . . 21 6.6. Lock Timeout . . . . . . . . . . . . . . . . . . . . . . 22
6.7. Locks and Multiple Bindings . . . . . . . . . . . . . . 21 6.7. Lock Capability Discovery . . . . . . . . . . . . . . . 22
7. Write Lock . . . . . . . . . . . . . . . . . . . . . . . . . 22 6.8. Active Lock Discovery . . . . . . . . . . . . . . . . . 22
7.1. Methods Restricted by Write Locks . . . . . . . . . . . 22 6.9. Locks and Multiple Bindings . . . . . . . . . . . . . . 22
7.2. Write Locks and Lock Tokens . . . . . . . . . . . . . . 22 7. Write Lock . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.3. Write Locks and Properties . . . . . . . . . . . . . . . 23 7.1. Write Locks and Properties . . . . . . . . . . . . . . . 23
7.4. Avoiding Lost Updates . . . . . . . . . . . . . . . . . 23 7.2. Avoiding Lost Updates . . . . . . . . . . . . . . . . . 24
7.5. Write Locks and Unmapped URLs . . . . . . . . . . . . . 24 7.3. Write Locks and Unmapped URLs . . . . . . . . . . . . . 25
7.6. Write Locks and Collections . . . . . . . . . . . . . . 26 7.4. Write Locks and Collections . . . . . . . . . . . . . . 27
7.7. Write Locks and the If Request Header . . . . . . . . . 27 7.5. Write Locks and the If Request Header . . . . . . . . . 28
7.7.1. Example - Write Lock and COPY . . . . . . . . . . . 28 7.5.1. Example - Write Lock and COPY . . . . . . . . . . . 29
7.7.2. Example - Deleting a member of a locked collection . 28 7.5.2. Example - Deleting a member of a locked collection . 29
7.8. Write Locks and COPY/MOVE . . . . . . . . . . . . . . . 29 7.6. Write Locks and COPY/MOVE . . . . . . . . . . . . . . . 30
7.9. Refreshing Write Locks . . . . . . . . . . . . . . . . . 30 7.7. Refreshing Write Locks . . . . . . . . . . . . . . . . . 31
8. HTTP Methods for Distributed Authoring . . . . . . . . . . . 31 8. General Request and Response Handling . . . . . . . . . . . . 32
8.1. General Request and Response Handling . . . . . . . . . 31 8.1. Use of XML . . . . . . . . . . . . . . . . . . . . . . . 32
8.1.1. Use of XML . . . . . . . . . . . . . . . . . . . . . 31 8.2. URL Handling . . . . . . . . . . . . . . . . . . . . . . 32
8.1.2. Required Bodies in Requests . . . . . . . . . . . . 31 8.2.1. Example - Correct URL Handling . . . . . . . . . . . 33
8.1.3. HTTP Headers for use in WebDAV . . . . . . . . . . . 31 8.3. Required Bodies in Requests . . . . . . . . . . . . . . 34
8.1.4. ETag . . . . . . . . . . . . . . . . . . . . . . . . 32 8.4. HTTP Headers for use in WebDAV . . . . . . . . . . . . . 34
8.1.5. Including error response bodies . . . . . . . . . . 32 8.5. ETag . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.1.6. Impact of Namespace Operations on Cache Validators . 33 8.6. Including error response bodies . . . . . . . . . . . . 35
8.2. PROPFIND Method . . . . . . . . . . . . . . . . . . . . 33 8.7. Impact of Namespace Operations on Cache Validators . . . 35
8.2.1. PROPFIND status codes . . . . . . . . . . . . . . . 35 9. HTTP Methods for Distributed Authoring . . . . . . . . . . . 37
8.2.2. Status codes for use with 207 (Multi-Status) . . . . 35 9.1. PROPFIND Method . . . . . . . . . . . . . . . . . . . . 37
8.2.3. Example - Retrieving Named Properties . . . . . . . 36 9.1.1. PROPFIND status codes . . . . . . . . . . . . . . . 38
8.2.4. Example - Retrieving Named and Dead Properties . . . 38 9.1.2. Status codes for use with 207 (Multi-Status) . . . . 39
8.2.5. Example - Using 'propname' to Retrieve all 9.1.3. Example - Retrieving Named Properties . . . . . . . 39
Property Names . . . . . . . . . . . . . . . . . . . 38 9.1.4. Example - Retrieving Named and Dead Properties . . . 41
8.2.6. Example - Using 'allprop' . . . . . . . . . . . . . 40 9.1.5. Example - Using 'propname' to Retrieve all
8.3. PROPPATCH Method . . . . . . . . . . . . . . . . . . . . 42 Property Names . . . . . . . . . . . . . . . . . . . 41
8.3.1. Status Codes for use in 207 (Multi-Status) . . . . . 43 9.1.6. Example - Using 'allprop' . . . . . . . . . . . . . 43
8.3.2. Example - PROPPATCH . . . . . . . . . . . . . . . . 44 9.2. PROPPATCH Method . . . . . . . . . . . . . . . . . . . . 45
8.4. MKCOL Method . . . . . . . . . . . . . . . . . . . . . . 45 9.2.1. Status Codes for use in 207 (Multi-Status) . . . . . 46
8.4.1. MKCOL Status Codes . . . . . . . . . . . . . . . . . 46 9.2.2. Example - PROPPATCH . . . . . . . . . . . . . . . . 47
8.4.2. Example - MKCOL . . . . . . . . . . . . . . . . . . 46 9.3. MKCOL Method . . . . . . . . . . . . . . . . . . . . . . 48
8.5. GET, HEAD for Collections . . . . . . . . . . . . . . . 47 9.3.1. MKCOL Status Codes . . . . . . . . . . . . . . . . . 49
8.6. POST for Collections . . . . . . . . . . . . . . . . . . 47 9.3.2. Example - MKCOL . . . . . . . . . . . . . . . . . . 49
8.7. DELETE Requirements . . . . . . . . . . . . . . . . . . 47 9.4. GET, HEAD for Collections . . . . . . . . . . . . . . . 50
8.7.1. DELETE for Collections . . . . . . . . . . . . . . . 48 9.5. POST for Collections . . . . . . . . . . . . . . . . . . 50
8.7.2. Example - DELETE . . . . . . . . . . . . . . . . . . 48 9.6. DELETE Requirements . . . . . . . . . . . . . . . . . . 50
8.8. PUT Requirements . . . . . . . . . . . . . . . . . . . . 49 9.6.1. DELETE for Collections . . . . . . . . . . . . . . . 51
8.8.1. PUT for Non-Collection Resources . . . . . . . . . . 49 9.6.2. Example - DELETE . . . . . . . . . . . . . . . . . . 51
8.8.2. PUT for Collections . . . . . . . . . . . . . . . . 50 9.7. PUT Requirements . . . . . . . . . . . . . . . . . . . . 52
8.9. COPY Method . . . . . . . . . . . . . . . . . . . . . . 50 9.7.1. PUT for Non-Collection Resources . . . . . . . . . . 52
8.9.1. COPY for Non-collection Resources . . . . . . . . . 50 9.7.2. PUT for Collections . . . . . . . . . . . . . . . . 53
8.9.2. COPY for Properties . . . . . . . . . . . . . . . . 51 9.8. COPY Method . . . . . . . . . . . . . . . . . . . . . . 53
8.9.3. COPY for Collections . . . . . . . . . . . . . . . . 51 9.8.1. COPY for Non-collection Resources . . . . . . . . . 53
8.9.4. COPY and Overwriting Destination Resources . . . . . 52 9.8.2. COPY for Properties . . . . . . . . . . . . . . . . 54
8.9.5. Status Codes . . . . . . . . . . . . . . . . . . . . 53 9.8.3. COPY for Collections . . . . . . . . . . . . . . . . 54
8.9.6. Example - COPY with Overwrite . . . . . . . . . . . 54 9.8.4. COPY and Overwriting Destination Resources . . . . . 55
8.9.7. Example - COPY with No Overwrite . . . . . . . . . . 54 9.8.5. Status Codes . . . . . . . . . . . . . . . . . . . . 56
8.9.8. Example - COPY of a Collection . . . . . . . . . . . 55 9.8.6. Example - COPY with Overwrite . . . . . . . . . . . 57
8.10. MOVE Method . . . . . . . . . . . . . . . . . . . . . . 55 9.8.7. Example - COPY with No Overwrite . . . . . . . . . . 57
8.10.1. MOVE for Properties . . . . . . . . . . . . . . . . 56 9.8.8. Example - COPY of a Collection . . . . . . . . . . . 58
8.10.2. MOVE for Collections . . . . . . . . . . . . . . . . 56 9.9. MOVE Method . . . . . . . . . . . . . . . . . . . . . . 58
8.10.3. MOVE and the Overwrite Header . . . . . . . . . . . 57 9.9.1. MOVE for Properties . . . . . . . . . . . . . . . . 59
8.10.4. Status Codes . . . . . . . . . . . . . . . . . . . . 57 9.9.2. MOVE for Collections . . . . . . . . . . . . . . . . 59
8.10.5. Example - MOVE of a Non-Collection . . . . . . . . . 58 9.9.3. MOVE and the Overwrite Header . . . . . . . . . . . 60
8.10.6. Example - MOVE of a Collection . . . . . . . . . . . 59 9.9.4. Status Codes . . . . . . . . . . . . . . . . . . . . 60
8.11. LOCK Method . . . . . . . . . . . . . . . . . . . . . . 59 9.9.5. Example - MOVE of a Non-Collection . . . . . . . . . 61
8.11.1. Refreshing Locks . . . . . . . . . . . . . . . . . . 60 9.9.6. Example - MOVE of a Collection . . . . . . . . . . . 62
8.11.2. Depth and Locking . . . . . . . . . . . . . . . . . 61 9.10. LOCK Method . . . . . . . . . . . . . . . . . . . . . . 62
8.11.3. Locking Unmapped URLs . . . . . . . . . . . . . . . 61 9.10.1. Creating a lock on existing resource . . . . . . . . 63
8.11.4. Lock Compatibility Table . . . . . . . . . . . . . . 62 9.10.2. Refreshing Locks . . . . . . . . . . . . . . . . . . 63
8.11.5. LOCK Responses . . . . . . . . . . . . . . . . . . . 62 9.10.3. Depth and Locking . . . . . . . . . . . . . . . . . 64
8.11.6. Example - Simple Lock Request . . . . . . . . . . . 63 9.10.4. Locking Unmapped URLs . . . . . . . . . . . . . . . 64
8.11.7. Example - Refreshing a Write Lock . . . . . . . . . 65 9.10.5. Lock Compatibility Table . . . . . . . . . . . . . . 65
8.11.8. Example - Multi-Resource Lock Request . . . . . . . 66 9.10.6. LOCK Responses . . . . . . . . . . . . . . . . . . . 65
8.12. UNLOCK Method . . . . . . . . . . . . . . . . . . . . . 67 9.10.7. Example - Simple Lock Request . . . . . . . . . . . 66
8.12.1. Status Codes . . . . . . . . . . . . . . . . . . . . 67 9.10.8. Example - Refreshing a Write Lock . . . . . . . . . 68
8.12.2. Example - UNLOCK . . . . . . . . . . . . . . . . . . 68 9.10.9. Example - Multi-Resource Lock Request . . . . . . . 69
9. HTTP Headers for Distributed Authoring . . . . . . . . . . . 69 9.11. UNLOCK Method . . . . . . . . . . . . . . . . . . . . . 70
9.1. DAV Header . . . . . . . . . . . . . . . . . . . . . . . 69 9.11.1. Status Codes . . . . . . . . . . . . . . . . . . . . 70
9.2. Depth Header . . . . . . . . . . . . . . . . . . . . . . 69 9.11.2. Example - UNLOCK . . . . . . . . . . . . . . . . . . 71
9.3. Destination Header . . . . . . . . . . . . . . . . . . . 71 10. HTTP Headers for Distributed Authoring . . . . . . . . . . . 72
9.4. If Header . . . . . . . . . . . . . . . . . . . . . . . 71 10.1. DAV Header . . . . . . . . . . . . . . . . . . . . . . . 72
9.4.1. No-tag-list Production . . . . . . . . . . . . . . . 72 10.2. Depth Header . . . . . . . . . . . . . . . . . . . . . . 73
9.4.2. Tagged-list Production . . . . . . . . . . . . . . . 72 10.3. Destination Header . . . . . . . . . . . . . . . . . . . 74
9.4.3. Example - Tagged List If header in COPY . . . . . . 73 10.4. If Header . . . . . . . . . . . . . . . . . . . . . . . 74
9.4.4. Not Production . . . . . . . . . . . . . . . . . . . 73 10.4.1. No-tag-list Production . . . . . . . . . . . . . . . 75
9.4.5. Matching Function . . . . . . . . . . . . . . . . . 74 10.4.2. Tagged-list Production . . . . . . . . . . . . . . . 75
9.4.6. If Header and Non-DAV Aware Proxies . . . . . . . . 74 10.4.3. Example - Tagged List If header in COPY . . . . . . 76
9.5. Lock-Token Header . . . . . . . . . . . . . . . . . . . 75 10.4.4. Not Production . . . . . . . . . . . . . . . . . . . 76
9.6. Overwrite Header . . . . . . . . . . . . . . . . . . . . 75 10.4.5. Matching Function . . . . . . . . . . . . . . . . . 77
9.7. Timeout Request Header . . . . . . . . . . . . . . . . . 75 10.4.6. If Header and Non-DAV Aware Proxies . . . . . . . . 77
10. Status Code Extensions to HTTP/1.1 . . . . . . . . . . . . . 77 10.5. Lock-Token Header . . . . . . . . . . . . . . . . . . . 78
10.1. 207 Multi-Status . . . . . . . . . . . . . . . . . . . . 77 10.6. Overwrite Header . . . . . . . . . . . . . . . . . . . . 78
10.2. 422 Unprocessable Entity . . . . . . . . . . . . . . . . 77 10.7. Timeout Request Header . . . . . . . . . . . . . . . . . 78
10.3. 423 Locked . . . . . . . . . . . . . . . . . . . . . . . 77 11. Status Code Extensions to HTTP/1.1 . . . . . . . . . . . . . 80
10.4. 424 Failed Dependency . . . . . . . . . . . . . . . . . 77 11.1. 207 Multi-Status . . . . . . . . . . . . . . . . . . . . 80
10.5. 507 Insufficient Storage . . . . . . . . . . . . . . . . 77 11.2. 422 Unprocessable Entity . . . . . . . . . . . . . . . . 80
11. Use of HTTP Status Codes . . . . . . . . . . . . . . . . . . 78 11.3. 423 Locked . . . . . . . . . . . . . . . . . . . . . . . 80
11.1. 412 Precondition Failed . . . . . . . . . . . . . . . . 78 11.4. 424 Failed Dependency . . . . . . . . . . . . . . . . . 80
11.2. 414 Request-URI Too Long . . . . . . . . . . . . . . . . 78 11.5. 507 Insufficient Storage . . . . . . . . . . . . . . . . 80
12. Multi-Status Response . . . . . . . . . . . . . . . . . . . . 79 12. Use of HTTP Status Codes . . . . . . . . . . . . . . . . . . 81
12.1. Response headers . . . . . . . . . . . . . . . . . . . . 79 12.1. 412 Precondition Failed . . . . . . . . . . . . . . . . 81
12.2. URL Handling . . . . . . . . . . . . . . . . . . . . . . 79 12.2. 414 Request-URI Too Long . . . . . . . . . . . . . . . . 81
12.3. Handling redirected child resources . . . . . . . . . . 80 13. Multi-Status Response . . . . . . . . . . . . . . . . . . . . 82
12.4. Internal Status Codes . . . . . . . . . . . . . . . . . 80 13.1. Response headers . . . . . . . . . . . . . . . . . . . . 82
13. XML Element Definitions . . . . . . . . . . . . . . . . . . . 81 13.2. Handling redirected child resources . . . . . . . . . . 82
13.1. activelock XML Element . . . . . . . . . . . . . . . . . 81 13.3. Internal Status Codes . . . . . . . . . . . . . . . . . 83
13.2. allprop XML Element . . . . . . . . . . . . . . . . . . 81 14. XML Element Definitions . . . . . . . . . . . . . . . . . . . 84
13.3. collection XML Element . . . . . . . . . . . . . . . . . 81 14.1. activelock XML Element . . . . . . . . . . . . . . . . . 84
13.4. depth XML Element . . . . . . . . . . . . . . . . . . . 82 14.2. allprop XML Element . . . . . . . . . . . . . . . . . . 84
13.5. error XML Element . . . . . . . . . . . . . . . . . . . 82 14.3. collection XML Element . . . . . . . . . . . . . . . . . 84
13.6. exclusive XML Element . . . . . . . . . . . . . . . . . 82 14.4. depth XML Element . . . . . . . . . . . . . . . . . . . 85
13.7. href XML Element . . . . . . . . . . . . . . . . . . . . 82 14.5. error XML Element . . . . . . . . . . . . . . . . . . . 85
13.8. include XML Element . . . . . . . . . . . . . . . . . . 83 14.6. exclusive XML Element . . . . . . . . . . . . . . . . . 85
13.9. location XML Element . . . . . . . . . . . . . . . . . . 83 14.7. href XML Element . . . . . . . . . . . . . . . . . . . . 85
13.10. lockentry XML Element . . . . . . . . . . . . . . . . . 83 14.8. include XML Element . . . . . . . . . . . . . . . . . . 86
13.11. lockinfo XML Element . . . . . . . . . . . . . . . . . . 83 14.9. location XML Element . . . . . . . . . . . . . . . . . . 86
13.12. lockroot XML Element . . . . . . . . . . . . . . . . . . 84 14.10. lockentry XML Element . . . . . . . . . . . . . . . . . 86
13.13. lockscope XML Element . . . . . . . . . . . . . . . . . 84 14.11. lockinfo XML Element . . . . . . . . . . . . . . . . . . 86
13.14. locktoken XML Element . . . . . . . . . . . . . . . . . 84 14.12. lockroot XML Element . . . . . . . . . . . . . . . . . . 87
13.15. locktype XML Element . . . . . . . . . . . . . . . . . . 84 14.13. lockscope XML Element . . . . . . . . . . . . . . . . . 87
13.16. multistatus XML Element . . . . . . . . . . . . . . . . 85 14.14. locktoken XML Element . . . . . . . . . . . . . . . . . 87
13.17. prop XML element . . . . . . . . . . . . . . . . . . . . 85 14.15. locktype XML Element . . . . . . . . . . . . . . . . . . 87
13.18. propertyupdate XML element . . . . . . . . . . . . . . . 85 14.16. multistatus XML Element . . . . . . . . . . . . . . . . 88
13.19. propfind XML Element . . . . . . . . . . . . . . . . . . 86 14.17. owner XML Element . . . . . . . . . . . . . . . . . . . 88
13.20. propname XML Element . . . . . . . . . . . . . . . . . . 86 14.18. prop XML element . . . . . . . . . . . . . . . . . . . . 89
13.21. propstat XML Element . . . . . . . . . . . . . . . . . . 86 14.19. propertyupdate XML element . . . . . . . . . . . . . . . 89
13.22. remove XML element . . . . . . . . . . . . . . . . . . . 86 14.20. propfind XML Element . . . . . . . . . . . . . . . . . . 89
13.23. response XML Element . . . . . . . . . . . . . . . . . . 87 14.21. propname XML Element . . . . . . . . . . . . . . . . . . 89
13.24. responsedescription XML Element . . . . . . . . . . . . 87 14.22. propstat XML Element . . . . . . . . . . . . . . . . . . 90
13.25. set XML element . . . . . . . . . . . . . . . . . . . . 87 14.23. remove XML element . . . . . . . . . . . . . . . . . . . 90
13.26. shared XML Element . . . . . . . . . . . . . . . . . . . 88 14.24. response XML Element . . . . . . . . . . . . . . . . . . 90
13.27. status XML Element . . . . . . . . . . . . . . . . . . . 88 14.25. responsedescription XML Element . . . . . . . . . . . . 91
13.28. timeout XML Element . . . . . . . . . . . . . . . . . . 88 14.26. set XML element . . . . . . . . . . . . . . . . . . . . 91
13.29. write XML Element . . . . . . . . . . . . . . . . . . . 89 14.27. shared XML Element . . . . . . . . . . . . . . . . . . . 91
14. DAV Properties . . . . . . . . . . . . . . . . . . . . . . . 90 14.28. status XML Element . . . . . . . . . . . . . . . . . . . 92
14.1. creationdate Property . . . . . . . . . . . . . . . . . 90 14.29. timeout XML Element . . . . . . . . . . . . . . . . . . 92
14.2. displayname Property . . . . . . . . . . . . . . . . . . 91 14.30. write XML Element . . . . . . . . . . . . . . . . . . . 92
14.3. getcontentlanguage Property . . . . . . . . . . . . . . 91 15. DAV Properties . . . . . . . . . . . . . . . . . . . . . . . 93
14.4. getcontentlength Property . . . . . . . . . . . . . . . 92 15.1. creationdate Property . . . . . . . . . . . . . . . . . 93
14.5. getcontenttype Property . . . . . . . . . . . . . . . . 92 15.2. displayname Property . . . . . . . . . . . . . . . . . . 94
14.6. getetag Property . . . . . . . . . . . . . . . . . . . . 93 15.3. getcontentlanguage Property . . . . . . . . . . . . . . 94
14.7. getlastmodified Property . . . . . . . . . . . . . . . . 93 15.4. getcontentlength Property . . . . . . . . . . . . . . . 95
14.8. lockdiscovery Property . . . . . . . . . . . . . . . . . 94 15.5. getcontenttype Property . . . . . . . . . . . . . . . . 95
14.8.1. Example - Retrieving DAV:lockdiscovery . . . . . . . 95 15.6. getetag Property . . . . . . . . . . . . . . . . . . . . 96
14.9. resourcetype Property . . . . . . . . . . . . . . . . . 96 15.7. getlastmodified Property . . . . . . . . . . . . . . . . 96
14.10. supportedlock Property . . . . . . . . . . . . . . . . . 97 15.8. lockdiscovery Property . . . . . . . . . . . . . . . . . 97
14.10.1. Example - Retrieving DAV:supportedlock . . . . . . . 98 15.8.1. Example - Retrieving DAV:lockdiscovery . . . . . . . 98
15. Precondition/postcondition XML elements . . . . . . . . . . . 99 15.9. resourcetype Property . . . . . . . . . . . . . . . . . 99
16. XML Extensibility in DAV . . . . . . . . . . . . . . . . . . 103 15.10. supportedlock Property . . . . . . . . . . . . . . . . . 100
17. DAV Compliance Classes . . . . . . . . . . . . . . . . . . . 105 15.10.1. Example - Retrieving DAV:supportedlock . . . . . . . 101
17.1. Class 1 . . . . . . . . . . . . . . . . . . . . . . . . 105 16. Precondition/postcondition XML elements . . . . . . . . . . . 102
17.2. Class 2 . . . . . . . . . . . . . . . . . . . . . . . . 105 17. XML Extensibility in DAV . . . . . . . . . . . . . . . . . . 106
17.3. Class 'bis' . . . . . . . . . . . . . . . . . . . . . . 105 18. DAV Compliance Classes . . . . . . . . . . . . . . . . . . . 108
18. Internationalization Considerations . . . . . . . . . . . . . 106 18.1. Class 1 . . . . . . . . . . . . . . . . . . . . . . . . 108
19. Security Considerations . . . . . . . . . . . . . . . . . . . 108 18.2. Class 2 . . . . . . . . . . . . . . . . . . . . . . . . 108
19.1. Authentication of Clients . . . . . . . . . . . . . . . 108 18.3. Class 3 . . . . . . . . . . . . . . . . . . . . . . . . 108
19.2. Denial of Service . . . . . . . . . . . . . . . . . . . 108 19. Internationalization Considerations . . . . . . . . . . . . . 110
19.3. Security through Obscurity . . . . . . . . . . . . . . . 109 20. Security Considerations . . . . . . . . . . . . . . . . . . . 112
19.4. Privacy Issues Connected to Locks . . . . . . . . . . . 109 20.1. Authentication of Clients . . . . . . . . . . . . . . . 112
19.5. Privacy Issues Connected to Properties . . . . . . . . . 109 20.2. Denial of Service . . . . . . . . . . . . . . . . . . . 112
19.6. Implications of XML Entities . . . . . . . . . . . . . . 110 20.3. Security through Obscurity . . . . . . . . . . . . . . . 113
19.7. Risks Connected with Lock Tokens . . . . . . . . . . . . 111 20.4. Privacy Issues Connected to Locks . . . . . . . . . . . 113
19.8. Hosting malicious scripts executed on client machines . 111 20.5. Privacy Issues Connected to Properties . . . . . . . . . 113
20. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 113 20.6. Implications of XML Entities . . . . . . . . . . . . . . 114
20.1. New URI Schemes . . . . . . . . . . . . . . . . . . . . 113 20.7. Risks Connected with Lock Tokens . . . . . . . . . . . . 115
20.2. XML Namespaces . . . . . . . . . . . . . . . . . . . . . 113 20.8. Hosting Malicious Content . . . . . . . . . . . . . . . 115
20.3. Message Header Fields . . . . . . . . . . . . . . . . . 113 21. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 116
20.3.1. DAV . . . . . . . . . . . . . . . . . . . . . . . . 113 21.1. New URI Schemes . . . . . . . . . . . . . . . . . . . . 116
20.3.2. Depth . . . . . . . . . . . . . . . . . . . . . . . 113 21.2. XML Namespaces . . . . . . . . . . . . . . . . . . . . . 116
20.3.3. Destination . . . . . . . . . . . . . . . . . . . . 114 21.3. Message Header Fields . . . . . . . . . . . . . . . . . 116
20.3.4. If . . . . . . . . . . . . . . . . . . . . . . . . . 114 21.3.1. DAV . . . . . . . . . . . . . . . . . . . . . . . . 116
20.3.5. Lock-Token . . . . . . . . . . . . . . . . . . . . . 114 21.3.2. Depth . . . . . . . . . . . . . . . . . . . . . . . 116
20.3.6. Overwrite . . . . . . . . . . . . . . . . . . . . . 114 21.3.3. Destination . . . . . . . . . . . . . . . . . . . . 117
20.3.7. Timeout . . . . . . . . . . . . . . . . . . . . . . 115 21.3.4. If . . . . . . . . . . . . . . . . . . . . . . . . . 117
21. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 116 21.3.5. Lock-Token . . . . . . . . . . . . . . . . . . . . . 117
21.1. Previous Authors' Addresses . . . . . . . . . . . . . . 117 21.3.6. Overwrite . . . . . . . . . . . . . . . . . . . . . 117
22. References . . . . . . . . . . . . . . . . . . . . . . . . . 118 21.3.7. Timeout . . . . . . . . . . . . . . . . . . . . . . 118
22.1. Normative References . . . . . . . . . . . . . . . . . . 118 22. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 119
22.2. Informational References . . . . . . . . . . . . . . . . 119 22.1. Previous Authors' Addresses . . . . . . . . . . . . . . 120
Appendix A. Notes on Processing XML Elements . . . . . . . . . . 120 23. References . . . . . . . . . . . . . . . . . . . . . . . . . 121
A.1. Notes on Empty XML Elements . . . . . . . . . . . . . . 120 23.1. Normative References . . . . . . . . . . . . . . . . . . 121
A.2. Notes on Illegal XML Processing . . . . . . . . . . . . 120 23.2. Informational References . . . . . . . . . . . . . . . . 122
A.3. Example - XML Syntax Error . . . . . . . . . . . . . . . 120 Appendix A. Notes on Processing XML Elements . . . . . . . . . . 123
A.4. Example - Unknown XML Element . . . . . . . . . . . . . 121 A.1. Notes on Empty XML Elements . . . . . . . . . . . . . . 123
Appendix B. Notes on HTTP Client Compatibility . . . . . . . . . 122 A.2. Notes on Illegal XML Processing . . . . . . . . . . . . 123
Appendix C. The opaquelocktoken scheme and URIs . . . . . . . . 123 A.3. Example - XML Syntax Error . . . . . . . . . . . . . . . 123
Appendix D. Guidance for Clients Desiring to Authenticate . . . 124 A.4. Example - Unexpected XML Element . . . . . . . . . . . . 124
Appendix E. Summary of changes from RFC2518 . . . . . . . . . . 126 Appendix B. Notes on HTTP Client Compatibility . . . . . . . . . 125
E.1. Changes Notable to Server Implementors . . . . . . . . . 126 Appendix C. The opaquelocktoken scheme and URIs . . . . . . . . 126
E.2. Changes Notable to Client Implementors . . . . . . . . . 127 Appendix D. Guidance for Clients Desiring to Authenticate . . . 127
Appendix E. Summary of changes from RFC2518 . . . . . . . . . . 129
E.1. Changes for both Clients and Servers . . . . . . . . . . 129
E.2. Changes Notable to Server Implementors . . . . . . . . . 129
E.3. Changes Notable to Client Implementors . . . . . . . . . 130
Appendix F. Change Log (to be removed by RFC Editor before Appendix F. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 129 publication) . . . . . . . . . . . . . . . . . . . . 132
F.1. Changes from -05 to -06 . . . . . . . . . . . . . . . . 129 F.1. Changes from -05 to -06 . . . . . . . . . . . . . . . . 132
F.2. Changes in -07 . . . . . . . . . . . . . . . . . . . . . 129 F.2. Changes in -07 . . . . . . . . . . . . . . . . . . . . . 132
F.3. Changes in -08 . . . . . . . . . . . . . . . . . . . . . 130 F.3. Changes in -08 . . . . . . . . . . . . . . . . . . . . . 133
F.4. Changes in -09 . . . . . . . . . . . . . . . . . . . . . 131 F.4. Changes in -09 . . . . . . . . . . . . . . . . . . . . . 134
F.5. Changes in -10 . . . . . . . . . . . . . . . . . . . . . 132 F.5. Changes in -10 . . . . . . . . . . . . . . . . . . . . . 135
F.6. Changes in -11 . . . . . . . . . . . . . . . . . . . . . 132 F.6. Changes in -11 . . . . . . . . . . . . . . . . . . . . . 135
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 133 F.7. Changes in -11 . . . . . . . . . . . . . . . . . . . . . 135
Intellectual Property and Copyright Statements . . . . . . . . . 134 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 137
Intellectual Property and Copyright Statements . . . . . . . . . 138
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 7, line 43 skipping to change at page 7, line 43
This standard does not specify the versioning operations suggested by This standard does not specify the versioning operations suggested by
[RFC2291]. That work was done in a separate document, "Versioning [RFC2291]. That work was done in a separate document, "Versioning
Extensions to WebDAV" [RFC3253]. Extensions to WebDAV" [RFC3253].
The sections below provide a detailed introduction to various WebDAV The sections below provide a detailed introduction to various WebDAV
abstractions: resource properties (Section 4), collections of abstractions: resource properties (Section 4), collections of
resources (Section 5), locks (Section 6) in general and write locks resources (Section 5), locks (Section 6) in general and write locks
(Section 7) specifically. (Section 7) specifically.
These abstractions are manipulated by the WebDAV-specific HTTP These abstractions are manipulated by the WebDAV-specific HTTP
methods (Section 8) and the new HTTP headers (Section 9) used with methods (Section 9) and the new HTTP headers (Section 10) used with
WebDAV methods. WebDAV methods.
While the status codes provided by HTTP/1.1 are sufficient to While the status codes provided by HTTP/1.1 are sufficient to
describe most error conditions encountered by WebDAV methods, there describe most error conditions encountered by WebDAV methods, there
are some errors that do not fall neatly into the existing categories. are some errors that do not fall neatly into the existing categories.
This specification defines new status codes developed for WebDAV This specification defines new status codes developed for WebDAV
methods (Section 10) and describes existing HTTP status codes methods (Section 11) and describes existing HTTP status codes
(Section 11) as used in WebDAV. Since some WebDAV methods may (Section 12) 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 13)
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 16) 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 15)
and all other XML elements (Section 13) used in marshalling. WebDAV and all other XML elements (Section 14) used in marshalling. WebDAV
includes a few special rules on extending (Section 16) WebDAV XML includes a few special rules on extending (Section 17) WebDAV XML
marshalling in backwards-compatible ways. 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 18), on
internationalization support (Section 18), and on security internationalization support (Section 19), and on security
(Section 19). (Section 20).
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
is exactly the same as described in section 2.1 of [RFC2616], is exactly the same as described in section 2.1 of [RFC2616],
including the rules about implied linear white-space. Since this including the rules about implied linear white-space. Since this
augmented BNF uses the basic production rules provided in section 2.2 augmented BNF uses the basic production rules provided in section 2.2
of [RFC2616], these rules apply to this document as well. of [RFC2616], these rules apply to this document as well.
skipping to change at page 10, line 25 skipping to change at page 10, line 25
"http" scheme URI makes it possible to submit HTTP protocol requests "http" scheme URI makes it possible to submit HTTP protocol requests
to the resource using the URI. to the resource using the URI.
Collection - A resource that contains a set of URLs, which identify Collection - A resource that contains a set of URLs, which identify
and locate member resources and which meet the collections and locate member resources and which meet the collections
requirements (Section 5). requirements (Section 5).
Member URL - A URL which is a member of the set of URLs contained by Member URL - A URL which is a member of the set of URLs contained by
a collection. a collection.
Internal Member URL - A Member URL that is immediately relative to Path Segment - Informally, the characters found between slashes ("/")
the URL of the collection (the definition of immediately relative is in a URI. Formally, as defined in Section 3.3 of [RFC3986].
given later (Section 5.2)).
Internal Member URL - A member URL that is immediately relative to
the URL of the collection. That is, the internal member URL is equal
to a containing collection's URL plus an additional path segment for
non-collection resources, or additional segment plus trailing slash
"/" for collection resources.
Property - A name/value pair that contains descriptive information Property - A name/value pair that contains descriptive information
about a resource. about a resource.
Live Property - A property whose semantics and syntax are enforced by Live Property - A property whose semantics and syntax are enforced by
the server. For example, the live property DAV:getcontentlength has the server. For example, the live property DAV:getcontentlength has
its value, the length of the entity returned by a GET request, its value, the length of the entity returned by a GET request,
automatically calculated by the server. automatically calculated by the server.
Dead Property - A property whose semantics and syntax are not Dead Property - A property whose semantics and syntax are not
skipping to change at page 16, line 41 skipping to change at page 16, line 41
namespace be consistent -- a WebDAV-compatible resource may not have namespace be consistent -- a WebDAV-compatible resource may not have
a parent collection. However, certain WebDAV methods are prohibited a parent collection. However, certain WebDAV methods are prohibited
from producing results that cause namespace inconsistencies. from producing results that cause namespace inconsistencies.
Although implicit in [RFC2616] and [RFC3986], any resource, including Although implicit in [RFC2616] and [RFC3986], any resource, including
collection resources, MAY be identified by more than one URI. For collection resources, MAY be identified by more than one URI. For
example, a resource could be identified by multiple HTTP URLs. example, a resource could be identified by multiple HTTP URLs.
5.2. Collection Resources 5.2. Collection Resources
A collection is a resource whose state consists of at least a list of Collection resources differ from other resources in that they also
internal member URLs and a set of properties, but which may have act as containers. A collection is a resource whose state consists
additional state such as entity bodies returned by GET. An internal of at least a set of mappings between path segments and resources,
member URL MUST be immediately relative to a base URL of the and a set of properties on the collection itself. A collection MAY
collection. That is, the internal member URL is equal to a have additional state such as entity bodies returned by GET.
containing collection's URL plus an additional segment for non-
collection resources, or additional segment plus trailing slash "/"
for collection resources, where segment is defined in section 3.3 of
[RFC3986].
Any given internal member URL MUST only belong to the collection Any given internal member URL MUST only belong to the collection
once, i.e., it is illegal to have multiple instances of the same URL once, i.e., it is illegal to have multiple instances of the same URL
in a collection. Properties defined on collections behave exactly as in a collection. Properties defined on collections behave exactly as
do properties on non-collection resources. do properties on non-collection resources.
For all WebDAV compliant resources A and B, identified by URLs U and For all WebDAV compliant resources A and B, identified by URLs U and
V, for which U is immediately relative to V, B MUST be a collection V, for which U is immediately relative to V, B MUST be a collection
that has U as an internal member URL. So, if the resource with URL that has U as an internal member URL. So, if the resource with URL
http://example.com/bar/blah is WebDAV compliant and if the resource http://example.com/bar/blah is WebDAV compliant and if the resource
skipping to change at page 18, line 20 skipping to change at page 18, line 20
a resource while it is being edited. In this way, a client can a resource while it is being edited. In this way, a client can
prevent the "lost update" problem. prevent the "lost update" problem.
This specification allows locks to vary over two client-specified This specification allows locks to vary over two client-specified
parameters, the number of principals involved (exclusive vs. shared) parameters, the number of principals involved (exclusive vs. shared)
and the type of access to be granted. This document defines locking and the type of access to be granted. This document defines locking
for only one access type, write. However, the syntax is extensible, for only one access type, write. However, the syntax is extensible,
and permits the eventual specification of locking for other access and permits the eventual specification of locking for other access
types. types.
6.1. Exclusive Vs. Shared Locks 6.1. Lock Model
The most basic form of lock is an exclusive lock. Only one exclusive This section provides a concise model for how locking behaves. Later
lock may exist on any resource, whether it is directly or indirectly sections will provide more detail on some of the concepts and refer
locked (Section 7.6). Exclusive locks avoid having to merge results, back to these model statements. Normative statements related to LOCK
without requiring any coordination other than the methods described and UNLOCK handling can be found in the sections on those methods,
in this specification. whereas normative statements that cover any method are gathered here.
1. A lock either directly or indirectly locks a resource.
2. A resource becomes directly locked when a LOCK request to the URL
of that resource creates a new lock. The "lock-root" of the new
lock is that URL. If at the time of the request, the URL is not
mapped to a resource, a new empty resource is created and
directly locked.
3. An exclusive lock (Section 6.2) conflicts with any other kind of
lock on the same resource, whether either lock is direct or
indirect. A server MUST NOT create conflicting locks on a
resource.
4. For a collection that is locked with an infinite depth lock L,
all member resources are indirectly locked. Changes in
membership of a such a collection affect the set of indirectly
locked resources:
* If an internal member resource is added to the collection, and
if the new member resource does not already have a conflicting
lock, then the resource MUST become indirectly locked by L.
* If an internal member resource stops being a member of the
collection, then the resource MUST no longer be indirectly
locked by L.
5. Each lock is identified by a single unique lock token
(Section 6.5).
6. An UNLOCK request deletes the lock with the specified lock token,
provided that the request is addressed to a resource that is
either directly or indirectly locked by that lock. After a lock
is deleted, no resource is locked by that lock.
7. A lock token is "submitted" in a request when it appears in an If
header (the Write Lock (Section 7) section discusses when token
submission is required for write locks).
8. If a request causes the lock-root of any lock to become an
unmapped URL, then the lock MUST also be deleted by that request.
6.2. Exclusive Vs. Shared Locks
The most basic form of lock is an exclusive lock. Exclusive locks
avoid having to deal with content change conflicts, without requiring
any coordination other than the methods described in this
specification.
However, there are times when the goal of a lock is not to exclude However, there are times when the goal of a lock is not to exclude
others from exercising an access right but rather to provide a others from exercising an access right but rather to provide a
mechanism for principals to indicate that they intend to exercise mechanism for principals to indicate that they intend to exercise
their access rights. Shared locks are provided for this case. A their access rights. Shared locks are provided for this case. A
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.
With shared locks there are two trust sets that affect a resource. With shared locks there are two trust sets that affect a resource.
The first trust set is created by access permissions. Principals who The first trust set is created by access permissions. Principals who
skipping to change at page 19, line 20 skipping to change at page 20, line 18
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 creator 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 (Section 6.6) and
can be used to remove an offending lock, neither mechanism may be administrative action can be used to remove an offending lock,
available when needed; the timeout may be long or the administrator neither mechanism may be available when needed; the timeout may be
may not be available. long or the administrator may not be available.
6.2. Required Support A successful request for a new shared lock MUST result in the
generation of a unique lock token associated with the requesting
principal. Thus if five principals have taken out shared write locks
on the same resource there will be five locks and five lock tokens,
one for each principal.
6.3. 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.
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 Creator 6.4. Lock Creator
The creator of a lock has special privileges to use the locked 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 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- creator of the lock, both for shared and exclusive locks. For multi-
user shared lock cases, each authenticated principal MUST obtain its user shared lock cases, each authenticated principal MUST obtain its
own shared lock. own shared lock.
The server MAY allow privileged users other than the lock creator to The server MAY allow privileged users other than the lock creator to
destroy a lock (for example, the resource owner or an administrator) destroy a lock (for example, the resource owner or an administrator)
as a special case of lock usage. as a special case of lock usage.
If an anonymous user requests a lock, the server MAY refuse the If an anonymous user requests a lock, the server MAY refuse the
request. request.
6.4. Lock Tokens 6.5. 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
resource other than the one that returned it. resource other than the one that returned it.
When a LOCK operation creates a new lock, the new lock token is When a LOCK operation creates a new lock, the new lock token is
returned in the Lock-Token response header defined in Section 9.5, returned in the Lock-Token response header defined in Section 10.5,
and also in the body of the response. and also in the body of the response.
Submitting a lock token does not confer full privilege to use the Submitting a lock token does not confer full privilege to use the
lock token or modify the locked resource. Write access and other lock token or modify the locked resource. Write access and other
privileges MUST be enforced through normal privilege or privileges MUST be enforced through normal privilege or
authentication mechanisms, not based on the possible obscurity of authentication mechanisms, not based on the possible obscurity of
lock token values. lock token values.
Servers MAY make lock tokens publicly readable (e.g. in the DAV: Servers MAY make lock tokens publicly readable (e.g. in the DAV:
lockdiscovery property). One use case for making lock tokens lockdiscovery property). One use case for making lock tokens
skipping to change at page 20, line 49 skipping to change at page 22, line 5
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.5. Lock Capability Discovery 6.6. Lock Timeout
A lock MAY have a limited lifetime. The lifetime is suggested by the
client when creating or refreshing the lock, but the server
ultimately chooses the timeout value. Servers MUST remove locks
reasonably soon after the timeout expires if the lock is not
refreshed and given a new timeout.
Clients MUST assume that locks may arbitrarily disappear at any time,
regardless of the value given in the Timeout header. The Timeout
header only indicates the behavior of the server if extraordinary
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
way that it loses the record of the lock's existence.
6.7. 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.6. Active Lock Discovery 6.8. 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.7. Locks and Multiple Bindings 6.9. 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
lock type described in this specification. lock type described in this specification.
An exclusive write lock will prevent parallel changes to a resource An exclusive write lock will prevent parallel changes to a resource
by any principal other than the write lock holder. In general terms, by any principal other than the lock creator and in any case where
changes affected by write locks include changes to: the lock token is not submitted (e.g. by a client process other than
the one holding the lock).
o the content of the resource
o any dead property of the resource
o any live property defined to be lockable (all properties defined Clients MUST submit a lock-token they are authorized to use in any
in this specification are lockable) request which modifies a write-locked resource. The list of
modifications covered by a write-lock include:
o the direct membership of the resource, if it is a collection 1. A change to any of the following aspects of any write-locked
resource:
o the URL/location of a resource * any variant,
The next few sections describe in more specific terms how write locks * any dead property,
interact with various operations.
7.1. Methods Restricted by Write Locks * any live property which is lockable (a live property is
lockable unless otherwise defined.)
A server MUST reject any write request that alters a write-locked 2. For collections, any modification of an internal member URI. An
resource unless a valid lock token is provided. The write operations internal member URI of a collection is considered to be modified
defined in HTTP and WebDAV are PUT, POST, PROPPATCH, LOCK, UNLOCK, if it is added, removed, or identifies a different resource.
MOVE, COPY (for the destination resource), DELETE, and MKCOL. All More discussion on write locks and collections is found in
other HTTP/WebDAV methods, GET in particular, function independently Section 7.4.
of the lock. A shared write lock prevents the same operations
(except additional requests for shared write locks), however it also
allows access by any principal that has a shared write lock on the
same resource.
Note, however, that as new methods are created it will be necessary 3. A modification of the mapping of the root of the write lock,
to specify how they interact with a write lock. either to another resource or to no resource (e.g. DELETE).
7.2. Write Locks and Lock Tokens Of the methods defined in HTTP and WebDAV, PUT, POST, PROPPATCH,
LOCK, UNLOCK, MOVE, COPY (for the destination resource), DELETE, and
MKCOL are affected by write locks. All other HTTP/WebDAV methods
defined so far, GET in particular, function independently of a write
lock.
A successful request for an exclusive or shared write lock MUST The next few sections describe in more specific terms how write locks
result in the generation of a unique lock token associated with the interact with various operations.
requesting principal. Thus if five principals have a shared write
lock on the same resource there will be five lock tokens, one for
each principal.
7.3. Write Locks and Properties 7.1. 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.4. Avoiding Lost Updates 7.2. 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 24, line 10 skipping to change at page 25, line 5
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.5. Write Locks and Unmapped URLs 7.3. 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
skipping to change at page 25, line 27 skipping to change at page 26, line 19
o The server converts the lock-null resource into a collection if a o The server converts the lock-null resource into a collection if a
MKCOL request to the URL is successful (though interoperability MKCOL request to the URL is successful (though interoperability
experience showed that not all servers followed this requirement). experience showed that not all servers followed this requirement).
o Property values were defined for DAV:lockdiscovery and DAV: o Property values were defined for DAV:lockdiscovery and DAV:
supportedlock properties but not necessarily for other properties supportedlock properties but not necessarily for other properties
like DAV:getcontenttype. like DAV:getcontenttype.
In the "locked empty resource" model, which is now the recommended In the "locked empty resource" model, which is now the recommended
implementation, a resource created with a LOCK is empty but otherwise implementation, a resource created with a LOCK is empty but otherwise
behaves in every way as a normal resource. A locked empty resource: behaves in every way as a normal resource. It behaves as a same
resource that would result from a PUT request with an empty body (and
where a Content-Type and Content-Language was not specified),
followed by a LOCK request to the same resource. Following from this
model, a locked empty resource:
o Can be read, deleted, moved, copied, and in all ways behave as a o Can be read, deleted, moved, copied, and in all ways behave as a
regular resource, not a lock-null resource. regular resource, not a lock-null resource.
o Appears as a member of its parent collection. o Appears as a member of its parent collection.
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 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. o Can be updated (have content added) with a 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.
uses PUT to overwrite a locked empty resource the client MUST supply
a Content-Type if any is known.
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.6. Write Locks and Collections 7.4. 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 principals other than the lock member URLs of the collection by principals other than the lock
creator. 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
skipping to change at page 27, line 24 skipping to change at page 28, line 19
into an unlocked collection is thereafter unlocked. into an unlocked collection is thereafter unlocked.
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 new lock (see Section 6.1
MUST fail with a 423 (Locked) status code, and the response SHOULD point 3), the request MUST fail with a 423 (Locked) status code, and
contain the 'no-conflicting-lock' precondition. the response SHOULD contain the 'no-conflicting-lock' precondition.
If a lock creator 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.7. Write Locks and the If Request Header 7.5. 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 28, line 13 skipping to change at page 29, line 7
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.7.1. Example - Write Lock and COPY 7.5.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.example.com
Destination: http://www.ics.uci.edu/users/f/fielding/index.html Destination: http://www.example.com/users/f/fielding/index.html
If: <http://www.ics.uci.edu/users/f/fielding/index.html> If: <http://www.example.com/users/f/fielding/index.html>
(<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>) (<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>)
>>Response >>Response
HTTP/1.1 204 No Content HTTP/1.1 204 No Content
In this example, even though both the source and destination are In this example, even though both the source and destination are
locked, only one lock token must be submitted, for the lock on the locked, only one lock token must be submitted, for the lock on the
destination. This is because the source resource is not modified by destination. This is because the source resource is not modified by
a COPY, and hence unaffected by the write lock. In this example, a COPY, and hence unaffected by the write lock. In this example,
user agent authentication has previously occurred via a mechanism user agent authentication has previously occurred via a mechanism
outside the scope of the HTTP protocol, in the underlying transport outside the scope of the HTTP protocol, in the underlying transport
layer. layer.
7.7.2. Example - Deleting a member of a locked collection 7.5.2. Example - Deleting a member of a locked collection
Consider a collection "/locked" exclusively write-locked with Depth: Consider a collection "/locked" exclusively write-locked with Depth:
Infinity, and an attempt to delete an internal member "/locked/ Infinity, and an attempt to delete an internal member "/locked/
member": member":
>>Request >>Request
DELETE /locked/member HTTP/1.1 DELETE /locked/member HTTP/1.1
Host: example.com Host: example.com
>>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-submitted>
<D:href>/locked/</D:href> <D:href>/locked/</D:href>
</D:lock-token-present> </D:lock-token-submitted>
</D:error> </D:error>
Thus the client would need to submit the lock token with the request 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 to make it succeed. To do that, various forms of the If header (see
Section 9.4) could be used. Section 10.4) could be used.
"No-Tag-List" format: "No-Tag-List" format:
If: (<urn:uuid:150852e2-3847-42d5-8cbe-0f4f296f26cf>) If: (<urn:uuid:150852e2-3847-42d5-8cbe-0f4f296f26cf>)
"Tagged-List" format, for "http://example.com/locked/": "Tagged-List" format, for "http://example.com/locked/":
If: <http://example.com/locked/> If: <http://example.com/locked/>
(<urn:uuid:150852e2-3847-42d5-8cbe-0f4f296f26cf>) (<urn:uuid:150852e2-3847-42d5-8cbe-0f4f296f26cf>)
"Tagged-List" format, for "http://example.com/locked/member": "Tagged-List" format, for "http://example.com/locked/member":
If: <http://example.com/locked/member> If: <http://example.com/locked/member>
(<urn:uuid:150852e2-3847-42d5-8cbe-0f4f296f26cf>) (<urn:uuid:150852e2-3847-42d5-8cbe-0f4f296f26cf>)
Note that for the purpose of submitting the lock token the actual 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 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. in the If header, and that the If header itself evaluates to true.
7.8. Write Locks and COPY/MOVE 7.6. 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
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.7, an If header must be submitted containing a lock in Section 7.5, an If header must be submitted containing a lock
token for both the source and destination. token for both the source and destination.
7.9. Refreshing Write Locks 7.7. 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 5 skipping to change at page 32, line 5
different than the Timeout header returned when the lock was different than the Timeout header returned when the lock was
originally requested. Additionally clients may submit Timeout originally requested. Additionally clients may submit Timeout
headers of arbitrary value with their lock refresh requests. headers of arbitrary value with their lock refresh requests.
Servers, as always, may ignore Timeout headers submitted by the Servers, as always, may ignore Timeout headers submitted by the
client. Note that timeout is measured in seconds remaining until client. Note that timeout is measured in seconds remaining until
expiration. expiration.
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. General Request and Response Handling
8.1. General Request and Response Handling
8.1.1. Use of XML 8.1. Use of XML
In HTTP/1.1, method parameter information was exclusively encoded in In HTTP/1.1, method parameter information was exclusively encoded in
HTTP headers. Unlike HTTP/1.1, WebDAV encodes method parameter HTTP headers. Unlike HTTP/1.1, WebDAV encodes method parameter
information either in an [XML] request entity body, or in an HTTP information either in an [XML] request entity body, or in an HTTP
header. The use of XML to encode method parameters was motivated by header. The use of XML to encode method parameters was motivated by
the ability to add extra XML elements to existing structures, the ability to add extra XML elements to existing structures,
providing extensibility; and by XML's ability to encode information providing extensibility; and by XML's ability to encode information
in ISO 10646 character sets, providing internationalization support. in ISO 10646 character sets, providing internationalization support.
In addition to encoding method parameters, XML is used in WebDAV to In addition to encoding method parameters, XML is used in WebDAV to
skipping to change at page 31, line 36 skipping to change at page 32, line 34
All XML used in either requests or responses MUST be, at minimum, All XML used in either requests or responses MUST be, at minimum,
well formed and use namespaces correctly. If a server receives XML well formed and use namespaces correctly. If a server receives XML
that is not well-formed then the server MUST reject the entire 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 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 not well-formed in a response then the client MUST NOT assume
anything about the outcome of the executed method and SHOULD treat anything about the outcome of the executed method and SHOULD treat
the server as malfunctioning. 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 20). 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.2. URL Handling
URLs appear in many places in requests and responses.
Interoperability experience with [RFC2518] showed that many clients
parsing Multi-Status responses did not fully implement the full
Reference Resolution defined in Section 5 of [RFC3986]. Thus,
servers in particular need to be careful in handling URLs in
responses, to ensure that clients have enough context to be able to
interpret all the URLs. The rules in this section apply not only to
resource URLs in the 'href' element in Multi-Status responses, but
also to the Destination and If header resource URLs.
The sender has a choice between two approaches: using a relative
reference, which is resolved against the Request-URI, or a full URI.
A sender SHOULD generally be consistent once it has chosen one of
these approaches, but a server MUST ensure that every 'href' value
within a Multi-Status response uses the same format.
WebDAV only uses one form of relative reference in its extensions,
the absolute path.
Simple-ref = absolute-URI | ( path-absolute [ "?" query ] )
The absolute-URI and path-absolute productions are defined in section
4.3 and 4.1 of [RFC3986].
Within Simple-ref productions, senders MUST NOT:
o use dot-segments ("." or ".."), or
o have prefixes that do not match the Request-URI (using the
comparison rules defined in Section 3.2.3 of [RFC2616]).
Identifiers for collections SHOULD end in a '/' character.
8.2.1. Example - Correct URL Handling
Consider the collection http://example.com/sample/ with the internal
member URL http://example.com/sample/a%20test and the PROPFIND
request below:
>>Request:
PROPFIND /sample/ HTTP/1.1
Host: example.com
Depth: 1
In this case, the server should return two 'href' elements containing
either
o 'http://example.com/sample/' and
'http://example.com/sample/a%20test', or
o '/sample/' and '/sample/a%20test'
Note that even though the server may be storing the member resource
internally as 'a test', it has to be percent-encoded when used inside
a URI reference (see Section 2.1 of [RFC3986]). Also note that a
legal URI may still contain characters that need to be escaped within
XML character data, such as the ampersand character.
8.3. Required Bodies in Requests
Some of these new methods do not define bodies. Servers MUST examine Some of these new methods do not define bodies. Servers MUST examine
all requests for a body, even when a body was not expected. In cases all requests for a body, even when a body was not expected. In cases
where a request body is present but would be ignored by a server, the where a request body is present but would be ignored by a server, the
server MUST reject the request with 415 (Unsupported Media Type). server MUST reject the request with 415 (Unsupported Media Type).
This informs the client (which may have been attempting to use an This informs the client (which may have been attempting to use an
extension) that the body could not be processed as they intended. extension) that the body could not be processed as they intended.
8.1.3. HTTP Headers for use in WebDAV 8.4. HTTP Headers for use in WebDAV
HTTP defines many headers that can be used in WebDAV requests and HTTP defines many headers that can be used in WebDAV requests and
responses. Not all of these are appropriate in all situations and responses. Not all of these are appropriate in all situations and
some interactions may be undefined. Note that HTTP 1.1 requires the some interactions may be undefined. Note that HTTP 1.1 requires the
Date header in all responses if possible (see section 14.18, Date header in all responses if possible (see section 14.18,
[RFC2616]). [RFC2616]).
The server MUST do authorization checks before checking any HTTP The server MUST do authorization checks before checking any HTTP
conditional header. conditional header.
8.1.4. ETag 8.5. ETag
HTTP 1.1 recommends the use of the ETag header in responses to GET HTTP 1.1 recommends the use of the ETag header in responses to GET
and PUT requests. Correct use of ETags is even more important in a and PUT requests. Correct use of ETags is even more important in a
distributed authoring environment, because ETags are necessary along distributed authoring environment, because ETags are necessary along
with locks to avoid the lost-update problem. A client might fail to with locks to avoid the lost-update problem. A client might fail to
renew a lock, for example when the lock times out and the client is renew a lock, for example when the lock times out and the client is
accidentally offline or in the middle of a long upload. When a accidentally offline or in the middle of a long upload. When a
client fails to renew the lock, it's quite possible the resource can client fails to renew the lock, it's quite possible the resource can
still be relocked and the user can go on editing, as long as no still be relocked and the user can go on editing, as long as no
changes were made in the meantime. ETags are required for the client changes were made in the meantime. ETags are required for the client
to be able to distinguish this case. Otherwise, the client is forced to be able to distinguish this case. Otherwise, the client is forced
to ask the user whether to overwrite the resource on the server to ask the user whether to overwrite the resource on the server
without even being able to tell the user whether it has changed. without even being able to tell the user whether it has changed.
Timestamps do not solve this problem nearly as well as ETags. Timestamps do not solve this problem nearly as well as ETags.
WebDAV servers SHOULD support strong ETags for all resources that may Strong ETags are much more useful for authoring use cases than weak
be PUT. If ETags are supported for a resource, the server MUST ETags. Semantic equivalence can be a useful concept but that depends
return the ETag header in all PUT and GET responses to that resource. on the document type and the application type, and interoperability
might require some agreement or standard outside the scope of this
specification and HTTP. Note also that weak ETags have certain
restrictions in HTTP, e.g. these cannot be used in If-Match headers.
Note that the meaning of an ETag in a PUT response is not clearly
defined either in this document or in RFC2616 (i.e., whether the ETag
means that the resource is octet-for-octet equivalent to the body of
the PUT request, or whether the server could have made minor changes
in the formatting or content of the document upon storage). It is
hoped that future specification work will clarify this confusion.
Because clients may be forced to prompt users or throw away changed Because clients may be forced to prompt users or throw away changed
content if the ETag changes, a WebDAV server SHOULD NOT change the content if the ETag changes, a WebDAV server SHOULD NOT change the
ETag (or the Last-Modified time) for a resource that has an unchanged ETag (or the Last-Modified time) for a resource that has an unchanged
body and location. The ETag represents the state of the body or body and location. The ETag represents the state of the body or
contents of the resource. There is no similar way to tell if contents of the resource. There is no similar way to tell if
properties have changed. properties have changed.
8.1.5. Including error response bodies 8.6. Including error response bodies
HTTP and WebDAV did not use the bodies of most error responses for HTTP and WebDAV did not use the bodies of most error responses for
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 16
8.1.6. Impact of Namespace Operations on Cache Validators 8.7. Impact of Namespace Operations on Cache Validators
Note that the HTTP response headers "Etag" and "Last-Modified" (see Note that the HTTP response headers "Etag" and "Last-Modified" (see
[RFC2616], Sections 14.19 and 14.29) are defined per URL (not per [RFC2616], Sections 14.19 and 14.29) are defined per URL (not per
resource), and are used by clients for caching. Therefore servers resource), and are used by clients for caching. Therefore servers
must ensure that executing any operation that affects the URL must ensure that executing any operation that affects the URL
namespace (such as COPY, MOVE, DELETE, PUT or MKCOL) does preserve namespace (such as COPY, MOVE, DELETE, PUT or MKCOL) does preserve
their semantics, in particular: their semantics, in particular:
For any given URL, the "Last-Modified" value MUST increment every o For any given URL, the "Last-Modified" value MUST increment every
time the representation returned upon GET changes (within the time the representation returned upon GET changes (within the
limits of timestamp resolution). limits of timestamp resolution).
For any given URL, an "ETag" value MUST NOT be re-used for o For any given URL, an "ETag" value MUST NOT be re-used for
different representations returned by GET. different representations returned by GET.
In practice this means that servers In practice this means that servers
might have to increment "Last-Modified" timestamps for every o might have to increment "Last-Modified" timestamps for every
resource inside the destination namespace of a namespace operation resource inside the destination namespace of a namespace operation
unless it can do so more selectively, and unless it can do so more selectively, and
similarily, might have to re-assign "ETag" values for these o similarily, might have to re-assign "ETag" values for these
resources (unless the server allocates entity tags in a way so resources (unless the server allocates entity tags in a way so
that they are unique across the whole URL namespace managed by the that they are unique across the whole URL namespace managed by the
server). server).
Note that these considerations also apply to specific use cases, such 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 as using PUT to create a new resource at a URL that has been mapped
before, but has been deleted since then. before, but has been deleted since then.
Finally, WebDAV properties (such as DAV:getetag and DAV: Finally, WebDAV properties (such as DAV:getetag and DAV:
getlastmodified) that inherit their semantics from HTTP headers must getlastmodified) that inherit their semantics from HTTP headers must
behave accordingly. behave accordingly.
8.2. PROPFIND Method 9. HTTP Methods for Distributed Authoring
9.1. 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.19) along with all XML elements defined for use with that (Section 14.20) 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 "0" and "1" depth requests on WebDAV-compliant resources and support "0" and "1" depth requests on WebDAV-compliant resources and
SHOULD support "infinity" requests in the absence of serious SHOULD support "infinity" requests. In practice, support for depth
performance issues. By default, the PROPFIND method without a Depth infinity requests MAY be disabled, due to the performance and
header MUST act as if a "Depth: infinity" header was included. security concerns associated with this behavior. 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 property values for those properties defined in this o Request property values for those properties defined in this
skipping to change at page 34, line 34 skipping to change at page 37, line 52
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. For a live property defined
live properties from other specifications when responding to an elsewhere, that definition can specify whether that live property
'allprop' request, and MAY return only custom (dead) properties and would be returned in 'allprop' requests or not.
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
element which contains a 404 (Not Found) status value. element which contains a 404 (Not Found) status value.
Consequently, the 'multistatus' XML element for a collection resource Consequently, the 'multistatus' XML element for a collection resource
with member URLs MUST include a 'response' XML element for each with member URLs MUST include a 'response' XML element for each
member URL of the collection, to whatever depth was requested. Each member URL of the collection, to whatever depth was requested. Each
'response' XML element MUST contain an 'href' XML element that 'response' XML element MUST contain an 'href' XML element that
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. Note that a resource may have
only one value for a property of a given name, so the property may
only show up once in PROPFIND responses.
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.
Some PROPFIND results MAY be cached, with care as there is no cache Some PROPFIND results MAY be cached, with care as there is no cache
validation mechanism for most properties. This method is both safe validation mechanism for most properties. This method is both safe
and idempotent (see section 9.1 of [RFC2616]). and idempotent (see section 9.1 of [RFC2616]).
8.2.1. PROPFIND status codes 9.1.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 16) that might be particularly useful with
PROPFIND. PROPFIND.
403 Forbidden - A server MAY reject PROPFIND requests on collections 403 Forbidden - A server MAY reject PROPFIND requests on collections
with depth header of "Infinity", in which case it SHOULD use this with depth header of "Infinity", in which case it SHOULD use this
error with the precondition code 'propfind-finite-depth' inside the error with the precondition code 'propfind-finite-depth' inside the
error body. error body.
8.2.2. Status codes for use with 207 (Multi-Status) 9.1.2. Status codes for use with 207 (Multi-Status)
The following are examples of response codes one would expect to be The following are examples of response codes one would expect to be
used in a 207 (Multi-Status) response for this method. Note, used in a 207 (Multi-Status) response for this method. Note,
however, that unless explicitly prohibited any 2/3/4/5xx series however, that unless explicitly prohibited any 2/3/4/5xx series
response code may be used in a 207 (Multi-Status) response. response code may be used in a 207 (Multi-Status) response.
200 OK - 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.
404 Not Found - The property does not exist. 404 Not Found - The property does not exist.
8.2.3. Example - Retrieving Named Properties 9.1.3. Example - Retrieving Named Properties
>>Request >>Request
PROPFIND /file HTTP/1.1 PROPFIND /file HTTP/1.1
Host: www.example.com Host: www.example.com
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:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop xmlns:R="http://www.example.com/boxschema/"> <D:prop xmlns:R="http://ns.example.com/boxschema/">
<R:bigbox/> <R:bigbox/>
<R:author/> <R:author/>
<R:DingALing/> <R:DingALing/>
<R:Random/> <R:Random/>
</D:prop> </D:prop>
</D:propfind> </D:propfind>
>>Response >>Response
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
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:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response xmlns:R="http://www.example.com/boxschema/"> <D:response xmlns:R="http://ns.example.com/boxschema/">
<D:href>http://www.example.com/file</D:href> <D:href>http://www.example.com/file</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<R:bigbox> <R:bigbox>
<R:BoxType>Box type A</R:BoxType> <R:BoxType>Box type A</R:BoxType>
</R:bigbox> </R:bigbox>
<R:author> <R:author>
<R:Name>J.J. Johnson</R:Name> <R:Name>J.J. Johnson</R:Name>
</R:author> </R:author>
</D:prop> </D:prop>
skipping to change at page 38, line 5 skipping to change at page 41, line 5
</D:responsedescription> </D:responsedescription>
</D:multistatus> </D:multistatus>
In this example, PROPFIND is executed on a non-collection resource In this example, PROPFIND is executed on a non-collection resource
http://www.example.com/file. The propfind XML element specifies the http://www.example.com/file. The propfind XML element specifies the
name of four properties whose values are being requested. In this name of four properties whose values are being requested. In this
case only two properties were returned, since the principal issuing case only two properties were returned, since the principal issuing
the request did not have sufficient access rights to see the third the request did not have sufficient access rights to see the third
and fourth properties. and fourth properties.
8.2.4. Example - Retrieving Named and Dead Properties 9.1.4. Example - Retrieving Named and Dead Properties
>>Request >>Request
PROPFIND /mycol/ HTTP/1.1 PROPFIND /mycol/ HTTP/1.1
Host: www.example.com Host: www.example.com
Depth: 1 Depth: 1
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" ?>
skipping to change at page 38, line 29 skipping to change at page 41, line 29
<D:getlastmodified/> <D:getlastmodified/>
</D:prop> </D:prop>
<D:dead-props/> <D:dead-props/>
</D:propfind> </D:propfind>
In this example, PROPFIND is executed on a collection resource In this example, PROPFIND is executed on a collection resource
http://www.example.com/mycol/. The client requests the values of two http://www.example.com/mycol/. The client requests the values of two
specific live properties plus all dead properties (names and values). specific live properties plus all dead properties (names and values).
The response is not shown. The response is not shown.
8.2.5. Example - Using 'propname' to Retrieve all Property Names 9.1.5. Example - Using 'propname' to Retrieve all Property Names
>>Request >>Request
PROPFIND /container/ HTTP/1.1 PROPFIND /container/ HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: 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" ?>
<propfind xmlns="DAV:"> <propfind xmlns="DAV:">
skipping to change at page 39, line 15 skipping to change at page 42, line 15
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
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" ?>
<multistatus xmlns="DAV:"> <multistatus xmlns="DAV:">
<response> <response>
<href>http://www.example.com/container/</href> <href>http://www.example.com/container/</href>
<propstat> <propstat>
<prop xmlns:R="http://www.example.com/boxschema/"> <prop xmlns:R="http://ns.example.com/boxschema/">
<R:bigbox/> <R:bigbox/>
<R:author/> <R:author/>
<creationdate/> <creationdate/>
<displayname/> <displayname/>
<resourcetype/> <resourcetype/>
<supportedlock/> <supportedlock/>
</prop> </prop>
<status>HTTP/1.1 200 OK</status> <status>HTTP/1.1 200 OK</status>
</propstat> </propstat>
</response> </response>
<response> <response>
<href>http://www.example.com/container/front.html</href> <href>http://www.example.com/container/front.html</href>
<propstat> <propstat>
<prop xmlns:R="http://www.example.com/boxschema/"> <prop xmlns:R="http://ns.example.com/boxschema/">
<R:bigbox/> <R:bigbox/>
<creationdate/> <creationdate/>
<displayname/> <displayname/>
<getcontentlength/> <getcontentlength/>
<getcontenttype/> <getcontenttype/>
<getetag/> <getetag/>
<getlastmodified/> <getlastmodified/>
<resourcetype/> <resourcetype/>
<supportedlock/> <supportedlock/>
</prop> </prop>
skipping to change at page 40, line 7 skipping to change at page 43, line 7
In this example, PROPFIND is invoked on the collection resource In this example, PROPFIND is invoked on the collection resource
http://www.example.com/container/, with a propfind XML element http://www.example.com/container/, with a propfind XML element
containing the propname XML element, meaning the name of all containing the propname XML element, meaning the name of all
properties should be returned. Since no Depth header is present, it properties should be returned. Since no Depth header is present, it
assumes its default value of "infinity", meaning the name of the assumes its default value of "infinity", meaning the name of the
properties on the collection and all its descendents should be properties on the collection and all its descendents should be
returned. returned.
Consistent with the previous example, resource Consistent with the previous example, resource
http://www.example.com/container/ has six properties defined on it: http://www.example.com/container/ has six properties defined on it:
bigbox and author in the "http://www.example.com/boxschema/" bigbox and author in the "http://ns.example.com/boxschema/"
namespace, and creationdate, displayname, resourcetype, and namespace, and creationdate, displayname, resourcetype, and
supportedlock in the "DAV:" namespace. supportedlock in the "DAV:" namespace.
The resource http://www.example.com/container/index.html, a member of The resource http://www.example.com/container/index.html, a member of
the "container" collection, has nine properties defined on it, bigbox the "container" collection, has nine properties defined on it, bigbox
in the "http://www.example.com/boxschema/" namespace and, in the "http://ns.example.com/boxschema/" namespace and,
creationdate, displayname, getcontentlength, getcontenttype, getetag, creationdate, displayname, getcontentlength, getcontenttype, getetag,
getlastmodified, resourcetype, and supportedlock in the "DAV:" getlastmodified, resourcetype, and supportedlock in the "DAV:"
namespace. namespace.
This example also demonstrates the use of XML namespace scoping and This example also demonstrates the use of XML namespace scoping and
the default namespace. Since the "xmlns" attribute does not contain the default namespace. Since the "xmlns" attribute does not contain
a prefix, the namespace applies by default to all enclosed elements. a prefix, the namespace applies by default to all enclosed elements.
Hence, all elements which do not explicitly state the namespace to Hence, all elements which do not explicitly state the namespace to
which they belong are members of the "DAV:" namespace. which they belong are members of the "DAV:" namespace.
8.2.6. Example - Using 'allprop' 9.1.6. Example - Using 'allprop'
Note that 'allprop', despite its name which remains for backward- Note that 'allprop', despite its name which remains for backward-
compatibility, does not return every property, but only dead compatibility, does not return every property, but only dead
properties and the live properties defined in this specification. properties and the live properties defined in this specification.
>>Request >>Request
PROPFIND /container/ HTTP/1.1 PROPFIND /container/ HTTP/1.1
Host: www.example.com Host: www.example.com
Depth: 1 Depth: 1
skipping to change at page 41, line 6 skipping to change at page 44, line 6
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
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:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>/container/</D:href> <D:href>/container/</D:href>
<D:propstat> <D:propstat>
<D:prop xmlns:R="http://www.foo.bar/boxschema/"> <D:prop xmlns:R="http://ns.example.com/boxschema/">
<R:bigbox><R:BoxType>Box type A</R:BoxType></R:bigbox> <R:bigbox><R:BoxType>Box type A</R:BoxType></R:bigbox>
<R:author><R:Name>Hadrian</R:Name></R:author> <R:author><R:Name>Hadrian</R:Name></R:author>
<D:creationdate>1997-12-01T17:42:21-08:00</D:creationdate> <D:creationdate>1997-12-01T17:42:21-08:00</D:creationdate>
<D:displayname>Example collection</D:displayname> <D:displayname>Example collection</D:displayname>
<D:resourcetype><D:collection/></D:resourcetype> <D:resourcetype><D:collection/></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>
skipping to change at page 41, line 29 skipping to change at page 44, line 29
<D:locktype><D:write/></D:locktype> <D:locktype><D:write/></D:locktype>
</D:lockentry> </D:lockentry>
</D:supportedlock> </D:supportedlock>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
<D:response> <D:response>
<D:href>/container/front.html</D:href> <D:href>/container/front.html</D:href>
<D:propstat> <D:propstat>
<D:prop xmlns:R="http://www.foo.bar/boxschema/"> <D:prop xmlns:R="http://ns.example.com/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
>Mon, 12 Jan 1998 09:25:56 GMT</D:getlastmodified> >Mon, 12 Jan 1998 09:25:56 GMT</D:getlastmodified>
<D:resourcetype/> <D:resourcetype/>
skipping to change at page 42, line 9 skipping to change at page 45, line 9
<D:locktype><D:write/></D:locktype> <D:locktype><D:write/></D:locktype>
</D:lockentry> </D:lockentry>
</D:supportedlock> </D:supportedlock>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
In this example, PROPFIND was invoked on the resource In this example, PROPFIND was invoked on the resource
http://www.foo.bar/container/ with a Depth header of 1, meaning the http://www.example.com/container/ with a Depth header of 1, meaning
request applies to the resource and its children, and a propfind XML the request applies to the resource and its children, and a propfind
element containing the allprop XML element, meaning the request XML element containing the allprop XML element, meaning the request
should return the name and value of all the dead properties defined should return the name and value of all the dead properties defined
on the resources, plus the name and value of all the properties on the resources, plus the name and value of all the properties
defined in this specification. This example illustrates the use of defined in this specification. This example illustrates the use of
relative references in the 'href' elements of the response. relative references in the 'href' elements of the response.
The resource http://www.foo.bar/container/ has six properties defined The resource http://www.example.com/container/ has six properties
on it: 'bigbox' and 'author in the "http://www.foo.bar/boxschema/" defined on it: 'bigbox' and 'author in the
namespace, DAV:creationdate, DAV:displayname, DAV:resourcetype, and "http://ns.example.com/boxschema/" namespace, DAV:creationdate, DAV:
DAV:supportedlock. displayname, DAV:resourcetype, and DAV:supportedlock.
The last four properties are WebDAV-specific, defined in Section 14. The last four properties are WebDAV-specific, defined in Section 15.
Since GET is not supported on this resource, the get* properties Since GET is not supported on this resource, the get* properties
(e.g., DAV:getcontentlength) are not defined on this resource. The (e.g., DAV:getcontentlength) are not defined on this resource. The
WebDAV-specific properties assert that "container" was created on WebDAV-specific properties assert that "container" was created on
December 1, 1997, at 5:42:21PM, in a time zone 8 hours west of GMT December 1, 1997, at 5:42:21PM, in a time zone 8 hours west of GMT
(DAV:creationdate), has a name of "Example collection" (DAV: (DAV:creationdate), has a name of "Example collection" (DAV:
displayname), a collection resource type (DAV:resourcetype), and displayname), a collection resource type (DAV:resourcetype), and
supports exclusive write and shared write locks (DAV:supportedlock). supports exclusive write and shared write locks (DAV:supportedlock).
The resource http://www.foo.bar/container/front.html has nine The resource http://www.example.com/container/front.html has nine
properties defined on it: properties defined on it:
'bigbox' in the "http://www.foo.bar/boxschema/" namespace (another 'bigbox' in the "http://ns.example.com/boxschema/" namespace (another
instance of the "bigbox" property type), DAV:creationdate, DAV: instance of the "bigbox" property type), DAV:creationdate, DAV:
displayname, DAV:getcontentlength, DAV:getcontenttype, DAV:getetag, displayname, DAV:getcontentlength, DAV:getcontenttype, DAV:getetag,
DAV:getlastmodified, DAV:resourcetype, and DAV:supportedlock. DAV:getlastmodified, DAV:resourcetype, and DAV:supportedlock.
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 Method 9.2. 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
skipping to change at page 43, line 24 skipping to change at page 46, line 24
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. Clients SHOULD NOT alter the same propertyupdate XML element. Clients SHOULD NOT alter the same
property more than once in a single PROPPATCH request. property more than once in a single PROPPATCH request.
Servers MUST process PROPPATCH instructions in document order (an Servers MUST process PROPPATCH instructions in document order (an
exception to the normal rule that ordering is irrelevant). exception to the normal rule that ordering is irrelevant).
Instructions MUST either all be executed or none executed. Thus if Instructions MUST either all be executed or none executed. Thus if
any error occurs during processing all executed instructions MUST be any error occurs during processing all executed instructions MUST be
undone and a proper error result returned. Instruction processing undone and a proper error result returned. Instruction processing
details can be found in the definition of the set and remove details can be found in the definition of the set and remove
instructions in Section 13.22 and Section 13.25. instructions in Section 14.23 and Section 14.26.
This method is idempotent, but not safe (see section 9.1 of This method is idempotent, but not safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached. [RFC2616]). Responses to this method MUST NOT be cached.
8.3.1. Status Codes for use in 207 (Multi-Status) 9.2.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
response, due to the atomicity of PROPPATCH. response, due to the atomicity of PROPPATCH.
403 (Forbidden) - The client, for reasons the server chooses not to 403 (Forbidden) - The client, for reasons the server chooses not to
specify, cannot alter one of the properties. specify, cannot alter one of the properties.
403 (Forbidden): The client has attempted to set a read-only 403 (Forbidden): The client has attempted to set a read-only
property, such as DAV:getetag. If returning this error, the server property, such as DAV:getetag. If returning this error, the server
SHOULD use the precondition code 'writable-property' inside the SHOULD use the precondition code 'cannot-modify-protected-property'
response body. inside the response body.
409 (Conflict) - The client has provided a value whose semantics are 409 (Conflict) - The client has provided a value whose semantics are
not appropriate for the property. not appropriate for the property.
424 (Failed Dependency) - The property change could not be made 424 (Failed Dependency) - The property change could not be made
because of another property change that failed. because of another property change that failed.
507 (Insufficient Storage) - The server did not have sufficient space 507 (Insufficient Storage) - The server did not have sufficient space
to record the property. to record the property.
8.3.2. Example - PROPPATCH 9.2.2. Example - PROPPATCH
>>Request >>Request
PROPPATCH /bar.html HTTP/1.1 PROPPATCH /bar.html HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: 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:propertyupdate xmlns:D="DAV:" <D:propertyupdate xmlns:D="DAV:"
xmlns:Z="http://www.w3.com/standards/z39.50/"> xmlns:Z="http://ns.example.com/standards/z39.50/">
<D:set> <D:set>
<D:prop> <D:prop>
<Z:authors> <Z:Authors>
<Z:Author>Jim Whitehead</Z:Author> <Z:Author>Jim Whitehead</Z:Author>
<Z:Author>Roy Fielding</Z:Author> <Z:Author>Roy Fielding</Z:Author>
</Z:authors> </Z:Authors>
</D:prop> </D:prop>
</D:set> </D:set>
<D:remove> <D:remove>
<D:prop><Z:Copyright-Owner/></D:prop> <D:prop><Z:Copyright-Owner/></D:prop>
</D:remove> </D:remove>
</D:propertyupdate> </D:propertyupdate>
>>Response >>Response
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
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:multistatus xmlns:D="DAV:" <D:multistatus xmlns:D="DAV:"
xmlns:Z="http://www.w3.com/standards/z39.50"> xmlns:Z="http://ns.example.com/standards/z39.50/">
<D:response> <D:response>
<D:href>http://www.example.com/bar.html</D:href> <D:href>http://www.example.com/bar.html</D:href>
<D:propstat> <D:propstat>
<D:prop><Z:Authors/></D:prop> <D:prop><Z:Authors/></D:prop>
<D:status>HTTP/1.1 424 Failed Dependency</D:status> <D:status>HTTP/1.1 424 Failed Dependency</D:status>
</D:propstat> </D:propstat>
<D:propstat> <D:propstat>
<D:prop><Z:Copyright-Owner/></D:prop> <D:prop><Z:Copyright-Owner/></D:prop>
<D:status>HTTP/1.1 409 Conflict</D:status> <D:status>HTTP/1.1 409 Conflict</D:status>
</D:propstat> </D:propstat>
<D:responsedescription> Copyright Owner can not be deleted or <D:responsedescription> Copyright Owner can not be deleted or
altered.</D:responsedescription> altered.</D:responsedescription>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
In this example, the client requests the server to set the value of In this example, the client requests the server to set the value of
the "Authors" property in the "http://www.w3.com/standards/z39.50/" the "Authors" property in the
namespace, and to remove the property "Copyright-Owner" in the "http://ns.example.com/standards/z39.50/" namespace, and to remove
"http://www.w3.com/standards/z39.50/" namespace. Since the the property "Copyright-Owner" in the same namespace. Since the
Copyright-Owner property could not be removed, no property Copyright-Owner property could not be removed, no property
modifications occur. The 424 (Failed Dependency) status code for the modifications occur. The 424 (Failed Dependency) status code for the
Authors property indicates this action would have succeeded if it Authors property indicates this action would have succeeded if it
were not for the conflict with removing the Copyright-Owner property. were not for the conflict with removing the Copyright-Owner property.
8.4. MKCOL Method 9.3. MKCOL Method
The MKCOL method is used to create a new collection. All WebDAV The MKCOL method is used to create a new collection. All WebDAV
compliant resources MUST support the MKCOL method. compliant resources MUST support the MKCOL method.
MKCOL creates a new collection resource at the location specified by MKCOL creates a new collection resource at the location specified by
the Request-URI. If the Request-URI is already mapped to a resource the Request-URI. If the Request-URI is already mapped to a resource
then the MKCOL MUST fail. During MKCOL processing, a server MUST then the MKCOL MUST fail. During MKCOL processing, a server MUST
make the Request-URI a member of its parent collection, unless the make the Request-URI a member of its parent collection, unless the
Request-URI is "/". If no such ancestor exists, the method MUST Request-URI is "/". If no such ancestor exists, the method MUST
fail. When the MKCOL operation creates a new collection resource, fail. When the MKCOL operation creates a new collection resource,
skipping to change at page 46, line 21 skipping to change at page 49, line 21
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 This method is idempotent, but not safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached. [RFC2616]). Responses to this method MUST NOT be cached.
8.4.1. MKCOL Status Codes 9.3.1. MKCOL 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 MKCOL: 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.
skipping to change at page 46, line 48 skipping to change at page 49, line 48
MUST NOT create those intermediate collections automatically. MUST NOT create those intermediate collections automatically.
415 (Unsupported Media Type) - The server does not support the 415 (Unsupported Media Type) - The server does not support the
request body type (since this specification does not define any body request body type (since this specification does not define any body
for MKCOL requests). for MKCOL requests).
507 (Insufficient Storage) - The resource does not have sufficient 507 (Insufficient Storage) - The resource does not have sufficient
space to record the state of the resource after the execution of this space to record the state of the resource after the execution of this
method. method.
8.4.2. Example - MKCOL 9.3.2. Example - MKCOL
This example creates a collection called /webdisc/xfiles/ on the This example creates a collection called /webdisc/xfiles/ on the
server www.example.com. server www.example.com.
>>Request >>Request
MKCOL /webdisc/xfiles/ HTTP/1.1 MKCOL /webdisc/xfiles/ HTTP/1.1
Host: www.example.com Host: www.example.com
>>Response >>Response
HTTP/1.1 201 Created HTTP/1.1 201 Created
8.5. GET, HEAD for Collections 9.4. GET, HEAD for Collections
The semantics of GET are unchanged when applied to a collection, The semantics of GET are unchanged when applied to a collection,
since GET is defined as, "retrieve whatever information (in the form since GET is defined as, "retrieve whatever information (in the form
of an entity) is identified by the Request-URI" [RFC2616]. GET when of an entity) is identified by the Request-URI" [RFC2616]. GET when
applied to a collection may return the contents of an "index.html" applied to a collection may return the contents of an "index.html"
resource, a human-readable view of the contents of the collection, or resource, a human-readable view of the contents of the collection, or
something else altogether. Hence it is possible that the result of a something else altogether. Hence it is possible that the result of a
GET on a collection will bear no correlation to the membership of the GET on a collection will bear no correlation to the membership of the
collection. collection.
Similarly, since the definition of HEAD is a GET without a response Similarly, since the definition of HEAD is a GET without a response
message body, the semantics of HEAD are unmodified when applied to message body, the semantics of HEAD are unmodified when applied to
collection resources. collection resources.
8.6. POST for Collections 9.5. 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 Requirements 9.6. 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.
Thus, after a successful DELETE operation (and in the absence of Thus, after a successful DELETE operation (and in the absence of
other actions) a subsequent GET/HEAD/PROPFIND request to the target other actions) a subsequent GET/HEAD/PROPFIND request to the target
Request-URI MUST return 404 (Not Found). Request-URI MUST return 404 (Not Found).
8.7.1. DELETE for Collections 9.6.1. DELETE for Collections
The DELETE method on a collection MUST act as if a "Depth: infinity" The DELETE method on a collection MUST act as if a "Depth: infinity"
header was used on it. A client MUST NOT submit a Depth header with header was used on it. A client MUST NOT submit a Depth header with
a DELETE on a collection with any value but infinity. a DELETE on a collection with any value but infinity.
DELETE instructs that the collection specified in the Request-URI and DELETE instructs that the collection specified in the Request-URI and
all resources identified by its internal member URLs are to be all resources identified by its internal member URLs are to be
deleted. deleted.
If any resource identified by a member URL cannot be deleted then all If any resource identified by a member URL cannot be deleted then all
skipping to change at page 48, line 44 skipping to change at page 51, line 44
the request failed completely. the request failed completely.
424 (Failed Dependency) status codes SHOULD NOT be in the 207 (Multi- 424 (Failed Dependency) status codes SHOULD NOT be in the 207 (Multi-
Status) response for DELETE. They can be safely left out because the Status) response for DELETE. They can be safely left out because the
client will know that the ancestors of a resource could not be client will know that the ancestors of a resource could not be
deleted when the client receives an error for the ancestor's progeny. deleted when the client receives an error for the ancestor's progeny.
Additionally 204 (No Content) errors SHOULD NOT be returned in the Additionally 204 (No Content) errors SHOULD NOT be returned in the
207 (Multi-Status). The reason for this prohibition is that 204 (No 207 (Multi-Status). The reason for this prohibition is that 204 (No
Content) is the default success code. Content) is the default success code.
8.7.2. Example - DELETE 9.6.2. Example - DELETE
>>Request >>Request
DELETE /container/ HTTP/1.1 DELETE /container/ HTTP/1.1
Host: www.example.com Host: www.example.com
>>Response >>Response
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
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:multistatus xmlns:d="DAV:"> <d:multistatus xmlns:d="DAV:">
<d:response> <d:response>
<d:href>http://www.example.com/container/resource3</d:href> <d:href>http://www.example.com/container/resource3</d:href>
<d:status>HTTP/1.1 423 Locked</d:status> <d:status>HTTP/1.1 423 Locked</d:status>
<d:error><d:lock-token-submitted/></d:error>
</d:response> </d:response>
</d:multistatus> </d:multistatus>
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 Requirements 9.7. PUT Requirements
8.8.1. PUT for Non-Collection Resources 9.7.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 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 what Content-Type a resource should have, and whether it should
change if the resource is overwritten. Thus, a client MUST provide a 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 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 use the Content-Type header value on any PUT request as the
resource's type (unless security concerns or policy dictates resource's type (unless security concerns or policy dictates
otherwise). otherwise). If the client does not provide a Content-Type for a new
resource, the server MAY create a resource with no Content-Type
assigned, or it MAY attempt to assign a reasonable and legal Content-
Type.
Note that although a recipient should treat metadata supplied with an Note that although a recipient should treat metadata supplied with an
HTTP request as authorative, in practice there's no guarantee that a HTTP request as authorative, in practice there's no guarantee that a
server will accept Content- headers. Many servers do not allow server will accept Content- headers. Many servers do not allow
configuring the Content-Type on a per-resource basis in the first configuring the Content-Type on a per-resource basis in the first
place. Thus, clients should not rely on the ability to directly place. Thus, clients should not rely on the ability to directly
influence the content type by including a Content-Type request influence the content type by including a Content-Type request
header. header.
8.8.2. PUT for Collections 9.7.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 Method 9.8. 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 This method is idempotent, but not safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached. [RFC2616]). Responses to this method MUST NOT be cached.
8.9.1. COPY for Non-collection Resources 9.8.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
to the destination resource will not modify the source resource. to the destination resource will not modify the source resource.
Subsequent alterations to the source resource will not modify the Subsequent alterations to the source resource will not modify the
destination resource. destination resource.
8.9.2. COPY for Properties 9.8.2. COPY for Properties
After a successful COPY invocation, all dead properties on the source After a successful COPY invocation, all dead properties on the source
resource MUST be duplicated on the destination resource, along with resource MUST be duplicated on the destination resource, along with
all properties as appropriate. Live properties described in this all properties as appropriate. Live properties described in this
document SHOULD be duplicated as identically behaving live properties document SHOULD be duplicated as identically behaving live properties
at the destination resource, but not necessarily with the same at the destination resource, but not necessarily with the same
values. Servers SHOULD NOT convert live properties into dead values. Servers SHOULD NOT convert live properties into dead
properties on the destination resource, because clients may then draw properties on the destination resource, because clients may then draw
incorrect conclusions about the state or functionality of a resource. incorrect conclusions about the state or functionality of a resource.
Note that some live properties are defined such that the absence of Note that some live properties are defined such that the absence of
the property has a specific meaning (e.g. a flag with one meaning if the property has a specific meaning (e.g. a flag with one meaning if
present and the opposite if absent), and in these cases, a successful present and the opposite if absent), and in these cases, a successful
COPY might result in the property being reported as "Not Found" in COPY might result in the property being reported as "Not Found" in
subsequent requests. subsequent requests.
A COPY operation creates a new resource, much like a PUT operation A COPY operation creates a new resource, much like a PUT operation
does. Live properties which are related to resource creation (such does. Live properties which are related to resource creation (such
as DAV:creationdate) should have their values set accordingly. as DAV:creationdate) should have their values set accordingly.
8.9.3. COPY for Collections 9.8.3. COPY for Collections
The COPY method on a collection without a Depth header MUST act as if The COPY method on a collection without a Depth header MUST act as if
a Depth header with value "infinity" was included. A client may a Depth header with value "infinity" was included. A client may
submit a Depth header on a COPY on a collection with a value of "0" submit a Depth header on a COPY on a collection with a value of "0"
or "infinity". Servers MUST support the "0" and "infinity" Depth or "infinity". Servers MUST support the "0" and "infinity" Depth
header behaviors on WebDAV-compliant resources. header behaviors on WebDAV-compliant resources.
A COPY of depth infinity instructs that the collection resource A COPY of depth infinity instructs that the collection resource
identified by the Request-URI is to be copied to the location identified by the Request-URI is to be copied to the location
identified by the URI in the Destination header, and all its internal identified by the URI in the Destination header, and all its internal
skipping to change at page 52, line 40 skipping to change at page 55, line 42
The 424 (Failed Dependency) status code SHOULD NOT be returned in the The 424 (Failed Dependency) status code SHOULD NOT be returned in the
207 (Multi-Status) response from a COPY method. These responses can 207 (Multi-Status) response from a COPY method. These responses can
be safely omitted because the client will know that the progeny of a be safely omitted because the client will know that the progeny of a
resource could not be copied when the client receives an error for resource could not be copied when the client receives an error for
the parent. Additionally 201 (Created)/204 (No Content) status codes the parent. Additionally 201 (Created)/204 (No Content) status codes
SHOULD NOT be returned as values in 207 (Multi-Status) responses from SHOULD NOT be returned as values in 207 (Multi-Status) responses from
COPY methods. They, too, can be safely omitted because they are the COPY methods. They, too, can be safely omitted because they are the
default success codes. default success codes.
8.9.4. COPY and Overwriting Destination Resources 9.8.4. COPY and Overwriting Destination Resources
If a COPY request has an Overwrite header with a value of "F", and a If a COPY request has an Overwrite header with a value of "F", and a
resource exists at the Destination URL, the server MUST fail the resource exists at the Destination URL, the server MUST fail the
request. request.
When a server executes a COPY request and overwrites a destination When a server executes a COPY request and overwrites a destination
resource, the exact behavior MAY depend on many factors, including resource, the exact behavior MAY depend on many factors, including
WebDAV extension capabilities (see particularly [RFC3253]). For WebDAV extension capabilities (see particularly [RFC3253]). For
example, when an ordinary resource is overwritten, the server could example, when an ordinary resource is overwritten, the server could
delete the target resource before doing the copy, or could do an in- delete the target resource before doing the copy, or could do an in-
skipping to change at page 53, line 16 skipping to change at page 56, line 18
collection after the successful COPY request MUST be the same collection after the successful COPY request MUST be the same
membership as the source collection immediately before the COPY. membership as the source collection immediately before the COPY.
Thus, merging the membership of the source and destination Thus, merging the membership of the source and destination
collections together in the destination is not a compliant behavior. collections together in the destination is not a compliant behavior.
In general, if clients require the state of the destination URL to be In general, if clients require the state of the destination URL to be
wiped out prior to a COPY (e.g. to force live properties to be wiped out prior to a COPY (e.g. to force live properties to be
reset), then the client could send a DELETE to the destination before reset), then the client could send a DELETE to the destination before
the COPY request to ensure this reset. the COPY request to ensure this reset.
8.9.5. Status Codes 9.8.5. 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 COPY: status codes have specific applicability to COPY:
201 (Created) - The source resource was successfully copied. The 201 (Created) - The source resource was successfully copied. The
COPY operation resulted in the creation of a new resource. COPY operation resulted in the creation of a new resource.
204 (No Content) - The source resource was successfully copied to a 204 (No Content) - The source resource was successfully copied to a
pre-existing destination resource. pre-existing destination resource.
skipping to change at page 53, line 49 skipping to change at page 56, line 51
409 (Conflict) - A resource cannot be created at the destination 409 (Conflict) - A resource cannot be created at the destination
until one or more intermediate collections have been created. The until one or more intermediate collections have been created. The
server MUST NOT create those intermediate collections automatically. server MUST NOT create those intermediate collections automatically.
412 (Precondition Failed) - A precondition header check failed, e.g. 412 (Precondition Failed) - A precondition header check failed, e.g.
the Overwrite header is "F" and the destination URL is already mapped the Overwrite header is "F" and the destination URL is already mapped
to a resource. to a resource.
423 (Locked) - The destination resource, or resource within the 423 (Locked) - The destination resource, or resource within the
destination collection, was locked. This response SHOULD contain the destination collection, was locked. This response SHOULD contain the
'lock-token-present' precondition element. 'lock-token-submitted' precondition element.
502 (Bad Gateway) - This may occur when the destination is on another 502 (Bad Gateway) - This may occur when the destination is on another
server, repository or URL namespace. Either the source namespace server, repository or URL namespace. Either the source namespace
does not support copying to the destination namespace, or the does not support copying to the destination namespace, or the
destination namespace refuses to accept the resource. The client may destination namespace refuses to accept the resource. The client may
wish to try GET/PUT and PROPFIND/PROPPATCH instead. wish to try GET/PUT and PROPFIND/PROPPATCH instead.
507 (Insufficient Storage) - The destination resource does not have 507 (Insufficient Storage) - The destination resource does not have
sufficient space to record the state of the resource after the sufficient space to record the state of the resource after the
execution of this method. execution of this method.
8.9.6. Example - COPY with Overwrite 9.8.6. Example - COPY with Overwrite
This example shows resource This example shows resource
http://www.ics.uci.edu/~fielding/index.html being copied to the http://www.example.com/~fielding/index.html being copied to the
location http://www.ics.uci.edu/users/f/fielding/index.html. The 204 location http://www.example.com/users/f/fielding/index.html. The 204
(No Content) status code indicates the existing resource at the (No Content) status code indicates the existing resource at the
destination was overwritten. destination was overwritten.
>>Request >>Request
COPY /~fielding/index.html HTTP/1.1 COPY /~fielding/index.html HTTP/1.1
Host: www.ics.uci.edu Host: www.example.com
Destination: http://www.ics.uci.edu/users/f/fielding/index.html Destination: http://www.example.com/users/f/fielding/index.html
>>Response >>Response
HTTP/1.1 204 No Content HTTP/1.1 204 No Content
8.9.7. Example - COPY with No Overwrite 9.8.7. Example - COPY with No Overwrite
The following example shows the same copy operation being performed, The following example shows the same copy operation being performed,
but with the Overwrite header set to "F." A response of 412 but with the Overwrite header set to "F." A response of 412
(Precondition Failed) is returned because the destination URL is (Precondition Failed) is returned because the destination URL is
already mapped to a resource. already mapped to a resource.
>>Request >>Request
COPY /~fielding/index.html HTTP/1.1 COPY /~fielding/index.html HTTP/1.1
Host: www.ics.uci.edu Host: www.example.com
Destination: http://www.ics.uci.edu/users/f/fielding/index.html Destination: http://www.example.com/users/f/fielding/index.html
Overwrite: F Overwrite: F
>>Response >>Response
HTTP/1.1 412 Precondition Failed HTTP/1.1 412 Precondition Failed
8.9.8. Example - COPY of a Collection 9.8.8. Example - COPY of a Collection
>>Request >>Request
COPY /container/ HTTP/1.1 COPY /container/ HTTP/1.1
Host: www.example.com Host: www.example.com
Destination: http://www.example.com/othercontainer/ Destination: http://www.example.com/othercontainer/
Depth: infinity Depth: infinity
>>Response >>Response
skipping to change at page 55, line 38 skipping to change at page 58, 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 Method 9.9. 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 56, line 17 skipping to change at page 59, line 17
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 This method is idempotent, but not safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached. [RFC2616]). Responses to this method MUST NOT be cached.
8.10.1. MOVE for Properties 9.9.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
not work the same way at the destination, the server MAY fail the not work the same way at the destination, the server MAY fail the
request. request.
MOVE is frequently used by clients to rename a file without changing MOVE is frequently used by clients to rename a file without changing
its parent collection, so it's not appropriate to reset all live its parent collection, so it's not appropriate to reset all live
properties which are set at resource creation. For example, the DAV: properties which are set at resource creation. For example, the DAV:
creationdate property value SHOULD remain the same after a MOVE. creationdate property value SHOULD remain the same after a MOVE.
Dead properties MUST be moved along with the resource. Dead properties MUST be moved along with the resource.
8.10.2. MOVE for Collections 9.9.2. MOVE for Collections
A MOVE with "Depth: infinity" instructs that the collection A MOVE with "Depth: infinity" instructs that the collection
identified by the Request-URI be moved to the address specified in identified by the Request-URI be moved to the address specified in
the Destination header, and all resources identified by its internal the Destination header, and all resources identified by its internal
member URLs are to be moved to locations relative to it, recursively member URLs are to be moved to locations relative to it, recursively
through all levels of the collection hierarchy. through all levels of the collection hierarchy.
The MOVE method on a collection MUST act as if a "Depth: infinity" The MOVE method on a collection MUST act as if a "Depth: infinity"
header was used on it. A client MUST NOT submit a Depth header on a header was used on it. A client MUST NOT submit a Depth header on a
MOVE on a collection with any value but "infinity". MOVE on a collection with any value but "infinity".
skipping to change at page 57, line 36 skipping to change at page 60, line 36
The 424 (Failed Dependency) status code SHOULD NOT be returned in the The 424 (Failed Dependency) status code SHOULD NOT be returned in the
207 (Multi-Status) response from a MOVE method. These errors can be 207 (Multi-Status) response from a MOVE method. These errors can be
safely omitted because the client will know that the progeny of a safely omitted because the client will know that the progeny of a
resource could not be moved when the client receives an error for the resource could not be moved when the client receives an error for the
parent. Additionally 201 (Created)/204 (No Content) responses SHOULD parent. Additionally 201 (Created)/204 (No Content) responses SHOULD
NOT be returned as values in 207 (Multi-Status) responses from a NOT be returned as values in 207 (Multi-Status) responses from a
MOVE. These responses can be safely omitted because they are the MOVE. These responses can be safely omitted because they are the
default success codes. default success codes.
8.10.3. MOVE and the Overwrite Header 9.9.3. MOVE and the Overwrite Header
If a resource exists at the destination and the Overwrite header is If a resource exists at the destination and the Overwrite header is
"T" then prior to performing the move the server MUST perform a "T" then prior to performing the move the server MUST perform a
DELETE with "Depth: infinity" on the destination resource. If the DELETE with "Depth: infinity" on the destination resource. If the
Overwrite header is set to "F" then the operation will fail. Overwrite header is set to "F" then the operation will fail.
8.10.4. Status Codes 9.9.4. 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 MOVE: status codes have specific applicability to MOVE:
201 (Created) - The source resource was successfully moved, and a new 201 (Created) - The source resource was successfully moved, and a new
URL mapping was created at the destination. URL mapping was created at the destination.
204 (No Content) - The source resource was successfully moved to a 204 (No Content) - The source resource was successfully moved to a
URL that was already mapped. URL that was already mapped.
skipping to change at page 58, line 31 skipping to change at page 61, line 31
properties and still move the resource to the destination (see properties and still move the resource to the destination (see
'preserved-live-properties' postcondition). 'preserved-live-properties' postcondition).
412 (Precondition Failed) - A condition header failed. Specific to 412 (Precondition Failed) - A condition header failed. Specific to
MOVE, this could mean that the Overwrite header is "F" and the state MOVE, this could mean that the Overwrite header is "F" and the state
of the destination URL is already mapped to a resource. of the destination URL is already mapped to a resource.
423 (Locked) - The source or the destination resource, the source or 423 (Locked) - The source or the destination resource, the source or
destination resource parent, or some resource within the source or destination resource parent, or some resource within the source or
destination collection, was locked. This response SHOULD contain the destination collection, was locked. This response SHOULD contain the
'lock-token-present' precondition element. 'lock-token-submitted' precondition element.
502 (Bad Gateway) - This may occur when the destination is on another 502 (Bad Gateway) - This may occur when the destination is on another
server and the destination server refuses to accept the resource. server and the destination server refuses to accept the resource.
This could also occur when the destination is on another sub-section This could also occur when the destination is on another sub-section
of the same server namespace. of the same server namespace.
8.10.5. Example - MOVE of a Non-Collection 9.9.5. Example - MOVE of a Non-Collection
This example shows resource This example shows resource
http://www.ics.uci.edu/~fielding/index.html being moved to the http://www.example.com/~fielding/index.html being moved to the
location http://www.ics.uci.edu/users/f/fielding/index.html. The location http://www.example.com/users/f/fielding/index.html. The
contents of the destination resource would have been overwritten if contents of the destination resource would have been overwritten if
the destination URL was already mapped to a resource. In this case, the destination URL was already mapped to a resource. In this case,
since there was nothing at the destination resource, the response since there was nothing at the destination resource, the response
code is 201 (Created). code is 201 (Created).
>>Request >>Request
MOVE /~fielding/index.html HTTP/1.1 MOVE /~fielding/index.html HTTP/1.1
Host: www.ics.uci.edu Host: www.example.com
Destination: http://www.ics.uci.edu/users/f/fielding/index.html Destination: http://www.example/users/f/fielding/index.html
>>Response >>Response
HTTP/1.1 201 Created HTTP/1.1 201 Created
Location: http://www.ics.uci.edu/users/f/fielding/index.html Location: http://www.example.com/users/f/fielding/index.html
8.10.6. Example - MOVE of a Collection 9.9.6. Example - MOVE of a Collection
>>Request >>Request
MOVE /container/ HTTP/1.1 MOVE /container/ HTTP/1.1
Host: www.example.com Host: www.example.com
Destination: http://www.example.com/othercontainer/ Destination: http://www.example.com/othercontainer/
Overwrite: F Overwrite: F
If: (<urn:uuid:fe184f2e-6eec-41d0-c765-01adc56e6bb4>) If: (<urn:uuid:fe184f2e-6eec-41d0-c765-01adc56e6bb4>)
(<urn:uuid:e454f3f3-acdc-452a-56c7-00a5c91e4b77>) (<urn:uuid:e454f3f3-acdc-452a-56c7-00a5c91e4b77>)
skipping to change at page 59, line 47 skipping to change at page 62, line 47
method, that is locked. In this case the proper lock token was not method, that is locked. In this case the proper lock token was not
submitted for the destination submitted for the destination
http://www.example.com/othercontainer/C2/. This means that the http://www.example.com/othercontainer/C2/. This means that the
resource /container/C2/ could not be moved. Because there was an resource /container/C2/ could not be moved. Because there was an
error moving /container/C2/, none of /container/C2's members were error moving /container/C2/, none of /container/C2's members were
moved. However no errors were listed for those members due to the moved. However no errors were listed for those members due to the
error minimization rules. User agent authentication has previously error minimization rules. User agent authentication has previously
occurred via a mechanism outside the scope of the HTTP protocol, in occurred via a mechanism outside the scope of the HTTP protocol, in
an underlying transport layer. an underlying transport layer.
8.11. LOCK Method 9.10. LOCK Method
The following sections describe the LOCK method, which is used to The following sections describe the LOCK method, which is used to
take out a lock of any access type and to refresh an existing lock. take out a lock of any access type and to refresh an existing lock.
These sections on the LOCK method describe only those semantics that These sections on the LOCK method describe only those semantics that
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 This method is neither idempotent nor safe (see section 9.1 of
the resource identified by the Request-URI, which becomes the root of [RFC2616]). Responses to this method MUST NOT be cached.
the lock. Lock method requests to create a new lock MUST have a XML
request body which contains an 'owner' XML element and other
information for this lock request. The server MUST preserve the
information provided by the client in the 'owner' field when the lock
information is requested. The LOCK request MAY have a Timeout
header.
Clients MUST assume that locks may arbitrarily disappear at any time, 9.10.1. Creating a lock on existing resource
regardless of the value given in the Timeout header. The Timeout
header only indicates the behavior of the server if extraordinary A LOCK request to an existing resource will create a lock on the
circumstances do not occur. For example, a sufficiently privileged resource identified by the Request-URI, provided the resource is not
user may remove a lock at any time or the system may crash in such a already locked with a conflicting lock. The resource identified in
way that it loses the record of the lock's existence. the Request-URI becomes the root of the lock. Lock method requests
to create a new lock MUST have a XML request body. The server MUST
preserve the information provided by the client in the 'owner' field
in the request body when the lock information is requested. The LOCK
request MAY have a Timeout header.
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 9.10.2. Refreshing Locks
[RFC2616]). Responses to this method MUST NOT be cached.
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 to the URL of a
to the URL of a resource within the scope of the lock. This request resource within the scope of the lock. This request MUST NOT have a
MUST specify which lock to refresh by using the 'Lock-Token' header body and it MUST specify which lock to refresh by using the 'Lock-
with a single lock token (only one lock may be refreshed at a time). Token' header with a single lock token (only one lock may be
It MAY contain a Timeout header, which a server MAY accept to change refreshed at a time). It MAY contain a Timeout header, which a
the duration remaining on the lock to the new value. A server MUST server MAY accept to change the duration remaining on the lock to the
ignore the Depth header on a LOCK refresh. new value. A server MUST ignore the Depth header on a LOCK refresh.
If the resource has other (shared) locks, those locks are unaffected If the resource has other (shared) locks, those locks are unaffected
by a lock refresh. Additionally, those locks do not prevent the by a lock refresh. Additionally, those locks do not prevent the
named lock from being refreshed. named lock from being refreshed.
Note that in RFC2518, clients were indicated through the example in Note that in RFC2518, clients were indicated through the example in
the text to use the If header to specify what lock to refresh (rather the text to use the If header to specify what lock to refresh (rather
than the Lock-Token header). Servers are encouraged to continue to than the Lock-Token header). Servers are encouraged to continue to
support this as well as the Lock-Token header. support this as well as the Lock-Token header.
Note that the Lock-Token header is not be returned in the response Note that the Lock-Token header is not be returned in the response
for a successful refresh LOCK request, but the LOCK response body for a successful refresh LOCK request, but the LOCK response body
MUST contain the new value for the DAV:lockdiscovery body. MUST contain the new value for the DAV:lockdiscovery body.
8.11.2. Depth and Locking 9.10.3. Depth and Locking
The Depth header may be used with the LOCK method. Values other than The Depth header may be used with the LOCK method. Values other than
0 or infinity MUST NOT be used with the Depth header on a LOCK 0 or infinity MUST NOT be used with the Depth header on a LOCK
method. All resources that support the LOCK method MUST support the method. All resources that support the LOCK method MUST support the
Depth header. Depth header.
A Depth header of value 0 means to just lock the resource specified A Depth header of value 0 means to just lock the resource specified
by the Request-URI. by the Request-URI.
If the Depth header is set to infinity then the resource specified in If the Depth header is set to infinity then the resource specified in
skipping to change at page 61, line 45 skipping to change at page 64, line 40
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 SHOULD 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 9.10.4. Locking Unmapped URLs
A successful LOCK method MUST result in the creation of an empty A successful LOCK method MUST result in the creation of an empty
resource which is locked (and which is not a collection), when a resource which is locked (and which is not a collection), when a
resource did not previously exist at that URL. Later on, the lock resource did not previously exist at that URL. Later on, the lock
may go away but the empty resource remains. Empty resources MUST may go away but the empty resource remains. Empty resources MUST
then appear in PROPFIND responses including that URL in the response then appear in PROPFIND responses including that URL in the response
scope. A server MUST respond successfully to a GET request to an scope. A server MUST respond successfully to a GET request to an
empty resource, either by using a 204 No Content response, or by empty resource, either by using a 204 No Content response, or by
using 200 OK with a Content-Length header indicating zero length and using 200 OK with a Content-Length header indicating zero length and
no Content-Type. no Content-Type.
8.11.4. Lock Compatibility Table 9.10.5. Lock Compatibility Table
The table below describes the behavior that occurs when a lock The table below describes the behavior that occurs when a lock
request is made on a resource. request is made on a resource.
+--------------------------+----------------+-------------------+ +--------------------------+----------------+-------------------+
| Current State | Shared Lock OK | Exclusive Lock OK | | Current State | Shared Lock OK | Exclusive Lock OK |
+--------------------------+----------------+-------------------+ +--------------------------+----------------+-------------------+
| None | True | True | | None | True | True |
| | | | | | | |
| Shared Lock | True | False | | Shared Lock | True | False |
skipping to change at page 62, line 34 skipping to change at page 65, line 31
granted. *=It is illegal for a principal to request the same lock granted. *=It is illegal for a principal to request the same lock
twice. twice.
The current lock state of a resource is given in the leftmost column, The current lock state of a resource is given in the leftmost column,
and lock requests are listed in the first row. The intersection of a and lock requests are listed in the first row. The intersection of a
row and column gives the result of a lock request. For example, if a row and column gives the result of a lock request. For example, if a
shared lock is held on a resource, and an exclusive lock is shared lock is held on a resource, and an exclusive lock is
requested, the table entry is "false", indicating the lock must not requested, the table entry is "false", indicating the lock must not
be granted. be granted.
8.11.5. LOCK Responses 9.10.6. LOCK Responses
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 LOCK: status codes have specific applicability to LOCK:
200 (OK) - The LOCK request succeeded and the value of the DAV: 200 (OK) - The LOCK request succeeded and the value of the DAV:
lockdiscovery property is included in the response body. lockdiscovery property is included in the response body.
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
skipping to change at page 63, line 16 skipping to change at page 66, line 13
above). 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 9.10.7. Example - Simple Lock Request
>>Request >>Request
LOCK /workspace/webdav/proposal.doc HTTP/1.1 LOCK /workspace/webdav/proposal.doc HTTP/1.1
Host: example.com Host: example.com
Timeout: Infinite, Second-4100000000 Timeout: Infinite, Second-4100000000
Content-Type: application/xml; charset="utf-8" Content-Type: application/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
Authorization: Digest username="ejw", Authorization: Digest username="ejw",
realm="ejw@example.com", nonce="...", realm="ejw@example.com", nonce="...",
uri="/workspace/webdav/proposal.doc", uri="/workspace/webdav/proposal.doc",
response="...", opaque="..." response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:lockinfo xmlns:D='DAV:'> <D:lockinfo xmlns:D='DAV:'>
<D:lockscope><D:exclusive/></D:lockscope> <D:lockscope><D:exclusive/></D:lockscope>
<D:locktype><D:write/></D:locktype> <D:locktype><D:write/></D:locktype>
<D:owner> <D:owner>
<D:href>http://www.ics.uci.edu/~ejw/contact.html</D:href> <D:href>http://example.org/~ejw/contact.html</D:href>
</D:owner> </D:owner>
</D:lockinfo> </D:lockinfo>
>>Response >>Response
HTTP/1.1 200 OK HTTP/1.1 200 OK
Lock-Token: <urn:uuid:e71d4fae-5dec-22d6-fea5-00a0c91e6be4> Lock-Token: <urn:uuid:e71d4fae-5dec-22d6-fea5-00a0c91e6be4>
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:prop xmlns:D="DAV:"> <D:prop xmlns:D="DAV:">
<D:lockdiscovery> <D:lockdiscovery>
<D:activelock> <D:activelock>
<D:locktype><D:write/></D:locktype> <D:locktype><D:write/></D:locktype>
<D:lockscope><D:exclusive/></D:lockscope> <D:lockscope><D:exclusive/></D:lockscope>
<D:depth>infinity</D:depth> <D:depth>infinity</D:depth>
<D:owner> <D:owner>
<D:href>http://www.ics.uci.edu/~ejw/contact.html</D:href> <D:href>http://example.org/~ejw/contact.html</D:href>
</D:owner> </D:owner>
<D:timeout>Second-604800</D:timeout> <D:timeout>Second-604800</D:timeout>
<D:locktoken> <D:locktoken>
<D:href <D:href
>urn:uuid:e71d4fae-5dec-22d6-fea5-00a0c91e6be4</D:href> >urn:uuid:e71d4fae-5dec-22d6-fea5-00a0c91e6be4</D:href>
</D:locktoken> </D:locktoken>
<D:lockroot> <D:lockroot>
<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://example.org/~ejw/contact.html contains contact
information for the creator 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 9.10.8. Example - Refreshing a Write Lock
>>Request >>Request
LOCK /workspace/webdav/proposal.doc HTTP/1.1 LOCK /workspace/webdav/proposal.doc HTTP/1.1
Host: example.com Host: example.com
Timeout: Infinite, Second-4100000000 Timeout: Infinite, Second-4100000000
Lock-Token: <urn:uuid:e71d4fae-5dec-22d6-fea5-00a0c91e6be4> Lock-Token: <urn:uuid:e71d4fae-5dec-22d6-fea5-00a0c91e6be4>
Authorization: Digest username="ejw", Authorization: Digest username="ejw",
realm="ejw@example.com", nonce="...", realm="ejw@example.com", nonce="...",
uri="/workspace/webdav/proposal.doc", uri="/workspace/webdav/proposal.doc",
skipping to change at page 65, line 32 skipping to change at page 68, line 32
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:prop xmlns:D="DAV:"> <D:prop xmlns:D="DAV:">
<D:lockdiscovery> <D:lockdiscovery>
<D:activelock> <D:activelock>
<D:locktype><D:write/></D:locktype> <D:locktype><D:write/></D:locktype>
<D:lockscope><D:exclusive/></D:lockscope> <D:lockscope><D:exclusive/></D:lockscope>
<D:depth>infinity</D:depth> <D:depth>infinity</D:depth>
<D:owner> <D:owner>
<D:href>http://www.ics.uci.edu/~ejw/contact.html</D:href> <D:href>http://example.org/~ejw/contact.html</D:href>
</D:owner> </D:owner>
<D:timeout>Second-604800</D:timeout> <D:timeout>Second-604800</D:timeout>
<D:locktoken> <D:locktoken>
<D:href <D:href
>urn:uuid:e71d4fae-5dec-22d6-fea5-00a0c91e6be4</D:href> >urn:uuid:e71d4fae-5dec-22d6-fea5-00a0c91e6be4</D:href>
</D:locktoken> </D:locktoken>
<D:lockroot> <D:lockroot>
<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 request would refresh the lock, attempting to reset the timeout This request would refresh the lock, attempting to reset the timeout
to the new value specified in the timeout header. Notice that the to the new value specified in the timeout header. Notice that the
client asked for an infinite time out but the server choose to ignore client asked for an infinite time out but the server choose to ignore
the request. In this example, the nonce, response, and opaque fields the request. In this example, the nonce, response, and opaque fields
have not been calculated in the Authorization request header. have not been calculated in the Authorization request header.
8.11.8. Example - Multi-Resource Lock Request 9.10.9. Example - Multi-Resource Lock Request
>>Request >>Request
LOCK /webdav/ HTTP/1.1 LOCK /webdav/ HTTP/1.1
Host: example.com Host: example.com
Timeout: Infinite, Second-4100000000 Timeout: Infinite, Second-4100000000
Depth: infinity Depth: infinity
Content-Type: application/xml; charset="utf-8" Content-Type: application/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
Authorization: Digest username="ejw", Authorization: Digest username="ejw",
realm="ejw@example.com", nonce="...", realm="ejw@example.com", nonce="...",
uri="/workspace/webdav/proposal.doc", uri="/workspace/webdav/proposal.doc",
response="...", opaque="..." response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:lockinfo xmlns:D="DAV:"> <D:lockinfo xmlns:D="DAV:">
<D:locktype><D:write/></D:locktype> <D:locktype><D:write/></D:locktype>
<D:lockscope><D:exclusive/></D:lockscope> <D:lockscope><D:exclusive/></D:lockscope>
<D:owner> <D:owner>
<D:href>http://www.ics.uci.edu/~ejw/contact.html</D:href> <D:href>http://example.org/~ejw/contact.html</D:href>
</D:owner> </D:owner>
</D:lockinfo> </D:lockinfo>
>>Response >>Response
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
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" ?>
skipping to change at page 67, line 15 skipping to change at page 70, line 15
The error is a 403 (Forbidden) response on the resource The error is a 403 (Forbidden) response on the resource
http://example.com/webdav/secret. Because this resource could not be http://example.com/webdav/secret. Because this resource could not be
locked, none of the resources were locked. Note also that the a locked, none of the resources were locked. Note also that the a
'response' element for the Request-URI itself has been included as 'response' element for the Request-URI itself has been included as
required. required.
In this example, the nonce, response, and opaque fields have not been In this example, the nonce, response, and opaque fields have not been
calculated in the Authorization request header. calculated in the Authorization request header.
8.12. UNLOCK Method 9.11. UNLOCK Method
The UNLOCK method removes the lock identified by the lock token in The UNLOCK method removes the lock identified by the lock token in
the Lock-Token request header. The Request-URI MUST identify a the Lock-Token request header. The Request-URI MUST identify a
resource within the scope of the lock. resource within the scope of the lock.
Note that use of Lock-Token header to provide the lock token is not Note that use of Lock-Token header to provide the lock token is not
consistent with other state-changing methods which all require an If consistent with other state-changing methods which all require an If
header with the lock token. Thus, the If header is not needed to header with the lock token. Thus, the If header is not needed to
provide the lock token. Naturally when the If header is present it provide the lock token. Naturally when the If header is present it
has its normal meaning as a conditional header. has its normal meaning as a conditional header.
skipping to change at page 67, line 44 skipping to change at page 70, line 44
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 This method is idempotent, but not safe (see section 9.1 of
[RFC2616]). Responses to this method MUST NOT be cached. [RFC2616]). Responses to this method MUST NOT be cached.
8.12.1. Status Codes 9.11.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 submitted' precondition), or request was made to a Request-URI that
not within the scope of the lock (see 'lock-token-matches-request- was not within the scope of the lock (see 'lock-token-matches-
uri' precondition). request-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.
8.12.2. Example - UNLOCK 9.11.2. Example - UNLOCK
>>Request >>Request
UNLOCK /workspace/webdav/info.doc HTTP/1.1 UNLOCK /workspace/webdav/info.doc HTTP/1.1
Host: example.com Host: example.com
Lock-Token: <urn:uuid:a515cfa4-5da4-22e1-f5b5-00a0451e6bf7> Lock-Token: <urn:uuid:a515cfa4-5da4-22e1-f5b5-00a0451e6bf7>
Authorization: Digest username="ejw" Authorization: Digest username="ejw"
realm="ejw@example.com", nonce="...", realm="ejw@example.com", nonce="...",
uri="/workspace/webdav/proposal.doc", uri="/workspace/webdav/proposal.doc",
response="...", opaque="..." response="...", opaque="..."
skipping to change at page 69, line 5 skipping to change at page 72, line 5
"urn:uuid:a515cfa4-5da4-22e1-f5b5-00a0451e6bf7" is successfully "urn:uuid:a515cfa4-5da4-22e1-f5b5-00a0451e6bf7" is successfully
removed from the resource removed from the resource
http://example.com/workspace/webdav/info.doc. If this lock included http://example.com/workspace/webdav/info.doc. If this lock included
more than just one resource, the lock is removed from all resources more than just one resource, the lock is removed from all resources
included in the lock. The 204 (No Content) status code is used included in the lock. The 204 (No Content) status code is used
instead of 200 (OK) because there is no response entity body. instead of 200 (OK) because there is no response entity body.
In this example, the nonce, response, and opaque fields have not been In this example, the nonce, response, and opaque fields have not been
calculated in the Authorization request header. calculated in the Authorization request header.
9. HTTP Headers for Distributed Authoring 10. HTTP Headers for Distributed Authoring
All DAV headers follow the same basic formatting rules as HTTP All DAV headers follow the same basic formatting rules as HTTP
headers. This includes rules like line continuation and how to headers. This includes rules like line continuation and how to
combine (or separate) multiple instances of the same header using combine (or separate) multiple instances of the same header using
commas. WebDAV adds two new conditional headers to the set defined commas. WebDAV adds two new conditional headers to the set defined
in HTTP: the If and Overwrite headers. in HTTP: the If and Overwrite headers.
9.1. DAV Header 10.1. DAV Header
DAV = "DAV" ":" #( compliance-class ) DAV = "DAV" ":" #( compliance-class )
compliance-class = ( "1" | "2" | "bis" | extend ) compliance-class = ( "1" | "2" | "3" | 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. In cases where WebDAV is only "1" on all OPTIONS responses. In cases where WebDAV is only
supported in part of the server namespace, an OPTIONS request to non- supported in part of the server namespace, an OPTIONS request to non-
WebDAV resources (including "/") SHOULD NOT advertise WebDAV support. 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 3
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 17 for more entail support for any other, and in particular, support for
details on compliance classes defined in this specification. compliance class 3 does not require support for compliance class 2.
Please refer to Section 18 for more details on compliance classes
defined in this specification.
Note that many WebDAV servers do not advertise WebDAV support in Note that many WebDAV servers do not advertise WebDAV support in
response to "OPTIONS *". response to "OPTIONS *".
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 10.2. Depth Header
Depth = "Depth" ":" ("0" | "1" | "infinity") Depth = "Depth" ":" ("0" | "1" | "infinity")
The Depth request header is used with methods executed on resources The Depth request header is used with methods executed on resources
which could potentially have internal members to indicate whether the which could potentially have internal members to indicate whether the
method is to be applied only to the resource ("Depth: 0"), to the method is to be applied only to the resource ("Depth: 0"), to the
resource and its immediate children, ("Depth: 1"), or the resource resource and its immediate children, ("Depth: 1"), or the resource
and all its progeny ("Depth: infinity"). and all its progeny ("Depth: infinity").
The Depth header is only supported if a method's definition The Depth header is only supported if a method's definition
explicitly provides for such support. explicitly provides for such support.
skipping to change at page 71, line 10 skipping to change at page 74, line 12
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.
Please note, however, that it is always an error to submit a value Please note, however, that it is always an error to submit a value
for the Depth header that is not allowed by the method's definition. for the Depth header that is not allowed by the method's definition.
Thus submitting a "Depth: 1" on a COPY, even if the resource does not Thus submitting a "Depth: 1" on a COPY, even if the resource does not
have internal members, will result in a 400 (Bad Request). The have internal members, will result in a 400 (Bad Request). The
method should fail not because the resource doesn't have internal method should fail not because the resource doesn't have internal
members, but because of the illegal value in the header. members, but because of the illegal value in the header.
9.3. Destination Header 10.3. Destination Header
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.
defined in [RFC3986].
Since the Destination value is an absolute URI, it may name a Destination = "Destination" ":" ( Simple-ref )
different server (or different port or scheme). If the source server
cannot attempt a copy to the remote server, it MUST fail the request If the Destination value is an absolute URI, it may name a different
with a 502 (Bad Gateway) response. server (or different port or scheme). If the source server cannot
attempt a copy to the remote server, it MUST fail the request with a
502 (Bad Gateway) response.
If the Destination value is too long or otherwise unacceptable, the If the Destination value is too long or otherwise unacceptable, the
server SHOULD return 400 (Bad Request), ideally with helpful server SHOULD return 400 (Bad Request), ideally with helpful
information in an error body. information in an error body.
9.4. If Header 10.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-Reference
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
Coded-Reference = "<" Simple-ref ">"
; No LWS allowed in Coded-Reference
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 (not that it's special in will never match an actual valid lock token (not that it's special in
this regard). The purpose of this is described in Section 9.4.4. this regard). The purpose of this is described in Section 10.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
clauses, and if the conditional evaluates to false, fail as described clauses, and if the conditional evaluates to false, fail as described
above. above.
9.4.1. No-tag-list Production 10.4.1. No-tag-list Production
The No-tag-list production describes a series of state tokens and The No-tag-list production describes a series of state tokens and
ETags. If multiple No-tag-list productions are used then one only ETags. If multiple No-tag-list productions are used then one only
needs to match the state of the resource for the method to be allowed needs to match the state of the resource for the method to be allowed
to continue. All untagged tokens apply to the resource identified in to continue. All untagged tokens apply to the resource identified in
the Request-URI. the Request-URI.
Example - no-tag-list production Example - no-tag-list production
If: (<urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2> If: (<urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2>
["I am an ETag"]) (["I am another ETag"]) ["I am an ETag"]) (["I am another ETag"])
The previous header would require that the resource identified in the The previous header would require that the resource identified in the
Request-URI be locked with the specified lock token and in the state Request-URI be locked with the specified lock token and in the state
identified by the "I am an ETag" ETag or in the state identified by identified by the "I am an ETag" ETag or in the state identified by
the second ETag "I am another ETag". To put the matter more plainly the second ETag "I am another ETag". To put the matter more plainly
one can think of the previous If header as being in the form (or (and one can think of the previous If header as being in the form (or (and
<urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2> ["I am an ETag"]) <urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2> ["I am an ETag"])
(and ["I am another ETag"])). (and ["I am another ETag"])).
9.4.2. Tagged-list Production 10.4.2. Tagged-list Production
The tagged-list production may be used instead of the no-tag-list The tagged-list production may be used instead of the no-tag-list
production, in order to scope each token to a specific resource. production, in order to scope each token to a specific resource.
That is, it specifies that the lists following the resource That is, it specifies that the lists following the resource
specification only apply to the specified resource. The scope of the specification only apply to the specified resource. The scope of the
resource production begins with the list production immediately resource production begins with the list production immediately
following the resource production and ends with the next resource following the resource production and ends with the next resource
production, if any. All clauses must be evaluated. If the state of production, if any. All clauses must be evaluated. If the state of
the resource named in the tag does not match any of the associated the resource named in the tag does not match any of the associated
state lists then the request MUST fail with a 412 (Precondition state lists then the request MUST fail with a 412 (Precondition
Failed). Failed).
The same URI MUST NOT appear more than once in a resource production The same URI MUST NOT appear more than once in a resource production
in an If header. in an If header.
9.4.3. Example - Tagged List If header in COPY 10.4.3. Example - Tagged List If header in COPY
>>Request >>Request
COPY /resource1 HTTP/1.1 COPY /resource1 HTTP/1.1
Host: www.example.com Host: www.example.com
Destination: http://www.example.com/resource2 Destination: http://www.example.com/resource2
If: <http://www.example.com/resource1> If: <http://www.example.com/resource1>
(<urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2> (<urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2>
[W/"A weak ETag"]) (["strong ETag"]) [W/"A weak ETag"]) (["strong ETag"])
<http://www.example.com/random> <http://www.example.com/random>
skipping to change at page 73, line 32 skipping to change at page 76, line 32
weak ETag"]) (["strong ETag"])", that is, it either must be locked weak ETag"]) (["strong ETag"])", that is, it either must be locked
with a lock token of "urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2" with a lock token of "urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2"
and have a weak entity tag W/"A weak ETag" or it must have a strong and have a weak entity tag W/"A weak ETag" or it must have a strong
entity tag "strong ETag". entity tag "strong ETag".
That is the only success condition since the resource That is the only success condition since the resource
http://www.example.com/random never has the method applied to it (the http://www.example.com/random never has the method applied to it (the
only other resource listed in the If header) and only other resource listed in the If header) and
http://www.example.com/resource2 is not listed in the If header. http://www.example.com/resource2 is not listed in the If header.
9.4.4. Not Production 10.4.4. Not Production
Every state token or ETag is either current, and hence describes the Every state token or ETag is either current, and hence describes the
state of a resource, or is not current, and does not describe the state of a resource, or is not current, and does not describe the
state of a resource. The boolean operation of matching a state token state of a resource. The boolean operation of matching a state token
or ETag to the current state of a resource thus resolves to a true or or ETag to the current state of a resource thus resolves to a true or
false value. The "Not" production is used to reverse that value. false value. The "Not" production is used to reverse that value.
The scope of the not production is the state-token or entity-tag The scope of the not production is the state-token or entity-tag
immediately following it. immediately following it.
If: (Not <urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2> If: (Not <urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2>
<urn:uuid:58f202ac-22cf-11d1-b12d-002035b29092>) <urn:uuid:58f202ac-22cf-11d1-b12d-002035b29092>)
When submitted with a request, this If header requires that all When submitted with a request, this If header requires that all
operand resources must not be locked with operand resources must not be locked with
urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2 and must be locked with urn:uuid:181d4fae-7d8c-11d0-a765-00a0c91e6bf2 and must be locked with
urn:uuid:58f202ac-22cf-11d1-b12d-002035b29092. urn:uuid:58f202ac-22cf-11d1-b12d-002035b29092.
The Not production is particularly useful with a state token known The Not production is particularly useful with a state token that
not to ever identify a lock, such as the "<DAV:no-lock>" state token. never identifies a lock, such as the "<DAV:no-lock>" state token.
The clause "Not <DAV:no-lock>" MUST evaluate to true. Thus, any "OR" The server MUST evaluate any unrecognized state token as false.
statement containing the clause "Not <DAV:no-lock>" MUST also
evaluate to true.
9.4.5. Matching Function Thus, for example:
The clause "Not <DAV:no-lock>" evaluates to true.
Any "OR" statement containing the clause "Not <DAV:no-lock>"
evaluates to true.
10.4.5. Matching Function
When performing If header processing, the definition of a matching When performing If header processing, the definition of a matching
state token or entity tag is as follows. state token or entity tag is as follows.
Identifying a resource: The resource is identified by the URI along Identifying a resource: The resource is identified by the URI along
with the token, in tagged list production, or by the Request-URI in with the token, in tagged list production, or by the Request-URI in
untagged list production. untagged list production.
Matching entity tag: Where the entity tag matches an entity tag Matching entity tag: Where the entity tag matches an entity tag
associated with the identified resource. associated with the identified resource.
skipping to change at page 74, line 42 skipping to change at page 77, line 47
resource, which is the 'specs' collection identified by the URL in resource, which is the 'specs' collection identified by the URL in
the tagged list production. If the 'specs' collection is not locked the tagged list production. If the 'specs' collection is not locked
or has a lock with a different token, the request MUST fail. If the or has a lock with a different token, the request MUST fail. If the
'specs' collection is locked (depth infinity) with that lock token, 'specs' collection is locked (depth infinity) with that lock token,
then this request could succeed, both because the If header evaluates then this request could succeed, both because the If header evaluates
to true, and because the lock token for the lock affecting the to true, and because the lock token for the lock affecting the
affected resource has been provided. Alternatively, a request where affected resource has been provided. Alternatively, a request where
the 'rfc2518.txt' URL is associated with the lock token in the If the 'rfc2518.txt' URL is associated with the lock token in the If
header could also succeed. header could also succeed.
9.4.6. If Header and Non-DAV Aware Proxies 10.4.6. If Header and Non-DAV Aware Proxies
Non-DAV aware proxies will not honor the If header, since they will Non-DAV aware proxies will not honor the If header, since they will
not understand the If header, and HTTP requires non-understood not understand the If header, and HTTP requires non-understood
headers to be ignored. When communicating with HTTP/1.1 proxies, the headers to be ignored. When communicating with HTTP/1.1 proxies, the
"Cache-Control: no-cache" request header MUST be used so as to "Cache-Control: no-cache" request header MUST be used so as to
prevent the proxy from improperly trying to service the request from prevent the proxy from improperly trying to service the request from
its cache. When dealing with HTTP/1.0 proxies the "Pragma: no-cache" its cache. When dealing with HTTP/1.0 proxies the "Pragma: no-cache"
request header MUST be used for the same reason. request header MUST be used for the same reason.
9.5. Lock-Token Header 10.5. Lock-Token Header
Lock-Token = "Lock-Token" ":" Coded-URL Lock-Token = "Lock-Token" ":" Coded-URL
The Lock-Token request header is used with the UNLOCK method to The Lock-Token request header is used with the UNLOCK method to
identify the lock to be removed. The lock token in the Lock-Token identify the lock to be removed. The lock token in the Lock-Token
request header MUST identify a lock that contains the resource request header MUST identify a lock that contains the resource
identified by Request-URI as a member. identified by Request-URI as a member.
The Lock-Token response header is used with the LOCK method to The Lock-Token response header is used with the LOCK method to
indicate the lock token created as a result of a successful LOCK indicate the lock token created as a result of a successful LOCK
request to create a new lock. request to create a new lock.
9.6. Overwrite Header 10.6. Overwrite Header
Overwrite = "Overwrite" ":" ("T" | "F") Overwrite = "Overwrite" ":" ("T" | "F")
The Overwrite request header specifies whether the server should The Overwrite request header specifies whether the server should
overwrite a resource mapped to the destination URL during a COPY or overwrite a resource mapped to the destination URL during a COPY or
MOVE. A value of "F" states that the server must not perform the MOVE. A value of "F" states that the server must not perform the
COPY or MOVE operation if the state of the destination URL does map COPY or MOVE operation if the state of the destination URL does map
to a resource. If the overwrite header is not included in a COPY or to a resource. If the overwrite header is not included in a COPY or
MOVE request then the resource MUST treat the request as if it has an MOVE request then the resource MUST treat the request as if it has an
overwrite header of value "T". While the Overwrite header appears to overwrite header of value "T". While the Overwrite header appears to
skipping to change at page 75, line 40 skipping to change at page 78, line 43
If-Match applies only to the Request-URI, and not to the Destination If-Match applies only to the Request-URI, and not to the Destination
of a COPY or MOVE. of a COPY or MOVE.
If a COPY or MOVE is not performed due to the value of the Overwrite If a COPY or MOVE is not performed due to the value of the Overwrite
header, the method MUST fail with a 412 (Precondition Failed) status header, the method MUST fail with a 412 (Precondition Failed) status
code. The server MUST do authorization checks before checking this code. The server MUST do authorization checks before checking this
or any conditional header. or any conditional header.
All DAV compliant resources MUST support the Overwrite header. All DAV compliant resources MUST support the Overwrite header.
9.7. Timeout Request Header 10.7. Timeout Request Header
TimeOut = "Timeout" ":" 1#TimeType TimeOut = "Timeout" ":" 1#TimeType
TimeType = ("Second-" DAVTimeOutVal | "Infinite") TimeType = ("Second-" DAVTimeOutVal | "Infinite")
; No LWS allowed within TimeType ; No LWS allowed within TimeType
DAVTimeOutVal = 1*DIGIT DAVTimeOutVal = 1*DIGIT
Clients may include Timeout request headers in their LOCK requests. Clients may include Timeout request headers in their LOCK requests.
However, the server is not required to honor or even consider these However, the server is not required to honor or even consider these
requests. Clients MUST NOT submit a Timeout request header with any requests. Clients MUST NOT submit a Timeout request header with any
method other than a LOCK method. method other than a LOCK method.
skipping to change at page 77, line 5 skipping to change at page 80, line 5
ask for a relatively small timeout value so that if the applet dies, ask for a relatively small timeout value so that if the applet dies,
the lock can be quickly harvested. However, a document management the lock can be quickly harvested. However, a document management
system is likely to ask for an extremely long timeout because its system is likely to ask for an extremely long timeout because its
user may be planning on going off-line. user may be planning on going off-line.
A client MUST NOT assume that just because the time-out has expired A client MUST NOT assume that just because the time-out has expired
the lock has been lost. Likewise, a client MUST NOT assume that just the lock has been lost. Likewise, a client MUST NOT assume that just
because the time-out has not expired, the lock still exists (and for because the time-out has not expired, the lock still exists (and for
this reason, clients are strongly advised to use ETags as well). this reason, clients are strongly advised to use ETags as well).
10. Status Code Extensions to HTTP/1.1 11. Status Code Extensions to HTTP/1.1
The following status codes are added to those defined in HTTP/1.1 The following status codes are added to those defined in HTTP/1.1
[RFC2616]. [RFC2616].
10.1. 207 Multi-Status 11.1. 207 Multi-Status
The 207 (Multi-Status) status code provides status for multiple The 207 (Multi-Status) status code provides status for multiple
independent operations (see Section 12 for more information). independent operations (see Section 13 for more information).
10.2. 422 Unprocessable Entity 11.2. 422 Unprocessable Entity
The 422 (Unprocessable Entity) status code means the server The 422 (Unprocessable Entity) status code means the server
understands the content type of the request entity (hence a understands the content type of the request entity (hence a
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 11.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 an appropriate of a method is locked. This response SHOULD contain an appropriate
precondition or postcondition code, such as 'lock-token-present' or precondition or postcondition code, such as 'lock-token-submitted' or
'no-conflicting-lock". 'no-conflicting-lock".
10.4. 424 Failed Dependency 11.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 11.5. 507 Insufficient Storage
The 507 (Insufficient Storage) status code means the method could not The 507 (Insufficient Storage) status code means the method could not
be performed on the resource because the server is unable to store be performed on the resource because the server is unable to store
the representation needed to successfully complete the request. This the representation needed to successfully complete the request. This
condition is considered to be temporary. If the request which condition is considered to be temporary. If the request which
received this status code was the result of a user action, the received this status code was the result of a user action, the
request MUST NOT be repeated until it is requested by a separate user request MUST NOT be repeated until it is requested by a separate user
action. action.
11. Use of HTTP Status Codes 12. Use of HTTP Status Codes
These HTTP codes are not redefined, but their use is somewhat These HTTP codes are not redefined, but their use is somewhat
extended by WebDAV methods and requirements. In general, many HTTP extended by WebDAV methods and requirements. In general, many HTTP
status codes can be used in response to any request, not just in status codes can be used in response to any request, not just in
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 12.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 server conditional headers defined in this specification. If the server
evaluates 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. On the other hand, if the then this error code MUST be returned. On the other hand, if the
client did not include a conditional header in the request, then the client did not include a conditional header in the request, then the
server MUST NOT use this error. server MUST NOT use this error.
11.2. 414 Request-URI Too Long 12.2. 414 Request-URI Too Long
This status code is used in HTTP 1.1 only for Request-URIs, not URIs This status code is used in HTTP 1.1 only for Request-URIs, not URIs
in other locations. in other locations.
12. Multi-Status Response 13. 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.
The body of a 207 Multi-Status response MUST contain a URL associated The body of a 207 Multi-Status response MUST contain a URL associated
with each specific status code, so that the client can tell whether with each specific status code, so that the client can tell whether
the error occurred with the source resource, destination resource or the error occurred with the source resource, destination resource or
some other resource in the scope of the request. some other resource in the scope of the request.
12.1. Response headers 13.1. Response headers
HTTP defines the Location header to indicate a preferred URL for the HTTP defines the Location header to indicate a preferred URL for the
resource that was addressed in the Request-URI (e.g. in response to resource that was addressed in the Request-URI (e.g. in response to
successful PUT requests or in redirect responses). However, use of successful PUT requests or in redirect responses). However, use of
this header creates ambiguity when there are URLs in the body of the this header creates ambiguity when there are URLs in the body of the
response, as with Multi-Status. Thus, use of the Location header response, as with Multi-Status. Thus, use of the Location header
with the Multi-Status response is intentionally undefined. with the Multi-Status response is intentionally undefined.
12.2. URL Handling 13.2. Handling redirected child resources
A Multi-Status body contains one or more 'response' elements. Each
response element describes a resource, and has an 'href' element
identifying the resource. The 'href' element MUST contain an
absolute URI or relative reference. It MUST NOT include "." or ".."
as path elements.
If a 'href' element contains a relative reference, it MUST be
resolved against the Request-URI. A relative reference MUST be an
absolute path (note that clients are not known to support relative
paths).
Identifiers for collections appearing in the results SHOULD end in a
'/' character.
If a server allows resource names to include characters that aren't
legal in HTTP URL paths, these characters must be percent-encoded on
the wire (see [RFC3986], section 2.1). For example, it is illegal to
use a space character or double-quote in a URI. URIs appearing in
PROPFIND or PROPPATCH XML bodies (or other XML marshalling defined in
this specification) are still subject to all URI rules, including
forbidden characters.
12.3. Handling redirected child resources
Redirect responses (300-303, 305 and 307) defined in HTTP 1.1 Redirect responses (300-303, 305 and 307) defined in HTTP 1.1
normally take a Location header to indicate the new URI for the normally take a Location header to indicate the new URI for the
single resource redirected from the Request-URI. Multi-Status single resource redirected from the Request-URI. Multi-Status
responses contain many resource addresses, but the original responses contain many resource addresses, but the original
definition in RFC2518 did not have any place for the server to definition in RFC2518 did not have any place for the server to
provide the new URI for redirected resources. This specification provide the new URI for redirected resources. This specification
does define a 'location' element for this information (see does define a 'location' element for this information (see
Section 13.9). Servers MUST use this new element with redirect Section 14.9). Servers MUST use this new element with redirect
responses in Multi-Status. responses in Multi-Status.
Clients encountering redirected resources in Multi-Status MUST NOT Clients encountering redirected resources in Multi-Status MUST NOT
rely on the 'location' element being present with a new URI. If the rely on the 'location' element being present with a new URI. If the
element is not present, the client MAY reissue the request to the element is not present, the client MAY reissue the request to the
individual redirected resource, because the response to that request individual redirected resource, because the response to that request
can be redirected with a Location header containing the new URI. can be redirected with a Location header containing the new URI.
12.4. Internal Status Codes 13.3. Internal Status Codes
Section 8.3.1, Section 8.2.2, Section 8.7.1, Section 8.9.3 and Section 9.2.1, Section 9.1.2, Section 9.6.1, Section 9.8.3 and
Section 8.10.2 define various status codes used in Multi-Status Section 9.9.2 define various status codes used in Multi-Status
responses. This specification does not define the meaning of other responses. This specification does not define the meaning of other
status codes that could appear in these responses. status codes that could appear in these responses.
13. XML Element Definitions 14. XML Element Definitions
In this section, the final line of each section gives the element In this section, the final line of each section gives the element
type declaration using the format defined in [XML]. The "Value" type declaration using the format defined in [XML]. The "Value"
field, where present, specifies further restrictions on the allowable field, 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). The "Extensibility" field discusses how values of a PCDATA element). The "Extensibility" field discusses how
the element may be extended in the future (or in existing extensions the element may be extended in the future (or in existing extensions
to WebDAV. to WebDAV.
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 14.1. activelock XML Element
Name: activelock Name: activelock
Purpose: Describes a lock on a resource. Purpose: Describes a lock on a resource.
<!ELEMENT activelock (lockscope, locktype, depth, owner?, timeout?, <!ELEMENT activelock (lockscope, locktype, depth, owner?, timeout?,
locktoken?, lockroot)> locktoken?, lockroot)>
13.2. allprop XML Element 14.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.
<!ELEMENT allprop EMPTY > <!ELEMENT allprop EMPTY >
13.3. collection XML Element 14.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.
<!ELEMENT collection EMPTY > <!ELEMENT collection EMPTY >
13.4. depth XML Element 14.4. 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"
<!ELEMENT depth (#PCDATA) > <!ELEMENT depth (#PCDATA) >
13.5. error XML Element 14.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 at least one XML element, and MUST NOT contain Description: Contains at least one XML element, and MUST NOT contain
text or mixed content. Any element that is a child of the 'error' text or mixed content. Any element that is a child of the 'error'
element is considered to be a precondition or postcondition code. element is considered to be a precondition or postcondition code.
Unrecognized elements SHOULD be ignored if not recognized. Unrecognized elements SHOULD be ignored.
<!ELEMENT error ANY > <!ELEMENT error ANY >
13.6. exclusive XML Element 14.6. exclusive XML Element
Name: exclusive Name: exclusive
Purpose: Specifies an exclusive lock Purpose: Specifies an exclusive lock
<!ELEMENT exclusive EMPTY > <!ELEMENT exclusive EMPTY >
13.7. href XML Element 14.7. href XML Element
Name: href Name: href
Purpose: Identifies the content of the element as a URI or a Purpose: MUST contain a URI or a relative reference.
relative reference. There may be limits on the value of 'href'
depending on the context of its use. Refer to the specification
text where 'href' is used to see what limitations apply in each
case.
Value: URI-reference (See section 4.1 of [RFC3986]) Description: There may be limits on the value of 'href' depending on
the context of its use. Refer to the specification text where
'href' is used to see what limitations apply in each case.
Value: Simple-ref
<!ELEMENT href (#PCDATA)> <!ELEMENT href (#PCDATA)>
13.8. include XML Element 14.8. include XML Element
Name: include Name: include
Purpose: Any child element represents the name of a property to be Purpose: Any child element represents the name of a property to be
included in the PROPFIND response. All elements inside an included in the PROPFIND response. All elements inside an
'include' XML element MUST define properties related to the 'include' XML element MUST define properties related to the
resource, although possible property names are in no way limited resource, although possible property names are in no way limited
to those property names defined in this document or other to those property names defined in this document or other
standards. This element MUST NOT contain text or mixed content. standards. This element MUST NOT contain text or mixed content.
<!ELEMENT include ANY > <!ELEMENT include ANY >
13.9. location XML Element 14.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 'multistatus' series codes). When these codes are used inside a 'multistatus'
element, the 'location' element can be used to provide the element, the 'location' element can be used to provide the
accompanying Location header value. 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.
<!ELEMENT location (href)> <!ELEMENT location (href)>
13.10. lockentry XML Element 14.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.
<!ELEMENT lockentry (lockscope, locktype) > <!ELEMENT lockentry (lockscope, locktype) >
13.11. lockinfo XML Element 14.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.
<!ELEMENT lockinfo (lockscope, locktype, owner?) > <!ELEMENT lockinfo (lockscope, locktype, owner?) >
13.12. lockroot XML Element 14.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.
<!ELEMENT lockroot (href) > <!ELEMENT lockroot (href) >
13.13. lockscope XML Element 14.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.
<!ELEMENT lockscope (exclusive | shared) > <!ELEMENT lockscope (exclusive | shared) >
13.14. locktoken XML Element 14.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.
<!ELEMENT locktoken (href) > <!ELEMENT locktoken (href) >
13.15. locktype XML Element 14.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.
<!ELEMENT locktype (write) > <!ELEMENT locktype (write) >
13.16. multistatus XML Element 14.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.
<!ELEMENT multistatus (response*, responsedescription?) > <!ELEMENT multistatus (response*, responsedescription?) >
13.17. prop XML element 14.17. owner XML Element
Name: owner
Purpose: Provides information about the creator of a lock.
Description: Allows a client to provide 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 created a lock. The value provided MUST be
treated as a dead property in terms of XML Information Item
preservation. The server MUST NOT alter the value unless the
owner value provided by the client is empty. For a certain amount
of interoperability between different client implementations, if
clients have URI-formatted contact information for the lock
creator suitable for user display, then clients SHOULD put those
URIs in 'href' child elements of the 'owner' element.
Extensibility: MAY be extended with child elements, mixed content,
text content or attributes.
<!ELEMENT owner ANY >
14.18. 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 Description: A generic container for properties defined on
resources. All elements inside a 'prop' XML element MUST define resources. All elements inside a 'prop' XML element MUST define
properties related to the resource, although possible property properties related to the resource, although possible property
names are in no way limited to those property names defined in names are in no way limited to those property names defined in
this document or other standards. This element MUST NOT contain this document or other standards. This element MUST NOT contain
text or mixed content. text or mixed content.
<!ELEMENT prop ANY > <!ELEMENT prop ANY >
13.18. propertyupdate XML element 14.19. 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.
<!ELEMENT propertyupdate (remove | set)+ > <!ELEMENT propertyupdate (remove | set)+ >
13.19. propfind XML Element 14.20. 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', 'allprop', 'include' 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.
<!ELEMENT propfind ( propname | (allprop, include?) | prop ) > <!ELEMENT propfind ( propname | (allprop, include?) | prop ) >
13.20. propname XML Element 14.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.
<!ELEMENT propname EMPTY > <!ELEMENT propname EMPTY >
13.21. propstat XML Element 14.22. 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. The optional precondition/
postcondition error code and 'responsedescription' text also apply
to the properties named in 'prop'.
<!ELEMENT propstat (prop, status, responsedescription?) > <!ELEMENT propstat (prop, status, error?, responsedescription?) >
13.22. remove XML element 14.23. 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.
<!ELEMENT remove (prop) > <!ELEMENT remove (prop) >
skipping to change at page 87, line 14 skipping to change at page 90, line 35
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.
<!ELEMENT remove (prop) > <!ELEMENT remove (prop) >
13.23. response XML Element 14.24. 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. The optional
precondition/postcondition error code and 'responsedescription'
text can provide additional information about this resource
relative to the request or result.
<!ELEMENT response (href, ((href*, status)|(propstat+)), <!ELEMENT response (href, ((href*, status)|(propstat+)),
responsedescription? , location?) > error?, responsedescription? , location?) >
13.24. responsedescription XML Element 14.25. 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: Provides information suitable to be presented to a user Description: Provides information suitable to be presented to a
(PCDATA) and/or condition name elements (in 'error'). user.
<!ELEMENT responsedescription (#PCDATA | error)* > <!ELEMENT responsedescription (#PCDATA) >
14.26. set XML element
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.
<!ELEMENT set (prop) > <!ELEMENT set (prop) >
13.26. shared XML Element 14.27. shared XML Element
Name: shared Name: shared
Purpose: Specifies a shared lock Purpose: Specifies a shared lock
<!ELEMENT shared EMPTY > <!ELEMENT shared EMPTY >
13.27. status XML Element 14.28. 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])
<!ELEMENT status (#PCDATA) > <!ELEMENT status (#PCDATA) >
13.28. timeout XML Element 14.29. 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 10.7).
<!ELEMENT timeout (#PCDATA) > <!ELEMENT timeout (#PCDATA) >
13.29. write XML Element 14.30. write XML Element
Name: write Name: write
Purpose: Specifies a write lock. Purpose: Specifies a write lock.
<!ELEMENT write EMPTY > <!ELEMENT write EMPTY >
14. DAV Properties 15. 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).
value for a property of a given name, so the property may only show
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 LOCK request affects the value of to a protected property (as when a LOCK request affects the value of
DAV:lockdiscovery). Note that a given property could be protected on DAV:lockdiscovery). Note that a given property could be protected on
one type of resource, but not protected on another type of resource. one type of resource, but 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.
Server implementors SHOULD NOT include extra LWS in these values, Server implementors SHOULD NOT include extra LWS in these values,
however client implementors MUST be prepared to handle extra LWS. however client implementors MUST be prepared to handle extra LWS.
14.1. creationdate Property 15.1. creationdate Property
Name: creationdate Name: creationdate
Purpose: Records the time and date the resource was created. Purpose: Records the time and date the resource was created.
Value: date-time (defined in [RFC3339], see the ABNF in section Value: date-time (defined in [RFC3339], see the ABNF in section
5.6.) 5.6.)
Protected: MAY be protected. Some servers allow DAV:creationdate to Protected: MAY be protected. Some servers allow DAV:creationdate to
be changed to reflect the time the document was created if that is be changed to reflect the time the document was created if that is
skipping to change at page 91, line 17 skipping to change at page 94, line 13
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")
<!ELEMENT creationdate (#PCDATA) > <!ELEMENT creationdate (#PCDATA) >
14.2. displayname Property 15.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
Protected: SHOULD NOT be protected. Note that servers implementing Protected: SHOULD NOT be protected. Note that servers implementing
RFC2518 might have made this a protected property as this is a new RFC2518 might have made this a protected property as this is a new
skipping to change at page 91, line 43 skipping to change at page 94, line 39
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).
<!ELEMENT displayname (#PCDATA) > <!ELEMENT displayname (#PCDATA) >
14.3. getcontentlanguage Property 15.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]).
skipping to change at page 92, line 21 skipping to change at page 95, line 18
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.
<!ELEMENT getcontentlanguage (#PCDATA) > <!ELEMENT getcontentlanguage (#PCDATA) >
14.4. getcontentlength Property 15.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].
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.
<!ELEMENT getcontentlength (#PCDATA) > <!ELEMENT getcontentlength (#PCDATA) >
14.5. getcontenttype Property 15.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.
Value: media-type (defined in section 3.7 of [RFC2616]) Value: media-type (defined in section 3.7 of [RFC2616])
Protected: SHOULD NOT be protected, so clients may fix this value. Protected: Potentially protected if the server prefers to assign
Note that servers implementing RFC2518 might have made this a content types on its own (see also discussion in Section 9.7.1).
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.
<!ELEMENT getcontenttype (#PCDATA) > <!ELEMENT getcontenttype (#PCDATA) >
14.6. getetag Property 15.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. Also note the considerations in on the source resource. Also note the considerations in
Section 8.1.6. Section 8.7.
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, and to
changes in properties or lock state MUST not cause a resource's Section 8.5 for a discussion of ETags in WebDAV.
ETag to change.
<!ELEMENT getetag (#PCDATA) > <!ELEMENT getetag (#PCDATA) >
14.7. getlastmodified Property 15.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 94, line 23 skipping to change at page 97, line 14
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 can be preserved in a MOVE DAV:getlastmodified value, and this can be preserved in a MOVE
even when the HTTP Last-Modified value SHOULD change. Note that even when the HTTP Last-Modified value SHOULD change. Note that
since [RFC2616] requires clients to use ETags where provided, a since [RFC2616] requires clients to use ETags where provided, a
server implementing ETags can count on clients using a much better server implementing ETags can count on clients using a much better
mechanism that modification dates for offline synchronization or mechanism that modification dates for offline synchronization or
cache control. Also note the considerations in Section 8.1.6. cache control. Also note the considerations in Section 8.7.
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.
<!ELEMENT getlastmodified (#PCDATA) > <!ELEMENT getlastmodified (#PCDATA) >
14.8. lockdiscovery Property 15.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
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. This
property is NOT lockable with respect to write locks (Section 7).
<!ELEMENT lockdiscovery (activelock)* > <!ELEMENT lockdiscovery (activelock)* >
14.8.1. Example - Retrieving DAV:lockdiscovery 15.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 96, line 41 skipping to change at page 99, line 41
</D:lockdiscovery> </D:lockdiscovery>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
This resource has a single exclusive write lock on it, with an This resource has a single exclusive write lock on it, with an
infinite timeout. infinite timeout.
14.9. resourcetype Property 15.9. resourcetype Property
Name: resourcetype Name: resourcetype
Purpose: Specifies the nature of the resource. Purpose: Specifies the nature of the resource.
Protected: SHOULD be protected. Resource type is generally decided Protected: SHOULD be protected. Resource type is generally decided
through the operation creating the resource (MKCOL vs PUT), not by through the operation creating the resource (MKCOL vs PUT), not by
PROPPATCH. PROPPATCH.
COPY/MOVE behaviour: Generally a COPY/MOVE of a resource results in COPY/MOVE behaviour: Generally a COPY/MOVE of a resource results in
the same type of resource at the destination. 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 14.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 This element MUST NOT contain text or mixed content. Any custom
child element is considered to be an identifier for a resource child element is considered to be an identifier for a resource
type. 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 15.10. supportedlock Property
Name: supportedlock Name: supportedlock
Purpose: To provide a listing of the lock capabilities supported by Purpose: To provide a listing of the lock capabilities supported by
the resource. the resource.
Protected: MUST be protected. Servers determine what lock Protected: MUST be protected. Servers determine what lock
mechanisms are supported, not clients. mechanisms are supported, not clients.
COPY/MOVE behaviour: This property value is dependent on the kind of COPY/MOVE behaviour: This property value is dependent on the kind of
locks supported at the destination, not on the value of the locks supported at the destination, not on the value of the
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. This property is
NOT lockable with respect to write locks (Section 7).
<!ELEMENT supportedlock (lockentry)* > <!ELEMENT supportedlock (lockentry)* >
14.10.1. Example - Retrieving DAV:supportedlock 15.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 99, line 5 skipping to change at page 102, line 5
<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>
</D:supportedlock> </D:supportedlock>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
15. Precondition/postcondition XML elements 16. Precondition/postcondition XML elements
As introduced in section Section 8.1.5, extra information on error As introduced in section Section 8.6, extra information on error
conditions can be included in the body of many status responses. conditions can be included in the body of many status responses.
This section makes requirements on the use of the error body This section makes requirements on the use of the error body
mechanism and introduces a number of precondition and postcondition mechanism and introduces a number of precondition and postcondition
codes. codes.
A "precondition" of a method describes the state of the server that A "precondition" of a method describes the state of the server that
must be true for that method to be performed. A "postcondition" of a must be true for that method to be performed. A "postcondition" of a
method describes the state of the server that must be true after that method describes the state of the server that must be true after that
method has been completed. method has been completed.
Each precondition and postcondition has a unique XML element Each precondition and postcondition has a unique XML element
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 an 'error' element in the appropriate 'propstat or
responsedescription element. In all other error responses, the XML 'response' element depending on whether the condition applies to one
element MUST be returned as the child of a top-level DAV:error or more properties or the resource as a whole. In all other error
element in the response body, unless otherwise negotiated by the responses, the XML element MUST be returned as the child of a top-
request, along with an appropriate response status. The most common level 'error' element in the response body, unless otherwise
response status codes are 403 (Forbidden) if the request should not negotiated by the request, along with an appropriate response status.
be repeated because it will always fail, and 409 (Conflict) if it is The most common response status codes are 403 (Forbidden) if the
expected that the user might be able to resolve the conflict and request should not be repeated because it will always fail, and 409
resubmit the request. The DAV:error element MAY contain child (Conflict) if it is expected that the user might be able to resolve
elements with specific error information and MAY be extended with any the conflict and resubmit the request. The 'error' element MAY
custom child elements. contain child elements with specific error information and MAY be
extended with any 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 this specification SHOULD use the XML error
precondition or postcondition defined in this document is violated. whenever a precondition or postcondition defined in this document is
For error conditions not specified in this document, the server MAY violated. For error conditions not specified in this document, the
simply choose an appropriate numeric status and leave the response server MAY simply choose an appropriate numeric status and leave the
body blank. However, a server MAY instead use a custom error code response body blank. However, a server MAY instead use a custom
and other supporting text, because even when clients do not error code and other supporting text, because even when clients do
automatically recognize error codes they can be quite useful in not automatically recognize error codes they can be quite useful in
interoperability testing and debugging. interoperability testing and debugging.
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-submitted>
<D:href>/workspace/webdav/</D:href> <D:href>/workspace/webdav/</D:href>
</D:lock-token-present> </D:lock-token-submitted>
</D:error> </D:error>
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].
skipping to change at page 101, line 7 skipping to change at page 104, line 7
Purpose: The request could not succeed because a lock token should Purpose: The request could not succeed because a lock token should
have been submitted. This element, if present, MUST contain at have been submitted. This element, if present, MUST contain at
least one URL of a locked resource that prevented the request. In least one URL of a locked resource that prevented the request. In
cases of MOVE, COPY and DELETE where collection locks are cases of MOVE, COPY and DELETE where collection locks are
involved, it can be difficult for the client to find out which involved, it can be difficult for the client to find out which
locked resource made the request fail -- but the server is only locked resource made the request fail -- but the server is only
resonsible for returning one such locked resource. The server MAY resonsible for returning one such locked resource. The server MAY
return every locked resource that prevented the request from return every locked resource that prevented the request from
succeeding if it knows them all. succeeding if it knows them all.
<!ELEMENT lock-token-present (href+) > <!ELEMENT lock-token-submitted (href+) >
Name: no-conflicting-lock (precondition) Name: no-conflicting-lock (precondition)
Use with: Typically 423 Locked Use with: Typically 423 Locked
Purpose: A LOCK request failed due the presence of an already Purpose: A LOCK request failed due the presence of an already
existing conflicting lock. Note that a lock can be in conflict existing conflicting lock. Note that a lock can be in conflict
although the resource to which the request was directed is only although the resource to which the request was directed is only
indirectly locked. In this case, the precondition code can be indirectly locked. In this case, the precondition code can be
used to inform the client about the resource which is the root of used to inform the client about the resource which is the root of
skipping to change at page 102, line 9 skipping to change at page 105, line 9
<!ELEMENT preserved-live-properties EMPTY > <!ELEMENT preserved-live-properties 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: writable-property Name: cannot-modify-protected-property
Use with: 403 Forbidden Use with: 403 Forbidden
Purpose: (precondition) -- The client attempted to set a read-only Purpose: (precondition) -- The client attempted to set a read-only
property in a PROPPATCH (such as DAV:getetag). property in a PROPPATCH (such as DAV:getetag).
<!ELEMENT writable-property EMPTY > <!ELEMENT cannot-modify-protected-property EMPTY >
16. XML Extensibility in DAV 17. XML Extensibility in DAV
The XML namespace extension [W3C.REC-xml-names-19990114] is used in The XML namespace extension [W3C.REC-xml-names-19990114] is used in
this specification in order to allow for new XML elements to be added this specification in order to allow for new XML elements to be added
without fear of colliding with other element names. Although WebDAV without fear of colliding with other element names. Although WebDAV
request and response bodies can be extended by arbitrary XML request and response bodies can be extended by arbitrary XML
elements, which can be ignored by the message recipient, an 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 element in the "DAV:" namespace SHOULD NOT be used in the request or
response body unless that XML element is explicitly defined in an response body unless that XML element is explicitly defined in an
IETF RFC reviewed by a WebDAV working group. IETF RFC reviewed by a WebDAV working group.
Extensibility with backwards-compatibility requires that both clients For WebDAV to be both extensibile and backwards-compatible, both
and servers behave appropriately when unrecognized command extensions clients and servers need to know how to behave when unexpected or
are received. For XML processing, this means that clients and unrecognized command extensions are received. For XML processing,
servers MUST process received XML documents as if unrecognized this means that clients and servers MUST process received XML
elements (and all children) and unrecognized attributes were not documents as if unexpected elements and attributes (and all children
there. Ignoring custom elements for backwards-compatibility can of of unrecognized elements) were not there. An unexpected element or
course be consistent with logging all information or presenting for attribute includes one which may be used in another context but is
debugging. not expected here. Ignoring such items for purposes of processing
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 unexpected XML elements SHOULD be ignored
the property's schema declares otherwise. unless 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 all 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.
When XML is used for a request or response body, the Content-Type When XML is used for a request or response body, the Content-Type
type SHOULD be application/xml. Implementations MUST accept both type SHOULD be application/xml. Implementations MUST accept both
text/xml and application/xml in request and response bodies. Use of text/xml and application/xml in request and response bodies. Use of
text/xml is deprecated. text/xml is deprecated.
Processing instructions in XML SHOULD be ignored by recipients. Processing instructions in XML SHOULD be ignored by recipients.
Thus, specifications extending WebDAV SHOULD NOT use processing Thus, specifications extending WebDAV SHOULD NOT use processing
instructions to define normative behavior. 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, correct XML will not be valid according this specification. However, correct XML will not be valid according
to any DTD due to namespace usage and extension rules. In to any DTD due to namespace usage and extension rules. In
particular: particular:
All elements defined in this specification use the "DAV:" o All elements defined in this specification use the "DAV:"
namespace, namespace,
Element ordering is irrelevant unless otherwise stated,
Extension attributes MAY be added, o Element ordering is irrelevant unless otherwise stated,
For element type definitions of "ANY", the normative text o Extension attributes MAY be added,
o For element type definitions of "ANY", the normative text
definition for that element defines what can be in it and what definition for that element defines what can be in it and what
that means. that means.
For element type definitions of "#PCDATA", extension elements MUST o For element type definitions of "#PCDATA", extension elements MUST
NOT be added. NOT be added.
For other element type definitions, including "EMPTY", extension o For other element type definitions, including "EMPTY", extension
elements MAY be added. elements MAY be added.
Note that this means that elements containing elements cannot be Note that this means that elements containing elements cannot be
extended to contain text, and vice versa. extended to contain text, and vice versa.
With DTD validation relaxed by the rules above, the constraints With DTD validation relaxed by the rules above, the constraints
described by the DTD fragments are normative (see for example described by the DTD fragments are normative (see for example
Appendix A A recipient of a WebDAV message with an XML body MUST NOT 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- validate the XML document according to any hard-coded or dynamically-
declared DTD. declared DTD.
Note that this section describes backwards-compatible extensibility Note that this section describes backwards-compatible extensibility
rules. There might also be times when an extension is designed not rules. There might also be times when an extension is designed not
to be backwards-compatible, for example defining an extension that to be backwards-compatible, for example defining an extension that
reuses an XML element defined in this document but omitting one of reuses an XML element defined in this document but omitting one of
the child elements required by the DTDs in this specification. the child elements required by the DTDs in this specification.
17. DAV Compliance Classes 18. 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
like server was supported, even if that feature was not supported on like server was supported, even if that feature was not supported on
all servers. all servers.
Since this document describes extensions to the HTTP/1.1 protocol, Since this document describes extensions to the HTTP/1.1 protocol,
minimally all DAV compliant resources, clients, and proxies MUST be minimally all DAV compliant resources, clients, and proxies MUST be
compliant with [RFC2616]. compliant with [RFC2616].
A resource that is class 2 compliant must also be class 1 compliant, A resource that is class 2 compliant must also be class 1 compliant,
and a resource that is compliant with "bis" must also be class 1 and a resource that is class 3 compliant must also be class 1
compliant. compliant.
17.1. Class 1 18.1. Class 1
A class 1 compliant resource MUST meet all "MUST" requirements in all A class 1 compliant resource MUST meet all "MUST" requirements in all
sections of this document. sections of this document.
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 18.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' 18.3. Class 3
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. Advertising class 3 support in addition to
class 1 and 2 means that the server supports all the requirements in
this specification. Advertising class 3 and class 1 support, but not
class 2, means that the server supports all the requirements in this
specification except possibly those that involve locking support.
Example: Example:
DAV: 1, bis DAV: 1, 3
18. Internationalization Considerations 19. Internationalization Considerations
In the realm of internationalization, this specification complies In the realm of internationalization, this specification complies
with the IETF Character Set Policy [RFC2277]. In this specification, with the IETF Character Set Policy [RFC2277]. In this specification,
human-readable fields can be found either in the value of a property, human-readable fields can be found either in the value of a property,
or in an error message returned in a response entity body. In both or in an error message returned in a response entity body. In both
cases, the human-readable content is encoded using XML, which has cases, the human-readable content is encoded using XML, which has
explicit provisions for character set tagging and encoding, and explicit provisions for character set tagging and encoding, and
requires that XML processors read XML elements encoded, at minimum, requires that XML processors read XML elements encoded, at minimum,
using the UTF-8 [RFC3629] and UTF-16 encodings of the ISO 10646 using the UTF-8 [RFC3629] and UTF-16 encodings of the ISO 10646
multilingual plane. XML examples in this specification demonstrate multilingual plane. XML examples in this specification demonstrate
skipping to change at page 108, line 5 skipping to change at page 112, line 5
codes, including with each status code a short, English description codes, including with each status code a short, English description
of the code (e.g., 423 (Locked)). While the possibility exists that of the code (e.g., 423 (Locked)). While the possibility exists that
a poorly crafted user agent would display this message to a user, a poorly crafted user agent would display this message to a user,
internationalized applications will ignore this message, and display internationalized applications will ignore this message, and display
an appropriate message in the user's language and character set. an appropriate message in the user's language and character set.
Since interoperation of clients and servers does not require locale Since interoperation of clients and servers does not require locale
information, this specification does not specify any mechanism for information, this specification does not specify any mechanism for
transmission of this information. transmission of this information.
19. Security Considerations 20. Security Considerations
This section is provided to detail issues concerning security This section is provided to detail issues concerning security
implications of which WebDAV applications need to be aware. implications of which WebDAV applications need to be aware.
All of the security considerations of HTTP/1.1 (discussed in All of the security considerations of HTTP/1.1 (discussed in
[RFC2616]) and XML (discussed in [RFC3023]) also apply to WebDAV. In [RFC2616]) and XML (discussed in [RFC3023]) also apply to WebDAV. In
addition, the security risks inherent in remote authoring require addition, the security risks inherent in remote authoring require
stronger authentication technology, introduce several new privacy stronger authentication technology, introduce several new privacy
concerns, and may increase the hazards from poor server design. concerns, and may increase the hazards from poor server design.
These issues are detailed below. These issues are detailed below.
19.1. Authentication of Clients 20.1. Authentication of Clients
Due to their emphasis on authoring, WebDAV servers need to use Due to their emphasis on authoring, WebDAV servers need to use
authentication technology to protect not just access to a network authentication technology to protect not just access to a network
resource, but the integrity of the resource as well. Furthermore, resource, but the integrity of the resource as well. Furthermore,
the introduction of locking functionality requires support for the introduction of locking functionality requires support for
authentication. authentication.
A password sent in the clear over an insecure channel is an A password sent in the clear over an insecure channel is an
inadequate means for protecting the accessibility and integrity of a inadequate means for protecting the accessibility and integrity of a
resource as the password may be intercepted. Since Basic resource as the password may be intercepted. Since Basic
skipping to change at page 108, line 46 skipping to change at page 112, line 46
connection over a network which is physically secure, for example, an connection over a network which is physically secure, for example, an
isolated network in a building with restricted access. isolated network in a building with restricted access.
WebDAV applications MUST support the Digest authentication scheme WebDAV applications MUST support the Digest authentication scheme
[RFC2617]. Since Digest authentication verifies that both parties to [RFC2617]. Since Digest authentication verifies that both parties to
a communication know a shared secret, a password, without having to a communication know a shared secret, a password, without having to
send that secret in the clear, Digest authentication avoids the send that secret in the clear, Digest authentication avoids the
security problems inherent in Basic authentication while providing a security problems inherent in Basic authentication while providing a
level of authentication which is useful in a wide range of scenarios. level of authentication which is useful in a wide range of scenarios.
19.2. Denial of Service 20.2. Denial of Service
Denial of service attacks are of special concern to WebDAV servers. Denial of service attacks are of special concern to WebDAV servers.
WebDAV plus HTTP enables denial of service attacks on every part of a WebDAV plus HTTP enables denial of service attacks on every part of a
system's resources. system's resources.
o The underlying storage can be attacked by PUTting extremely large o The underlying storage can be attacked by PUTting extremely large
files. files.
o Asking for recursive operations on large collections can attack o Asking for recursive operations on large collections can attack
processing time. processing time.
skipping to change at page 109, line 23 skipping to change at page 113, line 23
WebDAV servers need to be aware of the possibility of a denial of WebDAV servers need to be aware of the possibility of a denial of
service attack at all levels. The proper response to such an attack service attack at all levels. The proper response to such an attack
MAY be to simply drop the connection, or if the server is able to MAY be to simply drop the connection, or if the server is able to
make a response, the server MAY use a 400-level status request such make a response, the server MAY use a 400-level status request such
as 400 (Bad Request) and indicate why the request was refused (a 500- as 400 (Bad Request) and indicate why the request was refused (a 500-
level status response would indicate that the problem is with the level status response would indicate that the problem is with the
server, whereas unintentional DOS attacks are something the client is server, whereas unintentional DOS attacks are something the client is
capable of remedying). capable of remedying).
19.3. Security through Obscurity 20.3. Security through Obscurity
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 20.4. Privacy Issues Connected to Locks
When submitting a lock request a user agent may also submit an When submitting a lock request a user agent may also submit an
'owner' XML field giving contact information for the person taking 'owner' XML field giving contact information for the person taking
out the lock (for those cases where a person, rather than a robot, is out the lock (for those cases where a person, rather than a robot, is
taking 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 20.5. Privacy Issues Connected to Properties
Since property values are typically used to hold information such as Since property values are typically used to hold information such as
the author of a document, there is the possibility that privacy the author of a document, there is the possibility that privacy
concerns could arise stemming from widespread access to a resource's concerns could arise stemming from widespread access to a resource's
property data. To reduce the risk of inadvertent release of private property data. To reduce the risk of inadvertent release of private
information via properties, servers are encouraged to develop access information via properties, servers are encouraged to develop access
control mechanisms that separate read access to the resource body and control mechanisms that separate read access to the resource body and
read access to the resource's properties. This allows a user to read access to the resource's properties. This allows a user to
control the dissemination of their property data without overly control the dissemination of their property data without overly
restricting access to the resource's contents. restricting access to the resource's contents.
19.6. Implications of XML Entities 20.6. Implications of XML Entities
XML supports a facility known as "external entities", defined in XML supports a facility known as "external entities", defined in
section 4.2.2 of [XML], which instruct an XML processor to retrieve section 4.2.2 of [XML], which instruct an XML processor to retrieve
and include additional XML. An external XML entity can be used to and include additional XML. An external XML entity can be used to
append or modify the document type declaration (DTD) associated with append or modify the document type declaration (DTD) associated with
an XML document. An external XML entity can also be used to include an XML document. An external XML entity can also be used to include
XML within the content of an XML document. For non-validating XML, XML within the content of an XML document. For non-validating XML,
such as the XML used in this specification, including an external XML such as the XML used in this specification, including an external XML
entity is not required by XML. However, XML does state that an XML entity is not required by XML. However, XML does state that an XML
processor may, at its discretion, include the external XML entity. processor may, at its discretion, include the external XML entity.
skipping to change at page 111, line 5 skipping to change at page 115, line 5
containing the external XML entity. containing the external XML entity.
Furthermore, there's also a risk based on the evaluation of "internal Furthermore, there's also a risk based on the evaluation of "internal
entities" as defined in section 4.2.2 of [XML]. A small, carefully entities" as defined in section 4.2.2 of [XML]. A small, carefully
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 20.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.4, in order to guarantee their uniqueness across space and Section 6.5, in order to guarantee their uniqueness across space and
time. Version 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". Since a WebDAV server will issue many locks over its can be used". Since a WebDAV server will issue many locks over its
lifetime, the implication is that it may also be publicly exposing lifetime, the implication is that it may also be publicly exposing
its IEEE 802 address. 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:
skipping to change at page 111, line 34 skipping to change at page 115, line 34
running a WebDAV server. running a WebDAV server.
o It may be possible to determine the number of each type of o It may be possible to determine the number of each type of
computer running WebDAV. computer running WebDAV.
This risk only applies to host address based UUID versions. Section This risk only applies to host address based UUID versions. Section
4 of [RFC4122] describes several other mechanisms for generating 4 of [RFC4122] describes several other mechanisms for generating
UUIDs that do involve the host address and therefore do not suffer UUIDs that do involve the host address and therefore do not suffer
from this risk. from this risk.
19.8. Hosting malicious scripts executed on client machines 20.8. Hosting Malicious Content
HTTP has the ability to host scripts which are executed on client
machines. These scripts can be used to read another user's cookies
and therefore may provide an attacker the ability to use another
user's session, assume their identity temporarily and gain access to
their resources. Other attacks are also possible with client-
executed scripts.
WebDAV may worsen this situation only by making it easier for a Web
server to host content provided by many different authors (making it
harder to trust the content providers) and to host content with
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
in areas where many authors contribute pages -- the server could, for
example, remove script from HTML pages.
This vulnerability should provide yet another reason for server
implementors and administrators not to replace authentication
mechanisms with cookie-based session tokens if there's any sensitive
information relying on the authenticated identity.
HTTP and WebDAV client implementors might consider locking down the HTTP has the ability to host programs which are executed on client
use of scripts and cookies based on these considerations. machines. These programs can take many forms including web scripts,
executables, plug in modules, and macros in documents. WebDAV does
not change any of the security concerns around these programs yet
often WebDAV is used in contexts where a wide range of users can
publish documents on a server. The server might not have a close
trust relationship with the author that is publishing the document.
Servers that allow clients to publish arbitrary content can usefully
implement precautions to check that content published to the server
is not harmful to other clients. Servers could do this by techniques
such as restricting the types of content that is allowed to be
published and running virus and malware detection software on
published content. Servers can also mitigate the risk by having
appropriate access restriction and authentication of users that are
allowed to publish content to the server.
20. IANA Considerations 21. IANA Considerations
20.1. New URI Schemes 21.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 Note that defining new URI schemes for XML namespaces is now
discouraged. "DAV:" was defined before standard best practices discouraged. "DAV:" was defined before standard best practices
emerged. emerged.
20.2. XML Namespaces 21.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 21.3. Message Header Fields
The message header fields below should be added to the permanent The message header fields below should be added to the permanent
registry (see [RFC3864]). registry (see [RFC3864]).
20.3.1. DAV 21.3.1. DAV
Header field name: DAV Header field name: DAV
Applicable protocol: http Applicable protocol: http
Status: standard Status: standard
Author/Change controller: IETF Author/Change controller: IETF
Specification document: this specification (Section 9.1) Specification document: this specification (Section 10.1)
20.3.2. Depth 21.3.2. Depth
Header field name: Depth Header field name: Depth
Applicable protocol: http Applicable protocol: http
Status: standard Status: standard
Author/Change controller: IETF Author/Change controller: IETF
Specification document: this specification (Section 9.2) Specification document: this specification (Section 10.2)
20.3.3. Destination 21.3.3. Destination
Header field name: Destination Header field name: Destination
Applicable protocol: http Applicable protocol: http
Status: standard Status: standard
Author/Change controller: IETF Author/Change controller: IETF
Specification document: this specification (Section 9.3) Specification document: this specification (Section 10.3)
20.3.4. If 21.3.4. If
Header field name: If Header field name: If
Applicable protocol: http Applicable protocol: http
Status: standard Status: standard
Author/Change controller: IETF Author/Change controller: IETF
Specification document: this specification (Section 9.4) Specification document: this specification (Section 10.4)
20.3.5. Lock-Token 21.3.5. Lock-Token
Header field name: Lock-Token Header field name: Lock-Token
Applicable protocol: http Applicable protocol: http
Status: standard Status: standard
Author/Change controller: IETF Author/Change controller: IETF
Specification document: this specification (Section 9.5) Specification document: this specification (Section 10.5)
20.3.6. Overwrite 21.3.6. Overwrite
Header field name: Overwrite Header field name: Overwrite
Applicable protocol: http Applicable protocol: http
Status: standard Status: standard
Author/Change controller: IETF Author/Change controller: IETF
Specification document: this specification (Section 9.6) Specification document: this specification (Section 10.6)
20.3.7. Timeout 21.3.7. Timeout
Header field name: Timeout Header field name: Timeout
Applicable protocol: http Applicable protocol: http
Status: standard Status: standard
Author/Change controller: IETF Author/Change controller: IETF
Specification document: this specification (Section 9.7) Specification document: this specification (Section 10.7)
21. Acknowledgements 22. 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
Babich, Sanford Barr, Dylan Barrell, Bernard Chester, Tim Berners- Babich, Sanford Barr, Dylan Barrell, Bernard Chester, Tim Berners-
skipping to change at page 116, line 52 skipping to change at page 119, line 52
due to IETF author count restrictions they can take credit for the due to IETF author count restrictions they can take credit for the
majority of the design of WebDAV. majority of the design of WebDAV.
Additional Contributors to This Specification Additional Contributors to This Specification
Valuable contributions to this specification came from some already Valuable contributions to this specification came from some already
named. New and significant contributors to this specification must named. New and significant contributors to this specification must
also be gratefully acknowledged. Julian Reschke, Geoff Clemm, Joel also be gratefully acknowledged. Julian Reschke, Geoff Clemm, Joel
Soderberg, and Dan Brotsky hashed out specific text on the list or in Soderberg, and Dan Brotsky hashed out specific text on the list or in
meetings. Joe Hildebrand and Cullen Jennings helped close many meetings. Joe Hildebrand and Cullen Jennings helped close many
issues. Barry Lind described an additional security consideration. issues. Barry Lind described an additional security consideration
and Cullen Jennings provided text for that consideration. Jason
Jason Crawford tracked issue status for this document for a period of Crawford tracked issue status for this document for a period of
years, followed by Elias Sinderson. Elias and Jim Whitehead years, followed by Elias Sinderson. Elias and Jim Whitehead
collaborated on specific document text. collaborated on specific document text.
21.1. Previous Authors' Addresses 22.1. Previous Authors' Addresses
Y. Y. Goland, Microsoft Corporation, One Microsoft Way, Redmond, WA Y. Y. Goland, Microsoft Corporation, One Microsoft Way, Redmond, WA
98052-6399. Email: yarong@microsoft.com. 98052-6399. Email: yarong@microsoft.com.
E. J. Whitehead, Jr., Dept. Of Information and Computer Science, E. J. Whitehead, Jr., Dept. Of Information and Computer Science,
University of California, Irvine, Irvine, CA 92697-3425. Email: University of California, Irvine, Irvine, CA 92697-3425. Email:
ejw@ics.uci.edu. ejw@ics.uci.edu.
A. Faizi, Netscape, 685 East Middlefield Road, Mountain View, CA A. Faizi, Netscape, 685 East Middlefield Road, Mountain View, CA
94043. Email: asad@netscape.com. 94043. Email: asad@netscape.com.
S. R. Carter, Novell, 1555 N. Technology Way, M/S ORM F111, Orem, UT S. R. Carter, Novell, 1555 N. Technology Way, M/S ORM F111, Orem, UT
84097-2399. Email: srcarter@novell.com. 84097-2399. Email: srcarter@novell.com.
D. Jensen, Novell, 1555 N. Technology Way, M/S ORM F111, Orem, UT D. Jensen, Novell, 1555 N. Technology Way, M/S ORM F111, Orem, UT
84097-2399. Email: dcjensen@novell.com. 84097-2399. Email: dcjensen@novell.com.
22. References 23. References
22.1. Normative References 23.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.