I have a proxy defined at the system level on my work laptop. We use a PAC script to configure the proxy settings.

The HTTP_PROXY and HTTPS_PROXY environment variables point at the PAC script, not to the proxy itself.

Clamwin seems to be completely unaware of PAC (proxy auto config). In the PAC, I have configured .clamav.net and clamav.net to NOT use the proxy. I don't know which part of the proxy config is responsible, but if those URLs go through the proxy, they are denied.

I tried configuring clamwin itself to use the proxy (which is https) on port 443, but this doesn't work, and locks my LDAP account that the proxy uses because of too many password failures.

So I can't update clamwin's virus database. I tried disabling the proxy and trying the update again, but that didn't work. I suspect that I will need to reboot after disabling the proxy, and since that is very disruptive, I haven't tried it yet.

I had a similar problem with the Keeper app for Windows. When I added keepersecurity.com to the PAC script in the list of domains that should not go through the proxy, that problem vanished. I think the reason that it worked is that keeper either knows how to handle PAC scripts, or it just lets Windows handle the proxy. It appears that clamwin doesn't, and thinks the URL in HTTPS_PROXY is the proxy itself, which it isn't -- it's the PAC script.

I'm not a proxy guy, so I've asked one of the ClamWin developers to drop by. Sounds to me like ClamWin is not set up to do what you want.

Regards,

freshclam uses libcurl, according to the documentation libcurl does not support pac files https://everything.curl.dev/usingcurl/proxies#pac

about the authentication:



I hope the environment variable can use same syntax of the curl cmdline