rPDmYQ

> xhttp中的单个client不会有其他目标 You are right that each `raceTransport` only connects to one endpoint and there can only have one inflight race per transport. > 这个等待压根不会生效 The race wait does happen...

Multiple clients will create multiple connections. Since they don't share connection, we should let them start race together - otherwise we would waste 1-RTT for all but one connections just...

Fixed a bug that request being raced would fail, due to failed roundtrip attempts closing the request body. I also observed some special Firewall behavior against HTTP3: the QUIC handshake...

My main motivation to implement this is not to select the better connection, but to mimic the normal client behavior when connecting to an H3 enabled site. - "Serving H3...

The current logic really prefers QUIC such that I don't expect H2 to be even attempted, let along selected, for a network that allows QUIC to properly function. (H2 will...

> 如果我要写这个的话分别挂个 http trace 即可 There are some subtleties that cannot be implemented with httptrace context: - "Detect QUIC blackhole after handshake complete" need some hooks on quic connection level...

> 所以应该会等到我们有 Chrome 指纹的 QUIC 后再考虑这个 In the mean time should we warn or even reject configurations that contains both h2 and h3 in ALPN? They currently do not work...