Skip to content

Move deactivation requirement out of security section #410

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 10, 2025
Merged

Move deactivation requirement out of security section #410

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 3 additions & 7 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -849,8 +849,8 @@ <h2>
delivered.
</p>
<p>
A <a>push subscription</a> without a [=push subscription/window-accessible scope=] is
<a>deactivated</a> when its associated <a>service worker registration</a> is
A <a>push subscription</a> without a [=push subscription/window-accessible scope=] MUST
be <a>deactivated</a> when its associated <a>service worker registration</a> is
unregistered, though a <a>push subscription</a> MAY be <a>deactivated</a> earlier.
</p>
<p class="note">
Expand Down Expand Up @@ -913,7 +913,7 @@ <h2>
The contents of a <a>push message</a> are encrypted [[RFC8291]]. However, the <a>push
service</a> is still exposed to the metadata of messages sent by an <a>application
server</a> to a <a>user agent</a> over a <a>push subscription</a>. This includes the
timing, frequency and size of messages. Other than changing <a>push services</a>, which
timing, frequency, and size of messages. Other than changing <a>push services</a>, which
user agents may disallow, the only known mitigation is to increase the apparent message
size by padding.
</p>
Expand Down Expand Up @@ -953,10 +953,6 @@ <h2>
as |oldSubscription|, and `null` as |newSubscription|. The <a>user agent</a> MUST
<a>deactivate</a> the affected subscriptions in parallel.
</p>
<p>
When a <a>service worker registration</a> is unregistered, any associated <a>push
subscription</a> MUST be <a>deactivated</a>.
</p>
<p>
The <a>push endpoint</a> MUST NOT expose information about the user to be derived by actors
other than the <a>push service</a>, such as the user's device, identity or location. See
Expand Down