New http code

[David Shaw]

Hi folks,

Now that 1.4.1rc2 is out, can I get a few people to help exercise the
new HTTP code?  There are two main tests that would be very helpful:

1) Build with the configure option --with-libcurl.  If you have
   libcurl installed, you should end up with a new program
   'gpgkeys_curl', that supports HTTP, HTTPS, FTP, and FTPS.  If you
   don't have libcurl installed, nothing should happen.

2) Build with the configure option --enable-fake-curl.  This should
   also result in a 'gpgkeys_curl', but it only supports HTTP.

Once built, if you could test the protocols by fetching some keys many
times over, trying with different servers, etc, that would be very
much appreciated.

Note that this is for files via HTTP (or HTTPS or FTP or FTPS).  It's
not full keyserver support (with searching and so on).  All you can do
is fetch keys, genenerally from a preferred keyserver URL set on a key
or signature.

To make testing easier so you don't have to keep making preferred
keyserver URLs all over the place, note you can test by doing
something like this:

gpg --keyserver http://www.example.com/a/key/is/stored/here.asc --recv-keys 99999999
or
gpg --keyserver https://www.example.com/a/key/is/stored/here.asc --recv-keys 99999999
etc.

The key stored in that file likely isn't key 99999999, but it'll work
anyway to test.

David