Web Distributed Authoring and Versioning (WebDAV) Redirect Reference ResourcesUC Santa Cruz, Dept. of Computer Science1156 High StreetSanta CruzCA95064USejw@cse.ucsc.eduIBM20 Maguire RoadLexingtonMA02421USgeoffrey.clemm@us.ibm.comgreenbytes GmbHSalzmannstrasse 152MuensterNW48159Germany+49 251 2807760+49 251 2807761julian.reschke@greenbytes.dehttp://greenbytes.de/tech/webdav/WEBDAV Working Group
Umbrella issue for editorial changes.
Use ABNF syntax from RFC2234.
Go back to RFC822+RFC2616extensions.
The errata to RFC2616 (see http://skrb.org/ietf/http_errata.html#location-fragments)
explicitly allow fragments in Location headers; so the spec needs to allow
authoring them.
There are (at least) two major design goals, but unfortunately both are
in direct contradiction:
#1: Maximum consistency with HTTP/1.1 (RFC2616). This means that any
request that addresses a redirect reference resource 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 why other methods such as
PUT or DELETE should behave differently). Therefore, the redirect
reference protocol introduces a new request header
("Apply-To-Redirect-Ref") through which a client can indicate that the
request indeed should be applied to the redirect reference resource itself.
#2: Maximum usability with existing clients. For instance, the Microsoft
Webfolder client will not be able to DELETE a redirect reference
resource unless the server deviates from #1.
Right now I'm not sure about the best way to resolve this. Currently the
spec chooses #1 (back when this decision was made, there was probably
the assumption that existing clients would quickly be updated --
something that probably isn't true today).
However this may result in implementers either just ignoring these
rules, or adding special workarounds based on "User Agent" detection.
There was little feedback, so it seems that no change should be made.
This specification defines redirect reference resources. A
redirect reference resource is a resource whose default response is an
HTTP/1.1 3xx (Redirection) status code (see RFC2616, Section 10.3), redirecting the client to a different
resource, the target resource. A redirect reference makes it possible
to access the target resource indirectly, through any URI mapped to the
redirect reference resource. There are no integrity guarantees
associated with redirect reference resources.
Distribution of this document is unlimited. Please send comments to the
Distributed Authoring and Versioning (WebDAV) working group at , which may be joined by sending a message with subject
"subscribe" to .
Discussions of the WEBDAV working group are archived at
.
An issues list and XML and HTML versions of this draft are available from
.
This specification extends the Web Distributed Authoring Protocol (WebDAV)
to enable clients to create new access paths to existing resources. This
capability is useful for several reasons:
WebDAV makes it possible to organize HTTP resources into
hierarchies, placing them into groupings, known as collections, which
are more easily browsed and manipulated than a single flat collection. However,
hierarchies require categorization decisions that locate
resources at a single location in the hierarchy, a drawback when a
resource has multiple valid categories. For example, in a hierarchy of
vehicle descriptions containing collections for cars and boats, a
description of a combination car/boat vehicle could belong in either
collection. Ideally, the description should be accessible from both.
Allowing clients to create new URIs that access the existing resource
lets them put that resource into multiple collections.
Hierarchies also make resource sharing more difficult, since resources
that have utility across many collections are still forced into a single
collection. For example, the mathematics department at one university
might create a collection of information on fractals that contains
bindings to some local resources, but also provides access to some
resources at other universities. For many reasons, it may be
undesirable to make physical copies of the shared resources: to conserve disk space, to respect copyright constraints, or to
make any changes in the shared resources visible automatically. Being
able to create new access paths to existing resources in other
collections or even on other unrelated systems is useful for this sort of case.
The redirect reference resources defined here provide a mechanism for
creating alternative access paths to existing resources. A redirect
reference resource is a resource in one collection whose purpose is to
redirect requests to another resource (its target), possibly in a
different collection. In this way, it allows clients to submit requests
to the target resource from another collection. It redirects most
requests to the target resource using a HTTP status code from the 3xx range (Redirection),
thereby providing a form of mediated access to the target resource.
A redirect reference is a resource with properties but no body of its own. Properties
of a redirect reference resource can contain such information as who created
the reference, when, and why. Since redirect reference resources are
implemented using HTTP 3xx responses, it generally takes two round trips to
submit a request to the intended resource. Redirect references work equally well for local
resources and for resources that reside on a different system from the
reference.
The remainder of this document is structured as follows:
defines terms that will be used throughout the specification.
provides an overview of redirect reference resources.
defines the semantics of existing methods when applied to redirect
reference resources.
discusses how to create a redirect reference resource, and
discusses updating redirect references. discusses their semantics when
applied to collections that contain redirect reference resources.
Sections
through discuss several other issues raised by the
existence of redirect reference resources. Sections through
define the new headers, properties, and XML elements required to support
redirect reference resources. Section discusses capability
discovery. Sections
through present the security,
internationalization, and IANA concerns raised by this specification.
The remaining sections provide a variety of supporting information.
Since this document describes a set of extensions to the WebDAV
Distributed Authoring Protocol , itself an extension to the
HTTP/1.1 protocol, the augmented BNF used here to describe protocol
elements is exactly the same as described in Section 2.1 of
. Since this augmented BNF uses the basic production rules provided in
Section 2.2 of , these rules apply to this document as well.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in .
This specification uses the Augmented Backus-Naur Form (ABNF) notation of .
The terminology used here follows and extends that in the WebDAV
Distributed Authoring Protocol specification . Definitions of
the terms resource, Uniform Resource Identifier (URI), and Uniform
Resource Locator (URL) are provided in
.
Redirect Reference Resource
A resource created to redirect all requests made to it, using
an HTTP status code from the 3xx range, to a defined target resource.
Non-Reference Resource
A resource that is not a reference to another resource.Target Resource
The resource to which requests are
redirected by a redirect reference
resource. A target resource can be anything that can be identified by an absolute URI
(see
, "absolute-URI").
This document uses the terms "precondition", "postcondition" and "protected property" as defined in
. Servers MUST report pre-/postcondition failures
as described in section 1.6 of this document.
For all operations submitted to a redirect reference resource, the
default response is a 302 (Found), accompanied by the Redirect-Ref
header (defined in below) and the Location header (, Section 14.30) set to
the URI of the target resource. With this information, the client can
resubmit the request to the URI of the target resource.
A redirect reference resource never automatically forwards requests to
its target resource. Redirect resources bring the same benefits as links
in HTML documents. They can be created and maintained without the
involvement or even knowledge of their target resource. This reduces the
cost of linking between resources.
If the client is aware that it is operating on a redirect reference
resource, it can resolve the reference by retrieving the reference
resource's DAV:reftarget property (defined in below), whose
value contains the URI of the target resource. It can then submit
requests to the target resource.
A redirect reference resource is a new type of resource. To distinguish
redirect reference resources from non-reference resources, a new value
of the DAV:resourcetype property (defined in ), DAV:redirectref,
is defined in below.
Since a redirect reference resource is a resource, methods can be applied to the reference
resource as well as to its target resource. The Apply-To-Redirect-Ref
request header (defined in below) is provided so that
referencing-aware clients can control whether an operation is applied to
the redirect reference resource or
standard HTTP/WebDAV behaviour (redirection with a 3xx status code)
should occur. The Apply-To-Redirect-Ref
header can be used with most requests to redirect
reference resources. This header is particularly useful with PROPFIND,
to retrieve the reference resource's own properties.
Implementation Note: Operations on the target of a redirect reference
usually do not affect the redirect reference itself. However, clients
should not rely on this behaviour (for instance, some servers may
update redirect references as a result of namespace operations on the
reference's target).
Although non-referencing-aware clients cannot create reference
resources, they should be able to submit requests through the reference
resources created by reference-aware WebDAV clients. They should be
able to follow any references to their targets. To make this possible,
a server that receives any request made via a redirect reference
resource MUST return a 3xx range (Redirection) status code, unless the request
includes an Apply-To-Redirect-Ref header specifying "T". The client and server MUST
follow Section 10.3, but with these additional
rules:
The Location response header MUST contain an absolute URIURI (see , Section 3) that
identifies the target of the reference resource.
The response MUST include the Redirect-Ref header. This header
allows reference-aware WebDAV clients to recognize the resource as a
reference resource and understand the reason for the redirection.
A reference-aware WebDAV client can, like a non-referencing client, resubmit the request to
the URI in the Location header in order to operate on the target
resource. Alternatively, it can resubmit the request to the URI of the
redirect reference resource with the "Apply-To-Redirect-Ref: T" header in
order to operate on the reference resource itself. In this case, the request MUST be applied to the
reference resource itself, and a 3xx response MUST NOT be returned.
As redirect references do not have bodies, GET and PUT requests with
"Apply-To-Redirect-Ref: T" MUST fail with status 403 (forbidden).
The MKREDIRECTREF method requests the creation of a redirect reference resource.
If a MKREDIRECTREF request fails, the server state preceding the request MUST be restored.
Responses from a MKREDIRECTREF request MUST NOT be cached, as MKREDIRECTREF
has non-idempotent and non-safe semantics
(see , section 9.1).
Marshalling:
The request body MUST be a DAV:mkredirectref XML element.
The DAV:href element is defined in (Section 12.3)
and MUST contain either an absolute-URI or a relative-ref (without fragment), see
, Sections 4.2 and 4.3)
URI or a relative-ref (see , Sections 3 and 4.2).
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) status.
If a response body for a successful request is included, it MUST 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 response body.
Preconditions:
(DAV:resource-must-be-null): A resource MUST NOT exist at the Request-URI.
(DAV:parent-resource-must-be-non-null): The Request-URI minus the last
past segment MUST identify a collection.
(DAV:name-allowed): The last segment of the Request-URI is available for
use as a resource name.
(DAV:locked-update-allowed): If the collection identified by the
Request-URI minus the last path segment is write-locked, then the appropriate
token MUST be specified in an If request header.
(DAV:redirect-lifetime-supported): If the request body contains a DAV:redirect-lifetime
element, the server MUST support the specified lifetime. Support for DAV:temporary is REQUIRED, while
support for DAV:permanent is OPTIONAL.
(DAV:legal-reftarget): The specified is a legal URI or relative-ref.
Postconditions:
(DAV:new-redirectref): a new redirect reference resource is created
whose DAV:reftarget property has the value specified in the request body.
This request resulted in the creation of a new redirect reference
resource at
http://www.example.com/~whitehead/dav/spec08.ref, which points to
the resource identified by the DAV:reftarget property. In this example,
the target resource is identified by the URI
http://www.example.com/i-d/draft-webdav-protocol-08.txt. The redirect
reference resource's DAV:resourcetype property is set to DAV:redirectref
and it's DAV:redirect-lifetime property has the value DAV:temporary.
The UPDATEREDIRECTREF method requests the update of a redirect reference resource.
If a UPDATEREDIRECTREF request fails, the server state preceding the request MUST be restored.
Responses from a UPDATEREDIRECTREF request MUST NOT be cached, as UPDATEREDIRECTREF has
non-safe semantics (see , section 9.1).
Marshalling:
The request body MUST be a DAV:updateredirectref XML element.
If no DAV:reftarget element is specified, the server MUST NOT change
the target of the redirect reference.
If no DAV:redirect-lifetime element is specified, the server MUST NOT change
the lifetime of the redirect reference.
If a response body for a successful request is included, it MUST be a
DAV:updateredirectref-response XML element. Note that this document does
not define any elements for the UPDATEREDIRECTREF response body, but the
DAV:updateredirectref-response element is defined to ensure
interoperability between future extensions that do define elements for
the response body.
Preconditions:
(DAV:locked-update-allowed): if the resource is write-locked, then the appropriate
token MUST be specified in an If request header.
(DAV:must-be-redirectref): the resource identified by the Request-URI
must be a redirect reference resource as defined by this specification.
(DAV:redirect-lifetime-supported): see .
(DAV:redirect-lifetime-update-supported): servers MAY support changing
the DAV:redirect-lifetime property; if they don't, this condition code can
be used to signal failure.
(DAV:legal-reftarget): see .
Postconditions:
(DAV:redirectref-updated): the DAV:reftarget and DAV:redirect-lifetime
properties of the redirect reference have been updated accordingly.
This request has updated the redirect reference's DAV:reftarget property to "/i-d/draft-webdav-protocol-08b.txt",
and has not changed the DAV:redirect-lifetime value. Note that
the "Apply-To-Redirect-Ref" request header must be used, otherwise the
request would result in a redirect (3xx) response status.
Consistent with the rules in , the response for each redirect
reference encountered while processing a collection MUST be a 3xx (Redirection) unless a "Apply-To-Redirect-Ref: T" header is included with the
request. The overall response will therefore be a 207 (Multi-Status). For
each DAV:response element representing a redirect reference, the server
MUST include an additional DAV:location element, specifying the value of the
"Location" header that would be returned otherwise. The extension is defined
in below.
The Apply-To-Redirect-Ref header (defined in ) MAY be used
with any request on a collection. If present, it will be applied to all
redirect reference resources encountered while processing the collection.
An attempt to lock (with Depth: infinity) a collection that contains redirect references
without specifying "Apply-To-Redirect-Ref: T" will always fail. The Multi-Status response will contain a
3xx response for each redirect reference.
Reference-aware clients can lock the collection by using Apply-To-Redirect-Ref,
and, if desired, lock the targets of the redirect references individually.
Non-referencing clients must resort to locking each resource
individually.
Suppose a PROPFIND request with Depth: infinity is submitted to the
following collection, with the members shown here:
In this example the Depth header is set to infinity, and the Apply-To-Redirect-Ref
header is set to "F". The collection contains one URI that
identifies a redirect reference resource. The response element for the
redirect reference resource has a status of 302 (Found), and includes a
DAV:location extension element to allow clients to retrieve the properties of
its target resource. (The response element for the redirect reference
resource does not include the requested properties. The client can
submit another PROPFIND request to the URI in the DAV:location pseudo-property
to retrieve those properties.)
Suppose a PROPFIND request with "Apply-To-Redirect-Ref: T" and Depth:
infinity is submitted to the following collection, with the members
shown here:
Since the "Apply-To-Redirect-Ref: T" header is present, the response shows
the properties of the redirect reference resource in the collection
rather than reporting a 302 status.
Suppose a COPY request is submitted to the following collection, with
the members shown:
In this case, since /MyCollection/nunavut is a redirect reference
resource, the COPY operation was only a partial success. The redirect
reference resource was not copied, but a 302 response was returned for
it. So the resulting collection is as follows:
Suppose a LOCK request is submitted to the following collection, with
the members shown:
The server returns a 302 response code for the redirect reference
resource in the collection. Consequently, neither the collection nor
any of the resources identified by its internal member URIs were locked. A
referencing-aware client can submit a separate LOCK request to the URI
in the DAV:location element returned for the redirect reference
resource, and can resubmit the LOCK request with the Apply-To-Redirect-Ref
header to the collection. At that point both the reference resource
and its target resource will be locked (as well as the collection and
all the resources identified by its other members).
Operations on targets of redirect reference resources have no effect on
the reference resource.
The URI in the href in a DAV:reftarget property MAY be a relative reference. In
this case, the base URI to be used for resolving it to
absolute form is the URI used in the HTTP message to identify the
redirect reference resource to which the DAV:reftarget property belongs.
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 element. The
value of this DAV:href element serves as the base URI for resolving
a relative reference in DAV:reftarget. The value of DAV:href may itself be
relative, in which case it must be resolved first in order to serve as
the base URI for the relative reference in DAV:reftarget. 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 request, and the
Request-URI.
In this example, the relative
reference "statistics/population/1997.html" is
returned as the value of the DAV:reftarget property for the reference resource identified
by href /geog/stats.html. The href is itself a relative reference, which
resolves to http://example.com/geog/stats.html. This is the base URI
for resolving the relative reference in reftarget. The absolute URI of
reftarget is http://example.com/geog/statistics/population/1997.html.
In a Request-URI /segment1/segment2/segment3, any of the three segments
may identify a redirect reference resource. (See
, Section 3.3,
for definitions of "path" and "segment".) If any segment in a Request-URI
identifies a redirect reference resource, the response SHOULD be a
3xx. The value of the Location header in the response is as follows:
The leftmost path segment of the Request-URI that identifies a redirect
reference resource, together with all path segments and separators to
the left of it, is replaced by the value of the redirect reference
resource's DAV:reftarget property (resolved to an absolute URI). The
remainder of the Request-URI is concatenated to this path.
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 "/"), the
final "/" in the DAV:reftarget property is dropped before the remainder
of the Request-URI is appended.
Consider Request-URI /x/y/z.html. Suppose that /x/ is a redirect
reference resource whose target resource is collection /a/, which
contains redirect reference resource y whose target resource is
collection /b/, which contains redirect reference resource z.html whose
target resource is /c/d.html.
In this case the client must follow up three separate 3xx responses
before finally reaching the target resource. The server responds to 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 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 request with a
3xx with Location: /c/d.html, and the client resubmits the request to
/c/d.html. This final request succeeds.
Note: the behavior described above may have a very serious impact on the
efficiency of mapping Request-URIs to resources in HTTP request
processing. Therefore servers MAY respond with a 404 status code if the cost of checking
all leading path segments for redirect references seems prohibitive.
The Redirect-Ref header is used in all 3xx responses from redirect
reference resources. The value is the link target as specified during
redirect reference resource creation.
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", the request MUST be
applied to the reference resource itself, and a 3xx response MUST NOT be
returned.
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
MUST ignore it.
The properties defined below are REQUIRED on redirect reference resources. A PROPFIND/allprop request SHOULD NOT return any of the properties defined in this document.
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.
This property provides an efficient way for clients to discover the 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.
redirectrefDAV:Used as the value of the DAV:resourcetype property to
specify that the resource type is a redirect reference
resource.
As described in , the DAV:location element
may be returned in the DAV:response element of a 207 Multi-Status response,
to allow clients to resubmit their requests to the target resource of a
redirect reference resource.
Consequently, the definition of the DAV:response XML element changes to
the following:
Sections 9.1 and 15 of describe the use of compliance classes
with the DAV header in responses to OPTIONS, to indicate which parts of
the WebDAV Distributed Authoring protocols the resource supports. This
specification defines an OPTIONAL extension to . It defines a
new compliance class, called redirectrefs, for use with the DAV header
in responses to OPTIONS requests. If a resource does support redirect
references, its response to an OPTIONS request may indicate that it
does, by listing the new redirectrefs compliance class in the DAV
header and by listing the MKREDIRECTREF method as one it supports.
When responding to an OPTIONS request, any type of resource can include
redirectrefs in the value of the DAV header. Doing so indicates that
the server permits a redirect reference resource at the Request-URI.
The DAV header in the response indicates that the resource
/somecollection/someresource is level 1 and level 2 compliant, as
defined in . In addition, /somecollection/someresource supports
redirect reference resources. The Allow header indicates that
MKREDIRECTREF requests can be submitted to /somecollection/someresource.
This section is provided to make applications that implement this protocol aware of the
security implications of this protocol.
All of the security considerations of HTTP/1.1 and the WebDAV
Distributed Authoring Protocol specification also apply to this protocol
specification. In addition, redirect reference resources introduce
several new security concerns and increase the risk of some existing
threats. These issues are detailed below.
By creating redirect reference resources on a trusted server, it is
possible for a hostile agent to induce users to send private information
to a target on an unrelated system. This risk is mitigated somewhat,
since clients are required to notify the user of the redirection for any
request other than GET or HEAD. (See , Section 10.3.3 302 Found.)
Although redirect loops were already possible in HTTP 1.1, the
introduction of the MKREDIRECTREF method creates a new avenue for clients
to create loops accidentally or maliciously. If the reference resource
and its target are on the same server, the server may be able to detect
MKREDIRECTREF requests that would create loops. See also , Section
10.3 "Redirection 3xx."
Denial of service attacks were already possible by posting URLs that
were intended for limited use at heavily used Web sites. The
introduction of MKREDIRECTREF creates a new avenue for similar denial of
service attacks. Clients can now create redirect reference resources at
heavily used sites to target locations that were not designed for heavy
usage.
There are several ways that redirect reference resources may reveal
information about collection structures. First, the DAV:reftarget
property of every redirect reference resource contains the URI of the
target resource. Anyone who has access to the reference resource can
discover the collection path that leads to the target resource. The
owner of the target resource may have wanted to limit knowledge of this
collection structure.
Sufficiently powerful access control mechanisms can control this risk to
some extent. Property-level access control could prevent users from
examining the DAV:reftarget property. (The Location header returned in
responses to requests on redirect reference resources reveals the same
information, however.)
This risk is no greater than the similar risk posed by HTML links.
All internationalization considerations mentioned in also apply to this document.
All IANA considerations mentioned in also
apply to this document.
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 specification.
This document has benefited from thoughtful discussion by Jim Amsden, Peter
Carlson, Steve Carter, Tyson Chihaya, Ken Coar, Ellis Cohen, Bruce
Cragun, Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Lisa Dusseault, Stefan Eissing, Roy
Fielding, Yaron Goland, Fred Hitt, Alex Hopmann, James Hunt, Marcus
Jager, Chris Kaler, Manoj Kasichainula, Rohit Khare, Daniel LaLiberte,
Steve Martin, Larry Masinter, Jeff McAffer, Joe Orton,
Surendra Koduru Reddy, Juergen Reuter, Max
Rible, Sam Ruby, Bradley Sergeant, Nick Shelness, John Stracke, John
Tigue, John Turner, Kevin Wiggen, and others.
Key words for use in RFCs to Indicate Requirement LevelsHarvard Universitysob@harvard.eduAugmented BNF for Syntax Specifications: ABNFInternet Mail Consortium675 Spruce Dr.SunnyvaleCA94086US+1 408 246 8253+1 408 249 6205dcrocker@imc.orgDemon Internet LtdDorking Business ParkDorkingSurreyEnglandRH4 1HNUKpaulo@turnpike.comUniform Resource Identifier (URI): Generic SyntaxWorld Wide Web Consortiumtimbl@w3.orgDay Softwarefielding@gbiv.comAdobe Systems IncorporatedLMM@acm.orgHTTP Extensions for Distributed Authoring -- WEBDAVMicrosoft Corporationyarong@microsoft.comDept. Of Information and Computer Science, University of California, Irvineejw@ics.uci.eduNetscapeasad@netscape.comNovellsrcarter@novell.comNovelldcjensen@novell.comHypertext Transfer Protocol -- HTTP/1.1University of California, Irvinefielding@ics.uci.eduW3Cjg@w3.orgCompaq Computer Corporationmogul@wrl.dec.comMIT Laboratory for Computer Sciencefrystyk@w3.orgXerox Corporationmasinter@parc.xerox.comMicrosoft Corporationpaulle@microsoft.comW3Ctimbl@w3.orgVersioning Extensions to WebDAV (Web Distributed Authoring and Versioning)Rational Softwaregeoffrey.clemm@rational.comIBMjamsden@us.ibm.comIBMtim_ellison@uk.ibm.comMicrosoftckaler@microsoft.comUC Santa Cruz, Dept. of Computer Scienceejw@cse.ucsc.edu
Remove "Changes to the WebDAV Document Type Definition". Section
"Extensions to the DAV:response XML Element for Multi-Status Responses"
already all information needed.
Done.
Julian Reschke takes editorial role (added to authors list). Cleanup
XML indentation. Start adding all unresolved last call issues. Update
some author's contact information. Update references, split into "normative"
and "informational". Remove non-RFC2616 headers ("Public") from examples.
Fixed width problems in artwork. Start resolving editorial issues.
Added Joe Orton and Juergen Reuter to Acknowledgements section. Close more
editorial issues. Remove dependencies on BIND spec.
More editorial fixes. Clarify that MKRESOURCE can only be used to create
redirect references (switch to new method in a future draft). Clarify
that redirect references do not have bodies.
Close (accept) issue "lc-79-accesscontrol". Add issue "rfc2606-compliance".
Close issues "lc-50-blindredirect", "lc-71-relative", "lc-74-terminology".
Update contact info for Geoff Clemm. Moved some of the original authors names to
new Contributors section.
Add and close issue "9-MKRESOURCE-vs-relative-URI".
Close issue "lc-72-trailingslash".
Close issue "lc-60-ex". Update issue "lc-85-301" with proposal.
Close issue "lc-06-reftarget-relative" (9-MKRESOURCE-vs-relative-URI was
a duplicate of this one). Also remove section 9.1 (example for MKRESOURCE
vs relative URIs).
Add and resolve issue "11.2-apply-to-redirect-ref-syntax" (header now has
values "T" and "F"). Also some cleanup for "rfc2606-compliance".
Typo fixes. Add and resolve "15.1-options-response".
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-80-i18n" and "rfc2606-compliance". Start work on index.
Add new issue "old_clients".
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.
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.
Resolve issues "lc-33-forwarding", "lc-36-server" and "lc-57-noautoupdate". Close issues "lc-48-s6",
"12.1-property-name", "3-terminology-redirectref" and "lc-58-update". Rearrange section 5 and 6.
Add some more terms to index (no change tracking).
Add and resolve issues "13_allprop" and "rfc2396bis".
Use the term "Request-URI" throughout (this is what RFC2616 defines).
Center some of the artwork.
Add and resolve issue "abnf".
Re-open and close issue "anbf" (implied LWS). Raise and close issue
"frag_in_target". Add precondition name for legal reftarget element
contents. Enhance index. Add and close issue "dtd-changes".