David Frank

I am not sure HTTP/2 is actually enforced in Fetch, see their headers requirement: #260, that's [explicitly not HTTP/2](https://http2.github.io/http2-spec/#rfc.section.8.1.2) AFAIK. (EDIT: also interesting to know what sort of use-cases people...

@TimothyGu a few things: - So I didn't know NodeJS come out with a native HTTP/2 support recently, that at least make this *feasible* without much userland code. https://nodejs.org/api/http2.html#http2_compatibility_api -...

I will take a PR that integrate `http2-wrapper` and see what issues might arise. My preference is to introduce it in a v3.1 release so that if it breaks something...

Yes, we are open to whatwg stream in v4, Jimmy will probably lead that effort. We are open to experimental PR on it. I am not certain fetch is the...

Thx, one thing that would be very useful for the nodejs community: **an abstraction on top of http1 and http2**, `node-fetch` can call into that API instead of `http` module....

@TimothyGu not sure your take on this but the nodejs core web stream PR didn't land; it seems the only viable solution is to use https://github.com/MattiasBuelens/web-streams-polyfill for now.

Some good news: https://github.com/nodejs/whatwg-stream

@jimmywarting don't think there is a verdict yet, stream is a different spec which I believe isn't quite finished yet, and browser support isn't quite on-par the last time I...

AFAIK what you want should be do able, see this test: https://github.com/node-fetch/node-fetch/blob/master/test/headers.js#L31-L50 I don't think set-cookie headers are handled any differently. But you should try `Cookie` instead of `Set-Cookie`, because...

I suspect we can't *fix* this issue for a few reasons: https://github.com/bitinn/node-fetch/blob/780598ad72d7205aa5616be2215692785270eda3/src/index.js#L87-L92 - Too many people rely on the behavior where `manual` flag giving the full url in `location` header....