Open
Conversation
Add a new guide page explaining how the Web Push infrastructure works end-to-end: subscription flow, push services (Mozilla Autopush, FCM, Apple), message encryption (RFC 8291), VAPID authentication (RFC 8292), delivery headers, and subscription lifecycle. Fixes mdn#39747
kovan
requested review from
caugner and
chrisdavidmills
and removed request for
a team
github-actions
bot
added
Content:WebAPI
github-actions
bot
removed
the
system
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Web/API/Push_API/Web_Push_Architecture) explaining how the Web Push infrastructure works end-to-endMotivation
The existing Push API docs explain the JavaScript interfaces but not the underlying architecture. Developers need to understand VAPID, encryption, and the delivery protocol to build a working implementation.
As requested in #39747.
Test plan