This page contains all the DAV specifications, along with specs that are related to DAV.
This document specifies the WebDAV Distributed Authoring Protocol, a set of headers and methods which extend the Hypertext Transfer Protocol to provide capabilities for overwrite prevention (locking), properties, and namespace management.
Note that the text version of the document is the authoritative representation, and if there are differences between the text version and other versions, the text version is always correct.
This obsoletes RFC 2518: HTTP Extensions for Distributed Authoring -- WEBDAV (text, PDF, XML), published in February 1999.
This document specifies extensions to WebDAV (and hence HTTP) to provide capabilities for versioning and configuration management.
Note that the text version of the document is the authoritative representation, and if there are differences between the text version and other versions, the text version is always correct.
This specification has an associated goals document, versioning model (sorry about the ad), and scenarios document.
This specification was developed in the IETF DeltaV Working Group. The latest information is available on the group's web site.
See the protocol's web site for the latest information.
Note that the text version of the document is the authoritative representation, and if there are differences between the text version and other versions, the text version is always correct.
A protocol for creating bindings to resources. Bindings allow a resource to appear at multiple URLs, much like symbolic links in a filesystem.
See the protocol's web site for the latest draft and the issues list.
A protocol for creating redirect resources. A redirect resource corresponds to a resource which responds with an HTTP 302 redirect. This protocol provides for remote creation and administration of these resources.
Note that the text version of the document is the authoritative representation, and if there are differences between the text version and other versions, the text version is always correct.
A protocol for creating and manipulating a persistent, server-defined ordering of a collection's member resources.
Note that the text version of the document is the authoritative representation, and if there are differences between the text version and other versions, the text version is always correct.
This specification has a companion goals document.
The ACL extensions are being developed in a sub-group of the IETF WebDAV Working Group. The latest information is available on the sub-group's web pages.
Note that the text version of the document is the authoritative representation, and if there are differences between the text version and other versions, the text version is always correct.
The ACL extensions was developed in a sub-group of the IETF WebDAV Working Group. The latest information is available on the sub-group's web pages.
This is not a formal part of the WebDAV group of
specifications, but it is used within WebDAV's
opaquelocktoken
lock token scheme. Thus, it has
relevance to people interested in the WebDAV protocol
specifications.
This specification details HTTP. It is essentially a revision of RFC 2068.
This specification details the Basic and Digest authentication mechanisms for HTTP. It is a replacement for RFC 2069 (Digest Access Authentication).
Note that DAV requires that the server must accept Digest authentication for access (Basic is not allowed over unsecure channels). See Section 20.1 of the DAV specification.
This RFC describes when to use text/xml
,
application/xml
,
and the use of the charset
parameter.
See also: XML Resources
Additional specifications can be found on the Working Group Home Page
Requirements documents are provided under the WebDAV -- Other Resources area.
Last modified: Jan 01 2009