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" conten...
As Здравко mentioned, please make sure you're encoding header values as documented here: https://www.dropbox.com/developers/reference/json-encoding
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
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?
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.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
