In which I survey CSRF countermeasures and existing Go libraries and propose we add CrossOriginForgeryHandler to net/http to solve this once and for all.

Turns out there is no need for tokens or keys in 2025! Browsers just send a This-Is-CSRF header now. (Sort of.)

github.com/golang/go/issues/73

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://abyssdomain.expert/users/filippo/statuses/114467524856484763 on your instance and quote it. (Note that quoting is not supported in Mastodon.)