Skip to content
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

Closed

Conversation

Misieq01
Copy link
Collaborator

@Misieq01 Misieq01 commented Oct 22, 2024

#905

[ Content ]

Added User-agent header to request that had it missing or was not descriptive

@Misieq01 Misieq01 changed the title working implementation fix: populate-user-agent-header Oct 22, 2024
Copy link
Collaborator

@brianp brianp left a 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"
Copy link
Collaborator

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" ?

Suggested change
"github adapter"
"tor adapter"

Copy link
Contributor

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.

@Misieq01
Copy link
Collaborator Author

Closing in favor of #935

@Misieq01 Misieq01 closed this Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants