Httpbis Workgroup RFCs

Browse Httpbis Workgroup RFCs by Number

RFC6266 - Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP): RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects. [STANDARDS-TRACK]
RFC7230 - Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing: The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document provides an overview of HTTP architecture and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes related security concerns for implementations.
RFC7231 - Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content: The Hypertext Transfer Protocol (HTTP) is a stateless \%application- level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.
RFC7232 - Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.
RFC7233 - Hypertext Transfer Protocol (HTTP/1.1): Range Requests: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.
RFC7234 - Hypertext Transfer Protocol (HTTP/1.1): Caching: The Hypertext Transfer Protocol (HTTP) is a stateless \%application- level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.
RFC7235 - Hypertext Transfer Protocol (HTTP/1.1): Authentication: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.
RFC7236 - Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme Registrations: This document registers Hypertext Transfer Protocol (HTTP) authentication schemes that have been defined in RFCs before the IANA HTTP Authentication Scheme Registry was established.
RFC7237 - Initial Hypertext Transfer Protocol (HTTP) Method Registrations: This document registers those Hypertext Transfer Protocol (HTTP) methods that have been defined in RFCs before the IANA HTTP Method Registry was established.
RFC7538 - The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect): This document specifies the additional Hypertext Transfer Protocol (HTTP) status code 308 (Permanent Redirect).
RFC7540 - Hypertext Transfer Protocol Version 2 (HTTP/2): This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients.; This specification is an alternative to, but does not obsolete, the HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged.
RFC7541 - HPACK: Header Compression for HTTP/2: This specification defines HPACK, a compression format for efficiently representing HTTP header fields, to be used in HTTP/2.