I’m on macOS 26.1. I repro the bug in Chrome 142.0, but not in Safari 26.1.
In Chrome Dev Tools, here’s what I see, with a few sensitive bits (code and state parameters) replaced with REDACTED below:
- POST to https://id.discourse.com/auth/facebook
- GET to https://www.facebook.com/v5.0/dialog/oauth?client_id=1002152602034172&redirect_uri=https%3A%2F%2Fid.discourse.com%2Fauth%2Ffacebook%2Fcallback&response_type=code&scope=email&state=REDACTED
- GET to https://www.facebook.com/dialog/consent/complete/?app_id=1002152602034172&close_uri=https%3A%2F%2Fid.discourse.com%2Fauth%2Ffacebook%2Fcallback%3Fcode%3DREDACTED%26state%3DREDACTED%23_%3D_&display=page&is_success_response=1&cache_buster=9053456441950167740&ext=1762813150&hash=AeRPfKHNpn86aMAA2Rk
- GET to https://id.discourse.com/auth/facebook/callback?code=REDACTED&state=REDACTED#_=_
- 302 redirect to https://id.discourse.com/oauth/authorize?client_id=w6frjy8zGCTX8HN5UoI20Jj0mMq3Z2cwPu-OJVExLbQ&redirect_uri=https%3A%2F%2Fmeta.discourse.org%2Fauth%2Fdiscourse_id%2Fcallback&response_type=code&scope=read&state=REDACTED
- ^^ note that this is where “meta” creeps in, from id.discourse.com response headers
- GET to https://id.discourse.com/oauth/authorize?client_id=w6frjy8zGCTX8HN5UoI20Jj0mMq3Z2cwPu-OJVExLbQ&redirect_uri=https%3A%2F%2Fmeta.discourse.org%2Fauth%2Fdiscourse_id%2Fcallback&response_type=code&scope=read&state=REDACTED
- GET to https://meta.discourse.org/auth/discourse_id/callback?code=REDACTED&state=REDACTED
- 302 redirect to
/auth/failure?message=csrf_detected&strategy=discourse_id
- 302 redirect to
And then I end up at https://meta.discourse.org/auth/failure?message=csrf_detected&strategy=discourse_id 200 OK ![]()