Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

VAPID auth scheme name is now "WebPush", not "Bearer" #592

Closed
ghost opened this issue Aug 10, 2016 · 0 comments · Fixed by #593
Closed

VAPID auth scheme name is now "WebPush", not "Bearer" #592

ghost opened this issue Aug 10, 2016 · 0 comments · Fixed by #593
Assignees

Comments

@ghost
Copy link

ghost commented Aug 10, 2016

I raised this in webpush-wg/webpush-vapid#7 a few months ago, and we decided to keep Bearer then...but that's since changed in webpush-wg/webpush-vapid#18. The correct scheme name is now WebPush (though we'll probably want to allow both for back-compat).

See also: web-push-libs/web-push#200

@ghost ghost assigned jrconlin Aug 10, 2016
jrconlin added a commit that referenced this issue Aug 10, 2016
VAPID spec recently changed to specify "WebPush" as valid Authorization
token ID. Code allows either Bearer or WebPush while external code
transitions.

Closes #592
jrconlin added a commit that referenced this issue Aug 10, 2016
VAPID spec recently changed to specify "WebPush" as valid Authorization
token ID. Code allows either Bearer or WebPush while external code
transitions.

Closes #592
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant