You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,9 +127,11 @@ Changelog
127
127
---------
128
128
### v0.3.0
129
129
* NEW: Support for using custom keys to group requests further (e.g. grouping login requests by username)
130
-
* NEW: Support for middleware from multiple instances of `BruteForce` on the same route.
130
+
* NEW: Support for middleware from multiple instances of `ExpressBrute` on the same route.
131
131
* NEW: Tracking `lifetime` now has a reasonable default derived from the other settings for that instance of `ExpressBrute`
132
132
* NEW: Keys are now hashed before saving to a store, to prevent really long key names and reduce the possibility of collisions.
133
+
* NEW: There is now a convience method that gets attached to `req` object as `req.brute.reset`. It takes a single parameter (a callback), and will reset all the counters used by `ExpressBrute` middleware that was called for the current route.
133
134
* CHANGED: Tracking `lifetime` is now specified on `ExpressBrute` instead of `MemcachedStore`. This also means lifetime is now supported by MemoryStore.
135
+
* CHANGED: The function signature for `ExpressBrute.reset` has changed. It now requires an IP and key be passed instead of a request object.
134
136
* IMPROVED: Efficiency for large values of `freeRetries`.
135
137
* BUG: Removed a small chance of incorrectly triggering brute force protection.
0 commit comments