http-proxy-middleware
4.2.2 · 15 Nov 2026MIT30.6M / weekRepositoryHomepagenpmAtom feed
Upgrading http-proxy-middleware From 1.0.3 to 1.3.1
10 releases in betweenevery note read
Reading releases, release notes and advisories…
Security
4 advisories still affect 1.3.1
- http-proxy-middleware can call writeBody twice because "else if" is not usedmoderate · GHSA-4www-5p9h-95mh
- http-proxy-middleware `router` host+path substring matching allows Host-header-driven backend routing bypassmoderate · GHSA-64mm-vxmg-q3vj
- http-proxy-middleware allows fixRequestBody to proceed even if bodyParser has failedmoderate · GHSA-9gqv-wp59-fq42
- Denial of service in http-proxy-middlewarehigh · GHSA-c7qv-q95q-8v27
Upgrading to 2.0.10 clears them.
Release by release
- Fixed
response interceptor: Proxy original response headers
- Fixed
- New
handler: Response interceptor
- Fixed
log error: Handle undefined target when websocket errors
- New
- Fixed
log error: Handle optional target
- Fixed
- Fixed
error handler: re-throw http-proxy missing target error
- Fixed
option: Optional
targetwhenrouteris used
- Fixed
- Fixed
errorHandler: Fix confusing error message
- Fixed
proxy: Close proxy when server closes
- Fixed
ETIMEDOUT: Return 504 on ETIMEDOUT (#480) (aremishevsky)
- Fixed
1.0.4 – 1.0.63 releases, nothing new or fixed in the notes
6 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.