Sono su macOS 26.1. Riproduco il bug in Chrome 142.0, ma non in Safari 26.1.
In Chrome Dev Tools, ecco cosa vedo, con alcuni dati sensibili (parametri code e state) sostituiti da REDACTED di seguito:
- POST a https://id.discourse.com/auth/facebook
- GET a 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 a 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
- reindirizzamento 302 a https://id.discourse.com/auth/facebook/callback?code=REDACTED&state=REDACTED#_=*
- GET a https://id.discourse.com/auth/facebook/callback?code=REDACTED&state=REDACTED#_=*
- reindirizzamento 302 a 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
- ^^ notare che è qui che “meta” entra in gioco, dalle intestazioni di risposta di id.discourse.com
- GET a 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
- reindirizzamento 302 a https://meta.discourse.org/auth/discourse_id/callback?code=REDACTED&state=REDACTED
- GET a https://meta.discourse.org/auth/discourse_id/callback?code=REDACTED&state=REDACTED
- reindirizzamento 302 a
/auth/failure?message=csrf_detected&strategy=discourse_id
- reindirizzamento 302 a
E poi finisco su https://meta.discourse.org/auth/failure?message=csrf_detected&strategy=discourse_id 200 OK ![]()