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

Add configuration to disable forgery protection in the test environment #730

Open
matthewmcgarvey opened this issue Jan 31, 2022 · 1 comment

Comments

@matthewmcgarvey
Copy link
Member

Now that luckyframework/lucky#1657 is merged, new projects should have CSRF protection turned off while running tests. We'll need to find the best place for it to live in the config/ directory.

@bararchy
Copy link
Contributor

bararchy commented Feb 1, 2022

I would say that the authentic file might be a good candidate as it works with authentication and security?
Cookies seems like a 2nd best, but because the CSRF isn't sent via cookies and instead is used as a form param I would say authentic or application makes the most sense to me

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