microsoft / microsoft/vscode-azureresourcegroups
Unable to Connect Through Corporate Proxy- No User-Agent String Provided to Allow
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
Our developers are working behind a corporate proxy server. All user-agent strings are denied by default with only approved client browser applications approved to pass through the proxy.
When attempting to connect to Azure using the Azure Resources extension in Visual Studio Code, access beyond the proxy is denied. We are not able to allow the extension through our proxy because there is no user-agent string provided, it is blank.
Please update the extension so that when it makes web requests a user-agent string is provided to identify the client source of the traffic. Once there is a user-agent string we will be able to put in a request to allow the extension through our corporate proxy.
As a workaround, we are using the Fiddler Classic development proxy to impersonate allowed user-agent strings.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Azure Resources extension's web-request entry points and inspect how request headers are assembled. Confirm which requests currently lack a User-Agent, then verify that the extension identifies itself on those requests and that the reported corporate-proxy access issue is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100