Increased Verbosity around WebPush 400 errors
Reported by
bhhro...@justin.tv,
Jun 13 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36 Steps to reproduce the problem: There are many ways to cause a 400(unauthorized registration) error when using WebPush on Chrome, so far I've encountered an issue with exp > 1 day, aud containing a trailing slash, and using Vapid spec 02 instead of Vapid spec 01. I think I've also caught wind of a thread where ordering of keys within a serialized json object has caused a 400 error(but I have not been able to confirm this one myself). What is the expected behavior? It would be nice to include more verbose error messaging around authorization errors which could be isolated to a specific cause(I think the ones above are reasonable candidates). What went wrong? Authorization errors can occur for a multitude of reasons, however as a client it is a bit difficult to fix the underlying issues as the error response is rather opaque: <HEAD> <TITLE>UnauthorizedRegistration</TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF" TEXT="#000000"> <H1>UnauthorizedRegistration</H1> <H2>Error 400</H2> </BODY> </HTML> Did this work before? N/A Does this work in other browsers? Yes Chrome version: 59.0.3071.86 Channel: stable OS Version: OS X 10.11.6 Flash Version: N/A
,
Jun 14 2017
Thank you for the report! We're aware of this and are working on a revision of our server that will, among other things, yield much clearer error messages. I don't have a date to announce yet, but we're on it :).
,
Jun 11 2018
Any update on the error message situation ? I am facing a similar issue in getting 400 error with an "Invalid Parameters" message which does not help solve the problem.
,
Jun 11 2018
Still being rolled out, sorry. |
||
►
Sign in to add a comment |
||
Comment 1 by nhiroki@chromium.org
, Jun 13 2017