<?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 [Web API] Bug: 403 Response with empty body instead of Error Object in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Web-API-Bug-403-Response-with-empty-body-instead-of-Error-Object/m-p/5095780#M1756</link>
    <description>&lt;P&gt;Observed behavior:&lt;BR /&gt;&lt;BR /&gt;As expected, a GET request to the endpoint at&amp;nbsp; &lt;A href="https://api.spotify.com/v1/me/top/artists" target="_blank" rel="noopener"&gt;https://api.spotify.com/v1/me/top/artists&lt;/A&gt;&lt;/P&gt;&lt;P&gt;receives an HTTP 403 response when the Token in use does not have the necessary Scope (i.e., lacking '&lt;SPAN&gt;user-top-read' scope)&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;However, the body of the HTTP response does&amp;nbsp;&lt;U&gt;not&lt;/U&gt; contain the expected JSON data -- an Error Object. In fact, the body of the response is empty.&lt;BR /&gt;&lt;BR /&gt;As per the documentation at&lt;BR /&gt;&lt;A href="https://developer.spotify.com/documentation/web-api/reference/personalization/get-users-top-artists-and-tracks/#response-format" target="_blank" rel="noopener"&gt;https://developer.spotify.com/documentation/web-api/reference/personalization/get-users-top-artists-and-tracks/#response-format&lt;/A&gt;&lt;BR /&gt;I expected a JSON-formatted Error Object in the body of the HTTP response.&lt;BR /&gt;&lt;BR /&gt;See Pastebin link for: CLI output from `curl -v` command demonstrating issue.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Note line 22: "&amp;lt; Content-Length: 0"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://pastebin.com/7YmvDUJu" target="_blank" rel="noopener"&gt;https://pastebin.com/7YmvDUJu&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 19 Dec 2020 09:04:24 GMT</pubDate>
    <dc:creator>NotHamlet</dc:creator>
    <dc:date>2020-12-19T09:04:24Z</dc:date>
    <item>
      <title>[Web API] Bug: 403 Response with empty body instead of Error Object</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Web-API-Bug-403-Response-with-empty-body-instead-of-Error-Object/m-p/5095780#M1756</link>
      <description>&lt;P&gt;Observed behavior:&lt;BR /&gt;&lt;BR /&gt;As expected, a GET request to the endpoint at&amp;nbsp; &lt;A href="https://api.spotify.com/v1/me/top/artists" target="_blank" rel="noopener"&gt;https://api.spotify.com/v1/me/top/artists&lt;/A&gt;&lt;/P&gt;&lt;P&gt;receives an HTTP 403 response when the Token in use does not have the necessary Scope (i.e., lacking '&lt;SPAN&gt;user-top-read' scope)&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;However, the body of the HTTP response does&amp;nbsp;&lt;U&gt;not&lt;/U&gt; contain the expected JSON data -- an Error Object. In fact, the body of the response is empty.&lt;BR /&gt;&lt;BR /&gt;As per the documentation at&lt;BR /&gt;&lt;A href="https://developer.spotify.com/documentation/web-api/reference/personalization/get-users-top-artists-and-tracks/#response-format" target="_blank" rel="noopener"&gt;https://developer.spotify.com/documentation/web-api/reference/personalization/get-users-top-artists-and-tracks/#response-format&lt;/A&gt;&lt;BR /&gt;I expected a JSON-formatted Error Object in the body of the HTTP response.&lt;BR /&gt;&lt;BR /&gt;See Pastebin link for: CLI output from `curl -v` command demonstrating issue.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Note line 22: "&amp;lt; Content-Length: 0"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://pastebin.com/7YmvDUJu" target="_blank" rel="noopener"&gt;https://pastebin.com/7YmvDUJu&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 19 Dec 2020 09:04:24 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Web-API-Bug-403-Response-with-empty-body-instead-of-Error-Object/m-p/5095780#M1756</guid>
      <dc:creator>NotHamlet</dc:creator>
      <dc:date>2020-12-19T09:04:24Z</dc:date>
    </item>
  </channel>
</rss>

