📎 Webclip
Phoenix CSRF protection in HTML forms, React forms, and APIs
The page explains how Phoenix protects non-GET requests with CSRF tokens. It shows that standard HTML forms get a hidden _csrf_token field automatically, while the router’s :protect_from_forgery plug validates that token and returns 403 Forbidden when validation fails.
It also shows how to reuse the token outside classic Phoenix forms. A React form can read the token from csrf_meta_tag() and send it in the X-CSRF-Token header, and a separate SPA can fetch the token from a controller action that writes it into a cookie. The text notes that the plug can also use :clear_session instead of raising an exception.
Reading notes#
- Phoenix injects a hidden CSRF token into standard HTML forms.
- The router should include
:protect_from_forgeryin the browser pipeline. - The CSRF token can arrive either in
_csrf_tokenparams or in thex-csrf-tokenheader. - The plug can use
:exceptionor:clear_session. - A React page can read the token from a meta tag and send it in
X-CSRF-Token. - A separate SPA can obtain the token through a controller action that stores it in a cookie.
