windows11 wsl2，The WSL_PAC_URL configuration does not take effect

[yuwenlong]

Windows Version

Microsoft Windows [版本 10.0.22635.4145]

WSL Version

2.3.17.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 23.10

Other Software

Repro Steps

1、windows .wslconfig

2、The wsl is started and the WSL_PAC_URL environment variable is found

3、HTTP_PROXY and HTTPS_PROXY are not set

4、Proxy service is available

5、WSL_PAC_URL is invalid

Expected Behavior

For the reason of Chinese GFW, WSL2 needs to automatically implement PAC implementation proxy according to WSL_PAC_URL.

Windows uses ShadowsocksR, which is set to allow Intranet access, and step 4 above proves to be valid.

Actual Behavior

WSL_PAC_URL is invalid

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• autoProxy=true doesn't works well on WSL2 preview 2.0.3.0 (#10583), similarity score: 0.77
• WSL cannot use proxy with networkingMode=mirrored (#10794), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[yuwenlong]

/question

I hope developers take a closer look at what I submitted above, thank you

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[yuwenlong]

/emailed-logs

The email has been sent with the subject line windows11 wsl2, The WSL_PAC_URL configuration does not take effect #11998

Please note that check, thank you.

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'

[CatalinFetoiu]

hello. thanks for reporting the issue

Linux does not support PAC URLs by default, so WSL configures the WSL_PAC_URL env variable so that it can be manually consumed by Linux apps that support using PAC URLs
please refer as well to docs at https://learn.microsoft.com/en-us/windows/wsl/troubleshooting#considerations-when-using-autoproxy-for-httpproxy-mirroring-in-wsl

my understanding is that curl does not support PAC URLs
you will need to use a Linux tool that knows how to resolve PAC URLs and feed the value of WSL_PAC_URL to this tool

let us know if you have any questions

[yuwenlong]

@CatalinFetoiu
Linux does not support PAC URLs by default, so it may be possible to add a configuration parameter to the "ubuntu.exe" file to enable support. For example:

ubuntu.exe --proxy-pac-url=http://127.0.0.1:1080/pac

The idea could be to add a virtual network card that intercepts traffic to the PAC server.