You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue that I'm running into is that both locally and when deployed, the spotipy requests are resulting in a redirect loop, where the location set by the redirect response is exactly the same every time. I've modified the requests session handler a little bit to print out the history that it collects when following redirects, and I get 30 items that look identical to this:
Is this bouncing happening on the Spotify end? Possibly due to some user agent or origin IP? Or Do I need to set an auth parameter to make the call from a GAE server?
When I run curl on the same URL from my local command line, I get a valid response:
Hi Paul,
I'm not sure if this is a GAE problem, a
requests
problem, or something on Spotify's end, but I'm opening this here to make sure it's not the latter.I have some python code that looks similar to the following:
The issue that I'm running into is that both locally and when deployed, the
spotipy
requests are resulting in a redirect loop, where thelocation
set by the redirect response is exactly the same every time. I've modified therequests
session handler a little bit to print out thehistory
that it collects when following redirects, and I get 30 items that look identical to this:Is this bouncing happening on the Spotify end? Possibly due to some user agent or origin IP? Or Do I need to set an auth parameter to make the call from a GAE server?
When I run
curl
on the same URL from my local command line, I get a valid response:Thanks!
The text was updated successfully, but these errors were encountered: