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
The returned error for http3.Server.Serve(...) is quic.ErrServerClosed in case of a normal shutdown/close.
It should be http.ErrServerClosed instead.
see method serveConn (some return paths already use http.ErrServerClosed).
The text was updated successfully, but these errors were encountered:
what is a "QUIC server" when working at HTTP/3 api level ? Do we need to know about such 'quic' stuff at this level ?
The http3 package tries to reproduce the same API as the net/http package.
With net/http, when we use ListenAndServeTLS or just ServeTLS and the call ends, it means the server stopped. As per the documentation:
So when http3.Server.Serve(...) ends, if the returned error is quic.ErrServerClosed what is the meaning of this ?
If we have existing code that use net/http and check for http.ErrServerClosed, when we switch or add http/3 we must add a special case to check for quic.ErrServerClosed which is confusing (which is what we're currently doing now).
The returned error for
http3.Server.Serve
(...) isquic.ErrServerClosed
in case of a normal shutdown/close.It should be
http.ErrServerClosed
instead.see method serveConn (some return paths already use
http.ErrServerClosed
).The text was updated successfully, but these errors were encountered: