apt, branch 1.5_alpha4Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.5_alpha42017-06-30T16:21:33ZUpload 1.5~alpha4 to experimental2017-06-30T16:21:33ZJulian Andres Klodejak@debian.org2017-06-30T16:18:47Zurn:sha1:3be04d30cbb801777dce9d3e46c19722ab480b14shippable: Run tests in parallel2017-06-30T16:16:51ZJulian Andres Klodejak@debian.org2017-06-30T15:56:49Zurn:sha1:d6bcfa40f170434c387acfd6e8c1425f3fe057af
Gbp-Dch: ignore
CMake: Do not allow FORCE_CURL=ON with WITH_CURL=OFF2017-06-30T16:16:42ZJulian Andres Klodejak@debian.org2017-06-30T15:50:23Zurn:sha1:551861110db67c7bad2bd0715f46191454c0b9a7
This makes no sense. We need both entries in the cache, as
we check FORCE_CURL in the test suite.
Gbp-Dch: ignore
TLS support: Error out on unsupported curl options2017-06-30T15:20:21ZJulian Andres Klodejak@debian.org2017-06-30T15:20:21Zurn:sha1:6a0e7acbf01e22665d89a9c6556f3a8220a78756
Silently ignoring the options might be a security issue,
so produce an error instead.
Improve closing the TLS connection2017-06-30T15:12:11ZJulian Andres Klodejak@debian.org2017-06-30T15:12:11Zurn:sha1:8f5db6b513b90b6ee5b625131a25b146fa912e0d
If gnutls_session_bye() exited with an error, we never closed
the underlying file descriptor, causing the method to think the
connection was still open. This caused problems especially in
test-partial-file-support where we checked that a "complete"
file and an incomplete file work. The first GET returns a 416
with Connection: close, and the next GET request then accidentally
reads the body of the 416 as the header for its own request.
Switch to 'http' as the default https method2017-06-30T14:33:09ZJulian Andres Klodejak@debian.org2017-06-30T14:33:09Zurn:sha1:c6a428e4d17b408c2701def5daa46ca950948980
The old curl based method is still available as 'curl',
'curl+http', and 'curl+https'.
travis: Switch to Docker2017-06-30T14:02:17ZJulian Andres Klodejak@debian.org2017-06-30T13:40:40Zurn:sha1:46c31341ef4b09bb3509ebbc49416e34b68e1be4
This runs parallel builds on docker, based on debian:testing
docker images, with ccache enabled and parallel running of the
test suite (ccache supports coverage builds these days, and
parallel testing just needs unbuffer to handle the stty stuff)
This is a huge step up from building on a mix of trusty, wily,
and xenial. Most importantly, coverage now correctly detects
partial covered lines instead of just reporting almost all of
them as fully covered.
We use ftp.de.debian.org as deb.debian.org backed by Amazon
503s too often.
Gbp-Dch: ignore
Allow http(s) and socks5h for http and https in proxy auto detect2017-06-30T13:00:41ZJulian Andres Klodejak@debian.org2017-06-30T12:38:25Zurn:sha1:535c06a759dc13c8e2858735973cac24ceaa36fa
This makes it possible to write sensible auto detect scripts.
http: Add support for https:// proxies2017-06-30T13:00:41ZJulian Andres Klodejak@debian.org2017-06-30T11:52:18Zurn:sha1:bafebf1afc59db7df7e0148b723f3f361770272c
HTTPS proxies just require unwrapping the TLS layer at the proxy
connection, that's easy, and of course sending proxy-specific
headers that are sent on "http" proxies.
http: Add support for CONNECT proxying to HTTPS locations2017-06-30T13:00:41ZJulian Andres Klodejak@debian.org2017-06-30T11:24:04Zurn:sha1:64207dad49f1c803d2b004ccf8fc6432789a8cc2
Proxying HTTPS traffic requires the proxy providing the
CONNECT method. This implements the client side of it,
although it is a bit hacky.
HTTP connect is a normal HTTP CONNECT request, followed
by a normal HTTP response, just that the body of the
response is the TCP stream of the target host.
We use a special wrapper in case there are data bytes
in the header packets - in that case, the bytes are
stored in a buffer and the buffer will be drained first,
afterwards the connection continues directly with the
TCP stream (with one more vcall).
Also: Do not send full URI to https destinations when proxying,
as we are directly interfacing with the destination data stream.