Additionally, the proxy currently has outdated DNS for the Heroku instance, which is causing H31 Misdirected Request errors. This is something that we cannot fix; only RC staff can fix, and they have a lot of work on their plates.
Other applications have moved to using the Heroku app URL directly. We should do the same.
This would involve generating a new RC OAuth application ID & secret that uses the new URL, and updating the environment variables (RC_OAUTH_ID, RC_OAUTH_SECRET, RC_OAUTH_REDIRECT_URI). Ideally, we would also be able to figure out if users are visiting niceties.recurse.com and redirect them to the Heroku app URL, or else OAuth will probably fail.
The
*.recurse.comsubdomains are provided by the proxy tool. However, it sometimes proxies requests to the wrong domain (see https://github.com/recursecenter/proxy/issues/3).Additionally, the proxy currently has outdated DNS for the Heroku instance, which is causing H31 Misdirected Request errors. This is something that we cannot fix; only RC staff can fix, and they have a lot of work on their plates.
Other applications have moved to using the Heroku app URL directly. We should do the same.
This would involve generating a new RC OAuth application ID & secret that uses the new URL, and updating the environment variables (
RC_OAUTH_ID,RC_OAUTH_SECRET,RC_OAUTH_REDIRECT_URI). Ideally, we would also be able to figure out if users are visitingniceties.recurse.comand redirect them to the Heroku app URL, or else OAuth will probably fail.