HTTP 400 Error Bodies

Bug #1369534 reported by Flavio Percoco
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zaqar
Confirmed
Low
Unassigned

Bug Description

Where it makes sense (e.g., HTTP 400), the response body should include a JSON doc with error info, link to documentation, long description of the problem.

Ideally this would use api-problem+json or similar.

(there was a bp for this https://blueprints.launchpad.net/zaqar/+spec/http-error-bodies )

Changed in zaqar:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Flavio Percoco (flaper87) wrote :

I think this is a great idea, except for the extra time we'll need to spend serializing the response. Food for thought

Changed in zaqar:
milestone: none → next
summary: - HTTP Error Bodies
+ HTTP 400 Error Bodies
Revision history for this message
Nishant Kumar (nishant-108) wrote :

Is this bug still open?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.