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.

Sign up for GitHub

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

Jump to bottom

Get ratelimiter instance from express-brute #24

Merged
merged 2 commits into from
Apr 23, 2018
Merged

Get ratelimiter instance from express-brute #24

merged 2 commits into from
Apr 23, 2018

Conversation

knor-el-snor
Copy link
Contributor

No description provided.

@coveralls
Copy link

coveralls commented Apr 23, 2018 •
edited
Loading

Pull Request Test Coverage Report for Build 169

  • 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 97.561%
Totals Coverage Status
Change from base Build 160: 0.0%
Covered Lines: 59
Relevant Lines: 59
💛 - Coveralls

horstenwillem
horstenwillem reviewed Apr 23, 2018
View reviewed changes
README.md Outdated

Set a rate limiter to prevent brute force attacks. At the moment there is support for a built in-memorystore or Redis. Both use the `express-brute` module.
Get a rate limiter instance prevent brute force attacks. This can be used as a middleware in Express.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"to prevent"

@knor-el-snor knor-el-snor merged commit ce2dcbd into master Apr 23, 2018
@knor-el-snor knor-el-snor deleted the feature/ratelimiter branch April 23, 2018 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@horstenwillem horstenwillem horstenwillem approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@knor-el-snor @coveralls @horstenwillem