Match IETF draft Authorization header

[benlast]

The Authorization header produced by this library includes Bearer as the scheme. The spec at https://tools.ietf.org/html/draft-ietf-webpush-vapid-01 states that the scheme should be WebPush (https://tools.ietf.org/html/draft-ietf-webpush-vapid-01#section-3).

[marco-c]

I think FCM doesn't support this yet, but still requires Bearer.

Thank you for opening the issue, I never would have noticed the change.

[gauntface]

Will follow up on this tomorrow, thanks for the bug.

Does this currently break any browsers if we switch to this?

[marco-c]

Does this currently break any browsers if we switch to this?

I've just tried to run the tests after the change, they're failing with Chrome, working with Firefox.

[gauntface]

Schweet thank you for the info

On Wed, 10 Aug 2016, 17:58 Marco, notifications@github.com wrote:

Does this currently break any browsers if we switch to this?

I've just tried to run the tests after the change, they're failing with
Chrome, working with Firefox.

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#200 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIh8Jpr5favSVU33c1gB7VgacGvN-5yks5qenOzgaJpZM4JhixR
.