RFC 8144: Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)
In plain English — editorial summary, not part of the RFC
This document defines how the Prefer header field (RFC 7240) can be used by a Web Distributed Authoring and Versioning (WebDAV) client to request that certain behaviors be employed by a server while constructing a response to a request. Furthermore, it defines the new "depth-noroot" preference.
Document record
- Document ID
- RFC8144
- Published
- April 2017
- Authors
- K. Murchison
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 28
- Also known as
- —
- Updates:
- RFC 7240
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8164Opportunistic Security for HTTP/2Current
May 2017
- RFC 8121Mutual Authentication Protocol for HTTP: Cryptographic Algorithms Based on the Key Agreement Mechanism 3 (KAM3)Current
April 2017
- RFC 8120Mutual Authentication Protocol for HTTPCurrent
April 2017
- RFC 8188Encrypted Content-Encoding for HTTPCurrent
June 2017
- RFC 8040RESTCONF ProtocolUpdated
January 2017
- RFC 8030Generic Event Delivery Using HTTP PushCurrent
December 2016
- RFC 8291Message Encryption for Web PushCurrent
November 2017
- RFC 7975Request Routing Redirection Interface for Content Delivery Network (CDN) InterconnectionCurrent
October 2016
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?