Opened 8 years ago

Closed 12 months ago

#1057 closed enhancement (fixed)

Google QUIC - statement

Reported by: Jack Bauer Owned by:
Priority: major Milestone:
Component: other Version: 1.11.x
Keywords: Cc:
uname -a:
nginx -V: latest



as Googles QUIC becomes more stable and discussed around the web, it should be mandatory for and/or to establish an statement about future development whether QUIC may be considered or not. And if so, what is the long term plan: 2016, 2017 or later.

Thank you.

For informational purpose:

Official Google description:

Inofficial standalone library maintained by official QUIC developers

Good introduction read-up with comment from Jim Roskind (QUIC architect)

Change History (11)

comment:2 by Neil Craig, 8 years ago

FWIW I'd be very interested in looking at QUIC support, especially as from what I hear from IETF land, it's likely to effectively be HTTP/2.5 or HTTP/3

comment:4 by alex-eri@…, 7 years ago

Nowdays QUIC seems take good part of traffic. Statistics from one hotspot.

udp/443 == QUIC

tcp/443 : 1.4GB , 7M pkts
udp/443 : 357MB , 3101k pkts
tcp/80 : 159MB , 2591k pkts
tcp/8080 : 146MB , 315k pkts

tcp/443 : 11.5GB , 9M pkts
udp/443 : 7.0GB , 5M pkts
tcp/80 : 5.5GB , 4091k pkts
tcp/8080 : 270MB , 355k pkts

comment:5 by shibumi@…, 6 years ago

HTTP/3 has been announced as HTTP over QUIC by the IETF:

I hope this is an additional argument for QUIC support in nginx.

comment:6 by raul.peixoto@…, 5 years ago

Can someone on Nginx please take a look at supporting QUIC already?

comment:7 by maxim, 5 years ago


We are planning to have this feature in our 2019 roadmap.

Thanks for your patience and patches.



comment:8 by rfxn@…, 5 years ago


Is QUIC still on the 2019 roadmap and/or what is the status of implementation?


comment:9 by suraj.tambe@…, 5 years ago

@rfxn Please use link for tracking.

Big Thanks to nginx Team.

comment:11 by Maxim Dounin, 12 months ago

Resolution: fixed
Status: newclosed

Experimental QUIC and HTTP/3 support is available in nginx 1.25.0.

Note: See TracTickets for help on using tickets.