[client] Set User-Agent in non-browser environments #161
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
|
Oh, thats super useful. Maybe we could use another header in the browser? |
bjoerge
approved these changes
Sep 8, 2017
|
I believe that would trigger preflight requests. Will have a think on it. |
|
Yea, think you're right about that. |
thomax
pushed a commit
that referenced
this pull request
Sep 14, 2017
bjoerge
pushed a commit
that referenced
this pull request
Sep 14, 2017
Merged
bjoerge
pushed a commit
that referenced
this pull request
Sep 19, 2017
rexxars
added a commit
that referenced
this pull request
Jan 26, 2022
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.
We're not allowed to override the user agent in browsers, but in Node, we want to include a user agent to help track down potential issues and get a general feel of client usage.