insecureHTTPParser in fetch RequestInit options

[witia87]

Hey!
Since the two things:

1. native fetch, as well as
2. insecureHTTPParser option available on http/https.requests

have been introduced in latest versions of node.js, it would be fitting so see this flag available also on fetch options.
Our teem would gladly see this improvement implemented and also you can see how this feature was requested/implemented in node-fetch v3:
node-fetch/node-fetch#724
https://github.com/node-fetch/node-fetch/blob/7b86e946b02dfdd28f4f8fca3d73a022cbb5ca1e/src/request.js#L139

Do you think it's possible to get this feature on node.js native fetch?

[krzysztof-o]

👍 I've had the same problem. Using --insecure-http-parser is annoying as it prints error on stdout.

[bnoordhuis]

fetch() is a web standard, insecureHTTPParser is not. You can plug your own agent into fetch() though.

[witia87]

Hey, could you tell a bit more on how could I plug this agent to help with insecure HTTP headers?

[bnoordhuis]

npm add undici, then:

import {Agent} from 'undici'
const dispatcher = new Agent({/*...*/})
fetch(url, {dispatcher})

[witia87]

thank you, I'll give it a try!