The Debian mirror I usually use from UBC has unceremoniously put in a forced HTTPS redirect thereby disabling HTTP access.
That sucks (don't get me started), but whatever dysfunction this is, it's the way of the world at this point.
Anyhow this revealed a couple of problems with proxy-mesh:
- When accessing the HTTP URL that is just serving the redirects, the 3xx of the redirect itself results in an error message -- we would want to pass this through or do something else that works as part of a seamless overall solution
- If I switch to HTTPS URLs in the
apt sources.list file, which wasn't supported as recently as Debian 8 but is now, the proxy found by the discovery logic will be used with HTTP CONNECT (i.e. as an HTTPS-supporting proxy). proxy-mesh doesn't support this, but it should be added for equivalent proxy functionality when HTTPS is used.
The Debian mirror I usually use from UBC has unceremoniously put in a forced HTTPS redirect thereby disabling HTTP access.
That sucks (don't get me started), but whatever dysfunction this is, it's the way of the world at this point.
Anyhow this revealed a couple of problems with
proxy-mesh:aptsources.listfile, which wasn't supported as recently as Debian 8 but is now, the proxy found by the discovery logic will be used with HTTP CONNECT (i.e. as an HTTPS-supporting proxy).proxy-meshdoesn't support this, but it should be added for equivalent proxy functionality when HTTPS is used.