News for hackers. Stuff that matters.
Re:Introducing QUIC support for HTTPS load balancing by Matthias247 on Thursday June 14, 2018 @12:32AM (#17309293)
It shouldn't be that complex. On top of both protocols are HTTP semantics. You get a request, which has some headers in both direction and then contains a bidirectional stream. You forward both in each direction.

It's not different than building a HTTP/2 (or HTTP/QUIC) to HTTP/1 gateway. On both sides are HTTP APIs.

The statefulness is on the lower level, where streams/requests are multiplexed. However that doesn't need to be conveyed or transferred during proxying.

Re:Introducing QUIC support for HTTPS load balancing by xfs on Thursday June 14, 2018 @09:54AM (#17311666)
You're basically describing attaching an h1 to h2 adapter behind the existing QUIC to h2 adapter with HTTP/1 as the intermediary protocol, which is a simplification for both sides. Of course that will not be that complex. But the downside is this approach limits both protocols from reaching their full potential by having to operate at a higher level.