install-dotnet.ps1 fails behind authenticated proxy: credentials not applied from ProxyAddress
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- networking
Research direction
Start in install-dotnet.ps1 at the code that constructs HttpClientHandler and WebProxy from ProxyAddress. Trace how proxy credentials and environment variables are handled, then reproduce the request through an authenticated proxy. Done means requests authenticate successfully and no longer fail with 407 Proxy Authentication Required.
Written by the indexing model from the issue text.
Description
The install-dotnet.ps1 script fails behind authenticated proxy because it does not apply proxy credentials, even when they are provided via the ProxyAddress parameter.
The script constructs its own HttpClientHandler and WebProxy object. It does not extract credentials from the proxy URL or use those set in environment variables. As a result, it sends unauthenticated requests to the proxy, resulting in 407 Proxy Authentication Required errors. Failure logs show that the ProxyAddress with credentials is passed correctly, but the script still receives a 407. Web proxy logs confirm the request reaches the proxy without credentials, indicating that authentication details are not being applied.
Please find error screenshot for reference.
Environment Context
The runners are in a restricted network without direct internet access, so all outbound traffic must go through an authenticated proxy.
- Dominant language
- PowerShell
- Stars
- 213
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
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.
More from dotnet/install-scripts
-
up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotnet/install-scripts#686 · 2 reactions ·
-
area-infra
dotnet/install-scripts#699 · 2 reactions · 1 assignee ·
-
needs-pm-discussion
Difficulty 5/5 Over a week Newbie friendliness 35/100
dotnet/install-scripts#583 · 1 comment · 2 reactions ·
-
needs-pm-discussion
Difficulty 5/5 Over a week Newbie friendliness 35/100
dotnet/install-scripts#580 · 1 comment · 5 reactions ·
-
needs-pm-discussion
Difficulty 3/5 1-2 days Newbie friendliness 42/100
dotnet/install-scripts#578 · 4 comments · 1 reaction ·
All issues in dotnet/install-scripts
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
TheManticoreProject/Manticore#1380 ·
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·
-
support
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100