http-proxy-middleware icon indicating copy to clipboard operation
http-proxy-middleware copied to clipboard

:zap: The one-liner node.js http-proxy middleware for connect, express, next.js and more

Results 138 http-proxy-middleware issues
Sort by recently updated
recently updated
newest added
trafficstars

### Expected behavior Flexibility to override the HTTP methods as the API may not support the user requested methods. ### Actual behavior Not able to override HTTP methods. ### Setup...

### Expected behavior Needed to relay request header to the proxy target, Already tried to relay using function relayRequestHeaders(proxyReq, req) { Object.keys(req.headers).forEach(function (key) { proxyReq.setHeader(key, req.headers[key]); }); } function relayResponseHeaders(proxyRes,...

With the last code commit made Dec 6, 2016, and 49 PR in the queue, I'm ready to declare [nodejitsu/node-http-proxy](https://github.com/nodejitsu/node-http-proxy) dead. Would you consider using [nxtedition/node-http2-proxy](https://github.com/nxtedition/node-http2-proxy) instead?

### Expected behavior Proxying to the locally running WebSocketServer on a different port succeeds. ### Actual behavior Proxying to the locally running WebSocketServer on a different port fails with an...

### Actual behavior If we declare two proxies where we enable WebSocket upgrade, see `ProxyMiddlwareLocal` and `proxyMiddlewareStun0` the Websocket request for the second proxies is redirected two the first. On...

Not an issue, not a question. Just wanted to send some 💌 for this middleware. It's an excellent extension to some of the flaws when implementing node-http-proxy. Feel free to...

### Expected behavior Able to proxy websockets with webpack 2. ### Actual behavior Not able to proxy websockets with webpack 2. ### Setup webpack-dev-server v2.2.1 was just pushed to stable....

I've got my proxy working, but there are some URLs that I know the backend will return 403 unauthorized for depending on the API path and the properties of the...

For special case with req.url 'http://host/user/vm/counter' and ``` router = '/vm/': 'http://192.168.1.1:8000' '/user/': 'http://192.179.1.1:8001' ``` Router would forward the request to 1st matched handler instead of the expected 2nd handler....

The documentation around the path rewrite config object is a bit confusing. One could infer that the object matches as many times it can against the path when in reality...