Weird problem with Content-Type headers / request type about droidnetworking

[zetxek]

By the way, I could solve the issue with the request by enabling on the service admin panel the parsing of request with content type application/x-www-form-urlencoded, but anyway it could be useful knowing if there is any problem on setting custom content types...

And for adding more information about the issue, the REST service is published with a drupal services module (v 3.x, http://drupal.org/node/736522)

[netdev]

DroidNetworking currently doesn't support multipart/form-data. Even if you can set the Content-Type to multipart/form-data the request body in a POST or PUT request will be form-urlencoded. Your work around is correct if you would like to use the current version of DroidNetworking.

I'm planning to add support for multipart/form-data within the near future.

[zetxek]

Thanks for telling! In case of working on its support I'll make a pull request, let's see if I get time for it.