While updating Is it on Spotify? to use the new(ish) Spotify Web API, I ran into an issue when testing things out locally.
The good old Cross-Origin Request Blocked. I seemed to remember having the same issue when first writing the app, though it was solved by just throwing jQuery at the problem. So why was it back now?
Even stranger, the problem only occurred when running locally. Everything worked fine when the app was served from GitHub Pages, which was the opposite of what I found when I searched online: everyone else seemed to only have issues after deploying to their server, despite things working locally.
I thought it had might somehow have something to do with the way I was hosting it locally - just using Python’s
SimpleHTTPServer - though switching to
node-serve or even Jekyll’s
serve (heh) didn’t make a difference.
After some more fruitless searching, I decided on a whim to fire up Internet Explorer 11 and check out the F12 Developer Tools (which
are, funnily enough, no longer totally are bound to the actual F12 key). That gave an interesting series of messages, instead of just the one that Firefox Aurora did:
The second message -
Redirect was blocked for CORS request. - was a little puzzling. Clicking on the
SEC7127 error code lead to this page, which had a pretty big hint:
That was the light-bulb moment: when I’d updated the API endpoint URL in the code, I’d left out the protocol (just as I did when using the old Metadata API), and so the request would just end up using whatever the app had been loaded over: HTTPS when on GitHub Pages, and plain HTTP locally. It turns out that the Spotify API is served through HTTPS, though making a request to it over HTTP results in a “correction” by means of a redirect.
A redirect that ended up being blocked for security reasons by the browser.
And so everything worked fine when deployed, but not locally.
The fix was simple - just changing the URL in the code to include HTTPS at the start.