apt's https method asks Acquire::https::Proxy first and then Acquire::http::Proxy, for the host and then for all. This was measured with apt 2.8.3's apt-helper against a dead port and against a proxy that answers 403. An 00proxy with the http line alone therefore sent download.docker.com and every other https source to apt-cacher-ng. Without a PassThroughPattern the cache answers 403 CONNECT denied, and the whole upgrade failed.
Report: carries https_proxy, https_per_host and https_settings. https_proxy_for(report, host) is the proxy apt takes for one https host.
check_https_source(): fetches one https source's InRelease the way apt does. It returns None where no https source goes through a proxy.
configure_package_proxy: gains an https step, which fetches one https source through the new proxy. Where the proxy refuses it:
00proxy also gets Acquire::https::Proxy "DIRECT";;
later https lines to the same proxy are commented out;
the source is fetched again, directly.
An HTTP error from the mirror counts as let through.
Helpers:apt_fetch_command takes https URLs, and comment_out_command takes a scheme.
Checked against real apt on a noble host: check_https_source() sees the http proxy as the https one and reports 403 CONNECT denied from a proxy that refuses CONNECT.
napalm-linux needs NAPALM/napalm-linux (fix/apt-https-step): one of its tests listed the fix's steps exactly. Merge this one first or together.
Prio: P2 (NetOrk/netork#1811)
apt's https method asks `Acquire::https::Proxy` first and then `Acquire::http::Proxy`, for the host and then for all. This was measured with apt 2.8.3's `apt-helper` against a dead port and against a proxy that answers 403. An `00proxy` with the http line alone therefore sent download.docker.com and every other https source to apt-cacher-ng. Without a `PassThroughPattern` the cache answers `403 CONNECT denied`, and the whole upgrade failed.
- **Report:** carries `https_proxy`, `https_per_host` and `https_settings`. `https_proxy_for(report, host)` is the proxy apt takes for one https host.
- **`check_https_source()`:** fetches one https source's `InRelease` the way apt does. It returns None where no https source goes through a proxy.
- **`configure_package_proxy`:** gains an `https` step, which fetches one https source through the new proxy. Where the proxy refuses it:
- `00proxy` also gets `Acquire::https::Proxy "DIRECT";`;
- later https lines to the same proxy are commented out;
- the source is fetched again, directly.
An HTTP error from the mirror counts as let through.
- **Helpers:** `apt_fetch_command` takes https URLs, and `comment_out_command` takes a `scheme`.
Checked against real apt on a noble host: `check_https_source()` sees the http proxy as the https one and reports `403 CONNECT denied` from a proxy that refuses CONNECT.
napalm-linux needs NAPALM/napalm-linux (fix/apt-https-step): one of its tests listed the fix's steps exactly. Merge this one first or together.
apt's https method asks Acquire::https::Proxy and then Acquire::http::Proxy,
for the host and then for all. An 00proxy with the http line alone therefore
sent download.docker.com and every other https source to apt-cacher-ng, which
answers 403 CONNECT denied without a PassThroughPattern, and the whole upgrade
failed.
- The report carries https_proxy, https_per_host and https_settings;
https_proxy_for(report, host) is the proxy apt takes for one https host.
- check_https_source() fetches one https source the way apt does.
- configure_package_proxy gains an https step: one https source through the
new proxy. Where the proxy refuses it, 00proxy also says
Acquire::https::Proxy "DIRECT", later https lines to the same proxy are
commented out, and the source is fetched direct. An HTTP error from the
mirror counts as let through.
- apt_fetch_command takes https URLs; comment_out_command takes a scheme.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Prio: P2 (NetOrk/netork#1811)
apt's https method asks
Acquire::https::Proxyfirst and thenAcquire::http::Proxy, for the host and then for all. This was measured with apt 2.8.3'sapt-helperagainst a dead port and against a proxy that answers 403. An00proxywith the http line alone therefore sent download.docker.com and every other https source to apt-cacher-ng. Without aPassThroughPatternthe cache answers403 CONNECT denied, and the whole upgrade failed.Report: carries
https_proxy,https_per_hostandhttps_settings.https_proxy_for(report, host)is the proxy apt takes for one https host.check_https_source(): fetches one https source'sInReleasethe way apt does. It returns None where no https source goes through a proxy.configure_package_proxy: gains anhttpsstep, which fetches one https source through the new proxy. Where the proxy refuses it:00proxyalso getsAcquire::https::Proxy "DIRECT";;An HTTP error from the mirror counts as let through.
Helpers:
apt_fetch_commandtakes https URLs, andcomment_out_commandtakes ascheme.Checked against real apt on a noble host:
check_https_source()sees the http proxy as the https one and reports403 CONNECT deniedfrom a proxy that refuses CONNECT.napalm-linux needs NAPALM/napalm-linux (fix/apt-https-step): one of its tests listed the fix's steps exactly. Merge this one first or together.