An independent QUIC server implementation in pure go

1,672 views
Skip to first unread message

Lucas Clemente

unread,
May 9, 2016, 6:07:06 AM5/9/16
to QUIC Prototype Protocol Discussion group, Marten Seemann
Hi all,

over the past few weeks, a friend (Marten, in CC) and I have been working on a from-scratch implementation of a QUIC server in go. We're now at the point where the basic protocol (crypto, loss detection & cubic congestion) works, and we're able to serve webpages without a problem. There's still a lot of rough edges though, and we are far from suitability for production, but making steady progress :)

You can find our code + roadmap here: https://github.com/lucas-clemente/quic-go

We also have a fork of caddy with QUIC support: https://github.com/lucas-clemente/caddy

We will be hitting the list with some technical questions soon, and look forward to your comments!

Lucas & Marten

Ryan Hamilton

unread,
May 9, 2016, 12:58:04 PM5/9/16
to proto...@chromium.org, Marten Seemann
That's fantastic! I can't wait to point Chrome at a running instance. Very exciting progress.

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.
To post to this group, send email to proto...@chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

Jana Iyengar

unread,
May 9, 2016, 1:40:42 PM5/9/16
to proto...@chromium.org, Marten Seemann
Awesome! By "serving webpages", did you use Chrome as the client? That's exciting!

Lucas Clemente

unread,
May 9, 2016, 2:02:22 PM5/9/16
to QUIC Prototype Protocol Discussion group, marten...@gmail.com

Yes, we use either the current Chrome dev, or a custom Chromium build (to test other versions) as the client. We currently support versions 31 and 32, so that may limit the Chrome versions that will work.


If you want to try it out, the instructions are in the readme :)

Hui Wang

unread,
Feb 1, 2018, 12:23:46 AM2/1/18
to QUIC Prototype Protocol Discussion group, marten...@gmail.com
I used caddy for a test server, but  i see the "
alt-svc:
quic=":443"; ma=2592000; v="38,37,36,35"
 from reponse header, does this support v 39 for now?

在 2016年5月9日星期一 UTC+8下午6:07:06,Lucas Clemente写道:

Marten Seemann

unread,
Feb 1, 2018, 12:28:22 AM2/1/18
to Hui Wang, QUIC Prototype Protocol Discussion group
Yes, quic-go has been supporting QUIC 39 since August last year. The problem is that Caddy didn’t update its quic-go dependency for quite a while, so Caddy users are currently stuck with an outdated quic-go version.

Hui Wang

unread,
Feb 1, 2018, 12:34:36 AM2/1/18
to Marten Seemann, QUIC Prototype Protocol Discussion group
Thanks for the info. 

Marten Seemann <marten...@gmail.com>于2018年2月1日周四 下午1:28写道:
Reply all
Reply to author
Forward
0 new messages