Fix user-agent used by buf curl
#2475
Merged
Conversation
This file contains 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
According to this page, it looks like I should add extensions to the user agent to the end, not the beginning. So this fixes the order to better comply with the way browsers construct user agent strings.
This also fixes a small bug: previously, the default Connect user-agent would be used for reflection requests, unless overridden with a
--reflect-headerargument. Now it uses the same user-agent as the other requests, which comes from the--user-agentargument and, lacking that, is the default Connect user-agent string plusbuf/<version>. For example:connect-go/1.11.1 (go1.20.1) buf/1.26.2-dev.