Wget Needs a Proxy Address, Not a PAC URL
A browser can evaluate a PAC script automatically while GNU Wget expects an actual proxy endpoint in its proxy settings.
Give GNU Wget an actual forwarding endpoint for the download destination:
https_proxy=http://proxy.example:8080 wget https://downloads.example/file.zipReplace the first example URL with the approved HTTP proxy and the second with the intended file. https_proxy selects HTTPS destination requests; its value names the listener, not a PAC script to evaluate.
A URL such as https://config.example/proxy.pac points to route-selection data. Putting it in the proxy variable does not ask Wget to execute JavaScript. Check the GNU Wget proxy inputs and installed version; another similarly named utility can behave differently.
Obtain the PAC result for the URLs involved. Copying one endpoint is appropriate only when that route applies throughout the operation. Redirects can change hosts, and internal destinations can be direct. A complex policy needs a supported adapter or management arrangement that preserves those decisions.
Ask for the approved endpoint or command-line integration rather than paste the PAC program into a shell profile or execute an unfamiliar script as unrestricted shell code.