[meta] QUIC support
Categories
(Core :: Networking, enhancement, P3)
Tracking
()
People
(Reporter: mt, Unassigned)
References
(Depends on 36 open bugs, )
Details
(Keywords: feature, meta, parity-chrome, Whiteboard: [necko-backlog])
Updated•9 years ago
|
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
Comment 3•9 years ago
|
||
Comment 4•9 years ago
|
||
Comment 6•9 years ago
|
||
Updated•9 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Comment 8•7 years ago
|
||
Comment 9•7 years ago
|
||
Comment 10•7 years ago
|
||
Comment 11•7 years ago
|
||
Updated•7 years ago
|
Comment 12•7 years ago
|
||
Comment 13•7 years ago
|
||
Comment 14•6 years ago
|
||
Comment 15•6 years ago
|
||
Comment 16•6 years ago
|
||
Comment 17•6 years ago
|
||
Comment 18•6 years ago
|
||
Comment 19•6 years ago
|
||
Comment 20•5 years ago
|
||
I considered modifying this to "HTTP/3 support" given that is the only current use case, but I realized that there are a few differences between HTTP/2 and HTTP/3 other than QUIC. (Some of which is just bypassing HTTP/2 flow control routines to calls into quic.) Should that be a separate bug, or just roll it up into this one since it's all part of the same push?
Comment 21•5 years ago
|
||
I believe HTTP/3 support should be a separate bug, depending on this one.
Updated•5 years ago
|
Comment 22•5 years ago
|
||
Updated•5 years ago
|
Comment 23•5 years ago
|
||
Couldn't help myself.
Comment 24•5 years ago
|
||
Excuse me, sorry for the intrusion.
"Initial support was added in Chrome 29 and Opera 16, and in LiteSpeed servers. Chrome support expanded this month, but the bigger news is Cloudflare making the protocol generally available for its customers."
Link:
https://www.zdnet.com/article/cloudflare-google-chrome-and-firefox-add-http3-support/
Thanks...
Comment 25•5 years ago
|
||
Excuse me, sorry for the intrusion(again).
There is this project in GO:
https://github.com/lucas-clemente/quic-go
Thanks!
Comment 26•5 years ago
|
||
INFO: currently that is a problem with QUIC/HTTP3 because some functionality in neqo has changed and necko has not adapted to it. I am working a solution. The problem can be experience that http3 connection will never be closed and will enter a busy wait state.
Comment 27•4 years ago
|
||
blog.cloudflare.com/how-to-test-http-3-and-quic-with-firefox-nightly/
when you enable network.http.http3.enabled to true >slows down Internet connect and request stopped
Comment 28•4 years ago
|
||
(In reply to artymka1 from comment #27)
blog.cloudflare.com/how-to-test-http-3-and-quic-with-firefox-nightly/
when you enable network.http.http3.enabled to true >slows down Internet connect and request stopped
¡Hola!
I'm sorry to learn that enabling HTTP/3 on your Nightly has negatively impacted performance.
Could you please elaborate on what exactly do you mean by "slows down Internet connect and request stopped"?
Could you please share URL(s) of where the slow down is observed and how exactly it manifests?
¡Gracias!
Alex
Comment 29•4 years ago
|
||
¡Hola Dragana!
Thanks so much for all of your work on HTTP/3 on Firefox!
Lazy Saturday so I was again testing the servers listed at https://bagder.github.io/HTTP3-test/ on today's Nightly...
Some work but I noticed that all of these fail with the initial request showing "Blocked" on the "Transferred" column on the 1st request in the "Network" tab of the Developer Tools:
https://quic.tech:8433/
https://pgjones.dev:4433/
https://f5quic.com:4433/
https://nghttp2.org:4433/
These fail with the initial request showing "0 B" on the "Transferred" column on the 1st request in the "Network" tab of the Developer Tools:
https://test.privateoctopus.com:4433/
https://fb.mvfst.net:4433/
The rest of test servers seem to work.
Are these known bugs? If not, are these worth filing?
¡Gracias!
Alex
Comment 30•3 years ago
|
||
🎉 QUIC is finalized and standardized 🎉
https://www.ietf.org/rfc/rfc9000.html
Comment 31•2 years ago
|
||
Redirect needinfos that are pending on inactive users to the triage owner.
:dragana, since the bug has recent activity, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Updated•2 years ago
|
Description
•