This looks like out of scope for TE, hence adding the respective label for it to  triage further.

If I can help, please let me know.

Blaise, could you please take a look?

This is a bigger scope than it seems. I believe we are going to be forced into re-thinking how we show resources to users, since H2 and Quik are breaking much of the old HTTP assumptions (like priority).

Even our ":" marker to show it's an H2 common header is not ideal since it's a bytecode (header compression). In the traditional sense we could just see the stream being terminated or something wrong with it and consider it failed, however with H2 it gets much more complicated. (and Quik is significantly worse, since each socket can hold multiple streams)

I am going to let this problem get a little bigger before I up the priority of it. I expect to see more pressure from netstack and loading teams and external adopters.

Thanks, I'll keep this bug around, but I probably won't start working around this area until we get more pressure.