Lucas Pardue
Lucas Pardue
The problem described here is just one case of aliasing of the HTTP representation that can occur by only relying on the "name" (aka URL). HTTP [Content Negotiation](https://tools.ietf.org/html/rfc7231#section-3.4) describes some...
I'm late to the issue and have trying to read up on the context but may have missed things, so apologies if that is the case. The OP states concern...
The case where a MITM proxy is involved is a bit different from tunneling. It terminates and recreates connections by impostering. In that case the client might not even be...
The text says > if a tunnel connection is established then this must be the ALPN Protocol ID of the tunneled protocol The "tunneled protocol" should always be a version...
Fair question > One possible route is to leverage TCP Fast Open, which would allow us to send the ClientHello within the TCP SYN packet — that would cut another...
Let me take a crack...
It should probably be a WIP PR until such a time as HTTP/3 is finalized - then it can reflect whether an implementation has mainline support for the singular RFC...
Apologies for dropping the ball on this one. 2 years on, since RFC 9000 is published now and most implementations are moving to support HTTP/3 with QUIC v1, I think...
If we accept that we'll punt detailing DATAGRAMS in the base qlog specs, then any of these options would still fundamentally work. It think its a crapshoot between option 2...
For reference, my changes on the `uni-stream-types-and-usp` branch demonstrate one way of getting this to work. Realistically, we'd want to incorporate unidirectional stream types during an uplift to a newer...