fix: update User-Agent string to latest Chrome version in webfetch #8284
+1
−1
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.
Summary
Update the default User-Agent string used for webfetch/http requests so OpenCode can successfully fetch web resources from customers that block outdated browser User-Agent strings at their internal proxy.
Motivation & Context
One of our customers (a large, legacy organization using a strict internal proxy) blocks requests that present old/legacy User-Agent headers. This caused OpenCode's webfetch functionality to fail for them. Updating the User-Agent resolves those proxy-based rejections.
What changed
Change the default User-Agent used by webfetch tool implementation to a updated version that proxies accept.
Testing
Linked issue
Fixes: #2943