Making HTTP User Agent a runtime option #559
Open
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
precurse
force-pushed
the
feature-user-agent
branch
2 times, most recently
from
057fc32 to
23f91e0
Compare
precurse
force-pushed
the
feature-user-agent
branch
from
23f91e0 to
f72fba1
Compare
precurse
changed the title
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.
I've had issues with some podcast feeds with Akamai CDN not liking the built-in hardcoded HTTP user agent, and blocking based on it.
This PR adds a new runtime option to change the HTTP User Agent on demand if needed.