Avoiding CSRF with Remix
watch on portal.gitnation.org ↗https://portal.gitnation.org/contents/avoiding-csrf-with-remixsummary
Covers how Remix defends against CSRF by modeling state-changing operations as HTML forms, recommending SameSite cookie attributes and an additional token. Describes a token-based workflow: generate a unique per-session-and-form token, include it in the rendered form, return it with the submission, and validate it securely on the server.
AI-written summary · about
related talks
28mUsing Remix, the wrong ? way
41mRemix, the hottest JavaScript framework as of today
20mRemixing How We Give
26mBuilding Better Websites with Remix
52mThe Past, Present, and Future of Cross-Site/Cross-Origin Request Forgery
45mCSRF: not all defenses are created equal
36mCSRF Vulnerabilities Are Still Relevant
26mThe Ultimate Full Stack Framework for 2024: Remix