| commit | f3008ae7b25404f8a5d2f4c1699abed5b0ecb1e7 | [log] [tgz] |
|---|---|---|
| author | peter <[email protected]> | Thu May 19 12:28:43 2016 |
| committer | Commit bot <[email protected]> | Thu May 19 12:30:04 2016 |
| tree | a6531a57a683a74bd6e49af8587028d9faa5f48c | |
| parent | 882a0d56956f13092af1b5167c29e7b7d538593b [diff] [blame] |
Ship Web Push subscription restrictions This exposes the "applicationServerKey" property when subscribing with the Push API, in which the developer can provide their application server's key per draft-ietf-webpush-vapid. https://tools.ietf.org/html/draft-ietf-webpush-vapid When doing so, Chrome will give them an endpoint for the subscription that supports the Web Push Protocol rather than the proprietary GCM protocol. The endpoint is still provided by GCM. Intent to Ship: https://groups.google.com/a/chromium.org/d/topic/blink-dev/Wo7fimlUUjc/discussion BUG=583753 Review-Url: https://codereview.chromium.org/1931843002 Cr-Commit-Position: refs/heads/master@{#394747}
diff --git a/chrome/browser/push_messaging/push_messaging_constants.cc b/chrome/browser/push_messaging/push_messaging_constants.cc index 57e603d..ec32bc1 100644 --- a/chrome/browser/push_messaging/push_messaging_constants.cc +++ b/chrome/browser/push_messaging/push_messaging_constants.cc
@@ -4,7 +4,11 @@ #include "chrome/browser/push_messaging/push_messaging_constants.h" -const char kPushMessagingEndpoint[] = "https://android.googleapis.com/gcm/send"; +const char kPushMessagingGcmEndpoint[] = + "https://android.googleapis.com/gcm/send/"; + +const char kPushMessagingPushProtocolEndpoint[] = + "https://fcm.googleapis.com/fcm/send/"; const char kPushMessagingForcedNotificationTag[] = "user_visible_auto_notification";