- From: Willy Tarreau <w@1wt.eu>
- Date: Thu, 23 Sep 2021 17:30:22 +0200
- To: HTTP Working Group <ietf-http-wg@w3.org>, IETF QUIC WG <quic@ietf.org>
Hi all, I'm really glad to say that my coworkers Fred and Amaury are seeing their long tireless work on H3+QUIC start to pay off. Today I was pleased to see an H3 request from curl pass through HAProxy, being forwarded to Apache in H2, and the H2 response being routed and translated back to H3 so that curl could print it. They would have preferred that I remain discrete about it given the extremely fragile state of the current code, but I'm really glad as the project's maintainer and I'm also glad from an interoperability perspective, because the more implementations we see, the faster we'll spot and fix bugs, so I was not going to keep that for me :-) Of course our implementation still has many limitations and bugs, but I know by experience that once requests and responses start to flow back and forth, the development tremendously speeds up. I clearly don't expect anything great for the 2.5 release due in 1.5 month but if it can at least help us progress faster and help others test their code against yet another server implementation, that will be great already (for now the client code is disabled, there's enough work to do with the server one :-)). I've posted a screenshot of curl's and haproxy's debug outputs side-by-side here for those interested: https://twitter.com/WillyTarreau/status/1441051288997924870 Obviously there's still a long way to go before it can be considered production ready, but we're seeing some faint light at the end of this long tunnel, it's pleasant :-) Willy
Received on Thursday, 23 September 2021 15:30:42 UTC