Skip to content

Commit fd3f5f1

Browse files
committed
Updated change log.
1 parent ee73df0 commit fd3f5f1

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,9 +127,11 @@ Changelog
127127
---------
128128
### v0.3.0
129129
* 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.
131131
* NEW: Tracking `lifetime` now has a reasonable default derived from the other settings for that instance of `ExpressBrute`
132132
* 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.
133134
* 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.
134136
* IMPROVED: Efficiency for large values of `freeRetries`.
135137
* BUG: Removed a small chance of incorrectly triggering brute force protection.

0 commit comments

Comments
 (0)