Please Deprecate Dropbox-Api-Arg header in V2

[w. 77]

Content-style endpoints accept parameters in JSON format using Dropbox-Api-Arg header.

But HTTP header is not for transferring arbitrary data. Some JSON writers(serializers)  produce character sequences which are not valid as HTTP Header values.

So Please stop sending JSON Text directly as HTTP Header values.

Some encodings are required before transferring like binary to hexstring,

base64 encoding. Or we need to create own custom JSON serializers just for this.

Then We need new Dropbox-Api-Arg2 header for this.

Thx.

[Greg-DB]

Thanks for the feedback! I'll send it along to the team.

One alternative that may help is using the "arg" query parameter as mentioned in the documentation:

"Content-style endpoints

These endpoints accept or return file content, so their arguments are instead passed as JSON in the Dropbox-Api-Arg request header, and returned JSON can be found in the Dropbox-Api-Result response header. These endpoints are available on the content.dropboxapi.com domain.

For compatibility with web browsers, content-style endpoints can also be used with HTTP GET requests. In this case, arg and authorization query parameters can be used as a replacement for those headers."

[w. 77]

>>For compatibility with web browsers, content-style endpoints can also be used with HTTP GET requests. In this case, arg and authorization query parameters can be used as a replacement for those headers."

arg parameter is only available for GET??How about POST or PUT?

[Greg-DB]

It also works for POST. (And API v2 doesn't use PUT.)