Push subscription restrictions, Web Push protocol

Category: Realtime / Communication
Type: New or changed feature
Status: Enabled by default (Chrome 52)
Intent stage: None

Summary

Supporting server authentication and subscription restrictions from the following IETF draft, that will allow developers to provide a public key when subscribing for push upon which Chrome will return a Web Push protocol-compatible endpoint. https://tools.ietf.org/html/draft-thomson-webpush-vapid-02 This will enable us to move away from our current GCM implementation requirements.

Standards & signals

Specification: https://github.com/w3c/push-api/pull/182/files
Firefox: Shipped/Shipping
Safari: No signal
Web developers: Strongly positive
Tracking bug: https://code.google.com/p/chromium/issues/detail?id=583753

Docs: https://tools.ietf.org/html/draft-thomson-webpush-vapid-02 https://developer.mozilla.org/en-US/docs/Web/API/PushManager/subscribe

View on chromestatus.com