keyserver scheme http broken?

[Bernhard Reiter]

I might miss something here, but for me on gnupg 2.0.13 (and 2.0.11)
retrieving keys via the "http://" scheme seems to be broken.

(Also it seem that --search-keys does not work with "http", although a lot of 
people claim that "http" is just "hkp" over port 80. )
Any ideas?

gpg2 --keyserver hkp://pgp.surfnet.nl --keyserver-options 
verbose,verbose,verbose,debug --recv-keys DA4A1116
gpg: fordere Schlüssel DA4A1116 von hkp-Server pgp.surfnet.nl an
gpgkeys: curl version = libcurl/7.15.5 GnuTLS/1.4.4 zlib/1.2.3 libidn/0.6.5
Host:           pgp.surfnet.nl
Command:        GET
gpgkeys: HTTP URL is 
`http://pgp.surfnet.nl:11371/pks/lookup?op=get&options=mr&search=0xDA4A1116'
* About to connect() to pgp.surfnet.nl port 11371
[..]
-> works!

gpg2 --keyserver http://http-keys.gnupg.net --keyserver-options 
verbose,verbose,verbose,debug --recv-keys DA4A1116                            
gpg: fordere Schlüssel DA4A1116 von http-Server http-keys.gnupg.net an
gpgkeys: curl version = libcurl/7.15.5 GnuTLS/1.4.4 zlib/1.2.3 libidn/0.6.5
Scheme:         http
Host:           http-keys.gnupg.net
Path:           /
Command:        GET
* About to connect() to http-keys.gnupg.net port 80
*   Trying 194.171.167.98... * connected
* Connected to http-keys.gnupg.net (194.171.167.98) port 80
> GET / HTTP/1.1
Host: http-keys.gnupg.net
Accept: */*
Pragma: no-cache
Cache-Control: no-cache

< HTTP/1.0 200 OK
< Server: sks_www/1.1.0
< Content-type: text/html; charset=UTF-8
* Closing connection #0
gpgkeys: no key data found for http://http-keys.gnupg.net/
gpg: Keine gültigen OpenPGP-Daten gefunden.
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 0
random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
              outmix=0 getlvl1=0/0 getlvl2=0/0
secmem usage: 0/32768 bytes in 0 blocks
bernhard at ploto:~$ gpg2 --keyserver http://pgp.surfnet.nl --keyserver-options 
verbose,verbose,verbose,debug --recv-keys DA4A1116
gpg: fordere Schlüssel DA4A1116 von http-Server pgp.surfnet.nl an
gpgkeys: curl version = libcurl/7.15.5 GnuTLS/1.4.4 zlib/1.2.3 libidn/0.6.5
Scheme:         http
Host:           pgp.surfnet.nl
Path:           /
Command:        GET
* About to connect() to pgp.surfnet.nl port 80
*   Trying 194.171.167.98... * connected
* Connected to pgp.surfnet.nl (194.171.167.98) port 80
> GET / HTTP/1.1
Host: pgp.surfnet.nl
Accept: */*
Pragma: no-cache
Cache-Control: no-cache

< HTTP/1.0 200 OK
< Server: sks_www/1.1.0
< Content-type: text/html; charset=UTF-8
* Closing connection #0
gpgkeys: no key data found for http://pgp.surfnet.nl/
gpg: Keine gültigen OpenPGP-Daten gefunden.
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 0
random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
              outmix=0 getlvl1=0/0 getlvl2=0/0
secmem usage: 0/32768 bytes in 0 blocks

(I've also tried this with the other http-key servers from 
http://keystats.gnupg.net/)

Best,
Bernhard
-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20091112/99012db2/attachment.pgp>