RFC 7236: Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme Registrations
In plain English — editorial summary, not part of the RFC
This document registers Hypertext Transfer Protocol (HTTP) authentication schemes that have been defined in RFCs before the IANA HTTP Authentication Scheme Registry was established.
Document record
- Document ID
- RFC7236
- Published
- June 2014
- Authors
- J. Reschke
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 3
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7237Initial Hypertext Transfer Protocol (HTTP) Method 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 7615HTTP Authentication-Info and Proxy-Authentication-Info Response Header FieldsObsoleted
September 2015
- RFC 9110HTTP SemanticsCurrent
June 2022
- RFC 9111HTTP CachingCurrent
June 2022
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?