Colin Bendell

yes. HEAD requests don't have a body, but it appears the use of stream.pipe() in the StreamResponse() constructor. However, when the h2stream is completed, the stream pipe is closed. However,...

I have a PR for this here: https://github.com/grantila/fetch-h2/pull/72

it appears that originSet always reports the current origin (servername from the TLS socket). I suspect that it was originally planned to reflect the Origin frame if the spec were...

+1 for @triblondon's use case. Like him, we are using fetch-h2 in one part as a triage tool to detect misbehaving servers. Escape valves like this are useful for the...

I think Image/Video parsing time and JS parsing time have different use cases and should probably be split to two different specs. 1. With media timings (image/video/font) you want to...

We should also consider also `finalResponseBodyStart` time to distinguish header-end and the data payload start

I agree with @tunetheweb's proposal. This focuses `responseStart` and `responseEnd` to target the whole response of the "final" response code and also preserves legacy interpretations. The added metrics optionally increase...

The HTTP spec calls these "Informational" responses (1xx). Should we converge on this language?

> I disagree with calling things informational responses. RFC 9110 doeant use that term, instead it defines interim responses, which use informational status codes. Terminology needs to be precise and...

There are a few use cases behind the above discussion: 1. responseStart is previously understood by the industry as 'time-to-first-byte'. Many libraries and rum products in the industry operate with...