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
..
company.go	Add cross-request forgery detection	2023-02-02 11:39:34 +01:00
contacts.go	Add cross-request forgery detection	2023-02-02 11:39:34 +01:00
db.go	Prefix with “Must” all functions that panic	2023-01-22 20:37:43 +01:00
form.go	Handle tax details and new tax forms with structs and validation	2023-02-01 14:15:02 +01:00
locale.go	Validate profile form and use templates for fields	2023-01-31 15:40:12 +01:00
logger.go	Move source file to the root of pkg	2023-01-17 10:40:22 +01:00
login.go	Add cross-request forgery detection	2023-02-02 11:39:34 +01:00
profile.go	Add cross-request forgery detection	2023-02-02 11:39:34 +01:00
recover.go	Gofmt recover.go	2023-01-22 20:37:34 +01:00
router.go	Rename extension of templates to .gohtml	2023-01-30 16:48:21 +01:00
template.go	Add cross-request forgery detection	2023-02-02 11:39:34 +01:00