-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/28/2013 09:44 AM, Kristian Fiskerstrand wrote: | Hi Doug, | | | On 02/28/2013 06:35 PM, Doug Barton wrote: |> Phil, | |> Could this curl issue be the cause of this error that I've been |> seeing the last few days: | |> gpg: sending key 1A1ABC84 to hkp server pool.sks-keyservers.net |> gpgkeys: HTTP post error 22: The requested URL returned error: |> 417 Expectation Failed | | | The 417 return code is typically used by a reverse proxy if the | backend (i.e. SKS) is non-responsive, so intuitively that is a | separate matter. Please add --keyserver-options verbose,debug to | see if you're talking to different servers.
Yes, I'm talking to different servers (as would be expected). Just tried it a few times ... 2001:470:1f09:5e7::2 worked 2001:470:1f0a:5d7::2 failed In any case thanks for clarifying the cause of the error ... it's just hard to debug without putting those options in first obviously, and with those options the output is very noisy. GnuPG folks, would it be possible to add a keyserver-option to show the IP address of the server connected to? I could live with that full time, and it would make reporting errors a lot easier. Doug -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQEcBAEBCAAGBQJRL5t6AAoJEFzGhvEaGryEOhEIAM3M29gBHr2Y855kJxuw9b+F j+kPmf+zTEBERWo7H4if+qBQ54jdubQ06G96ejYd7f+4kMlP7+KycB0kOWWBdRH0 J/w8VyYzaVVKLIi6QudzpuZ8g3SYz4auVoOjwSBYWUX3d9RUHgajpYgVaZIIEs9n RqCUrf6PdBgR08bOYX/jXRiaBqTdTCgQkzRd06hgjY0i+jo3AfJJuqdwKnGerZyi CE8AF8FfY2eIBxS1tmnA6S6tPiN080Xj+oWGA0t3B91hSGBLCJGFYe0OdJDlkM/1 A129MHfYqHVnzH1CCPITkb+v6r00RcqwkHOtt18ZH+CrUHBMz+ehTTsfqq5Tvpk= =U6+f -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
