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.
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
Dropbox Staff
Dropbox StaffThere 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.
- Greg-DB
MReizinho Thanks for the report. I just double checked the issue via the code shared in the original comment on this thread, and it is currently working properly.
If something is currently not working as expected, please share the code or steps to reproduce the issue and we'll look into it.
Either way, it is important that the developer of the app update it to properly encode HTTP headers.
Dear @Greg K. ,
Thank you very much for your prompt reply. I do believe that the code above is now working. But there are so many non-ASCII characters that perhaps some just fall into the loop. That would explain why the behaviour has changed from last week to ALL folders/files to just some.
Unfortunately, I'm not a developer like @wen_hsiao and don't know how to give you the code in API "language". What I can give you is a path and filename of some of my today errors. Perhaps you can run it and see if it works on your side:
\CONCURSOS PARTICULARES\2019\19.189 - Colombo Mobiliário\02 - ORCAMENTO\PROPOSTA ENVIADA\QUANTIDADES - COLOMBO (2019-07-16).xlsx
It was converted to:
\CONCURSOS PARTICULARES\2019\19.189 - Colombo Mobiliário\02 - ORCAMENTO\PROPOSTA ENVIADA\QUANTIDADES - COLOMBO (2019-07-16).xlsx
Another example:
\CONCURSOS PARTICULARES\2019\19.203 - Colombo Escritorios\06 - PROJECTOS\2_25-09-2019 - Pojeto segurança\
It was converted to:
\CONCURSOS PARTICULARES\2019\19.203 - Colombo Escritorios\06 - PROJECTOS\2_25-09-2019 - Pojeto segurança\
Hope it's useful. Please let me know if I can help in any way.
Thank you.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
