numerus/web/template
jordi fita mas 917db31227 Add cross-request forgery detection
I use the ten first digits of the cookie’s hash, that i believe it is
not a problem, has the advantage of not expiring until the user logs
out, and using a per user session token is explicitly allowed by
OWASP[0].

[0]: https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html#synchronizer-token-pattern
2023-02-02 11:39:34 +01:00
..
app.gohtml Add cross-request forgery detection 2023-02-02 11:39:34 +01:00
contacts-index.gohtml Rename Customer to Contact 2023-02-01 10:14:26 +01:00
contacts-new.gohtml Add cross-request forgery detection 2023-02-02 11:39:34 +01:00
dashboard.gohtml Move page titles to their respective templates 2023-01-31 13:07:17 +01:00
form.gohtml Handle tax details and new tax forms with structs and validation 2023-02-01 14:15:02 +01:00
login.gohtml Use a “proper” struct for the login form 2023-02-01 11:02:32 +01:00
profile.gohtml Add cross-request forgery detection 2023-02-02 11:39:34 +01:00
tax-details.gohtml Add cross-request forgery detection 2023-02-02 11:39:34 +01:00
web.gohtml Add custom function to get the current locale from templates 2023-01-31 15:45:51 +01:00