-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
http3: adding upstream API hooks #14839
Conversation
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
|
||
// [#not-implemented-hide:] | ||
message Http3ProtocolOptions { | ||
Http2ProtocolOptions http2_protocol_options = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does this configuration address the difference between H2 and H3? From a quick glance at the current spec, there are differences around SETTINGS, WINDOW_UPDATE frames.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the options are
- using Http2ProtocolOptions, and config-validating that fields which don't make sense don't apply
- copying most of the fields out of Http2ProtocolOptions so we don' t have the fields which make sense
- splitting Http2ProtocolOptions so we have http2/http3/shared today
I think 3) is undesirable today, especially as http3 hasn't fully landed yet. If we agree it may be the end goal, I think 1 is the least churn, so what I think we should go with, but I'm not committed to it so if you see other ideas or have other pros/cons let me know
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah agreed 1 is least churn, can we add some comment to address those fields?
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
comments addressed - PTAL when you get a chance! |
Only adding explicit (hard-configured, or downstream-initiated) HTTP/3. Getting Auto for UDP/TCP is going to take substantially more work. HTTP/3 config will be rejected initially to keep this PR simple as possible.
Risk Level: Low (unused, hidden)
Testing: new unit tests
Docs Changes: n/a
Release Notes: n/a
Part of #14829