שגיאת אסימון אותנטיות לא תקין במסלול של mailgun webhooks

סיכום מבוסס בינה מלאכותית

Users are encountering an ActionController::InvalidAuthenticityToken error when sending POST requests to the /webhooks/mailgun endpoint, resulting in HTTP 422 responses. This issue, first noticed around mid-May, occurs even on fresh installations without plugins. Wolftallemo confirmed the Mailgun API key is valid and doubts it’s the root cause, noting that invalid keys shouldn’t trigger CSRF errors. znedw reported a similar issue with AWS webhooks on build 99b0578b4ce. The issue was resolved via a pull request from Wolftallemo, which was merged by david with additional commit details available at https://github.com/discourse/discourse/commit/be556ef17b71bf30c95a4622fa1a792e04887b19.

Any post requests to /webhooks/mailgun are returned an HTTP 422, and the server logs show an ActionController::InvalidAuthenticityToken error. This was tested on a new installation with no plugins.

This first started around the middle of May looking at logs from my main forum.

Are you sure that the API key is valid?

Yeah I’ve checked the key and it’s definitely valid.

I don’t really think it has anything to do over whether they key is valid or not (unless an invalid key causes a csrf error for some reason)

https://meta.discourse.org/t/handling-bouncing-e-mails/45343/189?u=znedw

same issue here with the aws webhook, i’m on build 99b0578b4ce

Thanks for the PR @Wolftallemo - I just merged it and added some extra info in the commit message:

https://github.com/discourse/discourse/commit/be556ef17b71bf30c95a4622fa1a792e04887b19

6 לייקים

This topic was automatically closed after 6 days. New replies are no longer allowed.