draft-ietf-webdav-redirectref-protocol-07.txt   draft-ietf-webdav-redirectref-protocol-08.txt 
WEBDAV Working Group J. Whitehead WEBDAV Working Group J. Whitehead
Internet-Draft U.C. Santa Cruz Internet-Draft U.C. Santa Cruz
Expires: May 17, 2004 G. Clemm Expires: October 4, 2004 G. Clemm
IBM IBM
J. Reschke, Ed. J. Reschke, Ed.
greenbytes greenbytes
November 17, 2003 April 5, 2004
WebDAV Redirect Reference Resources Web Distributed Authoring and Versioning (WebDAV) Redirect Reference
draft-ietf-webdav-redirectref-protocol-07 Resources
draft-ietf-webdav-redirectref-protocol-08
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 17, 2004. This Internet-Draft will expire on October 4, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This specification defines redirect reference resources. A redirect This specification defines redirect reference resources. A redirect
reference resource is a resource whose default response is an HTTP/ reference resource is a resource whose default response is an HTTP/
1.1 302 (Found) status code, redirecting the client to a different 1.1 3xx (Redirection) status code (see [RFC2616], Section 10.3),
resource, the target resource. A redirect reference makes it redirecting the client to a different resource, the target resource.
possible to access the target resource indirectly, through any URI A redirect reference makes it possible to access the target resource
mapped to the redirect reference resource. There are no integrity indirectly, through any URI mapped to the redirect reference
guarantees associated with redirect reference resources. resource. There are no integrity guarantees associated with redirect
reference resources.
Distribution of this document is unlimited. Please send comments to Distribution of this document is unlimited. Please send comments to
the Distributed Authoring and Versioning (WebDAV) working group at the Distributed Authoring and Versioning (WebDAV) working group at
w3c-dist-auth@w3.org [1], which may be joined by sending a message <mailto:w3c-dist-auth@w3.org>, which may be joined by sending a
with subject "subscribe" to w3c-dist-auth-request@w3.org [2]. message with subject "subscribe" to
<mailto:w3c-dist-auth-request@w3.org?subject=subscribe>.
Discussions of the WEBDAV working group are archived at URL: http:// Discussions of the WEBDAV working group are archived at URL: <http://
lists.w3.org/Archives/Public/w3c-dist-auth/. lists.w3.org/Archives/Public/w3c-dist-auth/>.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Notational Conventions . . . . . . . . . . . . . . . . . . . 6 2. Notational Conventions . . . . . . . . . . . . . . . . . . . 5
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Overview of Redirect Reference Resources . . . . . . . . . . 8 4. Overview of Redirect Reference Resources . . . . . . . . . . 6
5. Creating a Redirect Reference Resource . . . . . . . . . . . 9 5. MKREDIRECTREF Method . . . . . . . . . . . . . . . . . . . . 7
5.1 MKRESOURCE . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.1 Example: Creating a Redirect Reference Resource with
5.2 Example: Creating a Redirect Reference Resource with MKREDIRECTREF . . . . . . . . . . . . . . . . . . . . . . 8
MKRESOURCE . . . . . . . . . . . . . . . . . . . . . . . . . 10 6. Operations on Redirect Reference Resources . . . . . . . . . 8
6. Operations on Redirect Reference Resources . . . . . . . . . 12
7. Operations on Collections That Contain Redirect Reference 7. Operations on Collections That Contain Redirect Reference
Resources . . . . . . . . . . . . . . . . . . . . . . . . . 13 Resources . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1 LOCK on a Collection That Contains Redirect References . . . 13 7.1 LOCK on a Collection That Contains Redirect References . . 9
7.2 Example: PROPFIND on a Collection with Redirect Reference 7.2 Example: PROPFIND on a Collection with Redirect
Resources . . . . . . . . . . . . . . . . . . . . . . . . . 13 Reference Resources . . . . . . . . . . . . . . . . . . . 10
7.3 Example: PROPFIND with Apply-To-Redirect-Ref on a 7.3 Example: PROPFIND with Apply-To-Redirect-Ref on a
Collection with Redirect Reference Resources . . . . . . . . 16 Collection with Redirect Reference Resources . . . . . . . 12
7.4 Example: COPY on a Collection That Contains a Redirect 7.4 Example: COPY on a Collection That Contains a Redirect
Reference Resource . . . . . . . . . . . . . . . . . . . . . 17 Reference Resource . . . . . . . . . . . . . . . . . . . . 13
7.5 Example: LOCK on a Collection That Contains a Redirect 7.5 Example: LOCK on a Collection That Contains a Redirect
Reference Resource . . . . . . . . . . . . . . . . . . . . . 18 Reference Resource . . . . . . . . . . . . . . . . . . . . 14
8. Operations on Targets of Redirect Reference Resources . . . 20 8. Operations on Targets of Redirect Reference Resources . . . 16
9. Relative URIs in DAV:reftarget . . . . . . . . . . . . . . . 21 9. Relative URIs in DAV:reftarget . . . . . . . . . . . . . . . 16
9.1 Example: Resolving a Relative URI in a Multi-Status 9.1 Example: Resolving a Relative URI in a Multi-Status
Response . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Response . . . . . . . . . . . . . . . . . . . . . . . . . 16
10. Redirect References to Collections . . . . . . . . . . . . . 23 10. Redirect References to Collections . . . . . . . . . . . . . 17
11. Headers . . . . . . . . . . . . . . . . . . . . . . . . . . 25 11. Headers . . . . . . . . . . . . . . . . . . . . . . . . . . 19
11.1 Redirect-Ref Response Header . . . . . . . . . . . . . . . . 25 11.1 Redirect-Ref Response Header . . . . . . . . . . . . . . 19
11.2 Apply-To-Redirect-Ref Request Header . . . . . . . . . . . . 25 11.2 Apply-To-Redirect-Ref Request Header . . . . . . . . . . 19
12. Properties . . . . . . . . . . . . . . . . . . . . . . . . . 26 12. Redirect Reference Resource Properties . . . . . . . . . . . 19
12.1 reftarget Property . . . . . . . . . . . . . . . . . . . . . 26 12.1 DAV:redirect-lifetime (protected) . . . . . . . . . . . 19
13. XML Elements . . . . . . . . . . . . . . . . . . . . . . . . 27 12.2 DAV:reftarget (protected) . . . . . . . . . . . . . . . 20
13.1 redirectref XML Element . . . . . . . . . . . . . . . . . . 27 13. XML Elements . . . . . . . . . . . . . . . . . . . . . . . . 20
13.1 redirectref XML Element . . . . . . . . . . . . . . . . 20
14. Extensions to the DAV:response XML Element for 14. Extensions to the DAV:response XML Element for
Multi-Status Responses . . . . . . . . . . . . . . . . . . . 28 Multi-Status Responses . . . . . . . . . . . . . . . . . . . 20
15. Capability Discovery . . . . . . . . . . . . . . . . . . . . 29 15. Capability Discovery . . . . . . . . . . . . . . . . . . . . 20
15.1 Example: Discovery of Support for Redirect Reference 15.1 Example: Discovery of Support for Redirect Reference
Resources . . . . . . . . . . . . . . . . . . . . . . . . . 29 Resources . . . . . . . . . . . . . . . . . . . . . . . 21
16. Security Considerations . . . . . . . . . . . . . . . . . . 30 16. Security Considerations . . . . . . . . . . . . . . . . . . 21
16.1 Privacy Concerns . . . . . . . . . . . . . . . . . . . . . . 30 16.1 Privacy Concerns . . . . . . . . . . . . . . . . . . . . 21
16.2 Redirect Loops . . . . . . . . . . . . . . . . . . . . . . . 30 16.2 Redirect Loops . . . . . . . . . . . . . . . . . . . . . 22
16.3 Redirect Reference Resources and Denial of Service . . . . . 30 16.3 Redirect Reference Resources and Denial of Service . . . 22
16.4 Revealing Private Locations . . . . . . . . . . . . . . . . 30 16.4 Revealing Private Locations . . . . . . . . . . . . . . 22
17. Internationalization Considerations . . . . . . . . . . . . 32 17. Internationalization Considerations . . . . . . . . . . . . 22
18. IANA Considerations . . . . . . . . . . . . . . . . . . . . 33 18. IANA Considerations . . . . . . . . . . . . . . . . . . . . 23
19. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 34 19. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23
20. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35 20. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23
Normative References . . . . . . . . . . . . . . . . . . . . 36 21. Normative References . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 24
A. Changes to the WebDAV Document Type Definition . . . . . . . 38 A. Changes to the WebDAV Document Type Definition . . . . . . . 24
B. Change Log (to be removed by RFC Editor before B. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . . . . . 39 publication) . . . . . . . . . . . . . . . . . . . . . . . . 25
B.1 Since draft-ietf-webdav-redirectref-protocol-02 . . . . . . 39 B.1 Since draft-ietf-webdav-redirectref-protocol-02 . . . . . 25
B.2 Since draft-ietf-webdav-redirectref-protocol-03 . . . . . . 39 B.2 Since draft-ietf-webdav-redirectref-protocol-03 . . . . . 25
B.3 Since draft-ietf-webdav-redirectref-protocol-04 . . . . . . 39 B.3 Since draft-ietf-webdav-redirectref-protocol-04 . . . . . 25
B.4 Since draft-ietf-webdav-redirectref-protocol-05 . . . . . . 39 B.4 Since draft-ietf-webdav-redirectref-protocol-05 . . . . . 25
B.5 Since draft-ietf-webdav-redirectref-protocol-06 . . . . . . 39 B.5 Since draft-ietf-webdav-redirectref-protocol-06 . . . . . 25
B.6 Since draft-ietf-webdav-redirectref-protocol-07 . . . . . 25
C. Resolved issues (to be removed by RFC Editor before C. Resolved issues (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . . . . . 40 publication) . . . . . . . . . . . . . . . . . . . . . . . . 26
C.1 lc-19-direct-ref . . . . . . . . . . . . . . . . . . . . . . 40 C.1 title . . . . . . . . . . . . . . . . . . . . . . . . . . 26
C.2 rfc2606-compliance . . . . . . . . . . . . . . . . . . . . . 40 C.2 lc-38-not-hierarchical . . . . . . . . . . . . . . . . . . 26
C.3 lc-28-lang . . . . . . . . . . . . . . . . . . . . . . . . . 40 C.3 lc-37-integrity . . . . . . . . . . . . . . . . . . . . . 26
C.4 lc-29-lang . . . . . . . . . . . . . . . . . . . . . . . . . 40 C.4 5_mkresource . . . . . . . . . . . . . . . . . . . . . . . 27
C.5 lc-44-pseudo . . . . . . . . . . . . . . . . . . . . . . . . 41 C.5 lc-41-no-webdav . . . . . . . . . . . . . . . . . . . . . 27
C.6 lc-61-pseudo . . . . . . . . . . . . . . . . . . . . . . . . 41 C.6 lc-24-properties . . . . . . . . . . . . . . . . . . . . . 27
C.7 lc-62-oldclient . . . . . . . . . . . . . . . . . . . . . . 41 C.7 lc-55-iana . . . . . . . . . . . . . . . . . . . . . . . . 28
C.8 lc-63-move . . . . . . . . . . . . . . . . . . . . . . . . . 42 C.8 A_DTD_cleanup . . . . . . . . . . . . . . . . . . . . . . 28
C.9 lc-53-s10 . . . . . . . . . . . . . . . . . . . . . . . . . 42 D. Open issues (to be removed by RFC Editor prior to
C.10 lc-76-location . . . . . . . . . . . . . . . . . . . . . . . 42 publication) . . . . . . . . . . . . . . . . . . . . . . . . 28
C.11 lc-80-i18n . . . . . . . . . . . . . . . . . . . . . . . . . 43 D.1 old_clients . . . . . . . . . . . . . . . . . . . . . . . 28
D. Open issues (to be removed by RFC Editor before D.2 lc-85-301 . . . . . . . . . . . . . . . . . . . . . . . . 29
publication) . . . . . . . . . . . . . . . . . . . . . . . . 44 D.3 lc-36-server . . . . . . . . . . . . . . . . . . . . . . . 29
D.1 old_clients . . . . . . . . . . . . . . . . . . . . . . . . 44 D.4 lc-33-forwarding . . . . . . . . . . . . . . . . . . . . . 29
D.2 lc-85-301 . . . . . . . . . . . . . . . . . . . . . . . . . 44 D.5 3-terminology-redirectref . . . . . . . . . . . . . . . . 30
D.3 lc-38-not-hierarchical . . . . . . . . . . . . . . . . . . . 45 D.6 lc-58-update . . . . . . . . . . . . . . . . . . . . . . . 30
D.4 lc-36-server . . . . . . . . . . . . . . . . . . . . . . . . 45 D.7 lc-48-s6 . . . . . . . . . . . . . . . . . . . . . . . . . 30
D.5 lc-33-forwarding . . . . . . . . . . . . . . . . . . . . . . 45 D.8 lc-57-noautoupdate . . . . . . . . . . . . . . . . . . . . 31
D.6 lc-37-integrity . . . . . . . . . . . . . . . . . . . . . . 46 D.9 12.1-property-name . . . . . . . . . . . . . . . . . . . . 31
D.7 3-terminology-redirectref . . . . . . . . . . . . . . . . . 46 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
D.8 lc-41-no-webdav . . . . . . . . . . . . . . . . . . . . . . 46 Intellectual Property and Copyright Statements . . . . . . . 33
D.9 lc-58-update . . . . . . . . . . . . . . . . . . . . . . . . 46
D.10 lc-24-properties . . . . . . . . . . . . . . . . . . . . . . 47
D.11 lc-48-s6 . . . . . . . . . . . . . . . . . . . . . . . . . . 47
D.12 lc-57-noautoupdate . . . . . . . . . . . . . . . . . . . . . 47
D.13 12.1-property-name . . . . . . . . . . . . . . . . . . . . . 48
D.14 lc-55-iana . . . . . . . . . . . . . . . . . . . . . . . . . 48
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Intellectual Property and Copyright Statements . . . . . . . 50
1. Introduction 1. Introduction
This is one of a pair of specifications that extend the WebDAV This is one of a pair of specifications that extend the WebDAV
Distributed Authoring Protocol to enable clients to create new access Distributed Authoring Protocol to enable clients to create new access
paths to existing resources. This capability is useful for several paths to existing resources. This capability is useful for several
reasons: reasons:
URIs of WebDAV-compliant resources are hierarchical and correspond to The WebDAV Distributed Authoring Protocol makes it possible to
a hierarchy of collections in resource space. The WebDAV Distributed organize HTTP resources into hierarchies, placing them into
Authoring Protocol makes it possible to organize these resources into groupings, known as collections, which are more easily browsed and
hierarchies, placing them into groupings, known as collections, which manipulated than a single flat collection. However, hierarchies
are more easily browsed and manipulated than a single flat require categorization decisions that locate resources at a single
collection. However, hierarchies require categorization decisions location in the hierarchy, a drawback when a resource has multiple
that locate resources at a single location in the hierarchy, a valid categories. For example, in a hierarchy of vehicle descriptions
drawback when a resource has multiple valid categories. For example, containing collections for cars and boats, a description of a
in a hierarchy of vehicle descriptions containing collections for combination car/boat vehicle could belong in either collection.
cars and boats, a description of a combination car/boat vehicle could Ideally, the description should be accessible from both. Allowing
belong in either collection. Ideally, the description should be clients to create new URIs that access the existing resource lets
accessible from both. Allowing clients to create new URIs that access them put that resource into multiple collections.
the existing resource lets them put that resource into multiple
collections.
Hierarchies also make resource sharing more difficult, since Hierarchies also make resource sharing more difficult, since
resources that have utility across many collections are still forced resources that have utility across many collections are still forced
into a single collection. For example, the mathematics department at into a single collection. For example, the mathematics department at
one university might create a collection of information on fractals one university might create a collection of information on fractals
that contains bindings to some local resources, but also provides that contains bindings to some local resources, but also provides
access to some resources at other universities. For many reasons, it access to some resources at other universities. For many reasons, it
may be undesirable to make physical copies of the shared resources on may be undesirable to make physical copies of the shared resources on
the local server: to conserve disk space, to respect copyright the local server: to conserve disk space, to respect copyright
constraints, or to make any changes in the shared resources visible constraints, or to make any changes in the shared resources visible
automatically. Being able to create new access paths to existing automatically. Being able to create new access paths to existing
resources in other collections or even on other servers is useful for resources in other collections or even on other servers is useful for
this sort of case. this sort of case.
The redirect reference resources defined here provide a mechanism for The redirect reference resources defined here provide a mechanism for
creating alternative access paths to existing resources. A redirect creating alternative access paths to existing resources. A redirect
reference resource is a resource in one collection whose purpose is reference resource is a resource in one collection whose purpose is
to forward requests to another resource (its target), possibly in a to forward requests to another resource (its target), possibly in a
different collection. In this way, it allows clients to submit different collection. In this way, it allows clients to submit
requests to the target resource from another collection. It requests to the target resource from another collection. It
redirects most requests to the target resource using the HTTP 302 redirects most requests to the target resource using a HTTP status
(Found) status code, thereby providing a form of mediated access to code from the 3xx range (Redirection), thereby providing a form of
the target resource. mediated access to the target resource.
A redirect reference is a resource with properties but no body of its A redirect reference is a resource with properties but no body of its
own. Properties of a redirect reference resource can contain such own. Properties of a redirect reference resource can contain such
information as who created the reference, when, and why. Since information as who created the reference, when, and why. Since
redirect reference resources are implemented using HTTP 302 redirect reference resources are implemented using HTTP 3xx
responses, it generally takes two round trips to submit a request to responses, it generally takes two round trips to submit a request to
the intended resource. Servers are not required to enforce the the intended resource. Redirect references work equally well for
integrity of redirect references. Redirect references work equally local resources and for resources that reside on a different server
well for local resources and for resources that reside on a different from the reference.
server from the reference.
The remainder of this document is structured as follows: Section 3 The remainder of this document is structured as follows: Section 3
defines terms that will be used throughout the specification. defines terms that will be used throughout the specification.
Section 4 provides an overview of redirect reference resources. Section 4 provides an overview of redirect reference resources.
Section 5 discusses how to create a redirect reference resource. Section 5 discusses how to create a redirect reference resource.
Section 6 defines the semantics of existing methods when applied to Section 6 defines the semantics of existing methods when applied to
redirect reference resources, and Section 7 discusses their semantics redirect reference resources, and Section 7 discusses their semantics
when applied to collections that contain redirect reference when applied to collections that contain redirect reference
resources. Sections 8 through 10 discuss several other issues raised resources. Sections 8 through 10 discuss several other issues raised
by the existence of redirect reference resources. Sections 11 by the existence of redirect reference resources. Sections 11
skipping to change at page 7, line 14 skipping to change at page 5, line 47
3. Terminology 3. Terminology
The terminology used here follows and extends that in the WebDAV The terminology used here follows and extends that in the WebDAV
Distributed Authoring Protocol specification [RFC2518]. Definitions Distributed Authoring Protocol specification [RFC2518]. Definitions
of the terms resource, Uniform Resource Identifier (URI), and Uniform of the terms resource, Uniform Resource Identifier (URI), and Uniform
Resource Locator (URL) are provided in [RFC2396]. Resource Locator (URL) are provided in [RFC2396].
Redirect Reference Resource Redirect Reference Resource
A resource created to redirect all requests made to it, using 302 A resource created to redirect all requests made to it, using an
(Found), to a defined target resource. HTTP status code from the 3xx range, to a defined target resource.
Non-Reference Resource Non-Reference Resource
A resource that is not a reference to another resource. A resource that is not a reference to another resource.
Target Resource Target Resource
The resource to which requests are forwarded by a reference The resource to which requests are forwarded by a reference
resource. A target resource can be anything that can be identified resource. A target resource can be anything that can be identified
by an absolute URI (see [RFC2396], "absoluteURI"). by an absolute URI (see [RFC2396], "absoluteURI").
This document uses the terms "precondition", "postcondition" and
"protected property" as defined in [RFC3253]. Servers MUST report
pre-/postcondition failures as described in section 1.6 of this
document.
4. Overview of Redirect Reference Resources 4. Overview of Redirect Reference Resources
For all operations submitted to a redirect reference resource, the For all operations submitted to a redirect reference resource, the
default response is a 302 (Found), accompanied by the Redirect-Ref default response is a 302 (Found), accompanied by the Redirect-Ref
header (defined in Section 11.1 below) and the Location header set to header (defined in Section 11.1 below) and the Location header set to
the URI of the target resource. With this information, the client the URI of the target resource. With this information, the client
can resubmit the request to the URI of the target resource. can resubmit the request to the URI of the target resource.
A redirect reference resource never automatically forwards requests A redirect reference resource never automatically forwards requests
to its target resource. Redirect resources bring the same benefits as to its target resource. Redirect resources bring the same benefits as
links in HTML documents. They can be created and maintained without links in HTML documents. They can be created and maintained without
the involvement or even knowledge of their target resource. This the involvement or even knowledge of their target resource. This
reduces the cost of linking between resources." reduces the cost of linking between resources."
If the client is aware that it is operating on a redirect reference If the client is aware that it is operating on a redirect reference
resource, it can resolve the reference by retrieving the reference resource, it can resolve the reference by retrieving the reference
resource's DAV:reftarget property (defined in Section 12.1 below), resource's DAV:reftarget property (defined in Section 12.2 below),
whose value contains the URI of the target resource. It can then whose value contains the URI of the target resource. It can then
submit requests to the target resource. submit requests to the target resource.
A redirect reference resource is a new type of resource. To A redirect reference resource is a new type of resource. To
distinguish redirect reference resources from non-reference distinguish redirect reference resources from non-reference
resources, a new value of the DAV:resourcetype property (defined in resources, a new value of the DAV:resourcetype property (defined in
[RFC2518]), DAV:redirectref, is defined in Section 13.1 below. [RFC2518]), DAV:redirectref, is defined in Section 13.1 below.
Since a redirect reference resource is a resource, methods can be Since a redirect reference resource is a resource, methods can be
applied to the reference resource as well as to its target resource. applied to the reference resource as well as to its target resource.
The Apply-To-Redirect-Ref request header (defined in Section 11.2 The Apply-To-Redirect-Ref request header (defined in Section 11.2
below) is provided so that referencing-aware clients can control below) is provided so that referencing-aware clients can control
whether an operation is applied to the redirect reference resource or whether an operation is applied to the redirect reference resource or
standard HTTP/WebDAV behaviour (redirection with a 3xx status code) standard HTTP/WebDAV behaviour (redirection with a 3xx status code)
should occur. The Apply-To-Redirect-Ref header can be used with most should occur. The Apply-To-Redirect-Ref header can be used with most
requests to redirect reference resources. This header is requests to redirect reference resources. This header is
particularly useful with PROPFIND, to retrieve the reference particularly useful with PROPFIND, to retrieve the reference
resource's own properties. resource's own properties.
5. Creating a Redirect Reference Resource 5. MKREDIRECTREF Method
The new MKRESOURCE method is used to create new redirect reference
resources. In order to create a redirect reference resource using
MKRESOURCE, the values of two properties must be set in the body of
the MKRESOURCE request. The value of DAV:resourcetype MUST be set to
DAV:redirectref, a new value of DAV:resourcetype defined in Section
13.1. The value of DAV:reftarget MUST be set to the URI of the target
resource.
Used in this way, the MKRESOURCE method creates a redirect reference
resource whose target is identified by the DAV:reftarget property.
5.1 MKRESOURCE
The MKRESOURCE method requests the creation of a redirect reference The MKREDIRECTREF method requests the creation of a redirect
resource and initialization of its properties in one atomic reference resource.
operation.
Preconditions: If a MKREDIRECTREF request fails, the server state preceding the
request MUST be restored.
A resource MUST NOT exist at the Request-URI. Responses from a MKREDIRECTREF request MUST NOT be cached, as
MKREDIRECTREF has non-idempotent semantics.
Request Marshalling: Marshalling:
The location of the new resource to be created is specified by the The request body MUST be a DAV:mkredirectref XML element.
Request-URI.
The request body of the MKRESOURCE method MUST consist of the <!ELEMENT mkredirectref (reftarget, redirect-lifetime?)>
DAV:propertyupdate XML element defined in Section 12.13 of <!ELEMENT reftarget (href)>
[RFC2518], specifying a DAV:resourcetype of "DAV:redirectref". <!ELEMENT redirect-lifetime (permanent | temporary)>
<!ELEMENT permanent EMPTY>
<!ELEMENT temporary EMPTY>
Postconditions: The DAV:href element is defined in [RFC2518] (Section 12.3) and
MUST contain either an absoluteURI or a relativeURI (see
[RFC2396], Section 3 and 5).
If the response status code is 201, a new resource exists at the If the request succeeds, the server MUST return 201 (Created)
Request-URI. status.
The properties of the new resource are as specified by the If a response body for a successful request is included, it MUST
DAV:propertyupdate request body, using PROPPATCH semantics. be a DAV:mkredirectref-response XML element. Note that this
document does not define any elements for the MKREDIRECTREF
response body, but the DAV:mkredirectref-response element is
defined to ensure interoperability between future extensions that
do define elements for the MKREDIRECTREF response body.
If the response status code is not 201, then a new resource is not <!ELEMENT mkredirectref-response ANY>
created at the Request-URI, and any existing resource at the
Request-URI is unaffected.
Response Marshalling: Preconditions:
Responses from a MKRESOURCE request MUST NOT be cached, as (DAV:resource-must-be-null): A resource MUST NOT exist at the
MKRESOURCE has non-idempotent semantics. request-URL.
The following status codes can be expected in responses to (DAV:parent-resource-must-be-non-null): The request-URL minus the
MKRESOURCE: last past segment MUST identify a collection.
201 (Created): The new resource was successfully created. (DAV:name-allowed): The last segment of the request URL is
available for use as a resource name.
403 (Forbidden): The server does not allow the creation of the (DAV:locked-update-allowed): If the collection identified by the
requested resource type at the requested location, or the parent Request-URL minus the last path segment is write-locked, then the
collection of the Request-URI exists but cannot accept members. appropriate token MUST be specified in an If request header.
409 (Conflict): A resource cannot be created at the Request-URI (DAV:redirect-lifetime-supported): If the request body contains a
because the parent collection for the resource does not exist, or DAV:redirect-lifetime element, the server MUST support the
because there is already a resource at that request-URL. specified liftime. Support for DAV:temporary is REQUIRED, while
support for DAV:permanent is OPTIONAL.
423 (Locked): The Request-URI is locked, and the lock token was Postconditions:
not passed with the request.
507 (Insufficient Storage): The server does not have sufficient (DAV:new-redirectref): a new redirect reference resource is
space to record the state of the resource. created whose DAV:reftarget property has the value specified in
the request body.
5.2 Example: Creating a Redirect Reference Resource with MKRESOURCE 5.1 Example: Creating a Redirect Reference Resource with MKREDIRECTREF
>> Request: >> Request:
MKRESOURCE /~whitehead/dav/spec08.ref HTTP/1.1 MKREDIRECTREF /~whitehead/dav/spec08.ref HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propertyupdate xmlns:D="DAV:"> <D:mkredirectref xmlns:D="DAV:">
<D:set>
<D:prop>
<D:resourcetype><D:redirectref/></D:resourcetype>
<D:reftarget> <D:reftarget>
<D:href>/i-d/draft-webdav-protocol-08.txt</D:href> <D:href>/i-d/draft-webdav-protocol-08.txt</D:href>
</D:reftarget> </D:reftarget>
</D:prop> </D:mkredirectref>
</D:set>
</D:propertyupdate>
>> Response: >> Response:
HTTP/1.1 201 Created HTTP/1.1 201 Created
This request resulted in the creation of a new redirect reference This request resulted in the creation of a new redirect reference
resource at http://www.example.com/~whitehead/dav/spec08.ref, which resource at http://www.example.com/~whitehead/dav/spec08.ref, which
points to the resource identified by the DAV:reftarget property. In points to the resource identified by the DAV:reftarget property. In
this example, the target resource is identified by the URI http:// this example, the target resource is identified by the URI http://
www.example.com/i-d/draft-webdav-protocol-08.txt. The redirect www.example.com/i-d/draft-webdav-protocol-08.txt. The redirect
reference resource's DAV:resourcetype property is set to reference resource's DAV:resourcetype property is set to
DAV:redirectref. DAV:redirectref.
6. Operations on Redirect Reference Resources 6. Operations on Redirect Reference Resources
Although non-referencing-aware clients cannot create reference Although non-referencing-aware clients cannot create reference
resources, they should be able to submit requests through the resources, they should be able to submit requests through the
reference resources created by reference-aware WebDAV clients. They reference resources created by reference-aware WebDAV clients. They
should be able to follow any references to their targets. To make should be able to follow any references to their targets. To make
this possible, a server that receives any request made via a redirect this possible, a server that receives any request made via a redirect
reference resource MUST return a 302 (Found) status code, unless the reference resource MUST return a 3xx range (Redirection) status code,
request includes an Apply-To-Redirect-Ref header specifying "T". The unless the request includes an Apply-To-Redirect-Ref header
client and server MUST follow [RFC2616] Section 10.3.3 "302 Found", specifying "T". The client and server MUST follow [RFC2616] Section
but with these additional rules: 10.3, but with these additional rules:
o The Location response header MUST contain an absolute URI that o The Location response header MUST contain an absolute URI that
identifies the target of the reference resource. identifies the target of the reference resource.
o The response MUST include the Redirect-Ref header. This header o The response MUST include the Redirect-Ref header. This header
allows reference-aware WebDAV clients to recognize the resource as allows reference-aware WebDAV clients to recognize the resource as
a reference resource and understand the reason for the a reference resource and understand the reason for the
redirection. redirection.
A reference-aware WebDAV client can, like a non-referencing client, A reference-aware WebDAV client can, like a non-referencing client,
resubmit the request to the URI in the Location header in order to resubmit the request to the URI in the Location header in order to
operate on the target resource. Alternatively, it can resubmit the operate on the target resource. Alternatively, it can resubmit the
request to the URI of the redirect reference resource with the request to the URI of the redirect reference resource with the
"Apply-To-Redirect-Ref: T" header in order to operate on the "Apply-To-Redirect-Ref: T" header in order to operate on the
reference resource itself. In this case, the request MUST be applied reference resource itself. In this case, the request MUST be applied
to the reference resource itself, and a 302 response MUST NOT be to the reference resource itself, and a 3xx response MUST NOT be
returned. returned.
As redirect references do not have bodies, GET and PUT requests with As redirect references do not have bodies, GET and PUT requests with
"Apply-To-Redirect-Ref: T" MUST fail with status 403 (forbidden). "Apply-To-Redirect-Ref: T" MUST fail with status 403 (forbidden).
7. Operations on Collections That Contain Redirect Reference Resources 7. Operations on Collections That Contain Redirect Reference Resources
Consistent with the rules in Section 6, the response for each Consistent with the rules in Section 6, the response for each
redirect reference encountered while processing a collection MUST be redirect reference encountered while processing a collection MUST be
a 302 (Found) unless a "Apply-To-Redirect-Ref: T" header is included a 3xx (Redirection) unless a "Apply-To-Redirect-Ref: T" header is
with the request. The overall response will therefore be a 207 included with the request. The overall response will therefore be a
(Multi-Status). For each DAV:response element representing a redirect 207 (Multi-Status). For each DAV:response element representing a
reference, the server MUST include an additional DAV:location redirect reference, the server MUST include an additional
element, specifying the value of the "Location" header that would be DAV:location element, specifying the value of the "Location" header
returned otherwise. The extension is defined in Section 14 below. that would be returned otherwise. The extension is defined in Section
14 below.
The Apply-To-Redirect-Ref header (defined in Section 11.2) MAY be The Apply-To-Redirect-Ref header (defined in Section 11.2) MAY be
used with any request on a collection. If present, it will be used with any request on a collection. If present, it will be
applied to all redirect reference resources encountered while applied to all redirect reference resources encountered while
processing the collection. processing the collection.
7.1 LOCK on a Collection That Contains Redirect References 7.1 LOCK on a Collection That Contains Redirect References
An attempt to lock (with Depth: infinity) a collection that contains An attempt to lock (with Depth: infinity) a collection that contains
redirect references without specifying "Apply-To-Redirect-Ref: T" redirect references without specifying "Apply-To-Redirect-Ref: T"
will always fail. The Multi-Status response will contain a 302 will always fail. The Multi-Status response will contain a 3xx
response for each redirect reference. response for each redirect reference.
Reference-aware clients can lock the collection by using Reference-aware clients can lock the collection by using
Apply-To-Redirect-Ref, and, if desired, lock the targets of the Apply-To-Redirect-Ref, and, if desired, lock the targets of the
redirect references individually. redirect references individually.
Non-referencing clients must resort to locking each resource Non-referencing clients must resort to locking each resource
individually. individually.
7.2 Example: PROPFIND on a Collection with Redirect Reference Resources 7.2 Example: PROPFIND on a Collection with Redirect Reference Resources
skipping to change at page 23, line 11 skipping to change at page 18, line 5
the base URI for resolving the relative URI in reftarget. The the base URI for resolving the relative URI in reftarget. The
absolute URI of reftarget is http://example.com/geog/statistics/ absolute URI of reftarget is http://example.com/geog/statistics/
population/1997.html. population/1997.html.
10. Redirect References to Collections 10. Redirect References to Collections
In a Request-URI /segment1/segment2/segment3, any of the three In a Request-URI /segment1/segment2/segment3, any of the three
segments may identify a redirect reference resource. (See [RFC2396], segments may identify a redirect reference resource. (See [RFC2396],
Section 3.3, for definitions of "path" and "segment".) If any Section 3.3, for definitions of "path" and "segment".) If any
segment in a Request-URI identifies a redirect reference resource, segment in a Request-URI identifies a redirect reference resource,
the response SHOULD be a 302. The value of the Location header in the the response SHOULD be a 3xx. The value of the Location header in the
302 response is as follows: response is as follows:
The leftmost path segment of the request-URI that identifies a The leftmost path segment of the request-URI that identifies a
redirect reference resource, together with all path segments and redirect reference resource, together with all path segments and
separators to the left of it, is replaced by the value of the separators to the left of it, is replaced by the value of the
redirect reference resource's DAV:reftarget property (resolved to an redirect reference resource's DAV:reftarget property (resolved to an
absolute URI). The remainder of the request-URI is concatenated to absolute URI). The remainder of the request-URI is concatenated to
this path. this path.
Note: If the DAV:reftarget property ends with a "/" and the remainder Note: If the DAV:reftarget property ends with a "/" and the remainder
of the Request-URI is non-empty (and therefore must begin with a "/ of the Request-URI is non-empty (and therefore must begin with a "/
skipping to change at page 23, line 49 skipping to change at page 18, line 43
| /a/y -> /b | /a/y -> /b
| |
v v
/b/z.html /b/z.html
| |
| /b/z.html -> /c/d.html | /b/z.html -> /c/d.html
| |
v v
/c/d.html /c/d.html
In this case the client must follow up three separate 302 responses In this case the client must follow up three separate 3xx responses
before finally reaching the target resource. The server responds to before finally reaching the target resource. The server responds to
the initial request with a 302 with Location: /a/y/z.html, and the the initial request with a 3xx with Location: /a/y/z.html, and the
client resubmits the request to /a/y/z.html. The server responds to client resubmits the request to /a/y/z.html. The server responds to
this request with a 302 with Location: /b/z.html, and the client this request with a 3xx with Location: /b/z.html, and the client
resubmits the request to /b/z.html. The server responds to this resubmits the request to /b/z.html. The server responds to this
request with a 302 with Location: /c/d.html, and the client resubmits request with a 3xx with Location: /c/d.html, and the client resubmits
the request to /c/d.html. This final request succeeds. the request to /c/d.html. This final request succeeds.
Note: the behavior described above may have a very serious impact Note: the behavior described above may have a very serious impact
on the efficiency of mapping Request-URIs to resources in HTTP on the efficiency of mapping Request-URIs to resources in HTTP
request processing. Therefore servers MAY respond with a 404 request processing. Therefore servers MAY respond with a 404
status code if the cost of checking all leading path segments for status code if the cost of checking all leading path segments for
redirect references seems prohibitive. redirect references seems prohibitive.
11. Headers 11. Headers
11.1 Redirect-Ref Response Header 11.1 Redirect-Ref Response Header
Redirect-Ref = "Redirect-Ref:" (absoluteURI | relativeURI) Redirect-Ref = "Redirect-Ref:" (absoluteURI | relativeURI)
; see sections 3 and 5 of [RFC2396] ; see sections 3 and 5 of [RFC2396]
The Redirect-Ref header is used in all 302 responses from redirect The Redirect-Ref header is used in all 3xx responses from redirect
reference resources. The value is the (possibly relative) URI of the reference resources. The value is the (possibly relative) URI of the
link target as specified during redirect reference resource creation. link target as specified during redirect reference resource creation.
11.2 Apply-To-Redirect-Ref Request Header 11.2 Apply-To-Redirect-Ref Request Header
Apply-To-Redirect-Ref = "Apply-To-Redirect-Ref" ":" ("T" | "F") Apply-To-Redirect-Ref = "Apply-To-Redirect-Ref" ":" ("T" | "F")
The optional Apply-To-Redirect-Ref header can be used on any request The optional Apply-To-Redirect-Ref header can be used on any request
to a redirect reference resource. When it is present and set to "T", to a redirect reference resource. When it is present and set to "T",
the request MUST be applied to the reference resource itself, and a the request MUST be applied to the reference resource itself, and a
302 response MUST NOT be returned. 3xx response MUST NOT be returned.
If the Apply-To-Redirect-Ref header is used on a request to any other If the Apply-To-Redirect-Ref header is used on a request to any other
sort of resource besides a redirect reference resource, the server sort of resource besides a redirect reference resource, the server
MUST ignore it. MUST ignore it.
12. Properties 12. Redirect Reference Resource Properties
12.1 reftarget Property The properties defined below are REQUIRED on redirect reference
resources.
Name: reftarget 12.1 DAV:redirect-lifetime (protected)
Namespace: DAV: This property provides information about the lifetime of a redirect.
It can either be DAV:permanent (HTTP status 301) or DAV:temporary
(HTTP status 302). Future protocols MAY define additional values.
Purpose: A property of redirect reference resources that provides an <!ELEMENT redirect-lifetime (permanent | temporary)>
efficient way for clients to discover the URI of the target <!ELEMENT permanent EMPTY>
resource. This is a read-only property after its initial <!ELEMENT temporary EMPTY>
creation. Its value can only be set in a MKRESOURCE request.
Value: href containing the URI of the target resource. This value 12.2 DAV:reftarget (protected)
MAY be a relative URI. The reftarget property can occur in the
entity bodies of MKRESOURCE requests and of responses to PROPFIND This property provides an efficient way for clients to discover the
requests. URI of the target resource. This is a read-only property after its
initial creation. Its value can only be set in a MKREDIRECTREF
request. The value is a DAV:href element containing the URI of the
target resource.
<!ELEMENT reftarget href > <!ELEMENT reftarget href >
13. XML Elements 13. XML Elements
13.1 redirectref XML Element 13.1 redirectref XML Element
Name: redirectref Name: redirectref
Namespace: DAV: Namespace: DAV:
skipping to change at page 29, line 16 skipping to change at page 21, line 9
Sections 9.1 and 15 of [RFC2518] describe the use of compliance Sections 9.1 and 15 of [RFC2518] describe the use of compliance
classes with the DAV header in responses to OPTIONS, to indicate classes with the DAV header in responses to OPTIONS, to indicate
which parts of the WebDAV Distributed Authoring protocols the which parts of the WebDAV Distributed Authoring protocols the
resource supports. This specification defines an OPTIONAL extension resource supports. This specification defines an OPTIONAL extension
to [RFC2518]. It defines a new compliance class, called to [RFC2518]. It defines a new compliance class, called
redirectrefs, for use with the DAV header in responses to OPTIONS redirectrefs, for use with the DAV header in responses to OPTIONS
requests. If a resource does support redirect references, its requests. If a resource does support redirect references, its
response to an OPTIONS request may indicate that it does, by listing response to an OPTIONS request may indicate that it does, by listing
the new redirectrefs compliance class in the DAV header and by the new redirectrefs compliance class in the DAV header and by
listing the MKRESOURCE method as one it supports. listing the MKREDIRECTREF method as one it supports.
When responding to an OPTIONS request, any type of resource can When responding to an OPTIONS request, any type of resource can
include redirectrefs in the value of the DAV header. Doing so include redirectrefs in the value of the DAV header. Doing so
indicates that the server permits a redirect reference resource at indicates that the server permits a redirect reference resource at
the request URI. the request URI.
15.1 Example: Discovery of Support for Redirect Reference Resources 15.1 Example: Discovery of Support for Redirect Reference Resources
>> Request: >> Request:
OPTIONS /somecollection/someresource HTTP/1.1 OPTIONS /somecollection/someresource HTTP/1.1
Host: example.org Host: example.org
>> Response: >> Response:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE
Allow: MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, MKRESOURCE Allow: MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, MKREDIRECTREF
DAV: 1, 2, redirectrefs DAV: 1, 2, redirectrefs
The DAV header in the response indicates that the resource / The DAV header in the response indicates that the resource /
somecollection/someresource is level 1 and level 2 compliant, as somecollection/someresource is level 1 and level 2 compliant, as
defined in [RFC2518]. In addition, /somecollection/someresource defined in [RFC2518]. In addition, /somecollection/someresource
supports redirect reference resources. The Allow header indicates supports redirect reference resources. The Allow header indicates
that MKRESOURCE requests can be submitted to /somecollection/ that MKREDIRECTREF requests can be submitted to /somecollection/
someresource. someresource.
16. Security Considerations 16. Security Considerations
This section is provided to make applications that implement this This section is provided to make applications that implement this
protocol aware of the security implications of this protocol. protocol aware of the security implications of this protocol.
All of the security considerations of HTTP/1.1 and the WebDAV All of the security considerations of HTTP/1.1 and the WebDAV
Distributed Authoring Protocol specification also apply to this Distributed Authoring Protocol specification also apply to this
protocol specification. In addition, redirect reference resources protocol specification. In addition, redirect reference resources
skipping to change at page 30, line 28 skipping to change at page 22, line 12
By creating redirect reference resources on a trusted server, it is By creating redirect reference resources on a trusted server, it is
possible for a hostile agent to induce users to send private possible for a hostile agent to induce users to send private
information to a target on a different server. This risk is information to a target on a different server. This risk is
mitigated somewhat, since clients are required to notify the user of mitigated somewhat, since clients are required to notify the user of
the redirection for any request other than GET or HEAD. (See the redirection for any request other than GET or HEAD. (See
[RFC2616], Section 10.3.3 302 Found.) [RFC2616], Section 10.3.3 302 Found.)
16.2 Redirect Loops 16.2 Redirect Loops
Although redirect loops were already possible in HTTP 1.1, the Although redirect loops were already possible in HTTP 1.1, the
introduction of the MKRESOURCE method creates a new avenue for introduction of the MKREDIRECTREF method creates a new avenue for
clients to create loops accidentally or maliciously. If the clients to create loops accidentally or maliciously. If the
reference resource and its target are on the same server, the server reference resource and its target are on the same server, the server
may be able to detect MKRESOURCE requests that would create loops. may be able to detect MKREDIRECTREF requests that would create loops.
See also [RFC2616], Section 10.3 "Redirection 3xx." See also [RFC2616], Section 10.3 "Redirection 3xx."
16.3 Redirect Reference Resources and Denial of Service 16.3 Redirect Reference Resources and Denial of Service
Denial of service attacks were already possible by posting URLs that Denial of service attacks were already possible by posting URLs that
were intended for limited use at heavily used Web sites. The were intended for limited use at heavily used Web sites. The
introduction of MKRESOURCE creates a new avenue for similar denial of introduction of MKREDIRECTREF creates a new avenue for similar denial
service attacks. Clients can now create redirect reference resources of service attacks. Clients can now create redirect reference
at heavily used sites to target locations that were not designed for resources at heavily used sites to target locations that were not
heavy usage. designed for heavy usage.
16.4 Revealing Private Locations 16.4 Revealing Private Locations
There are several ways that redirect reference resources may reveal There are several ways that redirect reference resources may reveal
information about collection structures. First, the DAV:reftarget information about collection structures. First, the DAV:reftarget
property of every redirect reference resource contains the URI of the property of every redirect reference resource contains the URI of the
target resource. Anyone who has access to the reference resource can target resource. Anyone who has access to the reference resource can
discover the collection path that leads to the target resource. The discover the collection path that leads to the target resource. The
owner of the target resource may have wanted to limit knowledge of owner of the target resource may have wanted to limit knowledge of
this collection structure. this collection structure.
skipping to change at page 35, line 10 skipping to change at page 23, line 21
Many thanks to Jason Crawford, Jim Davis, Chuck Fay and Judith Slein Many thanks to Jason Crawford, Jim Davis, Chuck Fay and Judith Slein
who can take credit for big parts of the original design of this who can take credit for big parts of the original design of this
specification. specification.
20. Acknowledgements 20. Acknowledgements
This document has benefited from thoughtful discussion by Jim Amsden, This document has benefited from thoughtful discussion by Jim Amsden,
Peter Carlson, Steve Carter, Tyson Chihaya, Ken Coar, Ellis Cohen, Peter Carlson, Steve Carter, Tyson Chihaya, Ken Coar, Ellis Cohen,
Bruce Cragun, Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Bruce Cragun, Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand,
Roy Fielding, Yaron Goland, Fred Hitt, Alex Hopmann, James Hunt, Lisa Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland, Fred
Marcus Jager, Chris Kaler, Manoj Kasichainula, Rohit Khare, Daniel Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris Kaler, Manoj
LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Joe Orton, Kasichainula, Rohit Khare, Daniel LaLiberte, Steve Martin, Larry
Surendra Koduru Reddy, Juergen Reuter, Max Rible, Sam Ruby, Bradley Masinter, Jeff McAffer, Joe Orton, Surendra Koduru Reddy, Juergen
Sergeant, Nick Shelness, John Stracke, John Tigue, John Turner, Kevin Reuter, Max Rible, Sam Ruby, Bradley Sergeant, Nick Shelness, John
Wiggen, and others. Stracke, John Tigue, John Turner, Kevin Wiggen, and others.
Normative References 21 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396, Resource Identifiers (URI): Generic Syntax", RFC 2396,
August 1998. August 1998.
[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D. [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D.
Jensen, "HTTP Extensions for Distributed Authoring -- Jensen, "HTTP Extensions for Distributed Authoring --
WEBDAV", RFC 2518, February 1999. WEBDAV", RFC 2518, February 1999.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[1] <mailto:w3c-dist-auth@w3.org> [RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C. and J.
Whitehead, "Versioning Extensions to WebDAV (Web
[2] <mailto:w3c-dist-auth-request@w3.org?subject=subscribe> Distributed Authoring and Versioning)", RFC 3253, March
2002.
Authors' Addresses Authors' Addresses
Jim Whitehead Jim Whitehead
UC Santa Cruz, Dept. of Computer Science UC Santa Cruz, Dept. of Computer Science
1156 High Street 1156 High Street
Santa Cruz, CA 95064 Santa Cruz, CA 95064
US US
EMail: ejw@cse.ucsc.edu EMail: ejw@cse.ucsc.edu
skipping to change at page 38, line 7 skipping to change at page 24, line 36
Muenster, NW 48159 Muenster, NW 48159
Germany Germany
Phone: +49 251 2807760 Phone: +49 251 2807760
Fax: +49 251 2807761 Fax: +49 251 2807761
EMail: julian.reschke@greenbytes.de EMail: julian.reschke@greenbytes.de
URI: http://greenbytes.de/tech/webdav/ URI: http://greenbytes.de/tech/webdav/
Appendix A. Changes to the WebDAV Document Type Definition Appendix A. Changes to the WebDAV Document Type Definition
<!-- XML Elements from Section 13 --> <!-- Property Elements from Section 12 -->
<!ELEMENT redirectref EMPTY >
<!-- -->Property Elements from Section 12 -->
<!ELEMENT reftarget href> <!ELEMENT reftarget href>
<!ELEMENT location href> <!ELEMENT location href>
<!-- XML Elements from Section 13-->
<!ELEMENT redirectref EMPTY >
<!-- Changes to the DAV:response Element from Section 14 --> <!-- Changes to the DAV:response Element from Section 14 -->
<!ELEMENT response (href, ((href*, status, prop?) | (propstat+)),
responsedescription?) > <!ELEMENT response (href, ((href*, status)|(propstat+)),
responsedescription?, location?) >
<!ELEMENT location (href) >
Appendix B. Change Log (to be removed by RFC Editor before publication) Appendix B. Change Log (to be removed by RFC Editor before publication)
B.1 Since draft-ietf-webdav-redirectref-protocol-02 B.1 Since draft-ietf-webdav-redirectref-protocol-02
Julian Reschke takes editorial role (added to authors list). Cleanup Julian Reschke takes editorial role (added to authors list). Cleanup
XML indentation. Start adding all unresolved last call issues. Update XML indentation. Start adding all unresolved last call issues. Update
some author's contact information. Update references, split into some author's contact information. Update references, split into
"normative" and "informational". Remove non-RFC2616 headers "normative" and "informational". Remove non-RFC2616 headers
("Public") from examples. Fixed width problems in artwork. Start ("Public") from examples. Fixed width problems in artwork. Start
skipping to change at page 40, line 5 skipping to change at page 25, line 49
values "T" and "F"). Also some cleanup for "rfc2606-compliance". values "T" and "F"). Also some cleanup for "rfc2606-compliance".
Typo fixes. Add and resolve "15.1-options-response". Typo fixes. Add and resolve "15.1-options-response".
B.5 Since draft-ietf-webdav-redirectref-protocol-06 B.5 Since draft-ietf-webdav-redirectref-protocol-06
Resolve issues "lc-19-direct-ref", "lc-28-lang", "lc-29-lang", Resolve issues "lc-19-direct-ref", "lc-28-lang", "lc-29-lang",
"lc-44-pseudo", "lc-53-s10", "lc-61-pseudo", "lc-63-move", "lc-44-pseudo", "lc-53-s10", "lc-61-pseudo", "lc-63-move",
"lc-80-i18n" and "rfc2606-compliance". Start work on index. Add new "lc-80-i18n" and "rfc2606-compliance". Start work on index. Add new
issue "old_clients". issue "old_clients".
B.6 Since draft-ietf-webdav-redirectref-protocol-07
Closed issue "lc-38-not-hierarchical". Cleaned up DTD fragments in
appendix. Close (reject) issues "lc-55-iana" and "lc-41-no-webdav".
Add issue "5_mkresource" and start work on MKREDIRECTREF (issue
closed, but more work on MKREDIRECTREF needs to be done for updates
and status codes other than 302). Start resolution of "lc-85-301",
replacing "302" by more generic language. Update issue
"lc-57-noautoupdate". Close issue "lc-37-integrity" (duplicate of
"lc-57-autoupdate"). Started work on "lc-85-301". Add L. Dusseault
and S. Eissing to Acknowledgments section.
Appendix C. Resolved issues (to be removed by RFC Editor before Appendix C. Resolved issues (to be removed by RFC Editor before
publication) publication)
Issues that were either rejected or resolved in this version of this Issues that were either rejected or resolved in this version of this
document. document.
C.1 lc-19-direct-ref C.1 title
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0266.html>
reuterj@ira.uka.de (2000-02-07): Section 4, para 5 and Section 6,
para 3 discussions of the Apply-to-Redirect-Ref header make it sound
as if we are specifying direct reference behavior.
Resolution (2003-11-04): Change these passages so that the contrast
is between applying the method to the redirect reference and
responding with a 302.
C.2 rfc2606-compliance
Type: editor
julian.reschke@greenbytes.de (2003-10-02): Ensure that examples use
only sample domains as per RFC2606.
C.3 lc-28-lang
Type: edit
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0266.html>
reuterj@ira.uka.de (2000-02-07): Section 6: Get rid of the sentence
"A reference-aware WebDAV client can act on this response in one of
two ways." A client can act on the response in any way it wants.
Resolution (2003-11-04): Agreed. See also issue 48.
C.4 lc-29-lang
Type: edit Type: edit
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ julian.reschke@greenbytes.de (2004-01-04): Expand "WebDAV" in
0266.html> document title.
reuterj@ira.uka.de (2000-02-07): Section 6, para 4: Obvious, doesn't
need to be stated. Maybe note in an example.
Resolution (2003-11-04): Agreed. See also issue 48. Resolution: Done (no change tracking).
C.5 lc-44-pseudo C.2 lc-38-not-hierarchical
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0302.html> 0289.html>
yarong@Exchange.Microsoft.com (2000-02-11): Instead of adding an yarong@Exchange.Microsoft.com (2000-02-11): Not Hierarchical: The
optional prop XML element to the response element in 207 responses, first sentence of the second paragraph of the introduction of the
define a new location XML element and a new refresource XML element. redirect spec asserts that the URIs of WebDAV compliant resources
match to collections. The WebDAV standard makes no such requirement.
I therefore move that this sentence be stricken.
Resolution: Agree to define new XML elements that are not Resolution (2003-11-19): State the more general HTTP rationale first
pseudo-properties. Disagreement about whether refresource is needed. (alternative names for the same resource), then introduce the
See issue 61. collection hierarchy rationale, which applies only if you are in a
WebDAV-compliant space.
C.6 lc-61-pseudo C.3 lc-37-integrity
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0316.html> 0288.html>
yarong@Exchange.Microsoft.com (2000-02-11): Integrity: Intro, para 7
reuterj@ira.uka.de (2000-02-14): Section 7: It doesn't make sense to "Servers are not required to enforce the integrity of redirect
ask future editors of RFC 2518 to define DAV:location with the references." Integrity is not defined. Replace with something
semantics it has here. RFC 2518 should provide the information in the clearer.
Location header somehow in multistatus responses, but not by using
properties.
Resolution (2003-10-31): Define an XML element for location that is Resolution (2004-01-19): Remove that sentence. Issue will be resolved
not a pseudo-property. We'll keep the recommendation that RFC 2518 as part of the resolution of "lc-57-noautoupdate".
add this for 302 responses. See also issue 44.
C.7 lc-62-oldclient C.4 5_mkresource
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ julian.reschke@greenbytes.de (2004-01-04): Umbrella issue for all
0316.html> changes caused by replacing the generic MKRESOURCE method by
MKREDIRECTREF.
reuterj@ira.uka.de (2000-02-14): Section 7: It's too strong to claim
that non-referencing clients can't process 302 responses occurring in
Multi-Status responses. They just have an extra round trip for each
302.
Resolution (2003-10-31): Remove last sentence of the paragraph that
recommends changes to RFC 2518.
C.8 lc-63-move C.5 lc-41-no-webdav
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0316.html> 0292.html>
reuterj@ira.uka.de (2000-02-14): Section 7.1: Is MOVE atomic from the yarong@Exchange.Microsoft.com (2000-02-11): Make redirect references
perspective of a client? Agrees that there should be no 302s for independent of the rest of WebDAV. The creation method for redirect
member redirect references, but finds the rationale dubious. references shouldn't require an XML request body.
Resolution (2003-11-11): Remove 7.1. Reword 7.2 to avoid concerns Resolution (2004-01-04): MKRESOURCE will be replaced by a specific
with "poses special problems" and "due to atomicity". method that doesn't rely on any PROPPATCH semantics, however it will
still use XML (see also BIND spec for similar marshalling).
C.9 lc-53-s10 C.6 lc-24-properties
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0304.html> 0266.html>
yarong@Exchange.Microsoft.com (2000-02-11): The behavior described in reuterj@ira.uka.de (2000-02-07): Section 5.1: Replace the sentence
this section would have a very serious impact on the efficiency of "The properties of the new resource are as specified by the
mapping Request-URIs to resources in HTTP request processing. Also DAV:propertyupdate request body, using PROPPATCH semantics" with the
specify another type of redirect resource that does not behave as in following: "The MKRESOURCE request MAY contain a DAV:propertyupdate
section 10, but instead would "expose the behavior we see today in request body to initialize resource properties. Herein, the semantics
various HTTP servers that allow their users to create 300 resources." is the same as when sending a MKRESOURCE request without a request
Be sure we know what behavior will be if the redirect location is not body, followed by a PROPPATCH with the DAV:propertyupdate request
an HTTP URL, but, say ftp. body."
Resolution (2003-11-04): We won't define 2 sorts of redirect Resolution (2004-01-04): MKRESOURCE will be replaced by simpler/more
references here. Servers SHOULD respond with 302 as described here, specific method.
but if they can't do that, respond with 404 Not Found. (It's hard to
modularize the behavior specified - it impacts processing Not Found
cases of all methods, so you can't just add it to an HTTP server in a
redirect ref module.)
C.10 lc-76-location C.7 lc-55-iana
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0359.html> 0305.html>
reuterj@ira.uka.de (2000-02-22): 12.2: Make DAV:location a real yarong@Exchange.Microsoft.com (2000-02-11): Expand the IANA section
(live) property, get rid of the DAV:reftarget property to list all methods, headers, XML elements, MIME types, URL schemes,
etc., defined by the spec.
Resolution (2003-10-31): Pseudo-property was removed. Resolution (2004-01-02): Rejected: this section is about registering
new spaces of identifiers. See RFC2434.
C.11 lc-80-i18n C.8 A_DTD_cleanup
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ julian.reschke@greenbytes.de (2003-11-18): Cleanup DTD.
0359.html>
reuterj@ira.uka.de (2000-02-22): Section 17: Could get rid of a lot
of this section, since this protocol extends WebDAV. Just reference
[WebDAV].
julian.reschke@greenbytes.de (2003-10-02): True, but I note that
other specs have re-stated these considerations as well. Opinions?
Resolution (2003-11-11): Just point to RFC2518. Remove RFC2277 and
XML from references (not needed anymore).
Appendix D. Open issues (to be removed by RFC Editor before publication) Appendix D. Open issues (to be removed by RFC Editor prior to
publication)
D.1 old_clients D.1 old_clients
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2003OctDec/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2003OctDec/
0180.html> 0180.html>
julian.reschke@greenbytes.de (2003-11-10): There are (at least) two julian.reschke@greenbytes.de (2003-11-10): There are (at least) two
major design goals, but unfortunately both are in direct major design goals, but unfortunately both are in direct
skipping to change at page 45, line 6 skipping to change at page 29, line 29
(b) seem to be well understood, so we should support both. (c) (b) seem to be well understood, so we should support both. (c)
doesn't seem to be applicable. (d) may become interesting when user doesn't seem to be applicable. (d) may become interesting when user
agents start supporting it, so the spec should be flexible enough to agents start supporting it, so the spec should be flexible enough to
support a feature extension for that. For now I propose that the support a feature extension for that. For now I propose that the
client is able to specify the redirection type as a resource type, client is able to specify the redirection type as a resource type,
such as "DAV:permanent-redirect-reference" and such as "DAV:permanent-redirect-reference" and
"DAV:temporary-redirect-reference". This spec would only define the "DAV:temporary-redirect-reference". This spec would only define the
behaviour for these two resource types and would allow future behaviour for these two resource types and would allow future
extensions using new resource types and suggested response codes. extensions using new resource types and suggested response codes.
D.3 lc-38-not-hierarchical Resolution (2004-01-19): Support creation of both permanent (301,
optional) and temporary (302, required) redirects. Keep protocol
Type: change extensible for other types. Make lifetime visible as protected
property.
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0289.html>
yarong@Exchange.Microsoft.com (2000-02-11): Not Hierarchical: The
first sentence of the second paragraph of the introduction of the
redirect spec asserts that the URIs of WebDAV compliant resources
match to collections. The WebDAV standard makes no such requirement.
I therefore move that this sentence be stricken.
Resolution: State the more general HTTP rationale first (alternative
names for the same resource), then introduce the collection hierarchy
rationale, which applies only if you are in a WebDAV-compliant space.
D.4 lc-36-server D.3 lc-36-server
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0285.html> 0285.html>
yarong@Exchange.Microsoft.com (2000-02-11): Servers: Replace "server" yarong@Exchange.Microsoft.com (2000-02-11): Servers: Replace "server"
with "unrelated system" throughout. with "unrelated system" throughout.
Resolution: Try replacing "server" with "host" in some contexts, Resolution: Try replacing "server" with "host" in some contexts,
rephrasing in passive voice in others. See also issue 40. rephrasing in passive voice in others. See also issue 40.
D.5 lc-33-forwarding D.4 lc-33-forwarding
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0284.html> 0284.html>
yarong@Exchange.Microsoft.com (2000-02-11): Forwarding: Replace yarong@Exchange.Microsoft.com (2000-02-11): Forwarding: Replace
"forward" with "redirect" throughout. "forward" with "redirect" throughout.
Resolution: Use "redirect" for the behavior redirect resources do Resolution: Use "redirect" for the behavior redirect resources do
exhibit. Use "forward" for the contrasting behavior (passing a method exhibit. Use "forward" for the contrasting behavior (passing a method
on to the target with no client action needed). Define these two on to the target with no client action needed). Define these two
terms. See also issue 40. terms. See also issue 40.
D.6 lc-37-integrity D.5 3-terminology-redirectref
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0288.html>
yarong@Exchange.Microsoft.com (2000-02-11): Integrity: Intro, para 7
"Servers are not required to enforce the integrity of redirect
references." Integrity is not defined. Replace with something
clearer.
Resolution: Rewrite to say that the server MUST NOT update the target
See also issue 6.
D.7 3-terminology-redirectref
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0290.html> 0290.html>
julian.reschke@greenbytes.de (2003-07-27): Consider global rename of julian.reschke@greenbytes.de (2003-07-27): Consider global rename of
"redirect reference resource" to "redirect resource". "redirect reference resource" to "redirect resource".
D.8 lc-41-no-webdav D.6 lc-58-update
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0292.html>
yarong@Exchange.Microsoft.com (2000-02-11): Make redirect references
independent of the rest of WebDAV. The creation method for redirect
references shouldn't require an XML request body.
Resolution: We will make redirect references independent of the rest
of WebDAV. MKREF will not have an XML request body.
D.9 lc-58-update
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0308.html> 0308.html>
yarong@Exchange.Microsoft.com (2000-02-11): There needs to be a way yarong@Exchange.Microsoft.com (2000-02-11): There needs to be a way
to update the target of a redirect reference. to update the target of a redirect reference.
Resolution: Agreed. See also issues 6, 43. Resolution: Agreed. See also issues 6, 43.
D.10 lc-24-properties D.7 lc-48-s6
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0266.html>
reuterj@ira.uka.de (2000-02-07): Section 5.1: Replace the sentence
"The properties of the new resource are as specified by the
DAV:propertyupdate request body, using PROPPATCH semantics" with the
following: "The MKRESOURCE request MAY contain a DAV:propertyupdate
request body to initialize resource properties. Herein, the semantics
is the same as when sending a MKRESOURCE request without a request
body, followed by a PROPPATCH with the DAV:propertyupdate request
body."
Resolution: No longer relevant once we switch to MKREF with no
request body.
D.11 lc-48-s6
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0298.html> 0298.html>
yarong@Exchange.Microsoft.com (2000-02-11): Replace all of section 6 yarong@Exchange.Microsoft.com (2000-02-11): Replace all of section 6
with just this: A redirect resource, upon receiving a request without with just this: A redirect resource, upon receiving a request without
an Apply-To-Redirect-Ref header, MUST respond with a 302 (Found) an Apply-To-Redirect-Ref header, MUST respond with a 302 (Found)
response. The 302 (Found) response MUST include a location header response. The 302 (Found) response MUST include a location header
identifying the target and a Redirect-Ref header. If a redirect identifying the target and a Redirect-Ref header. If a redirect
resource receives a request with an Apply-To-Redirect-Ref header then resource receives a request with an Apply-To-Redirect-Ref header then
the redirect reference resource MUST apply the method to itself the redirect reference resource MUST apply the method to itself
rather than blindly returning a 302 (Found) response. rather than blindly returning a 302 (Found) response.
Resolution: Keep a summary along the lines of Yaron's proposal (don't Resolution: Keep a summary along the lines of Yaron's proposal (don't
use the word "blindly"). Keep the bullets detailing the headers to be use the word "blindly"). Keep the bullets detailing the headers to be
returned. Delete the rest, including the examples. See also issue 28, returned. Delete the rest, including the examples. See also issue 28,
29, 30, 31, 32. 29, 30, 31, 32.
D.12 lc-57-noautoupdate D.8 lc-57-noautoupdate
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0307.html> 0307.html>
yarong@Exchange.Microsoft.com (2000-02-11): Add language to forbid yarong@Exchange.Microsoft.com (2000-02-11): Add language to forbid
servers from automatically updating redirect resources when their servers from automatically updating redirect resources when their
targets move. targets move.
Resolution: Agreed. See also issue 6. julian.reschke@greenbytes.de (2004-01-05): I don't think we can
forbid that. This spec consists of (a) clarifications of how a server
that supports redirects should behave for specific WebDAV methods,
and (b) extensions to explicitly create them (or to apply a method to
the redirect itself). As such, we shouldn't add any requirements that
HTTP doesn't add. What we could do is (1) note why auto-update may be
a bad idea, and possibly (2) define that redirects created by
MKREDIRECTREF should not behave that way (or alternatively define
more specific resource types).
D.13 12.1-property-name D.9 12.1-property-name
Type: change Type: change
julian.reschke@greenbytes.de (2003-10-06): Sync names for julian.reschke@greenbytes.de (2003-10-06): Sync names for
DAV:reftarget property and "Redirect-Ref" response headers. DAV:reftarget property and "Redirect-Ref" response headers.
D.14 lc-55-iana
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
0305.html>
yarong@Exchange.Microsoft.com (2000-02-11): Expand the IANA section
to list all methods, headers, XML elements, MIME types, URL schemes,
etc., defined by the spec.
Resolution: Agreed.
Index Index
A A
Apply-To-Redirect-Ref header 25 Apply-To-Redirect-Ref header 19
C
Condition Names
DAV:locked-update-allowed (pre) 8
DAV:name-allowed (pre) 7
DAV:new-redirectref (post) 8
DAV:redirect-lifetime-supported (pre) 8
parent-resource-must-be-non-null (pre) 7
resource-must-be-null (pre) 7
D D
DAV header DAV header
compliance class 'redirectrefs' 29 compliance class 'redirectrefs' 20
DAV:redirectref resource type 27 DAV:locked-update-allowed precondition 8
DAV:reftarget property 26 DAV:name-allowed precondition 7
DAV:new-redirectref postcondition 8
DAV:parent-resource-must-be-non-null precondition 7
DAV:redirect-lifetime property 19
DAV:redirect-lifetime-supported precondition 8
DAV:redirectref resource type 20
DAV:reftarget property 20
DAV:resource-must-be-null precondition 7
H H
Headers Headers
Apply-To-Redirect-Ref 25 Apply-To-Redirect-Ref 19
Redirect-Ref 25 Redirect-Ref 19
M M
Methods Methods
MKRESOURCE 9 MKREDIRECTREF 7
MKRESOURCE method 9 MKREDIRECTREF method 7
P P
Properties Properties
DAV:reftarget 26 DAV:redirect-lifetime 19
DAV:reftarget 20
R R
Redirect-Ref header 25 Redirect-Ref header 19
Resource Types Resource Types
DAV:redirectref 27 DAV:redirectref 20
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the IETF's procedures with respect to rights in IETF Documents can
standards-related documentation can be found in BCP-11. Copies of be found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ietf-ipr@ietf.org.
Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Disclaimer of Validity
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Copyright Statement
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an Copyright (C) The Internet Society (2004). This document is subject
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING to the rights, licenses and restrictions contained in BCP 78, and
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING except as set forth therein, the authors retain all their rights.
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

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