-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: populate-user-agent-header #912
fix: populate-user-agent-header #912
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need different user-agents per adapter github/tor/binary download. All the agents could just say universe with version and platform, and if this is the case it could be a static var instead of defined per file.
/cc @leet4tari opinions?
"universe {}({}) | {}", | ||
env!("CARGO_PKG_VERSION"), | ||
std::env::consts::OS, | ||
"github adapter" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this say "tor adapter" ?
"github adapter" | |
"tor adapter" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, only TU version and platform info I think is useful. Getting reports on TU version or platform usage from CDN provider is possible. Different adapter
would not request resources from different services.
Closing in favor of #935 |
#905
[ Content ]
Added User-agent header to request that had it missing or was not descriptive