-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Implement h2c with backend #3371
Conversation
2926b30
to
142dd63
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.
LGTM 🎉 👏 👏
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.
LGTM
docs/user-guide/grpc.md
Outdated
@@ -76,40 +60,25 @@ rootCAs = [ "./backend.cert" ] | |||
``` | |||
|
|||
!!! warning | |||
With some backends, the server URLs use the IP, so you may need to configure `insecureSkipVerify` instead of the `rootCAS` to activate HTTPS without hostname verification. | |||
For provider with label, you will have to specify the `frontend.protocol=h2c` |
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.
frontend.protocol
is a new label? It should be traefik.protocol
instead?
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.
LGTM 👏 🎉
What does this PR do?
Add h2c support with backend.
Motivation
Simplify the use of http2 with backend.
Fixes #2139
More
Additional Notes
This PR add a new "protocol" in the backend server.
h2c://{backend}