<?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 Re: Issue with Redirect URL when using react app + node on Heroku in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Issue-with-Redirect-URL-when-using-react-app-node-on-Heroku/m-p/5179590#M2268</link>
    <description>&lt;P&gt;I have only used heroku a few years ago, but doesn't heroku put a reverse proxy(HTTP routing) in front of your node process? So you can access it either on HTTP 80 or HTTPS 443 and don't have to care about the app port?&lt;BR /&gt;&lt;A href="https://devcenter.heroku.com/articles/http-routing" target="_blank"&gt;https://devcenter.heroku.com/articles/http-routing&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Apr 2021 09:10:20 GMT</pubDate>
    <dc:creator>tobikabla</dc:creator>
    <dc:date>2021-04-01T09:10:20Z</dc:date>
    <item>
      <title>Issue with Redirect URL when using react app + node on Heroku</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Issue-with-Redirect-URL-when-using-react-app-node-on-Heroku/m-p/5018663#M939</link>
      <description>&lt;P&gt;I'm developing an app using the Spotify API with a React from end running on localhost:3000 and a node back end running on localhost:8888. &amp;nbsp;The back end takes care of the authentication, where my redirect url is localhost:8888/callback. &amp;nbsp;This is fine in development because I will always know what port the backend is on, but when I deploy to Heroku, the back end port is chosen dynamically, so I can't enter a specific redirect url on my spotify dev page. &amp;nbsp;How could I make it that this callback url is known before hand? &amp;nbsp;My first thought was to make the the callback to my front end (the actual herokuapp link) and then redirect to the dynamically chosen port. &amp;nbsp;Is there a better way?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Aug 2020 15:43:58 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Issue-with-Redirect-URL-when-using-react-app-node-on-Heroku/m-p/5018663#M939</guid>
      <dc:creator>tannerwr64</dc:creator>
      <dc:date>2020-08-17T15:43:58Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with Redirect URL when using react app + node on Heroku</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Issue-with-Redirect-URL-when-using-react-app-node-on-Heroku/m-p/5179388#M2266</link>
      <description>Did you manage to resolve this issue? I am currently in the process of deploying my app on Heroku too and having similar issues.</description>
      <pubDate>Thu, 01 Apr 2021 00:33:23 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Issue-with-Redirect-URL-when-using-react-app-node-on-Heroku/m-p/5179388#M2266</guid>
      <dc:creator>Dxphii</dc:creator>
      <dc:date>2021-04-01T00:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with Redirect URL when using react app + node on Heroku</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Issue-with-Redirect-URL-when-using-react-app-node-on-Heroku/m-p/5179590#M2268</link>
      <description>&lt;P&gt;I have only used heroku a few years ago, but doesn't heroku put a reverse proxy(HTTP routing) in front of your node process? So you can access it either on HTTP 80 or HTTPS 443 and don't have to care about the app port?&lt;BR /&gt;&lt;A href="https://devcenter.heroku.com/articles/http-routing" target="_blank"&gt;https://devcenter.heroku.com/articles/http-routing&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 09:10:20 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Issue-with-Redirect-URL-when-using-react-app-node-on-Heroku/m-p/5179590#M2268</guid>
      <dc:creator>tobikabla</dc:creator>
      <dc:date>2021-04-01T09:10:20Z</dc:date>
    </item>
  </channel>
</rss>

