Bad HTTP Content-Type header on download

---

HairyWombat wrote:

...

Dropbox.Api.BadInputException: Error in call to API function “files/download”:

Bad HTTP “Content-Type” header: “application/x-www-form-urlencoded".

Expecting one of “text-plain”, “text-plain; charset =utf-8”, “application/octet-stream”, …..

...

---

Hi HairyWombat,

On different development platforms different underlying libraries may be in use for particular tasks processing implementation (including HTTP requests handling). There is no "replacing the native Android handler with the .NET one" - which is the dot net one? This is not mandatory one thing! 🙂

Usually most of the libraries use some default content type (when nothing explicitly set) and usually this is "application/x-www-form-urlencoded". Whenever this is inappropriate it should be changed to the correct one or wiped out. More stable solution is set new content type value whenever possible (it's usually possible). I don't know why .Net SDK of Dropbox tries to wipe it out for download tasks (that one you're using) - this may work, but is not so stable. You may try to set appropriate value like "application/octet-stream" (copy from here - like in upload tasks) and recompile the SDK. I haven't used and tested this in your environment, if I was in your shoes, this is the first thing I would try though - it's likely to work.

Good luck.