logo       

[issue739] recv-keys fails when built without libcurl and using polipo prox: msg#00028

web.polipo.user

Subject: [issue739] recv-keys fails when built without libcurl and using polipo proxy

On Tue, Dec 05, 2006 at 01:49:24PM +0100, Juliusz Chroboczek wrote:
>
> It's a bug in GnuPG. GnuPG will send the request to the proxy and
> then shutdown the write side of the connection, i.e. it uses
> a half-open connection to get the reply. Since HTTP doesn't allow
> half-open connections, Polipo assumes that a FIN segment from the
> client means that it has closed the connection, and hence shuts the
> connection down.
>
> As working around that would impair Polipo's performance, I'm not
> going to work around it. Would you be willing to report this bug with
> the GnuPG people?

I'm afraid this is way beyond me, so I will just forward Werner's
response here:

> Werner Koch <wk@xxxxxxxxx> added the comment:
>
> Can you please point me to relevant part of the standard which does not allow
> to
> close the write end of a connection?
>
> ----------
> status: unread -> chatting
>
> _________________________________________
> g10 Code's BTS <gnupg@xxxxxxxxxxxxxxxx>
> <https://bugs.g10code.com/gnupg/issue739>
> _________________________________________

Please note that AFAIK, the problem only occurs with GnuPG versions
1.4.3 and up if GnuPG is built *without* libcurl. Building with
libcurl, which GnuPG will do by default if it finds it, appears to take
care of the problem.

-ukh

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise