RFC 5995: Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections
In plain English — editorial summary, not part of the RFC
The Hypertext Transfer Protocol (HTTP) Extensions for the Web Distributed Authoring and Versioning (WebDAV) do not define the behavior for the "POST" method when applied to collections, as the base specification (HTTP) leaves implementers lots of freedom for the semantics of "POST". This has led to a situation where many WebDAV servers do not implement POST for collections at all, although it is well suited to be used for the purpose of adding new members to a collection, where the server remains in control of the newly assigned URL. In fact, the Atom Publishing Protocol (AtomPub) uses POST exactly for that purpose. On the other hand, WebDAV-based protocols, such as the Calendaring Extensions to WebDAV (CalDAV), frequently require clients to pick a unique URL, although the server could easily perform that task. This specification defines a discovery mechanism through which servers can advertise support for POST requests with the aforementioned "add collection member" semantics. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5995
- Published
- September 2010
- Authors
- J. Reschke
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5842Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)Current
April 2010
- RFC 5689Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)Current
September 2009
- RFC 5397WebDAV Current Principal ExtensionCurrent
December 2008
- RFC 4791Calendaring Extensions to WebDAV (CalDAV)Updated
March 2007
- RFC 3253Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)Current
March 2002
- RFC 5987Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field ParametersObsoleted
August 2010
- RFC 6011Session Initiation Protocol (SIP) User Agent ConfigurationCurrent
October 2010
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?