This is the wiki home of the IETF HTTPbis Working Group. We're chartered to:
- Revise and clarify RFC2616 -- the HTTP 1.1 specification -- to improve interoperability and security, and
- Develop the next version of HTTP -- HTTP/2.
See the HTTP/2 Home Page.
This Working Group was originally chartered to revise RFC2616, the specification of HTTP/1.1, folding in errata, implementation experience, and generally clarifying the specification. The result of that process was a a set of specifications, split up for readability as well as modularity:
- RFC7230 - HTTP/1.1: Message Syntax and Routing - low-level message parsing and connection management
- RFC7231 - HTTP/1.1: Semantics and Content - methods, status codes and headers
- RFC7232 - HTTP/1.1: Conditional Requests - e.g., If-Modified-Since
- RFC7233 - HTTP/1.1: Range Requests - getting partial content
- RFC7234 - HTTP/1.1: Caching - browser and intermediary caches
- RFC7235 - HTTP/1.1: Authentication - HTTP authentication framework
- RFC7236 - Initial HTTP Method Registrations - a document establishing the HTTP method registry's initial contents
- RFC7237 - Initial HTTP Authentication Scheme Registrations - a document establishing the HTTP authentication scheme registry's initial contents
- RFC6266 - RFC6266 - Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (test cases)
Other HTTP-Related Work
As with all IETF Working Groups, almost all discussion and decisions are made on our mailing list. Joining this list is "joining" the Working Group, and is the best way to participate.
During our official meetings, we use an XMPP (Jabber) channel at xmpp://email@example.com?join (archives) provided by the IETF.
ALL contributors and participants in the Working Group (i.e., on the mailing list and in physical meetings) MUST read and understand the NOTE WELL statement.