Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.4_beta3 2016-12-31T01:29:21Z 2016-12-31T01:29:21Z David Kalnischkies david@kalnischkies.de 2016-12-09T14:13:09Z urn:sha1:d8617331afc39281d5925033975b6097128786f4 This 'method' is the abstract base for http and https and should as such be called out like this rather using an easily confused name. Gbp-Dch: Ignore 2016-12-31T01:29:21Z David Kalnischkies david@kalnischkies.de 2016-11-09T11:25:44Z urn:sha1:13a9f08de18dea0dfc1951992b0ddeda9c2fa2dd Having a Reset(bool) method to partially reset certain variables like the download size always were strange, so this commit splits the ServerState into an additional RequestState living on the stack for as long as we deal with this request causing an automatic "reset". There is much to do still to make this code look better, but this is a good first step which compiles cleanly and passes all tests, so keeping it as history might be beneficial and due to avoiding explicit memory allocations it ends up fixing a small memory leak in https, too. Closes: #440057 2016-11-11T22:40:37Z David Kalnischkies david@kalnischkies.de 2016-11-11T09:32:31Z urn:sha1:11c96d7618faecc8fab9edfd83b2b2e0afefda3b Suggested in #529794 2016-11-10T15:39:07Z David Kalnischkies david@kalnischkies.de 2016-11-10T09:37:29Z urn:sha1:e40a4a3e381a8cb6c8b924e9ce545512769bddff The 0.0.0.0:0 tor reports is pretty useless by itself, but even if an IP would be reported it is better to show the user the hostname we wanted the proxy to connect to in the same error message. We improve upon it further by looking for this bind address in particular and remap error messages slightly to give users a better chance of figuring out what went wrong. Upstream Tor can't do that as it is technically wrong. 2016-08-16T16:49:37Z David Kalnischkies david@kalnischkies.de 2016-08-11T16:24:35Z urn:sha1:d94b1d80d8326334d17f6a43061368e783b8e0aa If the server told us in a previous request that it isn't supporting Ranges with bytes via an Accept-Ranges header missing bytes, we don't try to formulate requests using Ranges. 2016-08-16T16:49:37Z David Kalnischkies david@kalnischkies.de 2016-08-11T14:59:13Z urn:sha1:ebdb6f1810a20ac240b5b2192dc2e6532ff149d2 We keep various information bits about the server around, some only effecting the currently handled file (like sizes) while others should be persistent (like pipeline detections). http used to reset all file-related manually, which is a bit silly if we already have a Reset() method – which does reset all through –, so extending it with a parameter for reuse and calling it from https too (as this was previously resetting by just creating a new state struct – it uses no value of the persistent state-keeping yet as it supports no pipelining). Gbp-Dch: Ignore 2016-08-10T23:34:39Z David Kalnischkies david@kalnischkies.de 2016-08-06T20:54:31Z urn:sha1:0568d325ad8660a9966d552634aa17c90ed22516 With apts http transport supporting socks5h proxies and all the work in terms of configuration of methods based on the name it is called with it becomes surprisingly easy to implement Tor support equally (and perhaps even a bit exceeding) what is available currently in apt-transport-tor. How this will turn out to be handled packaging wise we will see in https://lists.debian.org/deity/2016/08/msg00012.html , but until this is resolved we can add the needed support without actively enabling it for now, so that this can be tested better. 2016-08-10T21:19:44Z David Kalnischkies david@kalnischkies.de 2016-08-04T06:45:38Z urn:sha1:61db48241f2d46697a291bfedaf398a1ca9a70e3 Socks support is a requested feature in sofar that the internet is actually believing Acquire::socks::Proxy would exist. It doesn't and this commit isn't adding it as that isn't how our configuration works, but it allows Acquire::http::Proxy="socks5h://…". The HTTPS method was changed already to support socks proxies (all versions) via curl. This commit implements only SOCKS5 (RFC1928) with no auth or pass&user auth (RFC1929), but not GSSAPI which is required by the RFC. The 'h' in the protocol name further indicates that DNS resolution is delegated to the socks proxy rather than performed locally. The implementation works and was tested with Tor as socks proxy for which implementing socks5h only can actually be considered a feature. Closes: 744934 2016-08-10T21:19:44Z David Kalnischkies david@kalnischkies.de 2016-07-31T16:05:56Z urn:sha1:30060442025824c491f58887ca7369f3c572fa57 The https method implemented for a long while now a hardcoded fallback to the same options in http, which, while it works, is rather inflexible if we want to allow the methods to use another name to change their behavior slightly, like apt-transport-tor does to https – most of the diff being s#https#tor#g which then fails to do the full circle fallthrough tor -> https -> http for https sources. With this config infrastructure this could be implemented now. 2016-08-10T21:19:44Z David Kalnischkies david@kalnischkies.de 2016-08-02T12:49:58Z urn:sha1:4bba5a88d0f6afde4414b586b64c48a4851d5324 cURL which backs our https implementation can handle redirects on its own, but by dealing with them on our own we gain finer control over which redirections will be performed (we don't like https → http) and by whom so that redirections to other hosts correctly spawn a new https method dealing with these instead of letting the current one deal with it.