Debian Codegraph @

rfc5842.html

raw
1 <pre>Internet Engineering Task Force (IETF) G. Clemm
2 Request for Comments: 5842 IBM
3 Category: Experimental J. Crawford
4 ISSN: 2070-1721 IBM Research
5 J. Reschke, Ed.
6 greenbytes
7 J. Whitehead
8 U.C. Santa Cruz
9 April 2010
10
11
12 <span class="h1">Binding Extensions to</span>
13 <span class="h1">Web Distributed Authoring and Versioning (WebDAV)</span>
14
15 Abstract
16
17 This specification defines bindings, and the BIND method for creating
18 multiple bindings to the same resource. Creating a new binding to a
19 resource causes at least one new URI to be mapped to that resource.
20 Servers are required to ensure the integrity of any bindings that
21 they allow to be created.
22
23 Status of This Memo
24
25 This document is not an Internet Standards Track specification; it is
26 published for examination, experimental implementation, and
27 evaluation.
28
29 This document defines an Experimental Protocol for the Internet
30 community. This document is a product of the Internet Engineering
31 Task Force (IETF). It represents the consensus of the IETF
32 community. It has received public review and has been approved for
33 publication by the Internet Engineering Steering Group (IESG). Not
34 all documents approved by the IESG are a candidate for any level of
35 Internet Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
36
37 Information about the current status of this document, any errata,
38 and how to provide feedback on it may be obtained at
39 <a href="http://www.rfc-editor.org/info/rfc5842">http://www.rfc-editor.org/info/rfc5842</a>.
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Clemm, et al. Experimental [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2010 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 This document may contain material from IETF Documents or IETF
73 Contributions published or made publicly available before November
74 10, 2008. The person(s) controlling the copyright in some of this
75 material may not have granted the IETF Trust the right to allow
76 modifications of such material outside the IETF Standards Process.
77 Without obtaining an adequate license from the person(s) controlling
78 the copyright in such materials, this document may not be modified
79 outside the IETF Standards Process, and derivative works of it may
80 not be created outside the IETF Standards Process, except to format
81 it for publication as an RFC or to translate it into languages other
82 than English.
83
84 Table of Contents
85
86 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
87 <a href="#section-1.1">1.1</a>. Terminology ................................................<a href="#page-5">5</a>
88 <a href="#section-1.2">1.2</a>. Method Preconditions and Postconditions ....................<a href="#page-6">6</a>
89 <a href="#section-2">2</a>. Overview of Bindings ............................................<a href="#page-7">7</a>
90 <a href="#section-2.1">2.1</a>. Bindings to Collections ....................................<a href="#page-7">7</a>
91 <a href="#section-2.1.1">2.1.1</a>. Bind Loops ..........................................<a href="#page-8">8</a>
92 <a href="#section-2.2">2.2</a>. URI Mappings Created by a New Binding ......................<a href="#page-8">8</a>
93 <a href="#section-2.3">2.3</a>. COPY and Bindings ..........................................<a href="#page-9">9</a>
94 2.3.1. Example: COPY with "Depth: infinity" in
95 Presence of Bind Loops .............................<a href="#page-11">11</a>
96 <a href="#section-2.3.2">2.3.2</a>. Example: COPY Updating Multiple Bindings ...........<a href="#page-13">13</a>
97 2.3.3. Example: COPY with "Depth: infinity" with
98 Multiple Bindings to a Leaf Resource ...............<a href="#page-14">14</a>
99 <a href="#section-2.4">2.4</a>. DELETE and Bindings .......................................<a href="#page-15">15</a>
100 <a href="#section-2.5">2.5</a>. MOVE and Bindings .........................................<a href="#page-15">15</a>
101 <a href="#section-2.5.1">2.5.1</a>. Example: Simple MOVE ...............................<a href="#page-16">16</a>
102 <a href="#section-2.5.2">2.5.2</a>. Example: MOVE Request Causing a Bind Loop ..........<a href="#page-16">16</a>
103 <a href="#section-2.6">2.6</a>. PROPFIND and Bindings .....................................<a href="#page-18">18</a>
104
105
106
107
108 <span class="grey">Clemm, et al. Experimental [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
111
112
113 2.7. Determining Whether Two Bindings Are to the Same
114 Resource ..................................................<a href="#page-18">18</a>
115 <a href="#section-2.8">2.8</a>. Discovering the Bindings to a Resource ....................<a href="#page-19">19</a>
116 <a href="#section-3">3</a>. Properties .....................................................<a href="#page-19">19</a>
117 <a href="#section-3.1">3.1</a>. DAV:resource-id Property ..................................<a href="#page-20">20</a>
118 <a href="#section-3.2">3.2</a>. DAV:parent-set Property ...................................<a href="#page-20">20</a>
119 <a href="#section-3.2.1">3.2.1</a>. Example for DAV:parent-set Property ................<a href="#page-20">20</a>
120 <a href="#section-4">4</a>. BIND Method ....................................................<a href="#page-21">21</a>
121 <a href="#section-4.1">4.1</a>. Example: BIND .............................................<a href="#page-24">24</a>
122 <a href="#section-5">5</a>. UNBIND Method ..................................................<a href="#page-24">24</a>
123 <a href="#section-5.1">5.1</a>. Example: UNBIND ...........................................<a href="#page-26">26</a>
124 <a href="#section-6">6</a>. REBIND Method ..................................................<a href="#page-26">26</a>
125 <a href="#section-6.1">6.1</a>. Example: REBIND ...........................................<a href="#page-28">28</a>
126 <a href="#section-6.2">6.2</a>. Example: REBIND in Presence of Locks and Bind Loops .......<a href="#page-29">29</a>
127 <a href="#section-7">7</a>. Additional Status Codes ........................................<a href="#page-31">31</a>
128 <a href="#section-7.1">7.1</a>. 208 Already Reported ......................................<a href="#page-31">31</a>
129 <a href="#section-7.1.1">7.1.1</a>. Example: PROPFIND by Bind-Aware Client .............<a href="#page-32">32</a>
130 <a href="#section-7.1.2">7.1.2</a>. Example: PROPFIND by Non-Bind-Aware Client .........<a href="#page-34">34</a>
131 <a href="#section-7.2">7.2</a>. 508 Loop Detected .........................................<a href="#page-34">34</a>
132 <a href="#section-8">8</a>. Capability Discovery ...........................................<a href="#page-34">34</a>
133 <a href="#section-8.1">8.1</a>. OPTIONS Method ............................................<a href="#page-34">34</a>
134 <a href="#section-8.2">8.2</a>. 'DAV' Request Header ......................................<a href="#page-34">34</a>
135 <a href="#section-9">9</a>. Relationship to Locking in WebDAV ..............................<a href="#page-35">35</a>
136 <a href="#section-9.1">9.1</a>. Example: Locking and Multiple Bindings ....................<a href="#page-36">36</a>
137 <a href="#section-10">10</a>. Relationship to WebDAV Access Control Protocol ................<a href="#page-37">37</a>
138 <a href="#section-11">11</a>. Relationship to Versioning Extensions to WebDAV ...............<a href="#page-37">37</a>
139 <a href="#section-12">12</a>. Security Considerations .......................................<a href="#page-40">40</a>
140 <a href="#section-12.1">12.1</a>. Privacy Concerns .........................................<a href="#page-40">40</a>
141 <a href="#section-12.2">12.2</a>. Bind Loops ...............................................<a href="#page-40">40</a>
142 <a href="#section-12.3">12.3</a>. Bindings and Denial of Service ...........................<a href="#page-40">40</a>
143 <a href="#section-12.4">12.4</a>. Private Locations May Be Revealed ........................<a href="#page-40">40</a>
144 <a href="#section-12.5">12.5</a>. DAV:parent-set and Denial of Service .....................<a href="#page-41">41</a>
145 <a href="#section-13">13</a>. Internationalization Considerations ...........................<a href="#page-41">41</a>
146 <a href="#section-14">14</a>. IANA Considerations ...........................................<a href="#page-41">41</a>
147 <a href="#section-15">15</a>. Acknowledgements ..............................................<a href="#page-41">41</a>
148 <a href="#section-16">16</a>. References ....................................................<a href="#page-41">41</a>
149 <a href="#section-16.1">16.1</a>. Normative References .....................................<a href="#page-41">41</a>
150 <a href="#section-16.2">16.2</a>. Informative References ...................................<a href="#page-42">42</a>
151 Index .............................................................<a href="#page-42">42</a>
152
153
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Clemm, et al. Experimental [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
167
168
169 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
170
171 This specification extends the WebDAV Distributed Authoring Protocol
172 ([<a href="./rfc4918" title="&quot;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)&quot;">RFC4918</a>]) to enable clients to create new access paths to existing
173 resources. This capability is useful for several reasons:
174
175 URIs of WebDAV-compliant resources are hierarchical and correspond to
176 a hierarchy of collections in resource space. The WebDAV Distributed
177 Authoring Protocol makes it possible to organize these resources into
178 hierarchies, placing them into groupings, known as collections, which
179 are more easily browsed and manipulated than a single flat
180 collection. However, hierarchies require categorization decisions
181 that locate resources at a single location in the hierarchy, a
182 drawback when a resource has multiple valid categories. For example,
183 in a hierarchy of vehicle descriptions containing collections for
184 cars and boats, a description of a combination car/boat vehicle could
185 belong in either collection. Ideally, the description should be
186 accessible from both. Allowing clients to create new URIs that
187 access the existing resource lets them put that resource into
188 multiple collections.
189
190 Hierarchies also make resource sharing more difficult, since
191 resources that have utility across many collections are still forced
192 into a single collection. For example, the mathematics department at
193 one university might create a collection of information on fractals
194 that contains bindings to some local resources but also provides
195 access to some resources at other universities. For many reasons, it
196 may be undesirable to make physical copies of the shared resources on
197 the local server, for example, to conserve disk space, to respect
198 copyright constraints, or to make any changes in the shared resources
199 visible automatically. Being able to create new access paths to
200 existing resources in other collections or even on other servers is
201 useful for this sort of case.
202
203 The BIND method, defined here, provides a mechanism for allowing
204 clients to create alternative access paths to existing WebDAV
205 resources. HTTP [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>] and WebDAV [<a href="./rfc4918" title="&quot;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)&quot;">RFC4918</a>] methods are able to
206 work because there are mappings between URIs and resources. A method
207 is addressed to a URI, and the server follows the mapping from that
208 URI to a resource, applying the method to that resource. Multiple
209 URIs may be mapped to the same resource, but until now, there has
210 been no way for clients to create additional URIs mapped to existing
211 resources.
212
213 BIND lets clients associate a new URI with an existing WebDAV
214 resource, and this URI can then be used to submit requests to the
215 resource. Since URIs of WebDAV resources are hierarchical, and
216 correspond to a hierarchy of collections in resource space, the BIND
217
218
219
220 <span class="grey">Clemm, et al. Experimental [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
223
224
225 method also has the effect of adding the resource to a collection.
226 As new URIs are associated with the resource, it appears in
227 additional collections.
228
229 A BIND request does not create a new resource, but simply makes a new
230 URI for submitting requests to an existing resource available. The
231 new URI is indistinguishable from any other URI when submitting a
232 request to a resource. Only one round trip is needed to submit a
233 request to the intended target. Servers are required to enforce the
234 integrity of the relationships between the new URIs and the resources
235 associated with them. Consequently, it may be very costly for
236 servers to support BIND requests that cross server boundaries.
237
238 This specification is organized as follows. <a href="#section-1.1">Section 1.1</a> defines
239 terminology used in the rest of the specification, while <a href="#section-2">Section 2</a>
240 overviews bindings. <a href="#section-3">Section 3</a> defines the new properties needed to
241 support multiple bindings to the same resource. <a href="#section-4">Section 4</a> specifies
242 the BIND method, used to create multiple bindings to the same
243 resource. <a href="#section-5">Section 5</a> specifies the UNBIND method, used to remove a
244 binding to a resource. <a href="#section-6">Section 6</a> specifies the REBIND method, used
245 to move a binding to another collection.
246
247 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
248
249 The terminology used here follows and extends that in the WebDAV
250 Distributed Authoring Protocol specification [<a href="./rfc4918" title="&quot;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)&quot;">RFC4918</a>].
251
252 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
253 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
254 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
255
256 This document uses XML DTD fragments ([<a href="#ref-XML" title="&quot;Extensible Markup Language (XML) 1.0 (Fifth Edition)&quot;">XML</a>]) as a notational
257 convention, using the rules defined in <a href="./rfc4918#section-17">Section&nbsp;17 of [RFC4918]</a>.
258
259 URI Mapping
260
261 A relation between an absolute URI and a resource. For an
262 absolute URI U and the resource it identifies R, the URI mapping
263 can be thought of as (U =&gt; R). Since a resource can represent
264 items that are not network retrievable as well as those that are,
265 it is possible for a resource to have zero, one, or many URI
266 mappings. Mapping a resource to an "http"-scheme URI makes it
267 possible to submit HTTP requests to the resource using the URI.
268
269 Path Segment
270
271 Informally, the characters found between slashes ("/") in a URI.
272 Formally, as defined in <a href="./rfc3986#section-3.3">Section&nbsp;3.3 of [RFC3986]</a>.
273
274
275
276 <span class="grey">Clemm, et al. Experimental [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
279
280
281 Binding
282
283 A relation between a single path segment (in a collection) and a
284 resource. A binding is part of the state of a collection. If two
285 different collections contain a binding between the same path
286 segment and the same resource, these are two distinct bindings.
287 So for a collection C, a path segment S, and a resource R, the
288 binding can be thought of as C:(S -&gt; R). Bindings create URI
289 mappings, and hence allow requests to be sent to a single resource
290 from multiple locations in a URI namespace. For example, given a
291 collection C (accessible through the URI
292 http://www.example.com/CollX), a path segment S (equal to
293 "foo.html"), and a resource R, then creating the binding C: (S -&gt;
294 R) makes it possible to use the URI
295 http://www.example.com/CollX/foo.html to access R.
296
297 Collection
298
299 A resource that contains, as part of its state, a set of bindings
300 that identify internal member resources.
301
302 Internal Member URI
303
304 The URI that identifies an internal member of a collection and
305 that consists of the URI for the collection, followed by a slash
306 character ('/'), followed by the path segment of the binding for
307 that internal member.
308
309 Binding Integrity
310
311 The property of a binding that says that:
312
313 * the binding continues to exist, and
314
315 * the identity of the resource identified by that binding does
316 not change,
317
318 unless an explicit request is executed that is defined to delete
319 that binding (examples of requests that delete a binding are
320 DELETE, MOVE, and -- defined later on -- UNBIND and REBIND).
321
322 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Method Preconditions and Postconditions</span>
323
324 See <a href="./rfc4918#section-16">Section&nbsp;16 of [RFC4918]</a> for the definitions of "precondition" and
325 "postcondition".
326
327
328
329
330
331
332 <span class="grey">Clemm, et al. Experimental [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
335
336
337 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Overview of Bindings</span>
338
339 Bindings are part of the state of a collection. They define the
340 internal members of the collection and the names of those internal
341 members.
342
343 Bindings are added and removed by a variety of existing HTTP methods.
344 A method that creates a new resource, such as PUT, COPY, and MKCOL,
345 adds a binding. A method that deletes a resource, such as DELETE,
346 removes a binding. A method that moves a resource (e.g., MOVE) both
347 adds a binding (in the destination collection) and removes a binding
348 (in the source collection). The BIND method introduced here provides
349 a mechanism for adding a second binding to an existing resource.
350 There is no difference between an initial binding added by PUT, COPY,
351 or MKCOL and additional bindings added with BIND.
352
353 It would be very undesirable if one binding could be destroyed as a
354 side effect of operating on the resource through a different binding.
355 In particular, the removal of one binding to a resource (e.g., with a
356 DELETE or a MOVE) MUST NOT disrupt another binding to that resource,
357 e.g., by turning that binding into a dangling path segment. The
358 server MUST NOT reclaim system resources after removing one binding,
359 while other bindings to the resource remain. In other words, the
360 server MUST maintain the integrity of a binding. It is permissible,
361 however, for future method definitions (e.g., a DESTROY method) to
362 have semantics that explicitly remove all bindings and/or immediately
363 reclaim system resources.
364
365 Note: the collection model described herein is not compatible with
366 systems in which resources inherit properties based solely on the
367 access path, as the ability to create additional bindings will
368 cause a single resource to appear as member of several different
369 collections at the same time.
370
371 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Bindings to Collections</span>
372
373 Creating a new binding to a collection makes each resource associated
374 with a binding in that collection accessible via a new URI, and thus
375 creates new URI mappings to those resources but no new bindings.
376
377 For example, suppose a new binding CollY is created for collection C1
378 in the figure below. It immediately becomes possible to access
379 resource R1 using the URI /CollY/x.gif and to access resource R2
380 using the URI /CollY/y.jpg, but no new bindings for these child
381 resources were created. This is because bindings are part of the
382 state of a collection, and they associate a URI that is relative to
383
384
385
386
387
388 <span class="grey">Clemm, et al. Experimental [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
391
392
393 that collection with its target resource. No change to the bindings
394 in Collection C1 is needed to make its children accessible using
395 /CollY/x.gif and /CollY/y.jpg.
396
397 +-------------------------+
398 | Root Collection |
399 | bindings: |
400 | CollX CollY |
401 +-------------------------+
402 | /
403 | /
404 | /
405 +------------------+
406 | Collection C1 |
407 | bindings: |
408 | x.gif y.jpg |
409 +------------------+
410 | \
411 | \
412 | \
413 +-------------+ +-------------+
414 | Resource R1 | | Resource R2 |
415 +-------------+ +-------------+
416
417 <span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>. Bind Loops</span>
418
419 Bindings to collections can result in loops ("cycles"), which servers
420 MUST detect when processing "Depth: infinity" requests. It is
421 sometimes possible to complete an operation in spite of the presence
422 of a loop. For instance, a PROPFIND can still succeed if the server
423 uses the new status code 208 (Already Reported) defined in
424 <a href="#section-7.1">Section 7.1</a>.
425
426 However, the 508 (Loop Detected) status code is defined in
427 <a href="#section-7.2">Section 7.2</a> for use in contexts where an operation is terminated
428 because a loop was encountered.
429
430 Support for loops is OPTIONAL: servers MAY reject requests that would
431 lead to the creation of a bind loop (see DAV:cycle-allowed
432 precondition defined in <a href="#section-4">Section 4</a>).
433
434 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. URI Mappings Created by a New Binding</span>
435
436 Suppose a binding from "Binding-Name" to resource R is to be added to
437 a collection, C. Then if C-MAP is the set of URIs that were mapped
438 to C before the BIND request, then for each URI "C-URI" in C-MAP, the
439 URI "C-URI/Binding-Name" is mapped to resource R following the BIND
440 request.
441
442
443
444 <span class="grey">Clemm, et al. Experimental [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
447
448
449 For example, if a binding from "foo.html" to R is added to a
450 collection C, and if the following URIs are mapped to C:
451
452 http://www.example.com/A/1/
453 http://example.com/A/one/
454
455 then the following new mappings to R are introduced:
456
457 http://www.example.com/A/1/foo.html
458 http://example.com/A/one/foo.html
459
460 Note that if R is a collection, additional URI mappings are created
461 to the descendents of R. Also, note that if a binding is made in
462 collection C to C itself (or to a parent of C), an infinite number of
463 mappings are introduced.
464
465 For example, if a binding from "myself" to C is then added to C, the
466 following infinite number of additional mappings to C are introduced:
467
468 http://www.example.com/A/1/myself
469 http://www.example.com/A/1/myself/myself
470 ...
471
472 and the following infinite number of additional mappings to R are
473 introduced:
474
475 http://www.example.com/A/1/myself/foo.html
476 http://www.example.com/A/1/myself/myself/foo.html
477 ...
478
479 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. COPY and Bindings</span>
480
481 As defined in <a href="./rfc4918#section-9.8">Section&nbsp;9.8 of [RFC4918]</a>, COPY causes the resource
482 identified by the Request-URI to be duplicated and makes the new
483 resource accessible using the URI specified in the Destination
484 header. Upon successful completion of a COPY, a new binding is
485 created between the last path segment of the Destination header and
486 the destination resource. The new binding is added to its parent
487 collection, identified by the Destination header minus its final
488 segment.
489
490
491
492
493
494
495
496
497
498
499
500 <span class="grey">Clemm, et al. Experimental [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
503
504
505 The following figure shows an example: suppose that a COPY is issued
506 to URI-3 for resource R (which is also mapped to URI-1 and URI-2),
507 with the Destination header set to URI-X. After successful
508 completion of the COPY operation, resource R is duplicated to create
509 resource R', and a new binding has been created that creates at least
510 the URI mapping between URI-X and the new resource (although other
511 URI mappings may also have been created).
512
513 URI-1 URI-2 URI-3 URI-X
514 | | | |
515 | | | &lt;---- URI Mappings ----&gt; |
516 | | | |
517 +---------------------+ +------------------------+
518 | Resource R | | Resource R' |
519 +---------------------+ +------------------------+
520
521 It might be thought that a COPY request with "Depth: 0" on a
522 collection would duplicate its bindings, since bindings are part of
523 the collection's state. This is not the case, however. The
524 definition of Depth in [<a href="./rfc4918" title="&quot;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)&quot;">RFC4918</a>] makes it clear that a "Depth: 0"
525 request does not apply to a collection's members. Consequently, a
526 COPY with "Depth: 0" does not duplicate the bindings contained by the
527 collection.
528
529 If a COPY request causes an existing resource to be updated, the
530 bindings to that resource MUST be unaffected by the COPY request.
531 Using the preceding example, suppose that a COPY request is issued to
532 URI-X for resource R', with the Destination header set to URI-2. The
533 content and dead properties of resource R would be updated to be a
534 copy of those of resource R', but the mappings from URI-1, URI-2, and
535 URI-3 to resource R remain unaffected. If, because of multiple
536 bindings to a resource, more than one source resource updates a
537 single destination resource, the order of the updates is server
538 defined (see <a href="#section-2.3.2">Section 2.3.2</a> for an example).
539
540 If a COPY request would cause a new resource to be created as a copy
541 of an existing resource, and that COPY request has already created a
542 copy of that existing resource, the COPY request instead creates
543 another binding to the previous copy, instead of creating a new
544 resource (see <a href="#section-2.3.3">Section 2.3.3</a> for an example).
545
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Clemm, et al. Experimental [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
559
560
561 <span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a>. Example: COPY with "Depth: infinity" in Presence of Bind Loops</span>
562
563 As an example of how COPY with "Depth: infinity" would work in the
564 presence of bindings, consider the following collection:
565
566 +------------------+
567 | Root Collection |
568 | bindings: |
569 | CollX |
570 +------------------+
571 |
572 |
573 +-------------------------------+
574 | Collection C1 |&lt;-------+
575 | bindings: | |
576 | x.gif CollY | |
577 +-------------------------------+ |
578 | \ (creates loop) |
579 | \ |
580 +-------------+ +------------------+ |
581 | Resource R1 | | Collection C2 | |
582 +-------------+ | bindings: | |
583 | y.gif CollZ | |
584 +------------------+ |
585 | | |
586 | +--------+
587 |
588 +-------------+
589 | Resource R2 |
590 +-------------+
591
592 If a COPY request with "Depth: infinity" is submitted to /CollX, with
593 a destination of /CollA, the outcome of the copy operation is that a
594 copy of the tree is replicated to the target /CollA:
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Clemm, et al. Experimental [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
615
616
617 +------------------+
618 | Root Collection |
619 | bindings: |
620 | CollX CollA |
621 +------------------+
622 | |
623 | +---------------------------+
624 | |
625 +-------------------+ |
626 | Collection C1 |&lt;------------------+ |
627 | bindings: | | |
628 | x.gif CollY | | |
629 +-------------------+ | |
630 | \ (creates loop) | |
631 | \ | |
632 +-------------+ +-----------------+ | |
633 | Resource R1 | | Collection C2 | | |
634 +-------------+ | bindings: | | |
635 | y.gif CollZ | | |
636 +-----------------+ | |
637 | | | |
638 | +-------+ |
639 | |
640 +-------------+ |
641 | Resource R2 | |
642 +-------------+ |
643 |
644 +-------------------------------+
645 |
646 +-------------------+
647 | Collection C3 |&lt;------------------+
648 | bindings: | |
649 | x.gif CollY | |
650 +-------------------+ |
651 | \ (creates loop) |
652 | \ |
653 +-------------+ +-----------------+ |
654 | Resource R3 | | Collection C4 | |
655 +-------------+ | bindings: | |
656 | y.gif CollZ | |
657 +-----------------+ |
658 | | |
659 | +-------+
660 |
661 +-------------+
662 | Resource R4 |
663 +-------------+
664
665
666
667
668 <span class="grey">Clemm, et al. Experimental [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
671
672
673 Note that the same would apply for more complex loops.
674
675 <span class="h4"><a class="selflink" id="section-2.3.2" href="#section-2.3.2">2.3.2</a>. Example: COPY Updating Multiple Bindings</span>
676
677 Given the following collection hierarchy:
678
679 +------------------+
680 | Root Collection |
681 | bindings: |
682 | CollX CollY |
683 +------------------+
684 / \
685 / \
686 / \
687 +--------------------------+ +-----------------+
688 | Collection C1 | | Collection C2 |
689 | bindings: | | bindings: |
690 | x.gif y.gif | | x.gif y.gif |
691 +--------------------------+ +-----------------+
692 | | | |
693 | | | |
694 +-------------+ +-------------+ +-------------+
695 | Resource R1 | | Resource R2 | | Resource R3 |
696 +-------------+ +-------------+ +-------------+
697
698 A COPY of /CollX with "Depth: infinity" to /CollY will not result in
699 a changed hierarchy, and Resource R3 will be updated with the content
700 of either Resource R1 or Resource R2.
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724 <span class="grey">Clemm, et al. Experimental [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
727
728
729 <span class="h4"><a class="selflink" id="section-2.3.3" href="#section-2.3.3">2.3.3</a>. Example: COPY with "Depth: infinity" with Multiple Bindings to a</span>
730 <span class="h4"> Leaf Resource</span>
731
732 Given the following collection hierarchy:
733
734 +------------------+
735 | Root Collection |
736 | bindings: |
737 | CollX |
738 +------------------+
739 |
740 |
741 |
742 +----------------+
743 | Collection C1 |
744 | bindings: |
745 | x.gif y.gif |
746 +----------------+
747 | |
748 | |
749 +-------------+
750 | Resource R1 |
751 +-------------+
752
753 A COPY of /CollX with "Depth: infinity" to /CollY results in the
754 following collection hierarchy:
755
756 +------------------+
757 | Root Collection |
758 | bindings: |
759 | CollX CollY |
760 +------------------+
761 | \
762 | \
763 | \
764 +----------------+ +-----------------+
765 | Collection C1 | | Collection C2 |
766 | bindings: | | bindings: |
767 | x.gif y.gif | | x.gif y.gif |
768 +----------------+ +-----------------+
769 | | | |
770 | | | |
771 +-------------+ +-------------+
772 | Resource R1 | | Resource R2 |
773 +-------------+ +-------------+
774
775
776
777
778
779
780 <span class="grey">Clemm, et al. Experimental [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
783
784
785 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. DELETE and Bindings</span>
786
787 When there are multiple bindings to a resource, a DELETE applied to
788 that resource MUST NOT remove any bindings to that resource other
789 than the one identified by the Request-URI. For example, suppose the
790 collection identified by the URI "/a" has a binding named "x" to a
791 resource R, and another collection identified by "/b" has a binding
792 named "y" to the same resource R. Then, a DELETE applied to "/a/x"
793 removes the binding named "x" from "/a" but MUST NOT remove the
794 binding named "y" from "/b" (i.e., after the DELETE, "/y/b" continues
795 to identify the resource R).
796
797 When DELETE is applied to a collection, it MUST NOT modify the
798 membership of any other collection that is not itself a member of the
799 collection being deleted. For example, if both "/a/.../x" and
800 "/b/.../y" identify the same collection, C, then applying DELETE to
801 "/a" must not delete an internal member from C or from any other
802 collection that is a member of C, because that would modify the
803 membership of "/b".
804
805 If a collection supports the UNBIND method (see <a href="#section-5">Section 5</a>), a DELETE
806 of an internal member of a collection MAY be implemented as an UNBIND
807 request. In this case, applying DELETE to a Request-URI has the
808 effect of removing the binding identified by the final segment of the
809 Request-URI from the collection identified by the Request-URI minus
810 its final segment. Although [<a href="./rfc4918" title="&quot;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)&quot;">RFC4918</a>] allows a DELETE to be a non-
811 atomic operation, when the DELETE operation is implemented as an
812 UNBIND, the operation is atomic. In particular, a DELETE on a
813 hierarchy of resources is simply the removal of a binding to the
814 collection identified by the Request-URI.
815
816 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. MOVE and Bindings</span>
817
818 When MOVE is applied to a resource, the other bindings to that
819 resource MUST be unaffected; and if the resource being moved is a
820 collection, the bindings to any members of that collection MUST be
821 unaffected. Also, if MOVE is used with Overwrite:T to delete an
822 existing resource, the constraints specified for DELETE apply.
823
824 If the destination collection of a MOVE request supports the REBIND
825 method (see <a href="#section-6">Section 6</a>), a MOVE of a resource into that collection MAY
826 be implemented as a REBIND request. Although [<a href="./rfc4918" title="&quot;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)&quot;">RFC4918</a>] allows a MOVE
827 to be a non-atomic operation, when the MOVE operation is implemented
828 as a REBIND, the operation is atomic. In particular, applying a MOVE
829 to a Request-URI and a Destination URI has the effect of removing a
830 binding to a resource (at the Request-URI) and creating a new binding
831
832
833
834
835
836 <span class="grey">Clemm, et al. Experimental [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
839
840
841 to that resource (at the Destination URI). Even when the Request-URI
842 identifies a collection, the MOVE operation involves only removing
843 one binding to that collection and adding another.
844
845 <span class="h4"><a class="selflink" id="section-2.5.1" href="#section-2.5.1">2.5.1</a>. Example: Simple MOVE</span>
846
847 As an example, suppose that a MOVE is issued to URI-3 for resource R
848 below (which is also mapped to URI-1 and URI-2), with the Destination
849 header set to URI-X. After successful completion of the MOVE
850 operation, a new binding has been created that creates the URI
851 mapping between URI-X and resource R. The binding corresponding to
852 the final segment of URI-3 has been removed, which also causes the
853 URI mapping between URI-3 and R to be removed. If resource R were a
854 collection, old URI-3-based mappings to members of R would have been
855 removed, and new URI-X-based mappings to members of R would have been
856 created.
857
858 &gt;&gt; Before Request:
859
860 URI-1 URI-2 URI-3
861 | | |
862 | | | &lt;---- URI Mappings
863 | | |
864 +---------------------+
865 | Resource R |
866 +---------------------+
867
868 &gt;&gt; After Request:
869
870 URI-1 URI-2 URI-X
871 | | |
872 | | | &lt;---- URI Mappings
873 | | |
874 +---------------------+
875 | Resource R |
876 +---------------------+
877
878 <span class="h4"><a class="selflink" id="section-2.5.2" href="#section-2.5.2">2.5.2</a>. Example: MOVE Request Causing a Bind Loop</span>
879
880 Note that in the presence of collection bindings, a MOVE request can
881 cause the creation of a bind loop.
882
883
884
885
886
887
888
889
890
891
892 <span class="grey">Clemm, et al. Experimental [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
895
896
897 Consider the top-level collections C1 and C2 with URIs "/CollW/" and
898 "/CollX/". C1 also contains an additional binding named "CollY" to
899 C2:
900
901 +------------------+
902 | Root Collection |
903 | bindings: |
904 | CollW CollX |
905 +------------------+
906 | |
907 | |
908 +------------------+ |
909 | Collection C1 | |
910 | bindings: | |
911 | CollY | |
912 +------------------+ |
913 | |
914 | |
915 +------------------+
916 | Collection C2 |
917 | |
918 | |
919 +------------------+
920
921 In this case, the MOVE request below would cause a bind loop:
922
923 &gt;&gt; Request:
924
925 MOVE /CollW HTTP/1.1
926 Host: example.com
927 Destination: /CollX/CollZ
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948 <span class="grey">Clemm, et al. Experimental [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
951
952
953 If the request succeeded, the resulting state would be:
954
955 +------------------+
956 | Root Collection |
957 | bindings: |
958 | CollX |
959 +------------------+
960 |
961 |
962 +------------------+ |
963 | Collection C1 | |
964 +----&gt; | bindings: | |
965 | | CollY | |
966 | +------------------+ |
967 | | |
968 | | |
969 | +------------------+
970 | | Collection C2 |
971 | | bindings: |
972 | | CollZ |
973 | +------------------+
974 | |
975 | |
976 +-------------------+
977
978 <span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. PROPFIND and Bindings</span>
979
980 Consistent with [<a href="./rfc4918" title="&quot;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)&quot;">RFC4918</a>], the value of a dead property MUST be
981 independent of the number of bindings to its host resource or of the
982 path submitted to PROPFIND. On the other hand, the behavior for each
983 live property depends on its individual definition (for example, see
984 <a href="./rfc3744#section-5">[RFC3744], Section&nbsp;5</a>, Paragraph 2 for a case where the value is
985 independent of its path and bindings, and <a href="./rfc4918#section-8.8">[RFC4918], Section&nbsp;8.8</a> for
986 a discussion about the live properties DAV:getetag and DAV:
987 getlastmodified, which may behave differently).
988
989 <span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Determining Whether Two Bindings Are to the Same Resource</span>
990
991 It is useful to have some way of determining whether two bindings are
992 to the same resource. Two resources might have identical contents
993 and properties, but not be the same resource (e.g., an update to one
994 resource does not affect the other resource).
995
996 The REQUIRED DAV:resource-id property defined in <a href="#section-3.1">Section 3.1</a> is a
997 resource identifier, which MUST be unique across all resources for
998 all time. If the values of DAV:resource-id returned by PROPFIND
999
1000
1001
1002
1003
1004 <span class="grey">Clemm, et al. Experimental [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1007
1008
1009 requests through two bindings are identical character by character,
1010 the client can be assured that the two bindings are to the same
1011 resource.
1012
1013 The DAV:resource-id property is created, and its value assigned, when
1014 the resource is created. The value of DAV:resource-id MUST NOT be
1015 changed. Even after the resource is no longer accessible through any
1016 URI, that value MUST NOT be reassigned to another resource's DAV:
1017 resource-id property.
1018
1019 Any method that creates a new resource MUST assign a new, unique
1020 value to its DAV:resource-id property. For example, a PUT applied to
1021 a null resource, COPY (when not overwriting an existing target) and
1022 CHECKIN (see <a href="./rfc3253#section-4.4">[RFC3253], Section&nbsp;4.4</a>) must assign a new, unique value
1023 to the DAV:resource-id property of the new resource they create.
1024
1025 On the other hand, any method that affects an existing resource must
1026 not change the value of its DAV:resource-id property. Specifically,
1027 a PUT or a COPY that updates an existing resource must not change the
1028 value of its DAV:resource-id property. A REBIND, since it does not
1029 create a new resource, but only changes the location of an existing
1030 resource, must not change the value of the DAV:resource-id property.
1031
1032 <span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Discovering the Bindings to a Resource</span>
1033
1034 An OPTIONAL DAV:parent-set property on a resource provides a list of
1035 the bindings that associate a collection and a URI segment with that
1036 resource. If the DAV:parent-set property exists on a given resource,
1037 it MUST contain a complete list of all bindings to that resource that
1038 the client is authorized to see. When deciding whether to support
1039 the DAV:parent-set property, server implementers / administrators
1040 should balance the benefits it provides against the cost of
1041 maintaining the property and the security risks enumerated in
1042 Sections <a href="#section-12.4">12.4</a> and <a href="#section-12.5">12.5</a>.
1043
1044 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Properties</span>
1045
1046 The bind feature introduces the properties defined below.
1047
1048 A DAV:allprop PROPFIND request SHOULD NOT return any of the
1049 properties defined by this document. This allows a binding server to
1050 perform efficiently when a naive client, which does not understand
1051 the cost of asking a server to compute all possible live properties,
1052 issues a DAV:allprop PROPFIND request.
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Clemm, et al. Experimental [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1063
1064
1065 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. DAV:resource-id Property</span>
1066
1067 The DAV:resource-id property is a REQUIRED property that enables
1068 clients to determine whether two bindings are to the same resource.
1069 The value of DAV:resource-id is a URI, and may use any registered URI
1070 scheme that guarantees the uniqueness of the value across all
1071 resources for all time (e.g., the urn:uuid: URN namespace defined in
1072 [<a href="./rfc4122" title="&quot;A Universally Unique IDentifier (UUID) URN Namespace&quot;">RFC4122</a>] or the opaquelocktoken: URI scheme defined in [<a href="./rfc4918" title="&quot;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)&quot;">RFC4918</a>]).
1073
1074 &lt;!ELEMENT resource-id (href)&gt;
1075
1076 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. DAV:parent-set Property</span>
1077
1078 The DAV:parent-set property is an OPTIONAL property that enables
1079 clients to discover what collections contain a binding to this
1080 resource (i.e., what collections have that resource as an internal
1081 member). It contains an href/segment pair for each collection that
1082 has a binding to the resource. The href identifies the collection,
1083 and the segment identifies the binding name of that resource in that
1084 collection.
1085
1086 A given collection MUST appear only once in the DAV:parent-set for
1087 any given binding, even if there are multiple URI mappings to that
1088 collection.
1089
1090 &lt;!ELEMENT parent-set (parent)*&gt;
1091 &lt;!ELEMENT parent (href, segment)&gt;
1092 &lt;!ELEMENT segment (#PCDATA)&gt;
1093 &lt;!-- PCDATA value: segment, as defined in <a href="./rfc3986#section-3.3">Section&nbsp;3.3 of
1094 [RFC3986]</a> --&gt;
1095
1096 <span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Example for DAV:parent-set Property</span>
1097
1098 For example, if collection C1 is mapped to both /CollX and /CollY,
1099 and C1 contains a binding named "x.gif" to a resource R1, then either
1100 [/CollX, x.gif] or [/CollY, x.gif] can appear in the DAV:parent-set
1101 of R1, but not both. But if C1 also had a binding named "y.gif" to
1102 R1, then there would be two entries for C1 in the DAV:parent-set of
1103 R1 (i.e., both [/CollX, x.gif] and [/CollX, y.gif] or, alternatively,
1104 both [/CollY, x.gif] and [/CollY, y.gif]).
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Clemm, et al. Experimental [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1119
1120
1121 +-------------------------+
1122 | Root Collection |
1123 | bindings: |
1124 | CollX CollY |
1125 +-------------------------+
1126 | /
1127 | /
1128 | /
1129 +-----------------+
1130 | Collection C1 |
1131 | bindings: |
1132 | x.gif y.gif |
1133 +-----------------+
1134 | |
1135 | |
1136 | |
1137 +-------------+
1138 | Resource R1 |
1139 +-------------+
1140
1141 In this case, one possible value for the DAV:parent-set property on
1142 "/CollX/x.gif" would be:
1143
1144 &lt;parent-set xmlns="DAV:"&gt;
1145 &lt;parent&gt;
1146 &lt;href&gt;/CollX&lt;/href&gt;
1147 &lt;segment&gt;x.gif&lt;/segment&gt;
1148 &lt;/parent&gt;
1149 &lt;parent&gt;
1150 &lt;href&gt;/CollX&lt;/href&gt;
1151 &lt;segment&gt;y.gif&lt;/segment&gt;
1152 &lt;/parent&gt;
1153 &lt;/parent-set&gt;
1154
1155 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. BIND Method</span>
1156
1157 The BIND method modifies the collection identified by the Request-
1158 URI, by adding a new binding from the segment specified in the BIND
1159 body to the resource identified in the BIND body.
1160
1161 If a server cannot guarantee the integrity of the binding, the BIND
1162 request MUST fail. Note that it is especially difficult to maintain
1163 the integrity of cross-server bindings. Unless the server where the
1164 resource resides knows about all bindings on all servers to that
1165 resource, it may unwittingly destroy the resource or make it
1166 inaccessible without notifying another server that manages a binding
1167 to the resource. For example, if server A permits the creation of a
1168
1169
1170
1171
1172 <span class="grey">Clemm, et al. Experimental [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1175
1176
1177 binding to a resource on server B, server A must notify server B
1178 about its binding and must have an agreement with B that B will not
1179 destroy the resource while A's binding exists. Otherwise, server B
1180 may receive a DELETE request that it thinks removes the last binding
1181 to the resource and destroy the resource while A's binding still
1182 exists. The precondition DAV:cross-server-binding is defined below
1183 for cases where servers fail cross-server BIND requests because they
1184 cannot guarantee the integrity of cross-server bindings.
1185
1186 By default, if there already is a binding for the specified segment
1187 in the collection, the new binding replaces the existing binding.
1188 This default binding replacement behavior can be overridden using the
1189 Overwrite header defined in <a href="./rfc4918#section-10.6">Section&nbsp;10.6 of [RFC4918]</a>.
1190
1191 If a BIND request fails, the server state preceding the request MUST
1192 be restored. This method is unsafe and idempotent (see <a href="./rfc2616#section-9.1">[RFC2616],
1193 Section&nbsp;9.1</a>).
1194
1195 Marshalling:
1196
1197 The request MAY include an Overwrite header.
1198
1199 The request body MUST be a DAV:bind XML element.
1200
1201 &lt;!ELEMENT bind (segment, href)&gt;
1202
1203 If the request succeeds, the server MUST return 201 (Created) when
1204 a new binding was created and 200 (OK) or 204 (No Content) when an
1205 existing binding was replaced.
1206
1207 If a response body for a successful request is included, it MUST
1208 be a DAV:bind-response XML element. Note that this document does
1209 not define any elements for the BIND response body, but the DAV:
1210 bind-response element is defined to ensure interoperability
1211 between future extensions that do define elements for the BIND
1212 response body.
1213
1214 &lt;!ELEMENT bind-response ANY&gt;
1215
1216 Preconditions:
1217
1218 (DAV:bind-into-collection): The Request-URI MUST identify a
1219 collection.
1220
1221 (DAV:bind-source-exists): The DAV:href element MUST identify a
1222 resource.
1223
1224
1225
1226
1227
1228 <span class="grey">Clemm, et al. Experimental [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1231
1232
1233 (DAV:binding-allowed): The resource identified by the DAV:href
1234 supports multiple bindings to it.
1235
1236 (DAV:cross-server-binding): If the resource identified by the DAV:
1237 href element in the request body is on another server from the
1238 collection identified by the Request-URI, the server MUST support
1239 cross-server bindings (servers that do not support cross-server
1240 bindings can use this condition code to signal the client exactly
1241 why the request failed).
1242
1243 (DAV:name-allowed): The name specified by the DAV:segment is
1244 available for use as a new binding name.
1245
1246 (DAV:can-overwrite): If the collection already contains a binding
1247 with the specified path segment, and if an Overwrite header is
1248 included, the value of the Overwrite header MUST be "T".
1249
1250 (DAV:cycle-allowed): If the DAV:href element identifies a
1251 collection, and if the Request-URI identifies a collection that is
1252 a member of that collection, the server MUST support cycles in the
1253 URI namespace (servers that do not support cycles can use this
1254 condition code to signal the client exactly why the request
1255 failed).
1256
1257 (DAV:locked-update-allowed): If the collection identified by the
1258 Request-URI is write-locked, then the appropriate token MUST be
1259 specified in an If request header.
1260
1261 (DAV:locked-overwrite-allowed): If the collection already contains
1262 a binding with the specified path segment, and if that binding is
1263 protected by a write lock, then the appropriate token MUST be
1264 specified in an If request header.
1265
1266 Postconditions:
1267
1268 (DAV:new-binding): The collection MUST have a binding that maps
1269 the segment specified in the DAV:segment element in the request
1270 body to the resource identified by the DAV:href element in the
1271 request body.
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Clemm, et al. Experimental [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1287
1288
1289 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Example: BIND</span>
1290
1291 &gt;&gt; Request:
1292
1293 BIND /CollY HTTP/1.1
1294 Host: www.example.com
1295 Content-Type: application/xml; charset="utf-8"
1296 Content-Length: 172
1297
1298 &lt;?xml version="1.0" encoding="utf-8" ?&gt;
1299 &lt;D:bind xmlns:D="DAV:"&gt;
1300 &lt;D:segment&gt;bar.html&lt;/D:segment&gt;
1301 &lt;D:href&gt;http://www.example.com/CollX/foo.html&lt;/D:href&gt;
1302 &lt;/D:bind&gt;
1303
1304 &gt;&gt; Response:
1305
1306 HTTP/1.1 201 Created
1307 Location: http://www.example.com/CollY/bar.html
1308
1309 The server added a new binding to the collection,
1310 "http://www.example.com/CollY", associating "bar.html" with the
1311 resource identified by the URI
1312 "http://www.example.com/CollX/foo.html". Clients can now use the URI
1313 "http://www.example.com/CollY/bar.html" to submit requests to that
1314 resource.
1315
1316 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. UNBIND Method</span>
1317
1318 The UNBIND method modifies the collection identified by the Request-
1319 URI by removing the binding identified by the segment specified in
1320 the UNBIND body.
1321
1322 Once a resource is unreachable by any URI mapping, the server MAY
1323 reclaim system resources associated with that resource. If UNBIND
1324 removes a binding to a resource, but there remain URI mappings to
1325 that resource, the server MUST NOT reclaim system resources
1326 associated with the resource.
1327
1328 If an UNBIND request fails, the server state preceding the request
1329 MUST be restored. This method is unsafe and idempotent (see
1330 <a href="./rfc2616#section-9.1">[RFC2616], Section&nbsp;9.1</a>).
1331
1332 Marshalling:
1333
1334 The request body MUST be a DAV:unbind XML element.
1335
1336 &lt;!ELEMENT unbind (segment)&gt;
1337
1338
1339
1340 <span class="grey">Clemm, et al. Experimental [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1343
1344
1345 If the request succeeds, the server MUST return 200 (OK) or 204
1346 (No Content) when the binding was successfully deleted.
1347
1348 If a response body for a successful request is included, it MUST
1349 be a DAV:unbind-response XML element. Note that this document
1350 does not define any elements for the UNBIND response body, but the
1351 DAV:unbind-response element is defined to ensure interoperability
1352 between future extensions that do define elements for the UNBIND
1353 response body.
1354
1355 &lt;!ELEMENT unbind-response ANY&gt;
1356
1357 Preconditions:
1358
1359 (DAV:unbind-from-collection): The Request-URI MUST identify a
1360 collection.
1361
1362 (DAV:unbind-source-exists): The DAV:segment element MUST identify
1363 a binding in the collection identified by the Request-URI.
1364
1365 (DAV:locked-update-allowed): If the collection identified by the
1366 Request-URI is write-locked, then the appropriate token MUST be
1367 specified in the request.
1368
1369 (DAV:protected-url-deletion-allowed): If the binding identified by
1370 the segment is protected by a write lock, then the appropriate
1371 token MUST be specified in the request.
1372
1373 Postconditions:
1374
1375 (DAV:binding-deleted): The collection MUST NOT have a binding for
1376 the segment specified in the DAV:segment element in the request
1377 body.
1378
1379 (DAV:lock-deleted): If the internal member URI of the binding
1380 specified by the Request-URI and the DAV:segment element in the
1381 request body was protected by a write lock at the time of the
1382 request, that write lock must have been deleted by the request.
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Clemm, et al. Experimental [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1399
1400
1401 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Example: UNBIND</span>
1402
1403 &gt;&gt; Request:
1404
1405 UNBIND /CollX HTTP/1.1
1406 Host: www.example.com
1407 Content-Type: application/xml; charset="utf-8"
1408 Content-Length: 117
1409
1410 &lt;?xml version="1.0" encoding="utf-8" ?&gt;
1411 &lt;D:unbind xmlns:D="DAV:"&gt;
1412 &lt;D:segment&gt;foo.html&lt;/D:segment&gt;
1413 &lt;/D:unbind&gt;
1414
1415 &gt;&gt; Response:
1416
1417 HTTP/1.1 200 OK
1418
1419 The server removed the binding named "foo.html" from the collection,
1420 "http://www.example.com/CollX". A request to the resource named
1421 "http://www.example.com/CollX/foo.html" will return a 404 (Not Found)
1422 response.
1423
1424 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. REBIND Method</span>
1425
1426 The REBIND method removes a binding to a resource from a collection,
1427 and adds a binding to that resource into the collection identified by
1428 the Request-URI. The request body specifies the binding to be added
1429 (segment) and the old binding to be removed (href). It is
1430 effectively an atomic form of a MOVE request, and MUST be treated the
1431 same way as MOVE for the purpose of determining access permissions.
1432
1433 If a REBIND request fails, the server state preceding the request
1434 MUST be restored. This method is unsafe and idempotent (see
1435 <a href="./rfc2616#section-9.1">[RFC2616], Section&nbsp;9.1</a>).
1436
1437 Marshalling:
1438
1439 The request MAY include an Overwrite header.
1440
1441 The request body MUST be a DAV:rebind XML element.
1442
1443 &lt;!ELEMENT rebind (segment, href)&gt;
1444
1445 If the request succeeds, the server MUST return 201 (Created) when
1446 a new binding was created and 200 (OK) or 204 (No Content) when an
1447 existing binding was replaced.
1448
1449
1450
1451
1452 <span class="grey">Clemm, et al. Experimental [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1455
1456
1457 If a response body for a successful request is included, it MUST
1458 be a DAV:rebind-response XML element. Note that this document
1459 does not define any elements for the REBIND response body, but the
1460 DAV:rebind-response element is defined to ensure interoperability
1461 between future extensions that do define elements for the REBIND
1462 response body.
1463
1464 &lt;!ELEMENT rebind-response ANY&gt;
1465
1466 Preconditions:
1467
1468 (DAV:rebind-into-collection): The Request-URI MUST identify a
1469 collection.
1470
1471 (DAV:rebind-source-exists): The DAV:href element MUST identify a
1472 resource.
1473
1474 (DAV:cross-server-binding): If the resource identified by the DAV:
1475 href element in the request body is on another server from the
1476 collection identified by the Request-URI, the server MUST support
1477 cross-server bindings (servers that do not support cross-server
1478 bindings can use this condition code to signal the client exactly
1479 why the request failed).
1480
1481 (DAV:name-allowed): The name specified by the DAV:segment is
1482 available for use as a new binding name.
1483
1484 (DAV:can-overwrite): If the collection already contains a binding
1485 with the specified path segment, and if an Overwrite header is
1486 included, the value of the Overwrite header MUST be "T".
1487
1488 (DAV:cycle-allowed): If the DAV:href element identifies a
1489 collection, and if the Request-URI identifies a collection that is
1490 a member of that collection, the server MUST support cycles in the
1491 URI namespace (servers that do not support cycles can use this
1492 condition code to signal the client exactly why the request
1493 failed).
1494
1495 (DAV:locked-update-allowed): If the collection identified by the
1496 Request-URI is write-locked, then the appropriate token MUST be
1497 specified in the request.
1498
1499 (DAV:protected-url-modification-allowed): If the collection
1500 identified by the Request-URI already contains a binding with the
1501 specified path segment, and if that binding is protected by a
1502 write lock, then the appropriate token MUST be specified in the
1503 request.
1504
1505
1506
1507
1508 <span class="grey">Clemm, et al. Experimental [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1511
1512
1513 (DAV:locked-source-collection-update-allowed): If the collection
1514 identified by the parent collection prefix of the DAV:href URI is
1515 write-locked, then the appropriate token MUST be specified in the
1516 request.
1517
1518 (DAV:protected-source-url-deletion-allowed): If the DAV:href URI
1519 is protected by a write lock, then the appropriate token MUST be
1520 specified in the request.
1521
1522 Postconditions:
1523
1524 (DAV:new-binding): The collection MUST have a binding that maps
1525 the segment specified in the DAV:segment element in the request
1526 body, to the resource that was identified by the DAV:href element
1527 in the request body.
1528
1529 (DAV:binding-deleted): The URL specified in the DAV:href element
1530 in the request body MUST NOT be mapped to a resource.
1531
1532 (DAV:lock-deleted): If the URL specified in the DAV:href element
1533 in the request body was protected by a write lock at the time of
1534 the request, that write lock must have been deleted by the
1535 request.
1536
1537 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Example: REBIND</span>
1538
1539 &gt;&gt; Request:
1540
1541 REBIND /CollX HTTP/1.1
1542 Host: www.example.com
1543 Content-Type: application/xml; charset="utf-8"
1544 Content-Length: 176
1545
1546 &lt;?xml version="1.0" encoding="utf-8" ?&gt;
1547 &lt;D:rebind xmlns:D="DAV:"&gt;
1548 &lt;D:segment&gt;foo.html&lt;/D:segment&gt;
1549 &lt;D:href&gt;http://www.example.com/CollY/bar.html&lt;/D:href&gt;
1550 &lt;/D:rebind&gt;
1551
1552 &gt;&gt; Response:
1553
1554 HTTP/1.1 200 OK
1555
1556 The server added a new binding to the collection,
1557 "http://www.example.com/CollX", associating "foo.html" with the
1558 resource identified by the URI
1559 "http://www.example.com/CollY/bar.html" and removes the binding named
1560 "bar.html" from the collection identified by the URI
1561
1562
1563
1564 <span class="grey">Clemm, et al. Experimental [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1567
1568
1569 "http://www.example.com/CollY". Clients can now use the URI
1570 "http://www.example.com/CollX/foo.html" to submit requests to that
1571 resource, and requests on the URI
1572 "http://www.example.com/CollY/bar.html" will fail with a 404 (Not
1573 Found) response.
1574
1575 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Example: REBIND in Presence of Locks and Bind Loops</span>
1576
1577 To illustrate the effects of locks and bind loops on a REBIND
1578 operation, consider the following collection:
1579
1580 +------------------+
1581 | Root Collection |
1582 | bindings: |
1583 | CollW |
1584 +------------------+
1585 |
1586 |
1587 |
1588 +-------------------------------+
1589 | Collection C1 |&lt;--------+
1590 | LOCKED infinity | |
1591 | (lock token L1) | |
1592 | bindings: | |
1593 | CollX CollY | |
1594 +-------------------------------+ |
1595 | | |
1596 | | (creates loop) |
1597 | | |
1598 +-----------------+ +------------------+ |
1599 | Collection C2 | | Collection C3 | |
1600 | (inherit lock) | | (inherit lock) | |
1601 | (lock token L1) | | (lock token L1) | |
1602 | bindings: | | bindings: | |
1603 | {none} | | y.gif CollZ | |
1604 +-----------------+ +------------------+ |
1605 | | |
1606 | +-----+
1607 |
1608 +---------------------------+
1609 | Resource R2 |
1610 | (lock inherited from C1) |
1611 | (lock token L1) |
1612 +---------------------------+
1613
1614 (where L1 is "urn:uuid:f92d4fae-7012-11ab-a765-00c0ca1f6bf9").
1615
1616
1617
1618
1619
1620 <span class="grey">Clemm, et al. Experimental [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1623
1624
1625 Note that the binding between CollZ and C1 creates a loop in the
1626 containment hierarchy. Servers are not required to support such
1627 loops, though the server in this example does.
1628
1629 The REBIND request below will remove the segment "CollZ" from C3 and
1630 add a new binding from "CollA" to the collection C2.
1631
1632 REBIND /CollW/CollX HTTP/1.1
1633 Host: www.example.com
1634 If: (&lt;urn:uuid:f92d4fae-7012-11ab-a765-00c0ca1f6bf9&gt;)
1635 Content-Type: application/xml; charset="utf-8"
1636 Content-Length: 152
1637
1638 &lt;?xml version="1.0" encoding="utf-8" ?&gt;
1639 &lt;D:rebind xmlns:D="DAV:"&gt;
1640 &lt;D:segment&gt;CollA&lt;/D:segment&gt;
1641 &lt;D:href&gt;/CollW/CollY/CollZ&lt;/D:href&gt;
1642 &lt;/D:rebind&gt;
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676 <span class="grey">Clemm, et al. Experimental [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1679
1680
1681 The outcome of the REBIND operation is:
1682
1683 +------------------+
1684 | Root Collection |
1685 | bindings: |
1686 | CollW |
1687 +------------------+
1688 |
1689 |
1690 |
1691 +-------------------------------+
1692 | Collection C1 |
1693 | LOCKED infinity |
1694 | (lock token L1) |
1695 | bindings: |
1696 | CollX CollY |
1697 +-------------------------------+
1698 | ^ |
1699 | | |
1700 +-----------------+ | +------------------+
1701 | Collection C2 | | | Collection C3 |
1702 |(inherited lock) | | | (inherited lock) |
1703 |(lock token L1) | | | (lock token L1) |
1704 | bindings: | | | bindings: |
1705 | CollA | | | y.gif |
1706 +-----------------+ | +------------------+
1707 | | |
1708 +---------------+ |
1709 (creates loop) |
1710 +---------------------------+
1711 | Resource R2 |
1712 | (inherited lock from C1) |
1713 | (lock token L1) |
1714 +---------------------------+
1715
1716 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Additional Status Codes</span>
1717
1718 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. 208 Already Reported</span>
1719
1720 The 208 (Already Reported) status code can be used inside a DAV:
1721 propstat response element to avoid enumerating the internal members
1722 of multiple bindings to the same collection repeatedly. For each
1723 binding to a collection inside the request's scope, only one will be
1724 reported with a 200 status, while subsequent DAV:response elements
1725 for all other bindings will use the 208 status, and no DAV:response
1726 elements for their descendants are included.
1727
1728
1729
1730
1731
1732 <span class="grey">Clemm, et al. Experimental [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1735
1736
1737 Note that the 208 status will only occur for "Depth: infinity"
1738 requests, and that it is of particular importance when the multiple
1739 collection bindings cause a bind loop as discussed in <a href="#section-2.2">Section 2.2</a>.
1740
1741 A client can request the DAV:resource-id property in a PROPFIND
1742 request to guarantee that they can accurately reconstruct the binding
1743 structure of a collection with multiple bindings to a single
1744 resource.
1745
1746 For backward compatibility with clients not aware of the 208 status
1747 code appearing in multistatus response bodies, it SHOULD NOT be used
1748 unless the client has signaled support for this specification using
1749 the "DAV" request header (see <a href="#section-8.2">Section 8.2</a>). Instead, a 508 status
1750 should be returned when a binding loop is discovered. This allows
1751 the server to return the 508 as the top-level return status, if it
1752 discovers it before it started the response, or in the middle of a
1753 multistatus, if it discovers it in the middle of streaming out a
1754 multistatus response.
1755
1756 <span class="h4"><a class="selflink" id="section-7.1.1" href="#section-7.1.1">7.1.1</a>. Example: PROPFIND by Bind-Aware Client</span>
1757
1758 For example, consider a PROPFIND request on /Coll (bound to
1759 collection C), where the members of /Coll are /Coll/Foo (bound to
1760 resource R) and /Coll/Bar (bound to collection C).
1761
1762 &gt;&gt; Request:
1763
1764 PROPFIND /Coll/ HTTP/1.1
1765 Host: www.example.com
1766 Depth: infinity
1767 DAV: bind
1768 Content-Type: application/xml; charset="utf-8"
1769 Content-Length: 152
1770
1771 &lt;?xml version="1.0" encoding="utf-8" ?&gt;
1772 &lt;D:propfind xmlns:D="DAV:"&gt;
1773 &lt;D:prop&gt;
1774 &lt;D:displayname/&gt;
1775 &lt;D:resource-id/&gt;
1776 &lt;/D:prop&gt;
1777 &lt;/D:propfind&gt;
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788 <span class="grey">Clemm, et al. Experimental [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1791
1792
1793 &gt;&gt; Response:
1794
1795 HTTP/1.1 207 Multi-Status
1796 Content-Type: application/xml; charset="utf-8"
1797 Content-Length: 1241
1798
1799 &lt;?xml version="1.0" encoding="utf-8" ?&gt;
1800 &lt;D:multistatus xmlns:D="DAV:"&gt;
1801 &lt;D:response&gt;
1802 &lt;D:href&gt;http://www.example.com/Coll/&lt;/D:href&gt;
1803 &lt;D:propstat&gt;
1804 &lt;D:prop&gt;
1805 &lt;D:displayname&gt;Loop Demo&lt;/D:displayname&gt;
1806 &lt;D:resource-id&gt;
1807 &lt;D:href
1808 &gt;urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf8&lt;/D:href&gt;
1809 &lt;/D:resource-id&gt;
1810 &lt;/D:prop&gt;
1811 &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
1812 &lt;/D:propstat&gt;
1813 &lt;/D:response&gt;
1814 &lt;D:response&gt;
1815 &lt;D:href&gt;http://www.example.com/Coll/Foo&lt;/D:href&gt;
1816 &lt;D:propstat&gt;
1817 &lt;D:prop&gt;
1818 &lt;D:displayname&gt;Bird Inventory&lt;/D:displayname&gt;
1819 &lt;D:resource-id&gt;
1820 &lt;D:href
1821 &gt;urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf9&lt;/D:href&gt;
1822 &lt;/D:resource-id&gt;
1823 &lt;/D:prop&gt;
1824 &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
1825 &lt;/D:propstat&gt;
1826 &lt;/D:response&gt;
1827 &lt;D:response&gt;
1828 &lt;D:href&gt;http://www.example.com/Coll/Bar&lt;/D:href&gt;
1829 &lt;D:propstat&gt;
1830 &lt;D:prop&gt;
1831 &lt;D:displayname&gt;Loop Demo&lt;/D:displayname&gt;
1832 &lt;D:resource-id&gt;
1833 &lt;D:href
1834 &gt;urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf8&lt;/D:href&gt;
1835 &lt;/D:resource-id&gt;
1836 &lt;/D:prop&gt;
1837 &lt;D:status&gt;HTTP/1.1 208 Already Reported&lt;/D:status&gt;
1838 &lt;/D:propstat&gt;
1839 &lt;/D:response&gt;
1840 &lt;/D:multistatus&gt;
1841
1842
1843
1844 <span class="grey">Clemm, et al. Experimental [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1847
1848
1849 <span class="h4"><a class="selflink" id="section-7.1.2" href="#section-7.1.2">7.1.2</a>. Example: PROPFIND by Non-Bind-Aware Client</span>
1850
1851 In this example, the client isn't aware of the 208 status code
1852 introduced by this specification. As the "Depth: infinity" PROPFIND
1853 request would cause a loop condition, the whole request is rejected
1854 with a 508 status.
1855
1856 &gt;&gt; Request:
1857
1858 PROPFIND /Coll/ HTTP/1.1
1859 Host: www.example.com
1860 Depth: infinity
1861 Content-Type: application/xml; charset="utf-8"
1862 Content-Length: 125
1863
1864 &lt;?xml version="1.0" encoding="utf-8" ?&gt;
1865 &lt;D:propfind xmlns:D="DAV:"&gt;
1866 &lt;D:prop&gt; &lt;D:displayname/&gt; &lt;/D:prop&gt;
1867 &lt;/D:propfind&gt;
1868
1869 &gt;&gt; Response:
1870
1871 HTTP/1.1 508 Loop Detected
1872
1873 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. 508 Loop Detected</span>
1874
1875 The 508 (Loop Detected) status code indicates that the server
1876 terminated an operation because it encountered an infinite loop while
1877 processing a request with "Depth: infinity". This status indicates
1878 that the entire operation failed.
1879
1880 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Capability Discovery</span>
1881
1882 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. OPTIONS Method</span>
1883
1884 If the server supports bindings, it MUST return the compliance class
1885 name "bind" as a field in the "DAV" response header (see <a href="./rfc4918#section-10.1">[RFC4918],
1886 Section&nbsp;10.1</a>) from an OPTIONS request on any resource implemented by
1887 that server. A value of "bind" in the "DAV" header MUST indicate
1888 that the server supports all MUST-level requirements and REQUIRED
1889 features specified in this document.
1890
1891 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. 'DAV' Request Header</span>
1892
1893 Clients SHOULD signal support for all MUST-level requirements and
1894 REQUIRED features by submitting a "DAV" request header containing the
1895 compliance class name "bind". In particular, the client MUST
1896 understand the 208 status code defined in <a href="#section-7.1">Section 7.1</a>.
1897
1898
1899
1900 <span class="grey">Clemm, et al. Experimental [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1903
1904
1905 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Relationship to Locking in WebDAV</span>
1906
1907 Locking is an optional feature of WebDAV ([<a href="./rfc4918" title="&quot;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)&quot;">RFC4918</a>]). The base
1908 WebDAV specification and this protocol extension have been designed
1909 in parallel, making sure that all features of WebDAV can be
1910 implemented on a server that implements this protocol as well.
1911
1912 Unfortunately, WebDAV uses the term "lock-root" inconsistently. It
1913 is introduced in <a href="./rfc4918#section-6.1">Section&nbsp;6.1 of [RFC4918]</a>, point 2, as:
1914
1915 2. A resource becomes directly locked when a LOCK request to a
1916 URL of that resource creates a new lock. The "lock-root" of the
1917 new lock is that URL. If at the time of the request, the URL is
1918 not mapped to a resource, a new empty resource is created and
1919 directly locked.
1920
1921 On the other hand, <a href="./rfc4918#section-9.10.1">[RFC4918], Section&nbsp;9.10.1</a> states:
1922
1923 A LOCK request to an existing resource will create a lock on the
1924 resource identified by the Request-URI, provided the resource is
1925 not already locked with a conflicting lock. The resource
1926 identified in the Request-URI becomes the root of the lock.
1927
1928 Servers that implement both WebDAV locking and support for multiple
1929 bindings MUST use the first interpretation: the lock-root is the URI
1930 through which the lock was created, not a resource. This URI, and
1931 potential aliases of this URI (<a href="./rfc4918#section-5">[RFC4918], Section&nbsp;5</a>), are said to be
1932 "protected" by the lock.
1933
1934 As defined in the introduction to <a href="./rfc4918#section-7">Section&nbsp;7 of [RFC4918]</a>, write
1935 operations that modify the state of a locked resource require that
1936 the lock token is submitted with the request. Consistent with
1937 WebDAV, the state of the resource consists of the content ("any
1938 variant"), dead properties, lockable live properties (item 1), plus,
1939 for a collection, all its bindings (item 2). Note that this, by
1940 definition, does not depend on the Request-URI to which the write
1941 operation is applied (the locked state is a property of the resource,
1942 not its URI).
1943
1944 However, the lock-root is the URI through which the lock was
1945 requested. Thus, the protection defined in item 3 of the list does
1946 not apply to additional URIs that may be mapped to the same resource
1947 due to the existence of multiple bindings.
1948
1949
1950
1951
1952
1953
1954
1955
1956 <span class="grey">Clemm, et al. Experimental [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
1959
1960
1961 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Example: Locking and Multiple Bindings</span>
1962
1963 Consider a root collection "/", containing the two collections C1 and
1964 C2, named "/CollX" and "/CollY", and a child resource R, bound to C1
1965 as "/CollX/test" and bound to C2 as "/CollY/test":
1966
1967 +-------------------------+
1968 | Root Collection |
1969 | bindings: |
1970 | CollX CollY |
1971 +-------------------------+
1972 | |
1973 | |
1974 | |
1975 +---------------+ +---------------+
1976 | Collection C1 | | Collection C2 |
1977 | bindings: | | bindings: |
1978 | test | | test |
1979 +---------------+ +---------------+
1980 | |
1981 | |
1982 | |
1983 +------------------+
1984 | Resource R |
1985 +------------------+
1986
1987 Given a host name of "www.example.com", applying a depth-zero write
1988 lock to "/CollX/test" will lock the resource R, and the lock-root of
1989 this lock will be "http://www.example.com/CollX/test".
1990
1991 Thus, the following operations will require that the associated lock
1992 token is submitted with the "If" request header ([<a href="./rfc4918" title="&quot;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)&quot;">RFC4918</a>], <a href="#section-10.4">Section</a>
1993 <a href="#section-10.4">10.4</a>):
1994
1995 o a PUT or PROPPATCH request modifying the content or lockable
1996 properties of resource R (as R is locked) -- no matter which URI
1997 is used as request target, and
1998
1999 o a MOVE, REBIND, UNBIND, or DELETE request causing "/CollX/test"
2000 not to be mapped to resource R anymore (be it addressed to
2001 "/CollX" or "/CollX/test").
2002
2003 The following operations will not require submission of the lock
2004 token:
2005
2006 o a DELETE request addressed to "/CollY" or "/CollY/test", as it
2007 does not affect the resource R, nor the lock-root,
2008
2009
2010
2011
2012 <span class="grey">Clemm, et al. Experimental [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
2015
2016
2017 o for the same reason, an UNBIND request removing the binding "test"
2018 from collection C2, or the binding "CollY" from the root
2019 collection, and
2020
2021 o similarly, a MOVE or REBIND request causing "/CollY/test" not
2022 being mapped to resource R anymore.
2023
2024 Note that despite the lock-root being
2025 "http://www.example.com/CollX/test", an UNLOCK request can be
2026 addressed through any URI mapped to resource R, as UNLOCK operates on
2027 the resource identified by the Request-URI, not that URI (see
2028 <a href="./rfc4918#section-9.11">[RFC4918], Section&nbsp;9.11</a>).
2029
2030 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Relationship to WebDAV Access Control Protocol</span>
2031
2032 Note that the WebDAV Access Control Protocol has been designed for
2033 compatibility with systems that allow multiple URIs to map to the
2034 same resource (see <a href="./rfc3744#section-5">[RFC3744], Section&nbsp;5</a>):
2035
2036 Access control properties (especially DAV:acl and DAV:inherited-
2037 acl-set) are defined on the resource identified by the Request-URI
2038 of a PROPFIND request. A direct consequence is that if the
2039 resource is accessible via multiple URI, the value of access
2040 control properties is the same across these URI.
2041
2042 Furthermore, note that BIND and REBIND behave the same as MOVE with
2043 respect to the DAV:acl property (see <a href="./rfc3744#section-7.3">[RFC3744], Section&nbsp;7.3</a>).
2044
2045 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Relationship to Versioning Extensions to WebDAV</span>
2046
2047 Servers that implement Workspaces (<a href="./rfc3253#section-6">[RFC3253], Section&nbsp;6</a>) and Version-
2048 Controlled Collections (<a href="./rfc3253#section-14">[RFC3253], Section&nbsp;14</a>) already need to
2049 implement BIND-like behavior in order to handle UPDATE and UNCHECKOUT
2050 semantics.
2051
2052 Consider a workspace "/ws1/", containing the version-controlled,
2053 checked-out collections C1 and C2, named "/ws1/CollX" and "/ws1/
2054 CollY", and a version-controlled resource R, bound to C1 as "/ws1/
2055 CollX/test":
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068 <span class="grey">Clemm, et al. Experimental [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
2071
2072
2073 +-------------------------+
2074 | Workspace |
2075 | bindings: |
2076 | CollX CollY |
2077 +-------------------------+
2078 | |
2079 | |
2080 | |
2081 +---------------+ +---------------+
2082 | Collection C1 | | Collection C2 |
2083 | bindings: | | |
2084 | test | | |
2085 +---------------+ +---------------+
2086 |
2087 |
2088 |
2089 +------------------+
2090 | Resource R |
2091 +------------------+
2092
2093 Moving "/ws1/CollX/test" into "/ws1/CollY", checking in C2, but
2094 undoing the checkout on C1 will undo part of the MOVE request, thus
2095 restoring the binding from C1 to R, but keeping the new binding from
2096 C2 to R:
2097
2098 &gt;&gt; Request:
2099
2100 MOVE /ws1/CollX/test HTTP/1.1
2101 Host: www.example.com
2102 Destination: /ws1/CollY/test
2103
2104 &gt;&gt; Response:
2105
2106 HTTP/1.1 204 No Content
2107
2108 &gt;&gt; Request:
2109
2110 CHECKIN /ws1/CollY/ HTTP/1.1
2111 Host: www.example.com
2112
2113 &gt;&gt; Response:
2114
2115 HTTP/1.1 201 Created
2116 Cache-Control: no-cache
2117 Location: http://repo.example.com/his/17/ver/42
2118
2119
2120
2121
2122
2123
2124 <span class="grey">Clemm, et al. Experimental [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
2127
2128
2129 &gt;&gt; Request:
2130
2131 UNCHECKOUT /ws1/CollX/ HTTP/1.1
2132 Host: www.example.com
2133
2134 &gt;&gt; Response:
2135
2136 HTTP/1.1 200 OK
2137 Cache-Control: no-cache
2138
2139 As a result, both C1 and C2 would have a binding to R:
2140
2141 +-------------------------+
2142 | Workspace |
2143 | bindings: |
2144 | CollX CollY |
2145 +-------------------------+
2146 | |
2147 | |
2148 | |
2149 +---------------+ +---------------+
2150 | Collection C1 | | Collection C2 |
2151 | bindings: | | bindings: |
2152 | test | | test |
2153 +---------------+ +---------------+
2154 | |
2155 | |
2156 | |
2157 +------------------+
2158 | Resource R |
2159 +------------------+
2160
2161 The MOVE semantics defined in <a href="./rfc3253#section-3.15">Section&nbsp;3.15 of [RFC3253]</a> already
2162 require that "/ws1/CollX/test" and "/ws1/CollY/test" will have the
2163 same version history (as exposed in the DAV:version-history
2164 property). Furthermore, the UNCHECKOUT semantics (which in this case
2165 is similar to UPDATE, see <a href="./rfc3253#section-14.11">Section&nbsp;14.11 of [RFC3253]</a>) require:
2166
2167 If a new version-controlled member is in a workspace that already
2168 has a version-controlled resource for that version history, then
2169 the new version-controlled member MUST be just a binding (i.e.,
2170 another name for) that existing version-controlled resource.
2171
2172 Thus, "/ws1/CollX/test" and "/ws1/CollY/test" will be bindings to the
2173 same resource R, and have identical DAV:resource-id properties.
2174
2175
2176
2177
2178
2179
2180 <span class="grey">Clemm, et al. Experimental [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
2183
2184
2185 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Security Considerations</span>
2186
2187 This section is provided to make WebDAV implementers aware of the
2188 security implications of this protocol.
2189
2190 All of the security considerations of HTTP/1.1 ([<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>], <a href="#section-15">Section</a>
2191 <a href="#section-15">15</a>) and the WebDAV Distributed Authoring Protocol specification
2192 (<a href="./rfc4918#section-20">[RFC4918], Section&nbsp;20</a>) also apply to this protocol specification.
2193 In addition, bindings introduce several new security concerns and
2194 increase the risk of some existing threats. These issues are
2195 detailed below.
2196
2197 <span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Privacy Concerns</span>
2198
2199 In a context where cross-server bindings are supported, creating
2200 bindings on a trusted server may make it possible for a hostile agent
2201 to induce users to send private information to a target on a
2202 different server.
2203
2204 <span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Bind Loops</span>
2205
2206 Although bind loops were already possible in HTTP 1.1, the
2207 introduction of the BIND method creates a new avenue for clients to
2208 create loops accidentally or maliciously. If the binding and its
2209 target are on the same server, the server may be able to detect BIND
2210 requests that would create loops. Servers are required to detect
2211 loops that are caused by bindings to collections during the
2212 processing of any requests with "Depth: infinity".
2213
2214 <span class="h3"><a class="selflink" id="section-12.3" href="#section-12.3">12.3</a>. Bindings and Denial of Service</span>
2215
2216 Denial-of-service attacks were already possible by posting URIs that
2217 were intended for limited use at heavily used Web sites. The
2218 introduction of BIND creates a new avenue for similar denial-of-
2219 service attacks. If cross-server bindings are supported, clients can
2220 now create bindings at heavily used sites to target locations that
2221 were not designed for heavy usage.
2222
2223 <span class="h3"><a class="selflink" id="section-12.4" href="#section-12.4">12.4</a>. Private Locations May Be Revealed</span>
2224
2225 If the DAV:parent-set property is maintained on a resource, the
2226 owners of the bindings risk revealing private locations. The
2227 directory structures where bindings are located are available to
2228 anyone who has access to the DAV:parent-set property on the resource.
2229 Moving a binding may reveal its new location to anyone with access to
2230 DAV:parent-set on its resource.
2231
2232
2233
2234
2235
2236 <span class="grey">Clemm, et al. Experimental [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
2239
2240
2241 <span class="h3"><a class="selflink" id="section-12.5" href="#section-12.5">12.5</a>. DAV:parent-set and Denial of Service</span>
2242
2243 If the server maintains the DAV:parent-set property in response to
2244 bindings created in other administrative domains, it is exposed to
2245 hostile attempts to make it devote resources to adding bindings to
2246 the list.
2247
2248 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Internationalization Considerations</span>
2249
2250 All internationalization considerations mentioned in <a href="./rfc4918#section-19">Section&nbsp;19 of
2251 [RFC4918]</a> also apply to this document.
2252
2253 <span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. IANA Considerations</span>
2254
2255 <a href="#section-7">Section 7</a> defines the HTTP status codes 208 (Already Reported) and
2256 508 (Loop Detected), which have been added to the HTTP Status Code
2257 Registry.
2258
2259 <span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a>. Acknowledgements</span>
2260
2261 This document is the collaborative product of the authors and Tyson
2262 Chihaya, Jim Davis, Chuck Fay and Judith Slein. It has benefited
2263 from thoughtful discussion by Jim Amsden, Peter Carlson, Steve
2264 Carter, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun, Cyrus
2265 Daboo, Spencer Dawkins, Mark Day, Werner Donne, Rajiv Dulepet, David
2266 Durand, Lisa Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland,
2267 Joe Hildebrand, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager,
2268 Chris Kaler, Manoj Kasichainula, Rohit Khare, Brian Korver, Daniel
2269 LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Alexey
2270 Melnikov, Surendra Koduru Reddy, Max Rible, Sam Ruby, Bradley
2271 Sergeant, Nick Shelness, John Stracke, John Tigue, John Turner, Kevin
2272 Wiggen, and other members of the concluded WebDAV working group.
2273
2274 <span class="h2"><a class="selflink" id="section-16" href="#section-16">16</a>. References</span>
2275
2276 <span class="h3"><a class="selflink" id="section-16.1" href="#section-16.1">16.1</a>. Normative References</span>
2277
2278 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
2279 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
2280
2281 [<a id="ref-RFC2616">RFC2616</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
2282 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
2283 Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.
2284
2285 [<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
2286 Resource Identifier (URI): Generic Syntax", STD 66,
2287 <a href="./rfc3986">RFC 3986</a>, January 2005.
2288
2289
2290
2291
2292 <span class="grey">Clemm, et al. Experimental [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
2295
2296
2297 [<a id="ref-RFC4918">RFC4918</a>] Dusseault, L., Ed., "HTTP Extensions for Web Distributed
2298 Authoring and Versioning (WebDAV)", <a href="./rfc4918">RFC 4918</a>, June 2007.
2299
2300 [<a id="ref-XML">XML</a>] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
2301 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth
2302 Edition)", W3C REC-xml-20081126, November 2008,
2303 &lt;<a href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</a>&gt;.
2304
2305 <span class="h3"><a class="selflink" id="section-16.2" href="#section-16.2">16.2</a>. Informative References</span>
2306
2307 [<a id="ref-RFC3253">RFC3253</a>] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J.
2308 Whitehead, "Versioning Extensions to WebDAV (Web
2309 Distributed Authoring and Versioning)", <a href="./rfc3253">RFC 3253</a>,
2310 March 2002.
2311
2312 [<a id="ref-RFC3744">RFC3744</a>] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web
2313 Distributed Authoring and Versioning (WebDAV) Access
2314 Control Protocol", <a href="./rfc3744">RFC 3744</a>, May 2004.
2315
2316 [<a id="ref-RFC4122">RFC4122</a>] Leach, P., Mealling, M., and R. Salz, "A Universally
2317 Unique IDentifier (UUID) URN Namespace", <a href="./rfc4122">RFC 4122</a>,
2318 July 2005.
2319
2320 Index
2321
2322 2
2323 208 Already Reported (status code) 31, 41
2324
2325 5
2326 508 Loop Detected (status code) 34, 41
2327
2328 B
2329 BIND method 21
2330 Marshalling 22
2331 Postconditions 23
2332 Preconditions 22
2333 Binding 6
2334 Binding Integrity 6-7, 21
2335
2336 C
2337 Collection 6
2338 Condition Names
2339 DAV:bind-into-collection (pre) 22
2340 DAV:bind-source-exists (pre) 22
2341 DAV:binding-allowed (pre) 23
2342 DAV:binding-deleted (post) 25, 28
2343 DAV:can-overwrite (pre) 23, 27
2344 DAV:cross-server-binding (pre) 23, 27
2345
2346
2347
2348 <span class="grey">Clemm, et al. Experimental [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
2351
2352
2353 DAV:cycle-allowed (pre) 23, 27
2354 DAV:lock-deleted (post) 25, 28
2355 DAV:locked-overwrite-allowed (pre) 23
2356 DAV:locked-source-collection-update-allowed (pre) 28
2357 DAV:locked-update-allowed (pre) 23, 25, 27
2358 DAV:name-allowed (pre) 23, 27
2359 DAV:new-binding (post) 23, 28
2360 DAV:protected-source-url-deletion-allowed (pre) 28
2361 DAV:protected-url-deletion-allowed (pre) 25
2362 DAV:protected-url-modification-allowed (pre) 27
2363 DAV:rebind-into-collection (pre) 27
2364 DAV:rebind-source-exists (pre) 27
2365 DAV:unbind-from-collection (pre) 25
2366 DAV:unbind-source-exists (pre) 25
2367
2368 D
2369 DAV header
2370 compliance class 'bind' 34
2371 DAV:bind-into-collection precondition 22
2372 DAV:bind-source-exists precondition 22
2373 DAV:binding-allowed precondition 23
2374 DAV:binding-deleted postcondition 25, 28
2375 DAV:can-overwrite precondition 23, 27
2376 DAV:cross-server-binding precondition 23, 27
2377 DAV:cycle-allowed precondition 23, 27
2378 DAV:lock-deleted postcondition 25, 28
2379 DAV:locked-overwrite-allowed precondition 23
2380 DAV:locked-source-collection-update-allowed precondition 28
2381 DAV:locked-update-allowed precondition 23, 25, 27
2382 DAV:name-allowed precondition 23, 27
2383 DAV:new-binding postcondition 23, 28
2384 DAV:parent-set property 20
2385 DAV:protected-source-url-deletion-allowed precondition 28
2386 DAV:protected-url-deletion-allowed precondition 25
2387 DAV:protected-url-modification-allowed precondition 27
2388 DAV:rebind-into-collection precondition 27
2389 DAV:rebind-source-exists precondition 27
2390 DAV:resource-id property 19
2391 DAV:unbind-from-collection precondition 25
2392 DAV:unbind-source-exists precondition 25
2393
2394 I
2395 Internal Member URI 6
2396
2397 L
2398 Locking 35
2399
2400
2401
2402
2403
2404 <span class="grey">Clemm, et al. Experimental [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
2407
2408
2409 M
2410 Methods
2411 BIND 21
2412 REBIND 26
2413 UNBIND 24
2414
2415 P
2416 Path Segment 5
2417 Properties
2418 DAV:parent-set 20
2419 DAV:resource-id 19
2420
2421 R
2422 REBIND method 26
2423 Marshalling 26
2424 Postconditions 28
2425 Preconditions 27
2426
2427 S
2428 Status Codes
2429 208 Already Reported 31, 41
2430 508 Loop Detected 34, 41
2431
2432 U
2433 UNBIND method 24
2434 Marshalling 24
2435 Postconditions 25
2436 Preconditions 25
2437 URI Mapping 5
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460 <span class="grey">Clemm, et al. Experimental [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc5842">RFC 5842</a> Binding Extensions to WebDAV April 2010</span>
2463
2464
2465 Authors' Addresses
2466
2467 Geoffrey Clemm
2468 IBM
2469 550 King Street
2470 Littleton, MA 01460
2471
2472 EMail: [email protected]
2473
2474
2475 Jason Crawford
2476 IBM Research
2477 P.O. Box 704
2478 Yorktown Heights, NY 10598
2479
2480 EMail: [email protected]
2481
2482
2483 Julian F. Reschke (editor)
2484 greenbytes GmbH
2485 Hafenweg 16
2486 Muenster, NW 48155
2487 Germany
2488
2489 EMail: [email protected]
2490
2491
2492 Jim Whitehead
2493 UC Santa Cruz, Dept. of Computer Science
2494 1156 High Street
2495 Santa Cruz, CA 95064
2496
2497 EMail: [email protected]
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516 Clemm, et al. Experimental [Page 45]
2517 </pre>