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

Error when sending notification with VAPID & payload #426

Closed
marco-c opened this issue Mar 23, 2016 · 2 comments
Closed

Error when sending notification with VAPID & payload #426

marco-c opened this issue Mar 23, 2016 · 2 comments

Comments

@marco-c
Copy link
Contributor

marco-c commented Mar 23, 2016

Only VAPID:

{
    "Content-Length": 0,
    "Authorization": "Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NiJ9.eyJhdWQiOiJodHRwczovL3d3dy5tb3ppbGxhLm9yZy8iLCJleHAiOjE0NTg4MjMyMzcsInN1YiI6Im1haWx0bzp3ZWItcHVzaEBtb3ppbGxhLm9yZyJ9.UwHDZekWIM6R0P7f1LZAN3bxsIYpqjbLsPbVWiiHZMymBH7fJNrBtGuVIoCOQYas6vgmxdcxyg-lUUQD56BB-g",
    "Crypto-Key": "p256ecdsa=BOZp8-DG0JTJu76TQxK2LIVJGUL20cQ-b2z_K6kSDpaDdGQtFfBgb_0iDoBRJPLw37E6hHGadKxnuMzaLNVdu3M",
    "TTL": 2419200
}

VAPID & payload:

{
    "Content-Length": 22,
    "Content-Type": "application/octet-stream",
    "Encryption": "keyid=p256dh;salt=sXWj6ENEHatT8S2n4QFRFA",
    "Crypto-Key": "keyid=p256dh;dh=BB7TngAZg1DWb232f2IRGRf_R2u0TlQsoWNEc4jOwu0DHrq1b_RzpVots0HI5_gLF0lfjLS46JIVbwqKLqTdtPc,p256ecdsa=BOZp8-DG0JTJu76TQxK2LIVJGUL20cQ-b2z_K6kSDpaDdGQtFfBgb_0iDoBRJPLw37E6hHGadKxnuMzaLNVdu3M",
    "Content-Encoding": "aesgcm128",
    "Authorization": "Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NiJ9.eyJhdWQiOiJodHRwczovL3d3dy5tb3ppbGxhLm9yZy8iLCJleHAiOjE0NTg4MjMyNDMsInN1YiI6Im1haWx0bzp3ZWItcHVzaEBtb3ppbGxhLm9yZyJ9.QRhwBqP4LO7Nr1oFk3Tx5CKZPb72fSk55MKn5H7nZ8ZpmVUQr9a0ll_llnqn89_pRilVdAxcdXF-x7sAuRTTwA",
    "TTL": 2419200
}

VAPID & payload fails with this error:

{
  "errno": 109,
  "message": "Invalid bearer token: improperly specified crypto-key",
  "code": 401,
  "error": "Unauthorized"
}
@marco-c
Copy link
Contributor Author

marco-c commented Mar 23, 2016

VAPID & payload fails with this error (if I reverse the keys in the Crypto-Key header):

{
  "errno": 999,
  "code": 500,
  "error": "Internal Server Error"
}

@marco-c
Copy link
Contributor Author

marco-c commented Mar 23, 2016

Duplicate of #410. I thought the fix had already been deployed.

@marco-c marco-c closed this as completed Mar 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant