http-proxy-middleware
4.2.2 · 15 Nov 2026MIT30.6M / weekRepositoryHomepagenpmAtom feed
Upgrading http-proxy-middleware From 0.10.0 to 0.21.0
19 releases in betweenevery note read
Reading releases, release notes and advisories…
- 3
- changes to make
- 0
- advisories fixed
- 16
- new
- 8
- fixes
Before you upgrade
Tick each one off as you go- Breaking0.20.0
- Breaking0.20.0
- Breaking0.20.0
Security
2 advisories still affect 0.21.0
- http-proxy-middleware `router` host+path substring matching allows Host-header-driven backend routing bypassmoderate · GHSA-64mm-vxmg-q3vj
- Denial of service in http-proxy-middlewarehigh · GHSA-c7qv-q95q-8v27
Upgrading to 2.0.10 clears them.
- 0.18.0
vulnerability: Update micromatch to v3.x (npm:braces:20180219)
Release by release
- Breaking
Drop node 6 (BREAKING CHANGE)
- Breaking
Update to micromatch@4 ((github.com/micromatch/micromatch/blob/master/CH…))
- Breaking
Remove legacy options
proxyHostandproxyTable(BREAKING CHANGE) - New
middleware: Promise / async support
- Fixed
ws: Concurrent websocket requests do not get upgraded
- Breaking
0.19.2nothing new or fixed in the note
- Fixed
log: Handle case when error code is missing
- Fixed
- New
http-proxy: Bump to v1.17.0
- New
- Security
vulnerability: Update micromatch to v3.x (npm:braces:20180219)
- Security
- Fixed
ntlm authentication: Fixed bug preventing proxying with ntlm authentication.
- Fixed
2 other lines we could not sort, mostly version bumps
5 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.