QUIC Reverse Proxy (and devsisters' libquic)

[Igor Gatis]

I'd like to try out QUIC using a reverse proxy. The idea is that my experimental client will talk QUIC to this proxy and it will talk to a test server using regular HTTPS.

I found https://devsisters.github.io/goquic/#quic-proxy-server-docker-image. I'm about to implement my clients both in C++ (using https://github.com/devsisters/libquic) and in Go (using https://github.com/devsisters/goquic). 

Does anyone recommend this reverse proxy and its client libraries?

TLS is mandatory in my scenario. The link above states:

Since Google QUIC team turned down insecure QUIC, most recent Chrome Canary (>= 46.0) may not be able to connect to our quic proxy container. We have a plan to release a https supporting reverse-proxy image soon.

AFAIU, that restriction only applies to Chrome. libquic (and thus goquic) are not affected. Is that correct?

[Joonsung Lee]

Hello, I am maintaining GoQuic and libquic projects.

GoQuic supports TLS connection and not supporting plain HTTP anymore. That document is outdated. Sorry for that, and I will update it soon.

GoQuic (and libquic) is based on chromium QUIC code, So any protocol changes to chromium code should be applied to GoQuic as well.

We currently supports QUIC version 25 ~ QUIC version 33 and are syncing chromium's QUIC code regularly.

FYI We are using our server implementation (GoQuic reverse proxy) on our production servers (with cronet on client side) and it's working well now. I think it is quiet stable.

GoQuic client should work well, but it is less stable than server implementation.