-
Notifications
You must be signed in to change notification settings - Fork 10.3k
HTTP/3: Add additional configuration to Http3Limits #32034
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for contacting us. |
A lot of QuicTransportOptions should be moved to Http3Limits and passed through as features instead. Could QuicTransportOptions be removed entirely? |
HandshakeIdleTimeoutMs maps to HttpsConnectionAdapterOptions.HandshakeTimeout |
Notes for MaxUnidirectionalStreamCount, MaxBidirectionalStreamCount.
|
WebTransport will want to establish more unidirectional streams. |
We'll need to go through https://github.com/dotnet/aspnetcore/blob/main/src/Servers/Kestrel/Transport.Quic/src/QuicTransportOptions.cs and rethink the ones that are marked as preview (do they still need to exist? If so, where? Can they be based on other existing settings?). |
msquic has various configuration options: https://github.com/microsoft/msquic/blob/main/docs/Settings.md
At the very least the msquic options that have matching configuration in Http2Limits should be added to Http3Limits.
Examples:
Also msquic's IdleTimeoutMs should be set to KestrelServerLimits.KeepAliveTimeout
The text was updated successfully, but these errors were encountered: