CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 11:33:03 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=Dq67_.VT.v3mwd88n7tIrXyAq0IvysxuGm0H1JdJJOc-1760095983-1.0.1.1-HTJ0V9ZDfaDGkzl7T_8DIZF7Af6RB.AH6FgZ91hXIu_SIEcfj37ZQWEU6oDuOPUnZ1W8rNkZhKM4jc3R3VovcCHZDg25KLD1kaMLZhHC.R0; path=/; expires=Fri, 10-Oct-25 12:03:03 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c5ccf4de3a9dfd-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8291 » RFC Editor
Search RFCs
RFC 8291
Message Encryption for Web Push, November 2017
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8291
Discuss this RFC: Send questions or comments to the mailing list webpush@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8291
Abstract
This document describes a message encryption scheme for the Web Push protocol. This scheme provides confidentiality and integrity for messages sent from an application server to a user agent.
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