This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 34
Web Push: Empty messages don't need crypto headers #132
Comments
ghost
changed the title
Empty messages don't need crypto headers
Web Push: Empty messages don't need crypto headers
Aug 17, 2015
Though, now that I look at the latest spec, I see |
ghost
pushed a commit
that referenced
this issue
Aug 19, 2015
ghost
mentioned this issue
Aug 19, 2015
From IRC:
Sounds like the distinction is still relevant, and the spec should be updated accordingly. |
ghost
pushed a commit
that referenced
this issue
Aug 24, 2015
ghost
pushed a commit
that referenced
this issue
Aug 25, 2015
ghost
pushed a commit
that referenced
this issue
Aug 25, 2015
ghost
pushed a commit
that referenced
this issue
Aug 25, 2015
ghost
pushed a commit
that referenced
this issue
Aug 25, 2015
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
0 participants
IIRC, it's okay to omit the
Content-Encoding
andEncryption
headers for push messages without a body. The DOM API can distinguish these from empty encrypted messages:pushEvent.data === null
for the former;pushEvent.data.text() === ""
for the latter.The text was updated successfully, but these errors were encountered: