<?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: Byte order marks on challenge response in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Byte-order-marks-on-challenge-response/m-p/199740#M9326</link>
    <description>&lt;P&gt;The&amp;nbsp;Dropbox webhook challenge string doesn't contain a BOM, so the&amp;nbsp;Dropbox webhooks service doesn't expect one in the echoed string. That being the case, it does look like something on your side is adding it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Unfortunately, that sounds like an issue with Node or your code itself, so I'm afraid I can't offer much insight. Perhaps someone else here is familiar with it though and can help if you share your code.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Dec 2016 21:47:21 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2016-12-28T21:47:21Z</dc:date>
    <item>
      <title>Byte order marks on challenge response</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Byte-order-marks-on-challenge-response/m-p/199704#M9321</link>
      <description>&lt;P&gt;I set up a Node.js server to respond to the API challange request for a webhook. I can't seem to get it to accept the challenge. I can't tell if it's appending byte order marks, or if Node.js is secretly sending them. I masked out some of the info below, but I kept the key parts.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Notice the extra "&lt;SPAN&gt;\xef\xbb\xbf&lt;/SPAN&gt;" prepended to the challenge response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Error: Incorrect response to challenge. We didn't receive the expected response xxxxx. See the actual response body we received below.&lt;/P&gt;&lt;P&gt;Request:&lt;BR /&gt;GET &lt;A href="http://xxxx.ngrok.io/api/DropboxWebhook?challenge=xxxxx" target="_blank"&gt;http://xxxx.ngrok.io/api/DropboxWebhook?challenge=xxxxx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Response:&lt;BR /&gt;HTTP/1.1 200 OK&lt;BR /&gt;Transfer-Encoding: chunked&lt;BR /&gt;Server: Microsoft-HTTPAPI/2.0&lt;BR /&gt;Connection: keep-alive&lt;BR /&gt;Date: Wed, 28 Dec 2016 18:10:30 GMT&lt;BR /&gt;Content-Type: text/plain; charset=utf-8&lt;/P&gt;&lt;P&gt;Response Body (First 256 bytes):&lt;BR /&gt;\xef\xbb\xbfxxxxx&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:27:18 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Byte-order-marks-on-challenge-response/m-p/199704#M9321</guid>
      <dc:creator>ytechie</dc:creator>
      <dc:date>2019-05-29T09:27:18Z</dc:date>
    </item>
    <item>
      <title>Re: Byte order marks on challenge response</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Byte-order-marks-on-challenge-response/m-p/199740#M9326</link>
      <description>&lt;P&gt;The&amp;nbsp;Dropbox webhook challenge string doesn't contain a BOM, so the&amp;nbsp;Dropbox webhooks service doesn't expect one in the echoed string. That being the case, it does look like something on your side is adding it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Unfortunately, that sounds like an issue with Node or your code itself, so I'm afraid I can't offer much insight. Perhaps someone else here is familiar with it though and can help if you share your code.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2016 21:47:21 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Byte-order-marks-on-challenge-response/m-p/199740#M9326</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2016-12-28T21:47:21Z</dc:date>
    </item>
    <item>
      <title>Re: Byte order marks on challenge response</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Byte-order-marks-on-challenge-response/m-p/200232#M9366</link>
      <description>&lt;P&gt;It was an issue specific to Azure Functions. The fix was to use a content type of "application/octet-stream".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is code that I confirmed works with dropbox:&lt;/P&gt;&lt;PRE&gt;res = {
            body: challenge,
            headers: {
                'Content-Type': 'application/octet-stream'
            }
        };&lt;/PRE&gt;</description>
      <pubDate>Mon, 02 Jan 2017 18:24:07 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Byte-order-marks-on-challenge-response/m-p/200232#M9366</guid>
      <dc:creator>ytechie</dc:creator>
      <dc:date>2017-01-02T18:24:07Z</dc:date>
    </item>
  </channel>
</rss>

