Bad response status on decribe non existent table

Bug #1298833 reported by Andrii Ostapenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MagnetoDB
Fix Released
Medium
Andrii Ostapenko

Bug Description

2014-03-28 07:57:03,092 Request: GET http://localhost:8480/v1/default_tenant/data/tables/testtempest880184980
2014-03-28 07:57:03,093 Request Headers: {'Content-Type': 'application/json', 'Accept': 'application/json'}
2014-03-28 07:57:03,096 Response Status: 400
2014-03-28 07:57:03,096 Response Headers: {'date': 'Fri, 28 Mar 2014 07:57:03 GMT', 'content-length': '137', 'content-type': 'application/x-amz-json-1.0'}
2014-03-28 07:57:03,096 Response Body: {"__type":"com.amazonaws.dynamodb.v20111205#ResourceNotFoundException","message":"The resource which is being requested does not exist."}

Expected status: 404

Changed in magnetodb:
milestone: none → 2.0.5
importance: Undecided → Medium
Changed in magnetodb:
status: New → Fix Committed
Changed in magnetodb:
assignee: nobody → Andrei V. Ostapenko (aostapenko)
Changed in magnetodb:
status: Fix Committed → Fix Released
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.