-
Notifications
You must be signed in to change notification settings - Fork 472
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
h2c (cleartext HTTP/2) protocol support #204
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten |
Closing in favor of #817 |
Based on the Listener definitions in #193, it's not all that clear how implementations should spec upgrading HTTP/1.1 to h2c.
This could be a property of the listener, but there's currently not a place for protocol-specific control fields. Otherwise, iit could be a property of the HTTPRoute, but that portion of the API is currently protocol-independent.
The text was updated successfully, but these errors were encountered: