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

Include URL to error details in error messages #354

Closed
bbangert opened this issue Feb 19, 2016 · 2 comments · Fixed by #547
Closed

Include URL to error details in error messages #354

bbangert opened this issue Feb 19, 2016 · 2 comments · Fixed by #547
Assignees

Comments

@bbangert
Copy link
Member

bbangert commented Feb 19, 2016

The JSON error response should include a URL to link to a fuller explanation of the error for better diagnosis for developers on what went wrong.

The autopush docs should be updated to include appropriate details of each errno and how they can be remedied (or link to MDN docs explaining it).

@bbangert bbangert added this to the PUSHSVC-0: quality milestone Feb 19, 2016
@bbangert bbangert added the ready label Feb 19, 2016
@jrconlin
Copy link
Member

#449 introduces "message" to websocket JSON responses. Once that's landed, I will add pointers to other errors and close this.

@jrconlin jrconlin self-assigned this Apr 20, 2016
@ghost
Copy link

ghost commented Apr 20, 2016

Very nice! I think it would be helpful to include detailed message URLs for endpoint responses, too.

Firefox can show the WebSocket message field in the browser console, but those are likely to be client bugs that aren't actionable by web developers. (Though they're handy for Mozilla folks that set a custom dom.push.serverURL pref).

jrconlin added a commit that referenced this issue Jul 22, 2016
Added some additional, descriptive logging for duplicate error conditions.

closes #354
jrconlin added a commit that referenced this issue Jul 22, 2016
Added some additional, descriptive logging for duplicate error conditions.

closes #354
jrconlin added a commit that referenced this issue Jul 23, 2016
Added some additional, descriptive logging for duplicate error conditions.

closes #354
jrconlin added a commit that referenced this issue Jul 23, 2016
Added some additional, descriptive logging for duplicate error conditions.

closes #354
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.

2 participants