| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 11:36:52 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=Bc9_FGyVxvDp0D9PVVdLGBd8slHAjcN5BkIGnaa2yik-1760096212-1.0.1.1-ZC0UFfCKf7CLWxT0MvupN0B.bHY91KZmpF0AZQmHR4uR.AraoMGBZ9PXnq1NwE9kv5jTMtekxXhTUzNQ_xdSyBKI0C2mXHNFuDFdUQjkdM8; path=/; expires=Fri, 10-Oct-25 12:06:52 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c5d28fbceddfa6-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 9292 » RFC Editor
Search RFCs
RFC 9292
Binary Representation of HTTP Messages, August 2022
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Authors:
- M. Thomson
C. A. Wood - Stream:
- IETF
- Source:
- httpbis (wit)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9292
Discuss this RFC: Send questions or comments to the mailing list ietf-http-wg@w3.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9292
Abstract
This document defines a binary format for representing HTTP messages.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us