Releases: azu/request-filtering-agent
Releases · azu/request-filtering-agent
v2.0.1
What's Changed
Bug Fixes
- Use lookup func instead of listener by @benasher44 in #20
New Contributors
- @benasher44 made their first contribution in #20
Full Changelog: v2.0.0...v2.0.1
v2.0.0
What's Changed
request-filtering-agent v2.0.0 support Node.js 18+ and drop support for Node.js 12, 14, 16.
Version | Node.js 12 | Node.js 14 | Node.js 16 | Node.js 18 | Node.js 20 |
---|---|---|---|---|---|
v1.x.x | Support | Support | Support | Support | Not Support |
v2.0.0 | No Support | No Support | No Support | Support | Support |
Breaking Changes
- fix: support Node.js 20 by @azu in #16
- BREAKING CHANGE: Drop Node.js 12, 14, 16 support by @azu in #17
v2.0.0 fixes following error on Node.js 20+
Uncaught Error: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
and, remove following method and option.
- Remove
applyRequestFilter(agent)
function- It is incompatible way for Node.js 20+
- So, It is just dropped
- Remove
stopPortScanningByUrlRedirection
option- We already block the redirect attack pattern
- It is duplicated option and just drop
stopPortScanningByUrlRedirection
- https://github.com/azu/request-filtering-agent/blob/a0a348ead386728aaf3e21cddbee3fb077c3d3bf/test/request-filtering-agent.test.ts#L195
Most users can simply upgrade without any problems.
CI
Full Changelog: v1.1.2...v2.0.0