fix: set User-Agent for HTTP retrieval client #259
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
makes is easier to track which specific rainbow build/release is responsible for requests. we need this, because Kubo and Rainbow may use the same boxo, but initialize client with slightly different config Ref. ipfs/kubo#10772
guillaumemichel
approved these changes
Apr 29, 2025
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.
Setting to the same value we already use for libp2p:
rainbow/setup_routing.go
Line 82 in 1bf59f7
This makes is easier to track which specific rainbow build/release is responsible for requests.
We need this, because Kubo and Rainbow may use the same boxo, but initialize client with slightly different config (Ref. ipfs/kubo#10772)