← Back to release summary

Push API: support for ietf-webpush-encryption-08

Category
Network / Connectivity
Type
New or changed feature
Status
Enabled by default (Chrome 60)
Intent stage
None

Summary

Chrome currently supports encrypted push message payloads encrypted with the `aesgcm` content encoding (draft 03). A series of substantial changes were made to the encryption drafts, yielding a new content coding: `aes128gcm` (draft 08). We'll continue to accept `aesgcm` for received push messages as well.

Standards & signals

Docs: https://tools.ietf.org/html/draft-ietf-webpush-encryption-03 https://tools.ietf.org/html/draft-ietf-webpush-encryption-08

View on chromestatus.com