-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Backport of Explicitly enable WebSocket upgrades into release/1.15.x #18210
Backport of Explicitly enable WebSocket upgrades into release/1.15.x #18210
Conversation
fc08634
to
0d77cc5
Compare
0d77cc5
to
fc08634
Compare
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.
Auto approved Consul Bot automated PR
🤔 This PR has changes in the |
This PR explicitly enables WebSocket upgrades in Envoy's UpgradeConfig for all proxy types. (API Gateway, Ingress, and Sidecar.) Fixes #8283
fc08634
to
9529d57
Compare
Backport
This PR is auto-generated from #18150 to be assessed for backporting due to the inclusion of the label backport/1.15.
🚨
The person who merged in the original PR is:
@blake
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
The below text is copied from the body of the original PR.
Description
Explicitly enable WebSocket connection upgrades in Envoy's HTTP connection manager. This is required to enable mesh applications configured with the
http
protocol to receive WebSocket connection upgrade requests from HTTP clients.Links
Resolves #8283.
PR Checklist
Overview of commits