Steven Chim

You might want try out [http-proxy-middleware](https://www.npmjs.com/package/http-proxy-middleware). The following code should do the trick; when `proxy` is used as middleware. ``` var proxy = require('http-proxy-middleware')('/sock', {target: 'http://localhost:8000', headers: {'ABC_HEADER': 'abc'}, ws:...

This can be achieved easily with `http-proxy-middleware`: Example: ``` javascript var gulp = require('gulp'); var webserver = require('gulp-webserver'); var proxy = require('http-proxy-middleware'); gulp.task('webserver', function() { gulp.src('app') .pipe(webserver({ livereload: true, directoryListing:...

Opinions aside; What are the issues you are facing with the current implementation? Curious wether the http-spec describes how to deal with mismatching domain cookies (drop them or throw error)

Thanks for looking up the client behaviour in the http-spec. With this change it would mean a potential breaking change, since cookies would be dropped by the client. I can...

Could you provide a minimal reproduction of the issue?

> Could you provide a **minimal** reproduction of the issue? I'm not really a Next.js user. Had a quick look and do see the POST is "hanging". Are you able...

With a simple express proxy server I'm able to proxy to your target server. ```js const express = require('express'); const { createProxyMiddleware } = require('http-proxy-middleware'); const app = express(); app.use(createProxyMiddleware({...

Can you share minimal working code with node-http-proxy? Issue can be investigated, you can recreated it with a `curl` command firing requests to the server. (without react)

Could you share which version of http-proxy-middleware you used/tried?

Do you have a minimal reproducible repo with the problem? Tried this setup and I'm able to proxy without log messages you were talking about: ```mjs // main.mjs import {...