[Bug 2055717] Re: Acquire::http::proxy ignored / used inconsistently?

[Benjamin Portner]

Okay, I realized that `no_proxy="" sudo ...` does not overwrite no_proxy
because it gets loaded again from /etc/environment when switching to the
su context. If I do `sudo su` and then call `no_proxy="" apt update`
then indeed the proxy is no longer by-passed.

> 3) configure Acquire::http::proxy (or http_proxy) and set no_proxy in
/etc/environment(.d)

This is exactly what I did and it leads to the described inconsistent
behavior. Apparently, /etc/environment is not read when apt.daily runs.
This means, no_proxy is *not* defined when apt runs as a service - but
it *is* defined when running apt from the terminal. So effectively, apt
does "suddenly pick different proxies when running as a service".

Note that this is not a support request as I did not ask for help or
pose any questions.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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