Bad response status on query with non existent table_name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MagnetoDB |
Fix Released
|
High
|
Andrii Ostapenko |
Bug Description
2014-03-30 22:39:03,263 Request: POST http://
2014-03-30 22:39:03,264 Request Headers: {'Content-Type': 'application/json', 'Accept': 'application/json'}
2014-03-30 22:39:03,264 Request Body: {"consistent_read": true, "key_conditions": {"forum": {"attribute_
2014-03-30 22:39:03,268 Response Status: 500
2014-03-30 22:39:03,269 Response Headers: {'date': 'Sun, 30 Mar 2014 19:39:03 GMT', 'content-length': '149', 'content-type': 'application/
2014-03-30 22:39:03,269 Response Body: {"__type"
On server side:
2014-03-30 22:39:03.266 2517 DEBUG routes.middleware [-] Matched POST /v1/default_
2014-03-30 22:39:03.266 2517 DEBUG routes.middleware [-] Route path: '/v1/{project_
2014-03-30 22:39:03.266 2517 DEBUG routes.middleware [-] Match dict: {'action': u'query', 'controller': <magnetodb.
Expected status: 404
Changed in magnetodb: | |
importance: | Undecided → High |
milestone: | none → 2.0.4 |
Changed in magnetodb: | |
status: | New → Fix Committed |
Changed in magnetodb: | |
assignee: | nobody → Andrei V. Ostapenko (aostapenko) |
status: | Fix Committed → Fix Released |