How we built it

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. This will enable us to move away from our current GCM implementation requirements.



Editor's draft

Status in Chromium

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

  • Shipped
  • No public signals
  • No public signals
  • Strongly positive


Last updated on 2016-07-28