Push subscription restrictions, Web Push protocol

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.

Documentation

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

Specification

Editor's draft

Status in Chromium

Blink components: Blink

Enabled by default (launch bug) in:

• Chrome for desktop release 52
• Chrome for Android release 52
• Opera release 39
• Opera for Android release 39

Consensus & Standardization

• Firefox: Shipped
• Edge: No public signals
• Safari: No public signals
• Web Developers: Strongly positive

Owner

• peter@chromium.org

Last updated on 2017-06-14