fix: add user-agent to outbound fetch requests #210
Merged
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
magurotuna
force-pushed
the
add-user-agent-to-outbound-request
branch
from
89204a0 to
3d28342
Compare
magurotuna
force-pushed
the
add-user-agent-to-outbound-request
branch
from
3d28342 to
29bd1bf
Compare
crowlKats
approved these changes
Jul 9, 2024
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.
This commit adds a special
User-Agentheader to outbound fetch requests.Currently the user-agent header that upstream servers see is
Deno/1.40.4which is a common value across all requests made from deployments on Deno Deploy. Having a special user-agent in docland will help upstreams easily identify requests coming from docland.