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
The /upload behavior has been changed ?
Recently, we received many feedbacks from our product users that the filename (use /upload) has become garbled. We found the "path" decode behavior might be changed by dropbox server.
For Example:...
There was a change on our server stack that affected how we handled HTTP headers without proper encoding. That resulted in malformed file paths/names. We've reverted that change, so that should be working again, but please make sure your headers get encoded properly.
Greg-DB
Dropbox Staff
Dropbox StaffThanks for the report! We'll look into whether something changed, but note that whenever you supply non-ASCII characters in HTTP headers, such as for the /upload endpoint, you should first encode them. We have documentation on this here:
https://www.dropbox.com/developers/reference/json-encoding
For example, you can see how this is done by the API v2 Explorer: (be sure to click "Show Code")
https://dropbox.github.io/dropbox-api-v2-explorer/#files_upload
Greg-DBDropbox Staff
Dropbox StaffThis should be working again.
However, please note that sending non-ASCII characters in HTTP headers is not officially supported, so please make sure to encode them as documented.
We would follow the documentation,
but the example request I stated works well for a long time (at least a year) ,
Have you changed the behavior recently?
- Greg-DB
There was a change on our server stack that affected how we handled HTTP headers without proper encoding. That resulted in malformed file paths/names. We've reverted that change, so that should be working again, but please make sure your headers get encoded properly.
Dear Greg-DB ,
I'm one of the people that is experiencing these problems, probably one of wen_hsiao product users.
I did some exhaustive testing and I'm sorry to say that the problem still remains.
Something has changed for sure: now it doesn't happen with ALL the files/folders with non-ASCII characters like it happened last week, but it still happens in most cases. The change to your server stack that affected the processing of the HTTP headers wasn't reverted completely.
For us, end users, I can only think of two solutions:
1. Dropbox reverts correctly the changes applied last week
2. The manufacturer of the product I purchased updates its client to correctly process HTTP headers
Meanwhile my corporate network remains inoperative.
Please help us out. Thank you very much.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
