Fix default User-Agent when using custom headers #592
Merged
Conversation
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
When using non-nil hdr parameter with c.Request method, and not setting User-Agent header explicitly, it would be left unset (when it should've been set to c.UserAgent). This means that Go HTTP client would use the default "Go-http-client/2.0" string. Suppressing the header altogether is still possible by setting it to empty string.
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.
When using non-nil
hdrparameter withc.Requestmethod, and not setting User-Agent header explicitly, it would be left unset (when it should've been set toc.UserAgent). This means that Go HTTP client would use the default "Go-http-client/2.0" string.Suppressing the header altogether is still possible by setting it to empty string.