gnupg --fetch-key problems

Werner Koch wk at
Tue Sep 1 10:10:39 CEST 2020

On Mon, 31 Aug 2020 02:48, Ángel said:

> HTTP/1.1 would require support for things that currently may not be
> present, such as chunked transfer encodings, whereas HTTP/1.0 is

That is for the server site but not for the client.  IIRC, the only
mandatory request header for a client has is "Host:".  This is optional
in 1.0 but we have always send this.  I see no benefit for requiring 1.1
and also no reason why a site should block 1.0 - that would be a pretty
lame DoS mitigation because bots could also send 1.1 without any
problems but don't do so because it is not needed.

> I agree it should provide an User-Agent, though.

There is no User-Agent header to minimize the amount of identifiable
information.  You want a User-Agent header to make debugging requests



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <>

More information about the Gnupg-users mailing list