Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Implicit Grant Flow doesn't redirect with respect to the #hash in the redirect url

Implicit Grant Flow doesn't redirect with respect to the #hash in the redirect url

I set and use the callback url "https://local.test:5500/#/callback", which works in the sense that the url is accepted as valid. But the #/callback part is stripped off and spotify redirects to "https://local.test:5500/#access_token=..." instead. 

 

I can (and will) work around that, but its rather peculiar. It could have been   https://local.test:5500/#/callback#access_token=...

 

I tried adding an extra # at the end, but everything behind the first # gets removed. And also weird, the part after the hash is stripped but it does need to be correctly passed as the redirect url. 

 

If you are thinking that I must be doing weird stuff, then you are correct. Lets just say the hash determines whether spotify support even needs to be enabled, and I just don't want spotify specific code to run when I don't need spotify. 

 

I want the url to be something like:

callback in settings: https://local.test:5500/#callback

redirect-uri: https://local.test:5500/#callback#anything

used uri: https://local.test:5500/#callback#access_token=...#anything

 

 

 

 

 

 

 

 

Reply
0 Replies

Suggested posts