Robert Nagy

Sorry I accidentally edited your response instead of quoting it. Sorry. Tried to restore it.

> > You can disable the keep-alive header by disabling keep-alive and the other headers > > Wait. Could you show me the example? ```js setGlobalDispatcher(new Agent({ pipelining: 0 }))...

Regarding the `"sec-fetch-mode": "navigate"`... as far as I can tell the spec doesn't allow it and neither does Chrome. We could bypass the spec to make more sense in a...

Actually we were doing it slight wrong, we should set, not append the header. https://github.com/nodejs/undici/commit/5b9acf23c65fe457739c20e8f27586c1d3ec149c

One way to do what you want would be: ```js await fetch(url, { mode: 'navigate' }); ``` But again... the spec explicitly disallows it. But maybe it would make sense...

> It does not remove any default header. We need to set one of the headers. I'm not sure what you want here? https://github.com/nodejs/undici/issues/1307 PR welcome. > As I already...

> undici is not a browser. Don't overengineer it. Easier said than done. Knowing what parts of the spec to ignore or not is not that easy. To keep things...

> [ModHeader](https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj) allows to edit and remove entirely any header (except "host", "connection", "cache-control" (on a page reload), "pragma" (on "Disable cache" with DevTools)). That's kind of non-standard. I wouldn't...

> Yeah, I also would like if Node.js have some permission list in `package.json` like it is in Web Extensions, Android Applications: [My comment in the topic about the recent...

From a quick glance I'm not sure I quite understand how we would apply it here.