On 8/04/2013 4:24 a.m., Christopher H. Laco wrote:
Ok, I've solved this as much as I need too without digging into the
squid source itself.
I fired up tcpdump and took a capture of the failed attempt from the
proxy to the keyserver using 3.1.19, then a capture of the successful
attempt from the
On 7/04/2013 6:45 a.m., Christopher H. Laco wrote:
I'm currently in the process of testing some software installs behind
a proxy and ran into something I don't quite understand.
While running behind a Squid proxy, apt-key calls were failing to
process key requests. The same requests run fine
I'm not an http/proxy guru. What I think is happening is that the
local Squid proxy receives the X-Cache MISS from upstream, and simply
halts the response as if it were a peer.
You say that BUT... the entire information about the failure consists of:
curl -vhttp://keyserver.ubuntu.com
Ok, I've solved this as much as I need too without digging into the
squid source itself.
I fired up tcpdump and took a capture of the failed attempt from the
proxy to the keyserver using 3.1.19, then a capture of the successful
attempt from the proxy to the keyserver using 3.3.3
(sorry for the
I'm currently in the process of testing some software installs behind
a proxy and ran into something I don't quite understand.
While running behind a Squid proxy, apt-key calls were failing to
process key requests. The same requests run fine directly connected to
the internet.
From a machine
