<?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 api.spotify.com CORS preflight broken in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/api-spotify-com-CORS-preflight-broken/m-p/7508125#M21744</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Browser apps calling the Spotify Web API are failing with CORS errors on authenticated requests (e.g. GET &lt;A href="https://api.spotify.com/v1/me" target="_blank" rel="noopener"&gt;https://api.spotify.com/v1/me&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;The OAuth login popup can still open/complete, but the follow-up browser fetch to api.spotify.com fails because the CORS preflight is broken.&lt;/P&gt;&lt;P&gt;Reproduction:&lt;/P&gt;&lt;P&gt;1) Broken — browser-style preflight WITH Origin&lt;BR /&gt;curl -i -X OPTIONS "&lt;A href="https://api.spotify.com/v1/me" target="_blank" rel="noopener"&gt;https://api.spotify.com/v1/me&lt;/A&gt;" \&lt;BR /&gt;-H "Origin: &lt;A href="https://example.com" target="_blank" rel="noopener"&gt;https://example.com&lt;/A&gt;" \&lt;BR /&gt;-H "Access-Control-Request-Method: GET" \&lt;BR /&gt;-H "Access-Control-Request-Headers: authorization"&lt;/P&gt;&lt;P&gt;Actual response:&lt;BR /&gt;HTTP/1.1 200 OK&lt;BR /&gt;Content-Length: 0&lt;BR /&gt;(no Access-Control-Allow-Origin / Allow-Methods / Allow-Headers)&lt;/P&gt;&lt;P&gt;This also fails the same way with:&lt;BR /&gt;- Origin: &lt;A href="https://dashboard-staging.lyricfind.com" target="_blank" rel="noopener"&gt;https://dashboard-staging.lyricfind.com&lt;/A&gt;&lt;BR /&gt;- Origin: &lt;A href="http://localhost:3000" target="_blank" rel="noopener"&gt;http://localhost:3000&lt;/A&gt;&lt;/P&gt;&lt;P&gt;So it does not appear to be app/domain specific.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;2) Control — OPTIONS WITHOUT Origin&lt;BR /&gt;curl -i -X OPTIONS "&lt;A href="https://api.spotify.com/v1/me" target="_blank" rel="noopener"&gt;https://api.spotify.com/v1/me&lt;/A&gt;" \&lt;BR /&gt;-H "Access-Control-Request-Method: GET" \&lt;BR /&gt;-H "Access-Control-Request-Headers: authorization"&lt;/P&gt;&lt;P&gt;Response:&lt;BR /&gt;HTTP/1.1 204 No Content&lt;BR /&gt;allow: GET, HEAD, OPTIONS&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;3) Control — accounts.spotify.com token OPTIONS still works&lt;BR /&gt;curl -i -X OPTIONS "&lt;A href="https://accounts.spotify.com/api/token" target="_blank" rel="noopener"&gt;https://accounts.spotify.com/api/token&lt;/A&gt;" \&lt;BR /&gt;-H "Origin: &lt;A href="https://example.com" target="_blank" rel="noopener"&gt;https://example.com&lt;/A&gt;" \&lt;BR /&gt;-H "Access-Control-Request-Method: POST" \&lt;BR /&gt;-H "Access-Control-Request-Headers: content-type"&lt;/P&gt;&lt;P&gt;Response includes:&lt;BR /&gt;access-control-allow-origin: &lt;A href="https://example.com" target="_blank" rel="noopener"&gt;https://example.com&lt;/A&gt;&lt;BR /&gt;access-control-allow-methods: OPTIONS, GET, POST, DELETE, PUT&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;4) GET responses still include CORS headers, but browsers never reach GET if preflight fails:&lt;BR /&gt;access-control-allow-origin: *&lt;/P&gt;&lt;P&gt;Impact&lt;BR /&gt;Any browser client calling api.spotify.com with Authorization (which triggers preflight) is blocked. We are seeing this across multiple independent web apps.&lt;/P&gt;&lt;P&gt;Observed: 2026-07-22 around 15:42 UTC&lt;/P&gt;&lt;P&gt;Please investigate CORS handling for OPTIONS requests to api.spotify.com when an Origin header is present.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jul 2026 15:47:35 GMT</pubDate>
    <dc:creator>thuvarT</dc:creator>
    <dc:date>2026-07-22T15:47:35Z</dc:date>
    <item>
      <title>api.spotify.com CORS preflight broken</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/api-spotify-com-CORS-preflight-broken/m-p/7508125#M21744</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Browser apps calling the Spotify Web API are failing with CORS errors on authenticated requests (e.g. GET &lt;A href="https://api.spotify.com/v1/me" target="_blank" rel="noopener"&gt;https://api.spotify.com/v1/me&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;The OAuth login popup can still open/complete, but the follow-up browser fetch to api.spotify.com fails because the CORS preflight is broken.&lt;/P&gt;&lt;P&gt;Reproduction:&lt;/P&gt;&lt;P&gt;1) Broken — browser-style preflight WITH Origin&lt;BR /&gt;curl -i -X OPTIONS "&lt;A href="https://api.spotify.com/v1/me" target="_blank" rel="noopener"&gt;https://api.spotify.com/v1/me&lt;/A&gt;" \&lt;BR /&gt;-H "Origin: &lt;A href="https://example.com" target="_blank" rel="noopener"&gt;https://example.com&lt;/A&gt;" \&lt;BR /&gt;-H "Access-Control-Request-Method: GET" \&lt;BR /&gt;-H "Access-Control-Request-Headers: authorization"&lt;/P&gt;&lt;P&gt;Actual response:&lt;BR /&gt;HTTP/1.1 200 OK&lt;BR /&gt;Content-Length: 0&lt;BR /&gt;(no Access-Control-Allow-Origin / Allow-Methods / Allow-Headers)&lt;/P&gt;&lt;P&gt;This also fails the same way with:&lt;BR /&gt;- Origin: &lt;A href="https://dashboard-staging.lyricfind.com" target="_blank" rel="noopener"&gt;https://dashboard-staging.lyricfind.com&lt;/A&gt;&lt;BR /&gt;- Origin: &lt;A href="http://localhost:3000" target="_blank" rel="noopener"&gt;http://localhost:3000&lt;/A&gt;&lt;/P&gt;&lt;P&gt;So it does not appear to be app/domain specific.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;2) Control — OPTIONS WITHOUT Origin&lt;BR /&gt;curl -i -X OPTIONS "&lt;A href="https://api.spotify.com/v1/me" target="_blank" rel="noopener"&gt;https://api.spotify.com/v1/me&lt;/A&gt;" \&lt;BR /&gt;-H "Access-Control-Request-Method: GET" \&lt;BR /&gt;-H "Access-Control-Request-Headers: authorization"&lt;/P&gt;&lt;P&gt;Response:&lt;BR /&gt;HTTP/1.1 204 No Content&lt;BR /&gt;allow: GET, HEAD, OPTIONS&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;3) Control — accounts.spotify.com token OPTIONS still works&lt;BR /&gt;curl -i -X OPTIONS "&lt;A href="https://accounts.spotify.com/api/token" target="_blank" rel="noopener"&gt;https://accounts.spotify.com/api/token&lt;/A&gt;" \&lt;BR /&gt;-H "Origin: &lt;A href="https://example.com" target="_blank" rel="noopener"&gt;https://example.com&lt;/A&gt;" \&lt;BR /&gt;-H "Access-Control-Request-Method: POST" \&lt;BR /&gt;-H "Access-Control-Request-Headers: content-type"&lt;/P&gt;&lt;P&gt;Response includes:&lt;BR /&gt;access-control-allow-origin: &lt;A href="https://example.com" target="_blank" rel="noopener"&gt;https://example.com&lt;/A&gt;&lt;BR /&gt;access-control-allow-methods: OPTIONS, GET, POST, DELETE, PUT&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;4) GET responses still include CORS headers, but browsers never reach GET if preflight fails:&lt;BR /&gt;access-control-allow-origin: *&lt;/P&gt;&lt;P&gt;Impact&lt;BR /&gt;Any browser client calling api.spotify.com with Authorization (which triggers preflight) is blocked. We are seeing this across multiple independent web apps.&lt;/P&gt;&lt;P&gt;Observed: 2026-07-22 around 15:42 UTC&lt;/P&gt;&lt;P&gt;Please investigate CORS handling for OPTIONS requests to api.spotify.com when an Origin header is present.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jul 2026 15:47:35 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/api-spotify-com-CORS-preflight-broken/m-p/7508125#M21744</guid>
      <dc:creator>thuvarT</dc:creator>
      <dc:date>2026-07-22T15:47:35Z</dc:date>
    </item>
  </channel>
</rss>

