Web Push: 401 Unauthorized

Duplicate Issue #15194523 • See Issue #15194521

Details

Author
Marco C.
Created
Dec 22, 2017
Privacy
This issue is public.
Duplicates
See progress on Bug #15194521
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

This bug is related to the Push API and Service Workers. I post in this general category of the bug tracker because I haven’t found a more specific category.

At Pushpad, a web push notification service, we are trying to add support for Edge. We already send millions of notifications daily to Mozilla autopush and Firebase Cloud Messaging using the Push API and VAPID. Everything works properly.

Now we are unable to support Microsoft Edge: when we try to subscribe to the notifications, we get the authorization prompt and we store the endpoint successfully on our server. However when we try to make a POST request to the endpoint we get 401 Unauthorized. Probably this is related to VAPID, however we use the exact same code for Firefox, Chrome and Opera and it works properly. The only problem is with Edge.

The error is too general to understand what’s wrong with the request. Could you please check your logs and provide additional information? It would be really helpful. You should be able to identify the requests sent by Pushpad because the VAPID payload contains 'sub’: 'mailto:support@pushpad.xyz’. If you need it I may also provide you the Ruby code used to generate the request (VAPID headers, etc.) and with the exact endpoint (in private).

Microsoft Edge 42.17063.1000.0
Microsoft EdgeHTML 17.17063

Attachments

0 attachments

    Comments and activity

    You need to sign in to your Microsoft account to add a comment.

    Sign in