Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upHeaders with the same name are combined into one entry in `http2` #35658
Comments
triblondon
mentioned this issue
|
Of course I didn't read enough of the docs. Sigh.
I'd argue this is a bug anyway, because it seems Node can't allow me to distinguish between multiple response headers with the same name, and one header with comma-separated values. This behaviour is also inconsistent with the H1 implementation in Node, which does allow these headers to be identified separately. But it is behaving as documented. |
|
@triblondon It's intentional designed, looking at the rfc 7230 here:
|
|
Being unable to see the wire format is somewhat limiting, though. My use case is a network instrumentation proxy, which is returning not quite accurate representations of the headers it received. And this is available in the h1 implementation. |


Version: 14.13.1
Platform: macOS, Darwin Kernel Version 19.6.0
What steps will reproduce the bug?
Versus cURL on the same URL:
How often does it reproduce? Is there a required condition?
Consistently reproducible
What is the expected behavior?
Quoting the docs:
What do you see instead?