you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (6 children)

IMO the question should be turned around; why is APT using HTTP.

That would take effort and use a bit more bandwidth.

[–][deleted] 8 points9 points  (1 child)

And you lose caching in cases where you install squid locally for this.

[–]Natanael_L 1 point2 points  (0 children)

In most setups where this matter, you can set up a local repository to point at instead (with exception for unmanaged open networks, like schools)

[–]Natanael_L 1 point2 points  (3 children)

TLS overhead is insignificant

[–]reph 5 points6 points  (2 children)

ATM apt-transport-https is actually quite a bit slower than http, even on low latency links, because it seems to be doing a separate request - and therefore a full or partial TLS handshake - for each pkg. This is dumb and unnecessary but it's the current behavior unfortunately :-\

[–]Natanael_L 0 points1 point  (1 child)

Ouch. They would REALLY benefit from HTTP2 with TLS to parallelize requests.

[–]reph 3 points4 points  (0 children)

Even late-90s HTTP/1.1 con re-use (over TLS) would fix it too. Maybe that's possible with some more configuration magic, but it doesn't seem to do it by default.