Bug#482279: Same thing happens with python-pycurl

[Mike]

For me it always happens when I was on a network with a Cisco ASA/ADSM 
dynamically routing traffic using lenny's packages. As I saw it, anytime 
you ping something and get Redirect() you will always get this message 
and not be able to connect from a binary built against libgnutls. In the 
case of python-pycurl, I just rebuilt against openssl to get me around 
the error since I needed a solution immediately. Unfortunately, none of 
those networks I saw it on are available to me for testing past fixing 
the problem for the appliance-like debian image we give to customers.

Anyways, just thought I would drop in and hopefully give you guys a clue 
into reproducing this bug. Seems like a rather nasty one considering it 
can't handshake at all and ~170 packages in stable depend on this 
library. Sorry I can't be of more use.