Default force_attempt_http2 to true and allow configuration#5050
Merged
Default force_attempt_http2 to true and allow configuration#5050
Conversation
dehaansa
added
the
publish-dev:linux
Contributor
|
💻 Deploy preview deleted (Default force_attempt_http2 to true and allow configuration). |
kgeckhart
approved these changes
Dec 10, 2025
dehaansa
force-pushed
the
force-http2
branch
from
45bc174 to
29b3960
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Description
When this setting was introduced upstream we missed it, and our default ended up being false instead of default true, changing the behavior of some clients. This was especially relevant if writing to (likely gateway) OTLP receivers with custom TLS configuration.
Which issue(s) this PR fixes
Notes to the Reviewer
PR Checklist