MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Authentication in WebVeiw2 using `--proxy-server` argument

Open
#3,667 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Hello,

I am trying to setup Webview2 with proxy. Afaik the way to go is to use the --proxy-server argument.

I've tried HTTP and SOCKSv5 without authentication using --proxy-server="protocol://ipaddress:port", and it works as intended. However, when I tried setting proxy server with credentials using --proxy-server="protocol://username:password@ipaddress:port" both HTTP and SOCKSv5 leads to "ERR_NO_SUPPORTED_PROXIES" error.

So I had some questions regarding this:

  • Does the --proxy-server argument currently support authentication?
  • If so, how to properly set it up? And if not, is there a workaround?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names WebView2 and the --proxy-server argument; start by verifying whether authenticated HTTP and SOCKSv5 proxy URLs are supported. Done means establishing the supported behavior and documenting a confirmed workaround or the requirements for adding support.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.