Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I hope to defend against CSRF by customizing the request header #302

Closed
zy010101 opened this issue Jun 20, 2023 · 2 comments
Closed

I hope to defend against CSRF by customizing the request header #302

zy010101 opened this issue Jun 20, 2023 · 2 comments

Comments

@zy010101
Copy link

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.

@zy010101
Copy link
Author

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.

@chrislearn
Copy link
Member

Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants