https://community.spotify.com/t5/Spotify-for-Developers/Invalid-redirect-url-validation/m-p/6972832#M17926 <P>The same thing happens to me, I even checked the <A href="https://www.rfc-editor.org/rfc/rfc8252.html#section-7.3" target="_blank" rel="noopener">IETF recommendations</A> definition and it has an example of a longer path.</P><PRE><A href="http://127.0.0.1:51004/oauth2redirect/example-provider" target="_blank" rel="noopener">http://127.0.0.1:51004/oauth2redirect/example-provider</A></PRE><P>&nbsp;<span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MrGenis_0-1747865596003.png" style="width: 400px;"><img src="https://community.spotify.com/t5/image/serverpage/image-id/195720i84B6DCB43020973E/image-size/medium?v=v2&amp;px=400" role="button" title="MrGenis_0-1747865596003.png" alt="MrGenis_0-1747865596003.png" /></span></P><P>&nbsp;</P> Wed, 21 May 2025 22:15:33 GMT MrGenis 2025-05-21T22:15:33Z https://community.spotify.com/t5/Spotify-for-Developers/Invalid-redirect-url-validation/m-p/6947680#M17775 <P>The redirect url validation when creating a new app on spotify developer portal does not work correctly for loopback addresses. In particular, it breaks if the rest of the url has a `-` in it.</P><P>&nbsp;</P><P>For instance, it does not accept <SPAN class=""><A href="http://127.0.0.1:8100/settings/music-services/spotify/callback" target="_blank" rel="noopener">http://127.0.0.1:8100/settings/music-services/spotify/callback&nbsp;</A></SPAN>but this works</P><P><SPAN class=""><A href="http://127.0.0.1:8100/settings/musicservices/spotify/callback" target="_blank" rel="noopener">http://127.0.0.1:8100/settings/musicservices/spotify/callback</A></SPAN>. Please fix this issue as soon as possible.</P> Mon, 05 May 2025 07:55:53 GMT https://community.spotify.com/t5/Spotify-for-Developers/Invalid-redirect-url-validation/m-p/6947680#M17775 _lucifer_ 2025-05-05T07:55:53Z https://community.spotify.com/t5/Spotify-for-Developers/Invalid-redirect-url-validation/m-p/6972832#M17926 <P>The same thing happens to me, I even checked the <A href="https://www.rfc-editor.org/rfc/rfc8252.html#section-7.3" target="_blank" rel="noopener">IETF recommendations</A> definition and it has an example of a longer path.</P><PRE><A href="http://127.0.0.1:51004/oauth2redirect/example-provider" target="_blank" rel="noopener">http://127.0.0.1:51004/oauth2redirect/example-provider</A></PRE><P>&nbsp;<span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MrGenis_0-1747865596003.png" style="width: 400px;"><img src="https://community.spotify.com/t5/image/serverpage/image-id/195720i84B6DCB43020973E/image-size/medium?v=v2&amp;px=400" role="button" title="MrGenis_0-1747865596003.png" alt="MrGenis_0-1747865596003.png" /></span></P><P>&nbsp;</P> Wed, 21 May 2025 22:15:33 GMT https://community.spotify.com/t5/Spotify-for-Developers/Invalid-redirect-url-validation/m-p/6972832#M17926 MrGenis 2025-05-21T22:15:33Z