apt/methods/http.h, branch 1.1.exp11Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.exp112015-08-10T15:27:17Zadd c++11 override marker to overridden methods2015-08-10T15:27:17ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-08T22:35:40Zurn:sha1:3b3028467ceccca0b73a8f53051c0fa4de313111
C++11 adds the 'override' specifier to mark that a method is overriding
a base class method and error out if not. We hide it in the APT_OVERRIDE
macro to ensure that we keep compiling in pre-c++11 standards.
Reported-By: clang-modernize -add-override -override-macros
Git-Dch: Ignore
calculate hashes while downloading in https2015-04-18T23:13:09ZDavid Kalnischkiesdavid@kalnischkies.de2015-04-11T08:23:52Zurn:sha1:34faa8f7ae2526f46cd1f84bb6962ad06d841e5e
We do this in HTTP already to give the CPU some exercise while the disk
is heavily spinning (or flashing?) to store the data avoiding the need
to reread the entire file again later on to calculate the hashes – which
happens outside of the eyes of progress reporting, so you might ended up
with a bunch of https workers 'stuck' at 100% while they were busy
calculating hashes.
This is a bummer for everyone using apt as a connection speedtest as the
https method works slower now (not really, it just isn't reporting done
too early anymore).
calculate only expected hashes in methods2015-04-18T23:13:09ZDavid Kalnischkiesdavid@kalnischkies.de2015-03-30T18:47:13Zurn:sha1:9224ce3d4d1ea0428a70e75134998e08aa45b1e6
Methods get told which hashes are expected by the acquire system, which
means we can use this list to restrict what we calculate in the methods
as any extra we are calculating is wasted effort as we can't compare it
with anything anyway.
Adding support for a new hash algorithm is therefore 'free' now and if a
algorithm is no longer provided in a repository for a file, we
automatically stop calculating it.
In practice this results in a speed-up in Debian as we don't have SHA512
here (so far), so we practically stop calculating it.
make http size check work2014-10-06T15:42:39ZMichael Vogtmvo@ubuntu.com2014-10-06T15:42:39Zurn:sha1:a2d40703e4a5590a689ace4466f92e590434944dMake Proxy-Auto-Detect check for each host2014-09-02T14:02:37ZMichael Vogtmvo@ubuntu.com2014-09-02T13:50:19Zurn:sha1:c6ee61eab54edf6cc3fbe118d304d72a860e1451
When doing Acquire::http{,s}::Proxy-Auto-Detect, run the auto-detect
command for each host instead of only once. This should make using
"proxy" from libproxy-tools feasible which can then be used for PAC
style or other proxy configurations.
Closes: #759264
Pass ExpectedSize to tthe backend method2014-08-27T02:08:37ZMichael Vogtmvo@debian.org2014-08-27T02:08:37Zurn:sha1:dcd5856b11c685ca6d4629212d2978ce196ea65c
This ensures that we can stop downloading if the server send
too much data by accident (or by a malicious attempt)
cleanup headers and especially #includes everywhere2014-03-13T12:58:45ZDavid Kalnischkiesdavid@kalnischkies.de2014-03-05T21:11:25Zurn:sha1:453b82a388013e522b3a1b9fcd6ed0810dab1f4f
Beside being a bit cleaner it hopefully also resolves oddball problems
I have with high levels of parallel jobs.
Git-Dch: Ignore
Reported-By: iwyu (include-what-you-use)
Fix typos in documentation (codespell)2014-02-22T17:34:33ZMichael Vogtmvo@debian.org2014-02-22T17:34:33Zurn:sha1:1e3f4083db29bba600b9725e9456b0e140975c99handle complete responses to https range requests2013-10-01T09:17:02ZDavid Kalnischkieskalnischkies@gmail.com2013-09-30T14:41:16Zurn:sha1:fd46d30571eb240ec3aae792e7a56061ede50524
Servers might respond with a complete file either because they don't
support Ranges at all or the If-Range condition isn't statisfied, so we
have to parse the headers curl gets ourself to seek or truncate the file
we have so far.
This also finially adds the testcase testing a bunch of partial
situations for both, http and https - which is now all green.
Closes: 617643, 667699
LP: 1157943
refactor http client implementation2013-10-01T09:06:56ZDavid Kalnischkieskalnischkies@gmail.com2013-09-17T20:35:44Zurn:sha1:7330f4df8b31e66f6557bf49c9c90ad9a73ff459
No effective behavior change, just shuffling big junks of code between
methods and classes to split them into those strongly related to our
client implementation and those implementing HTTP.
The idea is to get HTTPS to a point in which most of the implementation
can be shared even though the client implementations itself is
completely different. This isn't anywhere near yet though, but it should
beenough to reuse at least a few lines from http in https now.
Git-Dch: Ignore