Triage from upstream issues and PRs

[pi0]

Upstream has so many open PRs and Issues potentially some are valid bugs. Need to investigate and make a quick list of them:

• https://github.com/http-party/node-http-proxy/pulls

---

• Fixed type error when req.socket is undefined http-party/node-http-proxy#1634
• crash when 'options.target' is an object instead a string http-party/node-http-proxy#1600
• fix request abort for node 16+ http-party/node-http-proxy#1580
• Fix 'aborted' detection on Node v15.5.0+ http-party/node-http-proxy#1559
• header could be empty string http-party/node-http-proxy#1551
• Fix handling of client disconnect so that econnreset event is emitted instead of error http-party/node-http-proxy#1542
• X-Forwarded-* should be capitalized http-party/node-http-proxy#1532
• fix(outgoing-opts): preference for values in ssl http-party/node-http-proxy#1504
• do not pipe req into proxyReq until socket is connected http-party/node-http-proxy#1495
• feat: when get a chunked response, flush headers http-party/node-http-proxy#1494
• replace all http:/ with http:// bug fix http-party/node-http-proxy#1487
• Fix socket read error when websocket upgrade failed http-party/node-http-proxy#1439
• fix: check if socket is destroyed before writing to it http-party/node-http-proxy#1433
• adjust web-icoming handling of https protocol checks http-party/node-http-proxy#1419
• WIP: Convert to WHATWG URL http-party/node-http-proxy#1411
• Update removeChunked to include 204/304 http-party/node-http-proxy#1396
• FIX: Don't break on invalid headers http-party/node-http-proxy#1395
• Add x-forwarded-host header to websocket connections http-party/node-http-proxy#1379
• Fix option.target can't contains question mark http-party/node-http-proxy#1334
• Adds support for protocol relative URLs in location header http-party/node-http-proxy#1298
• Simplify outgoing path computation when there is no merging of paths http-party/node-http-proxy#1164
• Add headers duplications preservation http-party/node-http-proxy#1150
• support sending servername in proxied request http-party/node-http-proxy#1134
• location header rewriting for HTTP 303 http-party/node-http-proxy#1125

[muuvmuuv]

I would like to mention on issue that would enable HTTP2 for the proxy which would be a big + for this fork and as an alternative for Angular and Vite dev-servers.

http-party/node-http-proxy#1237

[pi0]

PR is more than welcome if you like to contribute 👍 (also feel free to make a dedicated issue so we can track http2 support separately)