Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Comsumer API get_metadata with invalid id not return 409 but 500 error
I am trying to implement the error handler of the response error body, but here is a bug existed:
I use get_metadata and give an invalid id as path, I got 500 in response but not 409 path not found.
If I use path based API, the response status is 409 as listed in document.
Furthermore, I try to use an invalid id just one char differed from correct one, I could got the other id's metadata.
POST data: {'path': u'id:FAIC-329TaAAAAAAAAOsXu'}
<Response [200]>: {".tag": "file", "name": "1m.1221.up", "path_lower": "/1m.1221.up", "id": "id:FAIC-329TaAAAAAAAAOsXg", "client_modified": "2015-12-21T09:10:21Z", "server_modified": "2015-12-21T09:10:21Z", "rev": "7c5503334341f", "size": 1048576}
I think there are two issues:
1) id as parameter will not response correctly if id is invalide
2) use id to get metadata will get other item's metadata
Please help to check these. Thanks.
5 Replies
Replies have been turned off for this discussion
- Greg-DB
Dropbox Community Moderator
Thanks for the report! We're looking into these issues.
hi, is there any updated about this issue?
- Greg-DB
No update on the 500 error issue. I'll follow up here when this is resolved.
The other issue, with the slightly changed file ID, behaves this way because of how these IDs are encoded. That is, a small portion of the ID (at the end) is irrelevant, so changing it doesn't affect the operation.
- Greg-DB
The 500 for invalid IDs should be fixed now.
It's great, I'll try to test it.
thanks!
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
