Bug #2443
attempt to create with bad request returns non-dataone error on GMN
Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_mn_GMN
Target version:
Start date:
2012-03-06
Due date:
% Done:
100%
Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:
Description
Calling create() with a bad request causes GMN to return a Django error rather than the expected DataONE exception.
e.g.:
curl -k -X POST "https://gmn-dev.dataone.org/mn/v1/object"
Related issues
History
#1 Updated by Dave Vieglais almost 13 years ago
- Target version changed from Sprint-2012.09-Block.2.1 to Sprint-2012.11-Block.2.2
- Position set to 2
#2 Updated by Roger Dahl over 12 years ago
- Status changed from New to Closed
