Implemented cookie protection #10
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks, I'll take a look through and fix up a couple things to make it work on 3.3. Should be using things like RequestStack instead of request, and there's a couple formatting issues. Have to add some instruction to README as well |
|
This would be great, thank you! |
(cherry picked from commit 3977118)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Spam bots do not use cookies (see http://impresswithwp.com/3-ways-fight-comment-spam-wordpress-website/, https://www.thoughtco.com/solutions-to-protect-web-forms-from-spam-3467469) so this could be used as an another protection method.
Unfortunately I have no possibility to implement this for Symfony 3.x so I've implemented this method on Symfony 2.8.