Bug #3869
closed
API error messages poorly formatted
Added by Thomas McKay almost 11 years ago.
Updated about 6 years ago.
Description
GET /api/users with an unauthorized user returns in the json below. Note the missing 'results' keyword.
{
"total": 0,
"subtotal": 0,
"page": 1,
"per_page": 20,
"search": null,
"sort": {
"by": null,
"order": null
},
"": {
"message": "Access denied",
"details": null
}
}
- Related to Feature #3011: default root name for api json index response to :results but make it configurable added
- Translation missing: en.field_release set to 2
- Target version set to 1.9.2
Should we go for this? It seems to me that 403 is meaningful enough for the client not to even try to read 'results'.
Daniel Lobato Garcia wrote:
Should we go for this? It seems to me that 403 is meaningful enough for the client not to even try to read 'results'.
I think so, because the message is valuable too for the reason, the client should be able to access it.
- Status changed from New to Assigned
- Assignee set to Daniel Lobato Garcia
- Translation missing: en.field_release deleted (
2)
- Status changed from Assigned to Ready For Testing
- Related to Bug #4190: Fix error handling to match the updated api format added
- Target version changed from 1.9.2 to 1.9.1
- Status changed from Ready For Testing to Closed
- Translation missing: en.field_release set to 2
Seems I put the wrong redmine number in the commit message (incorrectly #3960).
This was fixed in 0f7d219a4a65cd795eecd05117b08511d9025de2.
- % Done changed from 0 to 100
- Related to Bug #4315: Hosts power management API doesn't return standard error responses added
Also available in: Atom
PDF
Updated by 
Updated by Anonymous 
Updated by