Hello,
I released a functional version of
nosurf today. Nosurf is a HTTP "middleware" for Go that mitigates CSRF attacks. It leverages the standard http.Handler interface, so you can use it with almost any framework, router, etc.
As this is both my first Go library and the first time I'm dealing with code that does the actual protection from CSRF, some peer review would be appreciated. The library seems to be doing the job, but maybe there's an important feature it's missing? Or maybe I've missed a particular case, or left in a weird bug?
I'm looking forward to your feedback!
Regards,
Justinas