How to pipe the client request preserving the headers.

[royalpinto]

Whats is the equivalent alternative for the request library operation: req.pipe(request)

According to the migration doc:

// When someone makes a request to our server, we receive a body and some headers.
// These are passed to Got. Got proxies downloaded data to our server response,
// so you don't have to do response.writeHead(statusCode, headers) and response.end(body).
// It's done automatically.

await pipeline(got.stream('https://example.com/doodle.png'), res)

I could not get this working. The headers passed by the client are not forwarded to the target. I wonder how can the library read the client headers without using the req object 🤔

Only these headers I receive on the target.

{
  "user-agent": "got (https://github.com/sindresorhus/got)",
  "accept-encoding": "gzip, deflate, br"
}

I also tried the following options:

pipeline(req, got.get(url), output) // Throws "dest.once is not a function"
req.pipe(got.get(url)).pipe(res) // Throws "dest.once is not a function"
req.pipe(got.stream(url)).pipe(res) // Throws "Hostname/IP does not match certificate's altnames..."

[royalpinto]

I got it working with some workaround. The host header passing to the target was causing the problem. I don't know if it is expected like this or not. The request library handles this automatically may be.

delete req.headers.host // Workaround
req.pipe(got.stream(url)).pipe(res)

Also, I think the migration guide needs to be updated to have the req if the client headers need to be forwarded.

[royalpinto]

Probably related to #1241
It is still present in the case of req.pipe(got.stream(url)).pipe(res), checked it on the version 11.8.2.

Any thoughts @szmarczak @MittWillson

[szmarczak]

Please open a bug report with code to reproduce the bug.

[royalpinto]

Created a bug with a test to reproduce #1746

[szmarczak]

Answered.