<?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: How to parse /upload endpoint's response when using pipes in node in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269696#M15913</link>
    <description>&lt;P&gt;Thanks for the answer, if nothing helps I will resort to SO&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 23 Mar 2018 06:46:19 GMT</pubDate>
    <dc:creator>danthedev</dc:creator>
    <dc:date>2018-03-23T06:46:19Z</dc:date>
    <item>
      <title>How to parse /upload endpoint's response when using pipes in node</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269394#M15892</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am piping users request to /upload api endpoint. The file is saved properly, however I can't seem to handle server's response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As you can see from the picture below, my (probably naive) approach ends up in unreadable sequence of characters. Am I missing something here?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image.png" style="width: 522px;"&gt;&lt;img src="https://www.dropboxforum.com/t5/image/serverpage/image-id/2661iC2508A8F41981913/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:14:33 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269394#M15892</guid>
      <dc:creator>danthedev</dc:creator>
      <dc:date>2019-05-29T09:14:33Z</dc:date>
    </item>
    <item>
      <title>Re: How to parse /upload endpoint's response when using pipes in node</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269449#M15897</link>
      <description>We can't offer much help with Node itself or using pipes in Node in particular, but for reference, the Dropbox API /2/files/upload endpoint returns the uploaded file metadata as JSON in the HTTPS response body. Exactly what you do with that and how you handle it is up to you, so you may be better helped by asking for general Node help for handling data like this in a Node forum or on StackOverflow.</description>
      <pubDate>Wed, 21 Mar 2018 16:26:13 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269449#M15897</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2018-03-21T16:26:13Z</dc:date>
    </item>
    <item>
      <title>Re: How to parse /upload endpoint's response when using pipes in node</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269693#M15911</link>
      <description>&lt;P&gt;maybe the reply from DropBox is gzip or deflate compressed? look for the "Content-Encoding" header&amp;nbsp;in the REQUEST youre making.&amp;nbsp; Though not really sure what is up with node pipes&amp;nbsp;maybe its so low level you have to do your own http parsing or something.&amp;nbsp; But in general read the request and response headers to help figure out whats going on.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if thats right then just stop the "Accept-Encoding" header from sending to dropbox when you make the request.&amp;nbsp; You must be sending that already to get a compressed response. Avoiding sending thatll make the reply normal and not globelgook.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Mar 2018 04:16:16 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269693#M15911</guid>
      <dc:creator>thelwang</dc:creator>
      <dc:date>2018-03-23T04:16:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to parse /upload endpoint's response when using pipes in node</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269695#M15912</link>
      <description>&lt;P&gt;Thanks! I will dig into this&lt;/P&gt;</description>
      <pubDate>Fri, 23 Mar 2018 06:45:55 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269695#M15912</guid>
      <dc:creator>danthedev</dc:creator>
      <dc:date>2018-03-23T06:45:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to parse /upload endpoint's response when using pipes in node</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269696#M15913</link>
      <description>&lt;P&gt;Thanks for the answer, if nothing helps I will resort to SO&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Mar 2018 06:46:19 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-parse-upload-endpoint-s-response-when-using-pipes-in-node/m-p/269696#M15913</guid>
      <dc:creator>danthedev</dc:creator>
      <dc:date>2018-03-23T06:46:19Z</dc:date>
    </item>
  </channel>
</rss>

