CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 09:55:35 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=ONJirbHtWklDDko2aNSqrokQWwfiz5xwWtiOUBQjKNc-1760176535-1.0.1.1-IzDhzQwKlkpvpabRwZdpj5UBPBJWw7uN073k4QqN06Kg4_yG3Yk.uaN5iKQJTbp0yiI_RB29HK1s9HY4AvE1wlss7BWed67vw39me3H_Ij8; path=/; expires=Sat, 11-Oct-25 10:25:35 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cd7b9189598087-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8030 » RFC Editor
Search RFCs
RFC 8030
Generic Event Delivery Using HTTP Push, December 2016
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- M. Thomson
E. Damaggio
B. Raymor, Ed. - Stream:
- IETF
- Source:
- webpush (art)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8030
Discuss this RFC: Send questions or comments to the mailing list webpush@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8030
Abstract
This document describes a simple protocol for the delivery of real- time events to user agents. This scheme uses HTTP/2 server push.
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