Hello. We use Discourse for our forum at Exercism. Thank you for your work on it.
Part of our flow is that GitHub issues get automatically closed with a request to create a forum post instead, with the body of the forum post as part of the URL. This has worked great up to one post today.
If you visit this GitHub issue and click the “this link” link, you’ll see an oauth loop that ends in “Oops. The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience”.
If you are already logged into the forum it works and (at least it does for me, I’ve had some mixed reports from our maintainers).
I suspect there is some encoding issue that is occuring on the oauth setup or redirect-path.
The body includes text that should be URL encoded such as slashes, and pound symbols.
While it does work directly, because browsers are smart and handle things like this, our redirection logic sets a destination URL via given parameters, and targets whatever parameters were originally given - without proper encoding, I suspect this is what’s breaking that particular redirect.
Using a URL link with the body encoded, I do not get this issues. The properly encoded link looks like this:
