node-http-proxy
node-http-proxy copied to clipboard
A full-featured http proxy for node.js
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [eventemitter3](https://redirect.github.com/primus/eventemitter3) | [`^4.0.0` -> `^5.0.0`](https://renovatebot.com/diffs/npm/eventemitter3/4.0.0/5.0.1) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/)...
This issue has come up in Vite, which delegates proxying to http-proxy. > When Proxying to a WebSocket service in local development the socket connection can rejected by the server...
When building an app using Vite, there is this deprecationw arning when using Node.js 22: ``` [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead. ``` This PR...
changeOrigin has nothing to do with `origin` header which is confusing and harmful when working with CORS. As CORS middleware sometimes makes decisions depending on `origin` header. `changeOrigin` option handles...
**System and Environment Information**: * OS: debian bookworm * Runtime: Bun 1.1.3 **Details on the Issue**: Periodically, my server will crash with the error along the lines of: ``` Malformed_HTTP_Response:...
With Nodejs 18 another set of http timeouts have been introduced: - `headersTimeout` - `requestTimeout` see: https://nodejs.org/en/blog/release/v18.0.0/#http-timeouts These timeouts cause that established websocket connections are closed after roughly 60 seconds....
We need to upgrade this version "1.15.6" . We have found a vulnerability in the "follow-redirects" package. Please consider upgrading and releasing new release notes for the package. Here I...
when reverse a websocket connection it doesn't last few minutes then disconnect, how to set the websocket timeout? in the ASP.NET when I do a reverse proxy for a websocket...
node.js version: v20.10.0 node-http-proxy version: v1.18.1 **The error** When a client sends a http request with invalid http header (for example "User Agent" without a dash in the middle), the...
… to be handled by applications (fixed ERR_INVALID_HTTP_TOKEN) I've posted the related issue here https://github.com/http-party/node-http-proxy/issues/1679 Please review the fix. Thank you!