CARVIEW |
Select Language
HTTP/2 200
date: Wed, 08 Oct 2025 07:20:57 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=AdGbQNMF.MQa9o4qyF7gi.Ra1VkyQa69WyBLlce9s4g-1759908057-1.0.1.1-EQbm1UIqkdnyo7.7mqMwml0M4TJZS9hdP97JdeQMaJ9oXGPHNHV1znjJglI0viGjWwozgyCsy7F4WkQBuixTJ9RrWWUhEu7IUSaLt5XTAIM; path=/; expires=Wed, 08-Oct-25 07:50:57 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98b3e0e74e18a45e-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2397 » RFC Editor
Search RFCs
RFC 2397
The "data" URL scheme, August 1998
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2397
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2397
Abstract
A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. [STANDARDS-TRACK]
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