You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
/files/download API fails
Hi,
I'm using Dropbox API and found /files/download API fails since few days before.
The API return following response body,
<!DOCTYPE html>
<html>
<head><meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Dropbox - 400</title>
<link href="https://cfl.dropboxstatic.com/static/metaserver/static/css/error.css" rel="stylesheet" type="text/css"/>
<link rel="shortcut icon" href="https://cfl.dropboxstatic.com/static/images/favicon.ico"/>
</head>
<body>
<div class="figure">
<img src="https://assets.dropbox.com/www/en-us/illustrations/spot/target-miss.svg" alt="Error: 400"/>
</div>
<div id="errorbox">
<h1>Error (400)</h1>Something went wrong. Don't worry, your files are still safe and the Dropbox team has been notified. Check out our <a href="https://status.dropbox.com">Status Page</a> to see if there is a known incident, our <a href="https://www.dropbox.com/help">Help Center</a> and <a href="https://forums.dropbox.com">forums</a> for help, or head back to <a href="https://www.dropbox.com/home">home</a>.
</div>
some APIs are still works successfully ex.(/get_metadata, /list_folder, /get_thumbnail), but '/files/download' fail.
Is there any information about this issue?
Thanks in advance simotin13
As Здравко mentioned, please make sure you're encoding header values as documented here: https://www.dropbox.com/developers/reference/json-encoding
- Greg-DB
Dropbox Staff
As Здравко mentioned, please make sure you're encoding header values as documented here: https://www.dropbox.com/developers/reference/json-encoding
- Greg-DB
Thanks for confirming simotin13!
I'm correctly encoded.
I forgot to say that the API is used in an application in prod. I didnt modify the code since months.Thanks greg
- Greg-DB
Nico-Uretek If you're still seeing an issue when applying the encoding as documented, please share the specific steps, code, and parameter value(s) needed to reproduce the issue you're seeing so we can look into it. Be sure to redact any access/refresh tokens though. Thanks!
I'm still checking this issue and found that /files/download fails when path include multibyte string, but only ASCII it works.So it's a kind of character encoding problem I think.
curl -X POST https://content.dropboxapi.com/2/files/download --header "Authorization: Bearer access_token " --header "Dropbox-API-Arg: {\"path\":\"/aaa/bbb/sample.jpg\"}"
→ This request works
curl -X POST https://content.dropboxapi.com/2/files/download --header "Authorization: Bearer access_token " --header "Dropbox-API-Arg: {\"path\":\"/aaa/あいうえお/sample.jpg\"}"
→ This request doesn't work. I'm using API from japan so my args path include some japanese(UTF-8) string.
I would appreciate it if the Dropbox team could look into this issue.
Thanks
simotin13 wrote:... --header "Dropbox-API-Arg: {\"path\":\"/aaa/あいうえお/sample.jpg\"}"
→ This request doesn't work. ...
Hi simotin13,
This for sure wouldn't work. Dropbox doesn't support modern JSON encoding (RFC-8259) with UTF-8 inside! Dropbox supports the old JSON tagging style encoding only - take a look here. Just use some encoding tool instead of encode JSON by hand - jq on the command line for instance.
Hope this gives direction.
Thanks for your help ! That's right, Dropbox block now every special character and accents in the path name (not in accordance with the documentation haha).
I hope this will solve soon !
Thanks simotin13
Nico-Uretek wrote:..., Dropbox block now every special character and ... (not in accordance with the documentation haha). ...
Nico-Uretek, It depends on what you mean here. It's according Dropbox documentation, but NOT according standards. For instance, Dropbox (note the usage of Dropbox, not Dropbox API nor SDK) doesn't support all UNICODE symbols, but only those in Basic Multilingual Plane. 🤷 This is Dropbox core bug! Of course, the same results in impossible usage of surrogate pairs during JSON encoding - they are invalid according Dropbox API.
Do you use such symbols as file/folder names?
Hi ! Same error since yesterday but on insert file....
Some news from DB ? An issue ?
Thanks !
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
