<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Please Deprecate Dropbox-Api-Arg header in V2 in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Please-Deprecate-Dropbox-Api-Arg-header-in-V2/m-p/138810#M4289</link>
    <description>&lt;P&gt;&amp;gt;&amp;gt;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."&lt;/P&gt;
&lt;P&gt;arg parameter is only available for GET??How about POST or PUT?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 11 Dec 2015 13:19:31 GMT</pubDate>
    <dc:creator>w. 77</dc:creator>
    <dc:date>2015-12-11T13:19:31Z</dc:date>
    <item>
      <title>Please Deprecate Dropbox-Api-Arg header in V2</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Please-Deprecate-Dropbox-Api-Arg-header-in-V2/m-p/138808#M4287</link>
      <description>&lt;H4&gt;Content-style endpoints accept parameters in JSON format using Dropbox-Api-Arg header.&lt;/H4&gt;
&lt;P&gt;But HTTP header is not for transferring arbitrary data. Some JSON writers(serializers)&amp;nbsp; produce character sequences which are not valid as HTTP Header values.&lt;/P&gt;
&lt;P&gt;So Please stop sending JSON Text &lt;SPAN class="st"&gt;directly as HTTP Header values.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="st"&gt;Some encodings are required before transferring like binary to hexstring,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="st"&gt;base64 encoding. Or we need to create own custom JSON serializers just for this.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Then We need new Dropbox-Api-Arg2 header for this.&lt;/P&gt;
&lt;P&gt;Thx.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:37:41 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Please-Deprecate-Dropbox-Api-Arg-header-in-V2/m-p/138808#M4287</guid>
      <dc:creator>w. 77</dc:creator>
      <dc:date>2019-05-29T09:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: Please Deprecate Dropbox-Api-Arg header in V2</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Please-Deprecate-Dropbox-Api-Arg-header-in-V2/m-p/138809#M4288</link>
      <description>&lt;P&gt;Thanks for the feedback! I'll send it along to the team.&lt;/P&gt;
&lt;P&gt;One alternative that may help is using the "arg" query parameter as mentioned in the &lt;A href="https://www.dropbox.com/developers/documentation/http/documentation" target="_blank" rel="nofollow noreferrer"&gt;documentation&lt;/A&gt;:&lt;/P&gt;
&lt;P&gt;"Content-style endpoints&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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."&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2015 02:51:08 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Please-Deprecate-Dropbox-Api-Arg-header-in-V2/m-p/138809#M4288</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2015-12-10T02:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: Please Deprecate Dropbox-Api-Arg header in V2</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Please-Deprecate-Dropbox-Api-Arg-header-in-V2/m-p/138810#M4289</link>
      <description>&lt;P&gt;&amp;gt;&amp;gt;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."&lt;/P&gt;
&lt;P&gt;arg parameter is only available for GET??How about POST or PUT?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Dec 2015 13:19:31 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Please-Deprecate-Dropbox-Api-Arg-header-in-V2/m-p/138810#M4289</guid>
      <dc:creator>w. 77</dc:creator>
      <dc:date>2015-12-11T13:19:31Z</dc:date>
    </item>
    <item>
      <title>Re: Please Deprecate Dropbox-Api-Arg header in V2</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Please-Deprecate-Dropbox-Api-Arg-header-in-V2/m-p/138811#M4290</link>
      <description>&lt;P&gt;It also works for POST. (And API v2 doesn't use PUT.)&lt;/P&gt;</description>
      <pubDate>Sat, 12 Dec 2015 01:34:39 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Please-Deprecate-Dropbox-Api-Arg-header-in-V2/m-p/138811#M4290</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2015-12-12T01:34:39Z</dc:date>
    </item>
  </channel>
</rss>

