You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the poor user experience of synchronizer token pattern and double submit cookies, we would like to implement the Custom Request Headers approach mentioned in the linked document.
Now, CSRF token can be carried in Header, Query, and Form. It is recommended to carry it in the Header to separate it from the business logic. For security reasons, it is advisable to prohibit carrying the CSRF token in the Query.
Due to the poor user experience of synchronizer token pattern and double submit cookies, we would like to implement the Custom Request Headers approach mentioned in the linked document.
OWASP Cheat Sheet Series
The document also provides detailed explanations of the synchronizer token pattern and double submit cookies methods.
The text was updated successfully, but these errors were encountered: