Okay, I agree that this is not an apt bug. However, the fact that you and me got this part wrong shows that the documentation can be improved. I propose updating the apt-transport-http manpage "Proxy Configuration" section as follows:
- From the current description, it does not become clear that http_proxy does *not* override Acquire::http::proxy. This should be explicitly stated. - There should be an explicit note that apt, when run as a systemd service, does not read /etc/environment. It should be followed by a specific recommendation to use the Acquire::http::proxy::freightserverhostname "DIRECT" mechanism instead of "no_proxy" environment variables to ensure consistent behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2055717 Title: Acquire::http::proxy ignored / used inconsistently? Status in apt package in Ubuntu: Invalid Bug description: Problem description I have a client (A) and a freight server (B) serving apt packages on the same network. I also have a proxy server (C), which the client uses to talk to "the internet". When I run `sudo apt update`, my client talks to the freight server directly, without contacting the proxy. However, when `apt.daily` runs, the client contacts the proxy, which then connects to the freight server. Expected behavior Although updates work in both cases, the current behavior is inconsistent. The proxy should be used in both cases or in neither case. Setup details I use Ubuntu 22.04.4 with apt 2.4.11 (amd64). /etc/apt/sources.list.d/freight.list contains the local freight server. /etc/apt/sources.list lists the official Ubuntu repositories. /etc/apt/apt.config.d/95proxy contains one line `Acquire::http::proxy "http://my.proxy:8080/"`. Omitting the proxy config (`Acquire::http::proxy "false"`) lets the client contact the freight server directly during `apt.daily`, but updating the official repositories fails. Having the proxy properly configured,`apt.daily` succeeds but with the described inconsistent behavior. Note: I am aware that proxy exceptions can be configured using the "DIRECT" keyword. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
