<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-bug-990555-https-proxy-for-http, branch 2.9.1</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.9.1</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.9.1'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2021-09-13T14:09:19Z</updated>
<entry>
<title>Use https config on https proxies for http servers</title>
<updated>2021-09-13T14:09:19Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2021-09-12T22:54:38Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4e04cbafe7db326b52ee650a4f4ccc3444da6890'/>
<id>urn:sha1:4e04cbafe7db326b52ee650a4f4ccc3444da6890</id>
<content type='text'>
The settings used for unwrapping TLS connections depend on the access
and hostname we connect to more than what we eventually unwrap. The
bugreport mentions CaInfo, but all other https-settings should also
apply (regardless of generic or hostname specific) to an https proxy,
even if the connection we proxy through it is http-only.

Closes: #990555
</content>
</entry>
</feed>
