You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not an issue, yet, but I think the upcoming QUIC implementation won't work in the browser.
@thinkerou, @appleboy
Have you tested it in the browser?
I believe you will need to use http3.ListenAndServeTLS instead of http3.ListenAndServeQuic here:
I also meet this problem, QUIC protocol will not take effect in the Chrome browser's core. But you can test it in firefox core.And I also made a framework to support quic server(as high-performance as Gin, or even faster, and also support http1.0 to http 2.0).
Description
Not an issue, yet, but I think the upcoming QUIC implementation won't work in the browser.
@thinkerou, @appleboy
Have you tested it in the browser?
I believe you will need to use
http3.ListenAndServeTLS
instead ofhttp3.ListenAndServeQuic
here:gin/gin.go
Line 572 in 24d6764
The reason is the server first needs to advertise the QUIC support over TCP, apparently.
The issue was discussed here:
quic-go/quic-go#3890
I have made a few tests of your code and some own implementation and came across this issue.
Expectations
Browser connects
Actual result
Browser does not connect with
NS_ERROR_CONNECTION_REFUSED
Environment
The text was updated successfully, but these errors were encountered: