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

Safe csrf #179

Merged
merged 2 commits into from
Jul 19, 2024
Merged

Safe csrf #179

merged 2 commits into from
Jul 19, 2024

Conversation

jgonggrijp
Copy link
Contributor

Closes #134.

Advantages:

  • use well-tested, off-the-shelf code
  • less code to maintain
  • one potential bug less
  • less reliance on exotic Lodash functions. This will make an eventual switch to Underscore easier.

This branch has its first commit in common with #178. It should be rebased on develop before merging, but after #178 is merged.

Advantages:

- use well-tested, off-the-shelf code
- less code to maintain
- one potential bug less
- less reliance on exotic Lodash functions. This will make an eventual
  switch to Underscore easier.
@jgonggrijp jgonggrijp requested a review from tijmenbaarda July 11, 2024 16:49
@tijmenbaarda tijmenbaarda merged commit b385423 into develop Jul 19, 2024
@tijmenbaarda tijmenbaarda deleted the feature/safe-csrf branch July 19, 2024 15:46
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

Successfully merging this pull request may close these issues.

Prevent CSRF token leakage
2 participants