Closed
Bug 1200859
Opened 9 years ago
Closed 9 years ago
Push notification server rejects POST requests
Categories
(Cloud Services Graveyard :: Server: WebPush, defect)
Cloud Services Graveyard
Server: WebPush
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bdahl, Unassigned)
Details
STR 1) Get an endpoint url using the new PushManager API 2) Send a post request to the URL (e.g. curl -ivs -H "Content-Type: application/json" -X POST -d '{"username":"xyz","password":"xyz"}' https://updates.push.services.mozilla.com/push/<UUID>) Expected: HTTP/1.1 201 Created Got: HTTP/1.1 405 Method Not Allowed If I use a 'put' request the notification works, but I still get an incorrect response of HTTP/1.1 200. SPEC: https://tools.ietf.org/html/draft-ietf-webpush-protocol-00#section-5
Comment 1•9 years ago
|
||
This is correct. we have yet to roll out the WebPush spec version of push. We are currently using the older SimplePush specification until the WebPush spec becomes finalized. We currently have several deployed services that require the older service that have not yet been moved to the new spec. If you're interested in using push.services in it's current implementation, MDN has information about how to configure your app to use it. https://developer.mozilla.org/en-US/docs/Web/API/Push_API Unfortunately, we don't have a schedule for when we will have a WebPush compliant server available, as there are still some significant issues outstanding in the spec.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•