[wsgi] 400 response body is not standardized

Bug #1236540 reported by Kurt Griffiths
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zaqar
Invalid
Low
Unassigned

Bug Description

Identify the category of the error (e.g., "Invalid header value"), and ensure that the description mentions the header or param or body element that is problematic.

Tags: bugsmash
Kurt Griffiths (kgriffs)
summary: - 400 response body is not standardized
+ [wsgi] 400 response body is not standardized
Changed in marconi:
importance: Medium → Low
Kurt Griffiths (kgriffs)
Changed in marconi:
milestone: none → icehouse-3
Kurt Griffiths (kgriffs)
no longer affects: marconi/icehouse
Changed in marconi:
milestone: icehouse-3 → none
Revision history for this message
prashanth raghu (p-isprashanth) wrote :

Is someone already working on this ?

Revision history for this message
peng fei wang (wpf) wrote :

recently, I am reading the latest code, and found that we provide HTTPBadRequestBody & HTTPBadRequestAPI exceptions,

and commonly, for the BadRequestBody exception, we have the title of "Invalid request body" and with the concrete reason as description, such as "Request body can not be empty", "Missing {xxx} field.", "The value of the {name} must be a {type}“ and so on

for BadRequestAPI exception, most of them are validation errors ,and there should be some details information.

is that OK?

Changed in marconi:
assignee: Cindy Pallares (cindy-pallaresq) → nobody
Griffin Ashe (gashe5363)
Changed in zaqar:
assignee: nobody → Griffin Ashe (gashe5363)
Revision history for this message
Griffin Ashe (gashe5363) wrote :

It doesn't look like anyone is working on this, so I'm going to try to tackle it.

Griffin Ashe (gashe5363)
Changed in zaqar:
status: Triaged → In Progress
wangxiyuan (wangxiyuan)
Changed in zaqar:
status: In Progress → New
assignee: Griffin Ashe (gashe5363) → nobody
tags: added: bugsmash
Revision history for this message
wanghao (wanghao749) wrote :

Not sure this issue is still existing. This Bug could be closed.

Changed in zaqar:
status: New → Invalid
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.