RFC 7240: Prefer Header for HTTP
In plain English — editorial summary, not part of the RFC
This specification defines an HTTP header field that can be used by a client to request that certain behaviors be employed by a server while processing a request.
Document record
- Document ID
- RFC7240
- Published
- June 2014
- Authors
- J. Snell
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 17
- Also known as
- —
- Updated by:
- RFC 8144
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7238The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)Obsoleted
June 2014
- RFC 7237Initial Hypertext Transfer Protocol (HTTP) Method RegistrationsCurrent
June 2014
- RFC 7236Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme RegistrationsCurrent
June 2014
- RFC 7235Hypertext Transfer Protocol (HTTP/1.1): AuthenticationObsoleted
June 2014
- RFC 7234Hypertext Transfer Protocol (HTTP/1.1): CachingObsoleted
June 2014
- RFC 7232Hypertext Transfer Protocol (HTTP/1.1): Conditional RequestsObsoleted
June 2014
- RFC 7231Hypertext Transfer Protocol (HTTP/1.1): Semantics and ContentObsoleted
June 2014
- RFC 7230Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and RoutingObsoleted
June 2014
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?