RFC 4437: Web Distributed Authoring and Versioning (WebDAV) Redirect Reference Resources
In plain English — editorial summary, not part of the RFC
This specification defines an extension to Web Distributed Authoring and Versioning (WebDAV) to allow clients to author HTTP redirect reference resources whose default response is an HTTP/1.1 3xx (Redirection) status code. A redirect reference makes it possible to access the target resourced indirectly through any URI mapped to the redirect reference resource. This specification does not address remapping of trees of resources or regular expression based redirections. There are no integrity guarantees associated with redirect reference resources. Other mechanisms can also be used to achieve the same functionality as this specification. This specification allows operators to experiment with this mechanism and develop experience on what is the best approach to the problem. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4437
- Published
- March 2006
- Authors
- J. Whitehead; G. Clemm; J. Reschke
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3253Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)Current
March 2002
- RFC 5689Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)Current
September 2009
- RFC 2965HTTP State Management MechanismObsoleted
October 2000
- RFC 2617HTTP Authentication: Basic and Digest Access AuthenticationObsoleted
June 1999
- RFC 2616Hypertext Transfer Protocol -- HTTP/1.1Obsoleted
June 1999
- RFC 2310The Safe Response Header FieldCurrent
April 1998
- RFC 2227Simple Hit-Metering and Usage-Limiting for HTTPCurrent
October 1997
- RFC 1945Hypertext Transfer Protocol -- HTTP/1.0Current
May 1996
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?