draft-ietf-webdav-redirectref-protocol-08.txt   draft-ietf-webdav-redirectref-protocol-09.txt 
WEBDAV Working Group J. Whitehead WEBDAV Working Group J. Whitehead
Internet-Draft U.C. Santa Cruz Internet-Draft U.C. Santa Cruz
Expires: October 4, 2004 G. Clemm Expires: April 5, 2005 G. Clemm
IBM IBM
J. Reschke, Ed. J. Reschke, Ed.
greenbytes greenbytes
April 5, 2004 October 5, 2004
Web Distributed Authoring and Versioning (WebDAV) Redirect Reference Web Distributed Authoring and Versioning (WebDAV) Redirect Reference
Resources Resources
draft-ietf-webdav-redirectref-protocol-08 draft-ietf-webdav-redirectref-protocol-latest-09
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable This document is an Internet-Draft and is subject to all provisions
patent or other IPR claims of which I am aware have been disclosed, of section 3 of RFC 3667. By submitting this Internet-Draft, each
and any of which I become aware will be disclosed, in accordance with author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with
RFC 3668. 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
groups may also distribute working documents as Internet-Drafts. other 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
www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 4, 2004. This Internet-Draft will expire on April 5, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004).
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
1.1 3xx (Redirection) status code (see [RFC2616], Section 10.3), HTTP/1.1 3xx (Redirection) status code (see RFC2616, Section 10.3),
redirecting the client to a different resource, the target resource. redirecting the client to a different resource, the target resource.
A redirect reference makes it possible to access the target resource A redirect reference makes it possible to access the target resource
indirectly, through any URI mapped to the redirect reference indirectly, through any URI mapped to the redirect reference
resource. There are no integrity guarantees associated with redirect resource. There are no integrity guarantees associated with redirect
reference resources. reference resources.
Editorial Note (To be removed by RFC Editor before publication)
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
<mailto:w3c-dist-auth@w3.org>, which may be joined by sending a <mailto:w3c-dist-auth@w3.org>, which may be joined by sending a
message with subject "subscribe" to message with subject "subscribe" to
<mailto:w3c-dist-auth-request@w3.org?subject=subscribe>. <mailto:w3c-dist-auth-request@w3.org>. Discussions of the WEBDAV
working group are archived at
<http://lists.w3.org/Archives/Public/w3c-dist-auth/>.
Discussions of the WEBDAV working group are archived at URL: <http:// An issues list and XML and HTML versions of this draft are available
lists.w3.org/Archives/Public/w3c-dist-auth/>. from
<http://greenbytes.de/tech/webdav/#draft-ietf-webdav-redirectref-prot
ocol>.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Notational Conventions . . . . . . . . . . . . . . . . . . . 5 2. Notational Conventions . . . . . . . . . . . . . . . . . . . 6
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Overview of Redirect Reference Resources . . . . . . . . . . 6 4. Overview of Redirect Reference Resources . . . . . . . . . . 7
5. MKREDIRECTREF Method . . . . . . . . . . . . . . . . . . . . 7 5. MKREDIRECTREF Method . . . . . . . . . . . . . . . . . . . . 8
5.1 Example: Creating a Redirect Reference Resource with 5.1 Example: Creating a Redirect Reference Resource with
MKREDIRECTREF . . . . . . . . . . . . . . . . . . . . . . 8 MKREDIRECTREF . . . . . . . . . . . . . . . . . . . . . . 9
6. Operations on Redirect Reference Resources . . . . . . . . . 8 6. Operations on Redirect Reference Resources . . . . . . . . . 10
7. Operations on Collections That Contain Redirect Reference 7. Operations on Collections That Contain Redirect Reference
Resources . . . . . . . . . . . . . . . . . . . . . . . . . 9 Resources . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.1 LOCK on a Collection That Contains Redirect References . . 9 7.1 LOCK on a Collection That Contains Redirect References . . 11
7.2 Example: PROPFIND on a Collection with Redirect 7.2 Example: PROPFIND on a Collection with Redirect
Reference Resources . . . . . . . . . . . . . . . . . . . 10 Reference Resources . . . . . . . . . . . . . . . . . . . 11
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 . . . . . . . 12 Collection with Redirect Reference Resources . . . . . . . 13
7.4 Example: COPY on a Collection That Contains a Redirect 7.4 Example: COPY on a Collection That Contains a Redirect
Reference Resource . . . . . . . . . . . . . . . . . . . . 13
7.5 Example: LOCK on a Collection That Contains a Redirect
Reference Resource . . . . . . . . . . . . . . . . . . . . 14 Reference Resource . . . . . . . . . . . . . . . . . . . . 14
8. Operations on Targets of Redirect Reference Resources . . . 16 7.5 Example: LOCK on a Collection That Contains a Redirect
9. Relative URIs in DAV:reftarget . . . . . . . . . . . . . . . 16 Reference Resource . . . . . . . . . . . . . . . . . . . . 15
8. Operations on Targets of Redirect Reference Resources . . . 17
9. Relative URIs in DAV:reftarget . . . . . . . . . . . . . . . 17
9.1 Example: Resolving a Relative URI in a Multi-Status 9.1 Example: Resolving a Relative URI in a Multi-Status
Response . . . . . . . . . . . . . . . . . . . . . . . . . 16 Response . . . . . . . . . . . . . . . . . . . . . . . . . 17
10. Redirect References to Collections . . . . . . . . . . . . . 17 10. Redirect References to Collections . . . . . . . . . . . . . 18
11. Headers . . . . . . . . . . . . . . . . . . . . . . . . . . 19 11. Headers . . . . . . . . . . . . . . . . . . . . . . . . . . 20
11.1 Redirect-Ref Response Header . . . . . . . . . . . . . . 19 11.1 Redirect-Ref Response Header . . . . . . . . . . . . . . 20
11.2 Apply-To-Redirect-Ref Request Header . . . . . . . . . . 19 11.2 Apply-To-Redirect-Ref Request Header . . . . . . . . . . 20
12. Redirect Reference Resource Properties . . . . . . . . . . . 19 12. Redirect Reference Resource Properties . . . . . . . . . . . 20
12.1 DAV:redirect-lifetime (protected) . . . . . . . . . . . 19 12.1 DAV:redirect-lifetime (protected) . . . . . . . . . . . 20
12.2 DAV:reftarget (protected) . . . . . . . . . . . . . . . 20 12.2 DAV:reftarget (protected) . . . . . . . . . . . . . . . 21
13. XML Elements . . . . . . . . . . . . . . . . . . . . . . . . 20 13. XML Elements . . . . . . . . . . . . . . . . . . . . . . . . 21
13.1 redirectref XML Element . . . . . . . . . . . . . . . . 20 13.1 redirectref XML Element . . . . . . . . . . . . . . . . 21
14. Extensions to the DAV:response XML Element for 14. Extensions to the DAV:response XML Element for
Multi-Status Responses . . . . . . . . . . . . . . . . . . . 20 Multi-Status Responses . . . . . . . . . . . . . . . . . . . 21
15. Capability Discovery . . . . . . . . . . . . . . . . . . . . 20 15. Capability Discovery . . . . . . . . . . . . . . . . . . . . 21
15.1 Example: Discovery of Support for Redirect Reference 15.1 Example: Discovery of Support for Redirect Reference
Resources . . . . . . . . . . . . . . . . . . . . . . . 21 Resources . . . . . . . . . . . . . . . . . . . . . . . 22
16. Security Considerations . . . . . . . . . . . . . . . . . . 21 16. Security Considerations . . . . . . . . . . . . . . . . . . 22
16.1 Privacy Concerns . . . . . . . . . . . . . . . . . . . . 21 16.1 Privacy Concerns . . . . . . . . . . . . . . . . . . . . 22
16.2 Redirect Loops . . . . . . . . . . . . . . . . . . . . . 22 16.2 Redirect Loops . . . . . . . . . . . . . . . . . . . . . 23
16.3 Redirect Reference Resources and Denial of Service . . . 22 16.3 Redirect Reference Resources and Denial of Service . . . 23
16.4 Revealing Private Locations . . . . . . . . . . . . . . 22 16.4 Revealing Private Locations . . . . . . . . . . . . . . 23
17. Internationalization Considerations . . . . . . . . . . . . 22 17. Internationalization Considerations . . . . . . . . . . . . 23
18. IANA Considerations . . . . . . . . . . . . . . . . . . . . 23 18. IANA Considerations . . . . . . . . . . . . . . . . . . . . 24
19. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23 19. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 24
20. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 20. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24
21. Normative References . . . . . . . . . . . . . . . . . . . . 23 21. Normative References . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 25
A. Changes to the WebDAV Document Type Definition . . . . . . . 24 A. Changes to the WebDAV Document Type Definition . . . . . . . 25
B. Change Log (to be removed by RFC Editor before B. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . . . . . 25
B.1 Since draft-ietf-webdav-redirectref-protocol-02 . . . . . 25
B.2 Since draft-ietf-webdav-redirectref-protocol-03 . . . . . 25
B.3 Since draft-ietf-webdav-redirectref-protocol-04 . . . . . 25
B.4 Since draft-ietf-webdav-redirectref-protocol-05 . . . . . 25
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
publication) . . . . . . . . . . . . . . . . . . . . . . . . 26 publication) . . . . . . . . . . . . . . . . . . . . . . . . 26
C.1 title . . . . . . . . . . . . . . . . . . . . . . . . . . 26 B.1 Since draft-ietf-webdav-redirectref-protocol-02 . . . . . 26
C.2 lc-38-not-hierarchical . . . . . . . . . . . . . . . . . . 26 B.2 Since draft-ietf-webdav-redirectref-protocol-03 . . . . . 26
C.3 lc-37-integrity . . . . . . . . . . . . . . . . . . . . . 26 B.3 Since draft-ietf-webdav-redirectref-protocol-04 . . . . . 26
C.4 5_mkresource . . . . . . . . . . . . . . . . . . . . . . . 27 B.4 Since draft-ietf-webdav-redirectref-protocol-05 . . . . . 26
C.5 lc-41-no-webdav . . . . . . . . . . . . . . . . . . . . . 27 B.5 Since draft-ietf-webdav-redirectref-protocol-06 . . . . . 26
C.6 lc-24-properties . . . . . . . . . . . . . . . . . . . . . 27 B.6 Since draft-ietf-webdav-redirectref-protocol-07 . . . . . 26
C.7 lc-55-iana . . . . . . . . . . . . . . . . . . . . . . . . 28 B.7 Since draft-ietf-webdav-redirectref-protocol-08 . . . . . 27
C.8 A_DTD_cleanup . . . . . . . . . . . . . . . . . . . . . . 28 C. Resolved issues (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . . . . . 27
C.1 lc-85-301 . . . . . . . . . . . . . . . . . . . . . . . . 27
C.2 specify_safeness . . . . . . . . . . . . . . . . . . . . . 28
D. Open issues (to be removed by RFC Editor prior to D. Open issues (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . . . . . 28 publication) . . . . . . . . . . . . . . . . . . . . . . . . 28
D.1 old_clients . . . . . . . . . . . . . . . . . . . . . . . 28 D.1 edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
D.2 lc-85-301 . . . . . . . . . . . . . . . . . . . . . . . . 29 D.2 old_clients . . . . . . . . . . . . . . . . . . . . . . . 28
D.3 lc-36-server . . . . . . . . . . . . . . . . . . . . . . . 29 D.3 lc-36-server . . . . . . . . . . . . . . . . . . . . . . . 29
D.4 lc-33-forwarding . . . . . . . . . . . . . . . . . . . . . 29 D.4 lc-33-forwarding . . . . . . . . . . . . . . . . . . . . . 29
D.5 3-terminology-redirectref . . . . . . . . . . . . . . . . 30 D.5 3-terminology-redirectref . . . . . . . . . . . . . . . . 29
D.6 lc-58-update . . . . . . . . . . . . . . . . . . . . . . . 30 D.6 lc-58-update . . . . . . . . . . . . . . . . . . . . . . . 29
D.7 lc-48-s6 . . . . . . . . . . . . . . . . . . . . . . . . . 30 D.7 lc-48-s6 . . . . . . . . . . . . . . . . . . . . . . . . . 30
D.8 lc-57-noautoupdate . . . . . . . . . . . . . . . . . . . . 31 D.8 lc-57-noautoupdate . . . . . . . . . . . . . . . . . . . . 30
D.9 12.1-property-name . . . . . . . . . . . . . . . . . . . . 31 D.9 12.1-property-name . . . . . . . . . . . . . . . . . . . . 30
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Intellectual Property and Copyright Statements . . . . . . . 33 Intellectual Property and Copyright Statements . . . . . . . 33
1. Introduction 1. Introduction
This is one of a pair of specifications that extend the WebDAV This specification extends the Web Distributed Authoring Protocol
Distributed Authoring Protocol to enable clients to create new access (WebDAV) to enable clients to create new access paths to existing
paths to existing resources. This capability is useful for several resources. This capability is useful for several reasons:
reasons:
The WebDAV Distributed Authoring Protocol makes it possible to WebDAV makes it possible to organize HTTP resources into hierarchies,
organize HTTP resources into hierarchies, placing them into placing them into groupings, known as collections, which are more
groupings, known as collections, which are more easily browsed and easily browsed and manipulated than a single flat collection.
manipulated than a single flat collection. However, hierarchies However, hierarchies require categorization decisions that locate
require categorization decisions that locate resources at a single resources at a single location in the hierarchy, a drawback when a
location in the hierarchy, a drawback when a resource has multiple resource has multiple valid categories. For example, in a hierarchy
valid categories. For example, in a hierarchy of vehicle descriptions of vehicle descriptions containing collections for cars and boats, a
containing collections for cars and boats, a description of a description of a combination car/boat vehicle could belong in either
combination car/boat vehicle could belong in either collection. collection. Ideally, the description should be accessible from both.
Ideally, the description should be accessible from both. Allowing Allowing clients to create new URIs that access the existing resource
clients to create new URIs that access the existing resource lets lets them put that resource into multiple collections.
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
skipping to change at page 5, line 21 skipping to change at page 6, line 19
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
through 14 define the new headers, properties, and XML elements through 14 define the new headers, properties, and XML elements
required to support redirect reference resources. Section 15 required to support redirect reference resources. Section 15
discusses capability discovery. Sections 16 through 18 present the discusses capability discovery. Sections 16 through 18 present the
security, internationalization, and IANA concerns raised by this security, internationalization, and IANA concerns raised by this
specification. The remaining sections provide a variety of supporting specification. The remaining sections provide a variety of
information. supporting information.
2. Notational Conventions 2. Notational Conventions
Since this document describes a set of extensions to the WebDAV Since this document describes a set of extensions to the WebDAV
Distributed Authoring Protocol [RFC2518], itself an extension to the Distributed Authoring Protocol [RFC2518], itself an extension to the
HTTP/1.1 protocol, the augmented BNF used here to describe protocol HTTP/1.1 protocol, the augmented BNF used here to describe protocol
elements is exactly the same as described in Section 2.1 of elements is exactly the same as described in Section 2.1 of
[RFC2616]. Since this augmented BNF uses the basic production rules [RFC2616]. Since this augmented BNF uses the basic production rules
provided in Section 2.2 of [RFC2616], these rules apply to this provided in Section 2.2 of [RFC2616], these rules apply to this
document as well. document as well.
skipping to change at page 6, line 4 skipping to change at page 6, line 49
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 an A resource created to redirect all requests made to it, using an
HTTP status code from the 3xx range, 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
by an absolute URI (see [RFC2396], "absoluteURI"). identified by an absolute URI (see [RFC2396], "absoluteURI").
This document uses the terms "precondition", "postcondition" and This document uses the terms "precondition", "postcondition" and
"protected property" as defined in [RFC3253]. Servers MUST report "protected property" as defined in [RFC3253]. Servers MUST report
pre-/postcondition failures as described in section 1.6 of this pre-/postcondition failures as described in section 1.6 of this
document. 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
links in HTML documents. They can be created and maintained without as links in HTML documents. They can be created and maintained
the involvement or even knowledge of their target resource. This without the involvement or even knowledge of their target resource.
reduces the cost of linking between resources." This 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.2 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
skipping to change at page 7, line 14 skipping to change at page 8, line 14
5. MKREDIRECTREF Method 5. MKREDIRECTREF Method
The MKREDIRECTREF method requests the creation of a redirect The MKREDIRECTREF method requests the creation of a redirect
reference resource. reference resource.
If a MKREDIRECTREF request fails, the server state preceding the If a MKREDIRECTREF request fails, the server state preceding the
request MUST be restored. request MUST be restored.
Responses from a MKREDIRECTREF request MUST NOT be cached, as Responses from a MKREDIRECTREF request MUST NOT be cached, as
MKREDIRECTREF has non-idempotent semantics. MKREDIRECTREF has non-idempotent and non-safe semantics (see
[RFC2616], section 9.1)..
Marshalling: Marshalling:
The request body MUST be a DAV:mkredirectref XML element. The request body MUST be a DAV:mkredirectref XML element.
<!ELEMENT mkredirectref (reftarget, redirect-lifetime?)> <!ELEMENT mkredirectref (reftarget, redirect-lifetime?)>
<!ELEMENT reftarget (href)> <!ELEMENT reftarget (href)>
<!ELEMENT redirect-lifetime (permanent | temporary)> <!ELEMENT redirect-lifetime (permanent | temporary)>
<!ELEMENT permanent EMPTY> <!ELEMENT permanent EMPTY>
<!ELEMENT temporary EMPTY> <!ELEMENT temporary EMPTY>
The DAV:href element is defined in [RFC2518] (Section 12.3) and The DAV:href element is defined in [RFC2518] (Section 12.3) and
MUST contain either an absoluteURI or a relativeURI (see MUST contain either an absoluteURI or a relativeURI (see
[RFC2396], Section 3 and 5). [RFC2396], Section 3 and 5).
If no DAV:redirect-lifetime element is specified, the server MUST
behave as if a value of DAV:temporary was specified.
If the request succeeds, the server MUST return 201 (Created) If the request succeeds, the server MUST return 201 (Created)
status. status.
If a response body for a successful request is included, it MUST If a response body for a successful request is included, it MUST
be a DAV:mkredirectref-response XML element. Note that this be a DAV:mkredirectref-response XML element. Note that this
document does not define any elements for the MKREDIRECTREF document does not define any elements for the MKREDIRECTREF
response body, but the DAV:mkredirectref-response element is response body, but the DAV:mkredirectref-response element is
defined to ensure interoperability between future extensions that defined to ensure interoperability between future extensions that
do define elements for the MKREDIRECTREF response body. do define elements for the MKREDIRECTREF response body.
skipping to change at page 8, line 11 skipping to change at page 9, line 14
(DAV:name-allowed): The last segment of the request URL is (DAV:name-allowed): The last segment of the request URL is
available for use as a resource name. available for use as a resource name.
(DAV:locked-update-allowed): If the collection identified by the (DAV:locked-update-allowed): If the collection identified by the
Request-URL minus the last path segment is write-locked, then the Request-URL minus the last path segment is write-locked, then the
appropriate token MUST be specified in an If request header. appropriate token MUST be specified in an If request header.
(DAV:redirect-lifetime-supported): If the request body contains a (DAV:redirect-lifetime-supported): If the request body contains a
DAV:redirect-lifetime element, the server MUST support the DAV:redirect-lifetime element, the server MUST support the
specified liftime. Support for DAV:temporary is REQUIRED, while specified lifetime. Support for DAV:temporary is REQUIRED, while
support for DAV:permanent is OPTIONAL. support for DAV:permanent is OPTIONAL.
Postconditions: Postconditions:
(DAV:new-redirectref): a new redirect reference resource is (DAV:new-redirectref): a new redirect reference resource is
created whose DAV:reftarget property has the value specified in created whose DAV:reftarget property has the value specified in
the request body. the request body.
5.1 Example: Creating a Redirect Reference Resource with MKREDIRECTREF 5.1 Example: Creating a Redirect Reference Resource with MKREDIRECTREF
skipping to change at page 8, line 43 skipping to change at page 9, line 46
</D:reftarget> </D:reftarget>
</D:mkredirectref> </D:mkredirectref>
>> 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
www.example.com/i-d/draft-webdav-protocol-08.txt. The redirect http://www.example.com/i-d/draft-webdav-protocol-08.txt. The
reference resource's DAV:resourcetype property is set to redirect reference resource's DAV:resourcetype property is set to
DAV:redirectref. DAV:redirectref and it's DAV:redirect-lifetime property has the value
DAV:temporary.
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 3xx range (Redirection) status code, reference resource MUST return a 3xx range (Redirection) status code,
unless the request includes an Apply-To-Redirect-Ref header unless the request includes an Apply-To-Redirect-Ref header
skipping to change at page 9, line 41 skipping to change at page 10, line 46
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 3xx (Redirection) unless a "Apply-To-Redirect-Ref: T" header is a 3xx (Redirection) unless a "Apply-To-Redirect-Ref: T" header is
included with the request. The overall response will therefore be a included with the request. The overall response will therefore be a
207 (Multi-Status). For each DAV:response element representing a 207 (Multi-Status). For each DAV:response element representing a
redirect reference, the server MUST include an additional redirect reference, the server MUST include an additional
DAV:location element, specifying the value of the "Location" header DAV:location element, specifying the value of the "Location" header
that would be returned otherwise. The extension is defined in Section that would be returned otherwise. The extension is defined in
14 below. 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"
skipping to change at page 12, line 30 skipping to change at page 13, line 30
Depth: infinity Depth: infinity
Apply-To-Redirect-Ref: T Apply-To-Redirect-Ref: T
Content-Type: text/xml Content-Type: text/xml
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" ?> <?xml version="1.0" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop> <D:prop>
<D:resourcetype/> <D:resourcetype/>
<D:reftarget/> <D:reftarget/>
<D:redirect-lifetime/>
</D:prop> </D:prop>
</D:propfind> </D:propfind>
>> Response: >> Response:
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml Content-Type: text/xml
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" ?> <?xml version="1.0" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>/MyCollection/</D:href> <D:href>/MyCollection/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:resourcetype><D:collection/></D:resourcetype> <D:resourcetype><D:collection/></D:resourcetype>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
<D:propstat> <D:propstat>
<D:prop><D:reftarget/></D:prop> <D:prop>
<D:reftarget/>
<D:redirect-lifetime/>
</D:prop>
<D:status>HTTP/1.1 404 Not Found</D:status> <D:status>HTTP/1.1 404 Not Found</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
<D:response> <D:response>
<D:href>/MyCollection/diary.html</D:href> <D:href>/MyCollection/diary.html</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:resourcetype/> <D:resourcetype/>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
<D:propstat> <D:propstat>
<D:prop><D:reftarget/></D:prop> <D:prop>
<D:reftarget/>
<D:redirect-lifetime/>
</D:prop>
<D:status>HTTP/1.1 404 Not Found</D:status> <D:status>HTTP/1.1 404 Not Found</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
<D:response> <D:response>
<D:href>/MyCollection/nunavut</D:href> <D:href>/MyCollection/nunavut</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:resourcetype><D:redirectref/></D:resourcetype> <D:resourcetype><D:redirectref/></D:resourcetype>
<D:reftarget> <D:reftarget>
<D:href>http://example.ca/art/inuit/</D:href> <D:href>http://example.ca/art/inuit/</D:href>
</D:reftarget> </D:reftarget>
<D:redirect-lifetime><D:temporary/></D:redirect-lifetime>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
Since the "Apply-To-Redirect-Ref: T" header is present, the response Since the "Apply-To-Redirect-Ref: T" header is present, the response
shows the properties of the redirect reference resource in the shows the properties of the redirect reference resource in the
collection rather than reporting a 302 status. collection rather than reporting a 302 status.
skipping to change at page 15, line 45 skipping to change at page 16, line 45
<D:status>HTTP/1.1 302 Found</D:status> <D:status>HTTP/1.1 302 Found</D:status>
<D:location> <D:location>
<D:href>http://example.ca/art/inuit/</D:href> <D:href>http://example.ca/art/inuit/</D:href>
</D:location> </D:location>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
The server returns a 302 response code for the redirect reference The server returns a 302 response code for the redirect reference
resource in the collection. Consequently, neither the collection nor resource in the collection. Consequently, neither the collection nor
any of the resources identified by its internal member URIs were any of the resources identified by its internal member URIs were
locked. A referencing-aware client can submit a separate LOCK request locked. A referencing-aware client can submit a separate LOCK
to the URI in the DAV:location element returned for the redirect request to the URI in the DAV:location element returned for the
reference resource, and can resubmit the LOCK request with the redirect reference resource, and can resubmit the LOCK request with
Apply-To-Redirect-Ref header to the collection. At that point both the Apply-To-Redirect-Ref header to the collection. At that point
the reference resource and its target resource will be locked (as both the reference resource and its target resource will be locked
well as the collection and all the resources identified by its other (as well as the collection and all the resources identified by its
members). other members).
8. Operations on Targets of Redirect Reference Resources 8. Operations on Targets of Redirect Reference Resources
Operations on targets of redirect reference resources have no effect Operations on targets of redirect reference resources have no effect
on the reference resource. on the reference resource.
9. Relative URIs in DAV:reftarget 9. Relative URIs in DAV:reftarget
The URI in the href in a DAV:reftarget property MAY be a relative The URI in the href in a DAV:reftarget property MAY be a relative
URI. In this case, the base URI to be used for resolving the relative URI. In this case, the base URI to be used for resolving the
URI to absolute form is the URI used in the HTTP message to identify relative URI to absolute form is the URI used in the HTTP message to
the redirect reference resource to which the DAV:reftarget property identify the redirect reference resource to which the DAV:reftarget
belongs. property belongs.
When DAV:reftarget appears in the context of a Multi-Status response, When DAV:reftarget appears in the context of a Multi-Status response,
it is in a DAV:response element that contains a single DAV:href it is in a DAV:response element that contains a single DAV:href
element. The value of this DAV:href element serves as the base URI element. The value of this DAV:href element serves as the base URI
for resolving a relative URI in DAV:reftarget. The value of DAV:href for resolving a relative URI in DAV:reftarget. The value of DAV:href
may itself be relative, in which case it must be resolved first in may itself be relative, in which case it must be resolved first in
order to serve as the base URI for the relative URI in DAV:reftarget. order to serve as the base URI for the relative URI in DAV:reftarget.
If the DAV:href element is relative, its base URI is constructed from If the DAV:href element is relative, its base URI is constructed from
the scheme component "http", the value of the Host header in the the scheme component "http", the value of the Host header in the
request, and the request-URI. request, and the request-URI.
skipping to change at page 17, line 44 skipping to change at page 18, line 44
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
In this example, the relative URI statistics/population/1997.html is In this example, the relative URI statistics/population/1997.html is
returned as the value of reftarget for the reference resource returned as the value of reftarget for the reference resource
identified by href /geog/stats.html. The href is itself a relative identified by href /geog/stats.html. The href is itself a relative
URI, which resolves to http://example.com/geog/stats.html. This is URI, which resolves to http://example.com/geog/stats.html. This is
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
population/1997.html. http://example.com/geog/statistics/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 3xx. The value of the Location header in the the response SHOULD be a 3xx. The value of the Location header in
response is as follows: the 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
"), the final "/" in the DAV:reftarget property is dropped before the "/"), the final "/" in the DAV:reftarget property is dropped before
remainder of the Request-URI is appended. the remainder of the Request-URI is appended.
Consider Request-URI /x/y/z.html. Suppose that /x/ is a redirect Consider Request-URI /x/y/z.html. Suppose that /x/ is a redirect
reference resource whose target resource is collection /a/, which reference resource whose target resource is collection /a/, which
contains redirect reference resource y whose target resource is contains redirect reference resource y whose target resource is
collection /b/, which contains redirect reference resource z.html collection /b/, which contains redirect reference resource z.html
whose target resource is /c/d.html. whose target resource is /c/d.html.
/x/y/z.html /x/y/z.html
| |
| /x -> /a | /x -> /a
skipping to change at page 21, line 30 skipping to change at page 22, line 30
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, MKREDIRECTREF 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 MKREDIRECTREF requests can be submitted to /somecollection/ that MKREDIRECTREF requests can be submitted to
someresource. /somecollection/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
introduce several new security concerns and increase the risk of some introduce several new security concerns and increase the risk of some
skipping to change at page 25, line 10 skipping to change at page 26, line 10
<!ELEMENT response (href, ((href*, status)|(propstat+)), <!ELEMENT response (href, ((href*, status)|(propstat+)),
responsedescription?, location?) > responsedescription?, location?) >
<!ELEMENT location (href) > <!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.
some author's contact information. Update references, split into Update some author's contact information. Update references, split
"normative" and "informational". Remove non-RFC2616 headers into "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
resolving editorial issues. resolving editorial issues.
B.2 Since draft-ietf-webdav-redirectref-protocol-03 B.2 Since draft-ietf-webdav-redirectref-protocol-03
Added Joe Orton and Juergen Reuter to Acknowledgements section. Close Added Joe Orton and Juergen Reuter to Acknowledgements section.
more editorial issues. Remove dependencies on BIND spec. Close more editorial issues. Remove dependencies on BIND spec.
B.3 Since draft-ietf-webdav-redirectref-protocol-04 B.3 Since draft-ietf-webdav-redirectref-protocol-04
More editorial fixes. Clarify that MKRESOURCE can only be used to More editorial fixes. Clarify that MKRESOURCE can only be used to
create redirect references (switch to new method in a future draft). create redirect references (switch to new method in a future draft).
Clarify that redirect references do not have bodies. Clarify that redirect references do not have bodies.
B.4 Since draft-ietf-webdav-redirectref-protocol-05 B.4 Since draft-ietf-webdav-redirectref-protocol-05
Close (accept) issue "lc-79-accesscontrol". Add issue Close (accept) issue "lc-79-accesscontrol". Add issue
skipping to change at page 26, line 13 skipping to change at page 27, line 13
appendix. Close (reject) issues "lc-55-iana" and "lc-41-no-webdav". appendix. Close (reject) issues "lc-55-iana" and "lc-41-no-webdav".
Add issue "5_mkresource" and start work on MKREDIRECTREF (issue Add issue "5_mkresource" and start work on MKREDIRECTREF (issue
closed, but more work on MKREDIRECTREF needs to be done for updates closed, but more work on MKREDIRECTREF needs to be done for updates
and status codes other than 302). Start resolution of "lc-85-301", and status codes other than 302). Start resolution of "lc-85-301",
replacing "302" by more generic language. Update issue replacing "302" by more generic language. Update issue
"lc-57-noautoupdate". Close issue "lc-37-integrity" (duplicate of "lc-57-noautoupdate". Close issue "lc-37-integrity" (duplicate of
"lc-57-autoupdate"). Started work on "lc-85-301". Add L. Dusseault "lc-57-autoupdate"). Started work on "lc-85-301". Add L. Dusseault
and S. Eissing to Acknowledgments section. and S. Eissing to Acknowledgments section.
B.7 Since draft-ietf-webdav-redirectref-protocol-08
Fix index entries for conditions. Open and resolve issue
"specify_safeness". Rewrite editorial section and parts of intro.
Add more clarifications for issue "lc-85-301" and close it.
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 title C.1 lc-85-301
Type: edit
julian.reschke@greenbytes.de (2004-01-04): Expand "WebDAV" in
document title.
Resolution: Done (no change tracking).
C.2 lc-38-not-hierarchical
Type: change
<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 (2003-11-19): 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.
C.3 lc-37-integrity
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 (2004-01-19): Remove that sentence. Issue will be resolved
as part of the resolution of "lc-57-noautoupdate".
C.4 5_mkresource
Type: change
julian.reschke@greenbytes.de (2004-01-04): Umbrella issue for all
changes caused by replacing the generic MKRESOURCE method by
MKREDIRECTREF.
C.5 lc-41-no-webdav
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 (2004-01-04): MKRESOURCE will be replaced by a specific
method that doesn't rely on any PROPPATCH semantics, however it will
still use XML (see also BIND spec for similar marshalling).
C.6 lc-24-properties
Type: change Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ ejw@cse.ucsc.edu (2000-01-03): Support creation of other than 302
0266.html> redirects, especially 301.
reuterj@ira.uka.de (2000-02-07): Section 5.1: Replace the sentence julian.reschke@greenbytes.de (2003-10-13): HTTP seems to distinguish
"The properties of the new resource are as specified by the the following use cases: (a) permanent redirect (301), (b) temporary
DAV:propertyupdate request body, using PROPPATCH semantics" with the redirect (302 or 307), (c) redirect to a GET location after POST
following: "The MKRESOURCE request MAY contain a DAV:propertyupdate (303) and (d) agent-driven negotiation (300). Among these, (a) and
request body to initialize resource properties. Herein, the semantics (b) seem to be well understood, so we should support both. (c)
is the same as when sending a MKRESOURCE request without a request doesn't seem to be applicable. (d) may become interesting when user
body, followed by a PROPPATCH with the DAV:propertyupdate request agents start supporting it, so the spec should be flexible enough to
body." support a feature extension for that. For now I propose that the
client is able to specify the redirection type as a resource type,
such as "DAV:permanent-redirect-reference" and
"DAV:temporary-redirect-reference". This spec would only define the
behaviour for these two resource types and would allow future
extensions using new resource types and suggested response codes.
Resolution (2004-01-04): MKRESOURCE will be replaced by simpler/more Resolution (2004-10-05): Support creation of both permanent (301,
specific method. optional) and temporary (302, required) redirects. Keep protocol
extensible for other types. Make lifetime visible as protected
property.
C.7 lc-55-iana C.2 specify_safeness
Type: change Type: edit
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/ <http://lists.w3.org/Archives/Public/w3c-dist-auth/2004JulSep/0196.ht
0305.html> ml>
yarong@Exchange.Microsoft.com (2000-02-11): Expand the IANA section julian.reschke@greenbytes.de (2004-09-19): Specify safeness and
to list all methods, headers, XML elements, MIME types, URL schemes, idempotence of new methods.
etc., defined by the spec.
Resolution (2004-01-02): Rejected: this section is about registering Resolution (2004-09-20): Done.
new spaces of identifiers. See RFC2434.
C.8 A_DTD_cleanup Appendix D. Open issues (to be removed by RFC Editor prior to
publication)
Type: change D.1 edit
julian.reschke@greenbytes.de (2003-11-18): Cleanup DTD. Type: edit
Appendix D. Open issues (to be removed by RFC Editor prior to julian.reschke@greenbytes.de (2004-10-03): Umbrella issue for
publication) editorial changes.
D.1 old_clients D.2 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.ht
0180.html> ml>
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
contradiction: #1: Maximum consistency with HTTP/1.1 (RFC2616). This contradiction: #1: Maximum consistency with HTTP/1.1 (RFC2616). This
means that any request that addresses a redirect reference resource means that any request that addresses a redirect reference resource
MUST result in a 3xx status code (obviously the whole point is that MUST result in a 3xx status code (obviously the whole point is that
GET MUST result in a redirection, and if it does, it's hard to say GET MUST result in a redirection, and if it does, it's hard to say
why other methods such as PUT or DELETE should behave differently). why other methods such as PUT or DELETE should behave differently).
Therefore, the redirect reference protocol introduces a new request Therefore, the redirect reference protocol introduces a new request
header ("Apply-To-Redirect-Ref") through which a client can indicate header ("Apply-To-Redirect-Ref") through which a client can indicate
that the request indeed should be applied to the redirect reference that the request indeed should be applied to the redirect reference
resource itself. #2: Maximum usability with existing clients. For resource itself. #2: Maximum usability with existing clients. For
instance, the Microsoft Webfolder client will not be able to DELETE a instance, the Microsoft Webfolder client will not be able to DELETE a
redirect reference resource unless the server deviates from #1. Right redirect reference resource unless the server deviates from #1.
now I'm not sure about the best way to resolve this. Currently the Right now I'm not sure about the best way to resolve this. Currently
spec chooses #1 (back when this decision was made, there was probably the spec chooses #1 (back when this decision was made, there was
the assumption that existing clients would quickly be updated -- probably the assumption that existing clients would quickly be
something that probably isn't true today). However this may result in updated -- something that probably isn't true today). However this
implementers either just ignoring these rules, or adding special may result in implementers either just ignoring these rules, or
workarounds based on "User Agent" detection. adding special workarounds based on "User Agent" detection.
D.2 lc-85-301
Type: change
ejw@cse.ucsc.edu (2000-01-03): Support creation of other than 302
redirects, especially 301.
julian.reschke@greenbytes.de (2003-10-13): HTTP seems to distinguish
the following use cases: (a) permanent redirect (301), (b) temporary
redirect (302 or 307), (c) redirect to a GET location after POST
(303) and (d) agent-driven negotiation (300). Among these, (a) and
(b) seem to be well understood, so we should support both. (c)
doesn't seem to be applicable. (d) may become interesting when user
agents start supporting it, so the spec should be flexible enough to
support a feature extension for that. For now I propose that the
client is able to specify the redirection type as a resource type,
such as "DAV:permanent-redirect-reference" and
"DAV:temporary-redirect-reference". This spec would only define the
behaviour for these two resource types and would allow future
extensions using new resource types and suggested response codes.
Resolution (2004-01-19): Support creation of both permanent (301,
optional) and temporary (302, required) redirects. Keep protocol
extensible for other types. Make lifetime visible as protected
property.
D.3 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.ht
0285.html> ml>
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.4 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.ht
0284.html> ml>
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
on to the target with no client action needed). Define these two method on to the target with no client action needed). Define these
terms. See also issue 40. two terms. See also issue 40.
D.5 3-terminology-redirectref D.5 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.ht
0290.html> ml>
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.6 lc-58-update D.6 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.ht
0308.html> ml>
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.7 lc-48-s6 D.7 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.ht
0298.html> ml>
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
returned. Delete the rest, including the examples. See also issue 28, be returned. Delete the rest, including the examples. See also
29, 30, 31, 32. issue 28, 29, 30, 31, 32.
D.8 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.ht
0307.html> ml>
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.
julian.reschke@greenbytes.de (2004-01-05): I don't think we can 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 forbid that. This spec consists of (a) clarifications of how a
that supports redirects should behave for specific WebDAV methods, server that supports redirects should behave for specific WebDAV
and (b) extensions to explicitly create them (or to apply a method to methods, and (b) extensions to explicitly create them (or to apply a
the redirect itself). As such, we shouldn't add any requirements that method to the redirect itself). As such, we shouldn't add any
HTTP doesn't add. What we could do is (1) note why auto-update may be requirements that HTTP doesn't add. What we could do is (1) note why
a bad idea, and possibly (2) define that redirects created by auto-update may be a bad idea, and possibly (2) define that redirects
MKREDIRECTREF should not behave that way (or alternatively define created by MKREDIRECTREF should not behave that way (or alternatively
more specific resource types). define more specific resource types).
D.9 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.
Index Index
A A
Apply-To-Redirect-Ref header 19 Apply-To-Redirect-Ref header 20
C C
Condition Names Condition Names
DAV:locked-update-allowed (pre) 8 DAV:locked-update-allowed (pre) 9
DAV:name-allowed (pre) 7 DAV:name-allowed (pre) 9
DAV:new-redirectref (post) 8 DAV:new-redirectref (post) 9
DAV:redirect-lifetime-supported (pre) 8 DAV:parent-resource-must-be-non-null (pre) 8
parent-resource-must-be-non-null (pre) 7 DAV:redirect-lifetime-supported (pre) 9
resource-must-be-null (pre) 7 DAV:resource-must-be-null (pre) 8
D D
DAV header DAV header
compliance class 'redirectrefs' 20 compliance class 'redirectrefs' 21
DAV:locked-update-allowed precondition 8 DAV:locked-update-allowed precondition 9
DAV:name-allowed precondition 7 DAV:name-allowed precondition 9
DAV:new-redirectref postcondition 8 DAV:new-redirectref postcondition 9
DAV:parent-resource-must-be-non-null precondition 7 DAV:parent-resource-must-be-non-null precondition 8
DAV:redirect-lifetime property 19 DAV:redirect-lifetime property 20
DAV:redirect-lifetime-supported precondition 8 DAV:redirect-lifetime-supported precondition 9
DAV:redirectref resource type 20 DAV:redirectref resource type 21
DAV:reftarget property 20 DAV:reftarget property 21
DAV:resource-must-be-null precondition 7 DAV:resource-must-be-null precondition 8
H H
Headers Headers
Apply-To-Redirect-Ref 19 Apply-To-Redirect-Ref 20
Redirect-Ref 19 Redirect-Ref 20
M M
Methods Methods
MKREDIRECTREF 7 MKREDIRECTREF 8
MKREDIRECTREF method 7 MKREDIRECTREF method 8
P P
Properties Properties
DAV:redirect-lifetime 19 DAV:redirect-lifetime 20
DAV:reftarget 20 DAV:reftarget 21
R R
Redirect-Ref header 19 Redirect-Ref header 20
Resource Types Resource Types
DAV:redirectref 20 DAV:redirectref 21
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 Rights 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; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the IETF's procedures with respect to rights in IETF Documents can on the procedures with respect to rights in RFC documents can be
be found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. 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
 End of changes. 

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