Just realized, that ideally 'apt-get update' would respect headers that were put in place by the source.
$ wget -S -q http://azure.archive.ubuntu.com/ubuntu/dists/vivid/Release -O /dev/null
HTTP/1.1 200 OK
Date: Tue, 31 Mar 2015 13:32:55 GMT
Server: Apache/2.2.22 (Ubuntu)
Last-Modified: Tue, 31 Mar 2015 12:28:00 GMT
ETag: "34f32-51294baae5400"
Accept-Ranges: bytes
Content-Length: 216882
Cache-Control: max-age=0, proxy-revalidate
Expires: Tue, 31 Mar 2015 13:32:55 GMT
Keep-Alive: timeout=5, max=100
Ie, by default apt-get should not bother pulling that again until the 'Expires' date. Subsequent 'apt-get update' would just skip it, unless told '--force' or some thing. Such a policy would drastically reduce load (and traffic on mirrors or original mirrors).
Just realized, that ideally 'apt-get update' would respect headers that were put in place by the source. azure.archive. ubuntu. com/ubuntu/ dists/vivid/ Release -O /dev/null 51294baae5400"
$ wget -S -q http://
HTTP/1.1 200 OK
Date: Tue, 31 Mar 2015 13:32:55 GMT
Server: Apache/2.2.22 (Ubuntu)
Last-Modified: Tue, 31 Mar 2015 12:28:00 GMT
ETag: "34f32-
Accept-Ranges: bytes
Content-Length: 216882
Cache-Control: max-age=0, proxy-revalidate
Expires: Tue, 31 Mar 2015 13:32:55 GMT
Keep-Alive: timeout=5, max=100
Ie, by default apt-get should not bother pulling that again until the 'Expires' date. Subsequent 'apt-get update' would just skip it, unless told '--force' or some thing. Such a policy would drastically reduce load (and traffic on mirrors or original mirrors).