-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/05/2013 01:18 PM, Kristian Fiskerstrand wrote:
| Thanks for the suggestion!
It was Phil's idea, I was just whining about the problem I saw. :)
Doug
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)
iQEcBAEBCAAGBQJRNsOOAAoJEF
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/01/2013 09:04 AM, Phil Pennock wrote:
> Short version: bad interaction of GnuPG, cURL and Apache. Can
> probably be worked around in Apache config, can definitely be
> worked around in GnuPG code, should aim to get both done.
>
...
>
> Kri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/01/2013 09:04 AM, Phil Pennock wrote:
..
>
> 417 is not load-related, Kristian's goofed.
>
> 417 _only_ happens when the client sends "Expect: 100-continue", in
> an HTTP/1.1 request, and a reverse proxy (or forward-proxy) knows
> that the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Short version: bad interaction of GnuPG, cURL and Apache. Can probably
be worked around in Apache config, can definitely be worked around in
GnuPG code, should aim to get both done.
On 2013-02-28 at 10:01 -0800, Doug Barton wrote:
> 2001:470:1f0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Wow, what a thorough analysis, thanks Phil. :) FWIW, I did see those
Expect: headers you describe in my debug output, and obviously if this
issue only affects certain servers it would explain why I was only
seeing it intermittently.
I should have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/28/2013 10:23 AM, Kristian Fiskerstrand wrote:
| On 02/28/2013 07:01 PM, Doug Barton wrote:
|> On 02/28/2013 09:44 AM, Kristian Fiskerstrand wrote: | Hi Doug,
|> |
|
|
| ...
|
|> Yes, I'm talking to different servers (as would be expected).
|>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/28/2013 07:01 PM, Doug Barton wrote:
> On 02/28/2013 09:44 AM, Kristian Fiskerstrand wrote: | Hi Doug, |
>
...
> Yes, I'm talking to different servers (as would be expected). Just
> tried it a few times ...
>
At least that explains it. Fo
-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 1A1ABC8
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
gpg: sending key D5B2F0FB to hkp server pool.s
On 2013-02-28 at 09:12 +0100, Niels Laukens wrote:
> On 2013-02-28 00:50, Phil Pennock wrote:
> > The best fix is to use gpg with a real cURL library.
>
> I'm currently using a downloaded binary from gpgtools.org. I don't see
> libcurl in the list of shared objects used by the binary (otool -L,
>
On 2013-02-27 at 10:57 +0100, Niels Laukens wrote:
> Apologies for cross-posting to both mailing lists, but since I got
> replies via both ways I feel this is the easiest way to sync them.
Current status: Kristian and I have debugged and he found the core
issue. If I load down my server, we can s
On 2013-02-28 09:36, Phil Pennock wrote:
> On 2013-02-28 at 09:12 +0100, Niels Laukens wrote:
>> On 2013-02-28 00:50, Phil Pennock wrote:
>>> The best fix is to use gpg with a real cURL library.
>>
>> I'm currently using a downloaded binary from gpgtools.org. I don't see
>> libcurl in the list of s
Thanks Phil for the very clear summary of the problem!
On 2013-02-28 00:50, Phil Pennock wrote:
> The best fix is to use gpg with a real cURL library.
I'm currently using a downloaded binary from gpgtools.org. I don't see
libcurl in the list of shared objects used by the binary (otool -L,
Mac's e
14 matches
Mail list logo
