Identifying clients with their User-Agent
header
#1136
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.
This is a suggestion that was discussed on the Discord support server. Related to lavalink-devs/lavalink-client#34, #1135 and holasoyender/lavalink-client@8dfaf59
This pull request adds the option for clients to set a
User-Agent
header on socket connections and HTTP requests to set extra information about the bot.Headers example (for websockets)
Headers example (for http requests)
When the
User-Agent
header is set, every log will have a prefix to identify the client its coming from.