We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
De L.1
11 years agoCollaborator | Level 9
BUG - Direct link to files created via /media API call return a corrupt URL!
I noticed that direct links generated via the /media API are currently returning a corrupt URL. Not all file formats seem to be affected, but I can reproduce the issue for PDF and Office files.
According to the documentation, the returned JSON should look like this:
{
"url": "https://dl.dropboxusercontent.com/1/view/abcdefghijk/example",
"expires": "Fri, 16 Sep 2011 01:01:25 +0000"
}
However, currently the following JSON is returned:
{
"url": "https://api-content.dropbox.com/1/files/auto/abcdefghijk/example.pdf?signature=1.uJpbEgcWOjAIBQ..1435610003.qbYUOzANtu_33g6uv6dJy0JcV9tjp-oF8nQCci_h2Mg",
"expires": "Fri, 16 Sep 2011 01:01:25 +0000"
}
The url however is invalid and give the following error:
{"error": "Signature did not match. STRING_TO_SIGN was u'1\\nuJpbEgcWOjAIBQ\\n\\n1435610160\\napi-content.dropbox.com\\nGET\\n/1/files/auto/abcdefghijk/example.pdf'"}
Has something changed in the API or is it a (quite severe) bug. If the /media call has changed, where can I find more information about this?
11 Replies
Replies have been turned off for this discussion
- Greg-DB11 years ago
Dropbox Community Moderator
That's certainly a reasonable request, and I've sent it along to the right people as a feature request.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!