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

Storage limit is not enforced during failed POST #47

Closed
Dravere opened this issue Feb 6, 2016 · 1 comment
Closed

Storage limit is not enforced during failed POST #47

Dravere opened this issue Feb 6, 2016 · 1 comment

Comments

@Dravere
Copy link

Dravere commented Feb 6, 2016

If a POST, PUT, DELETE, PATCH fails the storage limit is not enforced. I set the storage limit to one in the hopes that always only one valid CSRF token was available. But when the check failed it didn't enforce the limit thus making two CSRF available at the same time.

@arvindpdmn
Copy link

A somewhat related clarification since I don't understand sessions very well. Currently (v1.2.1), storage limit defaults to 200. What happens if more than 200 people are accessing the site?

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

3 participants