-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-03-01 17:03, Phil Pennock wrote:
Folks,
We now have two separate issues affecting SKS (and GnuKS)
keyservers which have nginx or Apache in front of them, affecting
interop compatibility with various versions of GnuPG (and other
clients)
On 2013-03-06 at 18:51 -0500, Eric Benoit wrote:
Lighttpd has rather limited header manipulation facilities, at least
in 1.4.x. I was just about ready to add this feature when I came
across a not very well documented option:
server.reject-expect-100-with-417 = disable
Which when added to
Phil Pennock wrote:
Folks,
We now have two separate issues affecting SKS (and GnuKS) keyservers
which have nginx or Apache in front of them, affecting interop
compatibility with various versions of GnuPG (and other clients) as
deployed.
Even as changed clients roll out, we can expect to
On 2013-03-02 at 13:38 -0600, John Clizbe wrote:
Does not appear to be failing. I have not added the RequestHeader unset
Expect early directive you suggest. Perhaps this is sensitive to particular
releases of Apache?
That's what I was afraid of.
It's failing against keys.wuschelpuschel.org
On 2013-03-02 at 20:39 -0500, Phil Pennock wrote:
On 2013-03-02 at 13:38 -0600, John Clizbe wrote:
Does not appear to be failing. I have not added the RequestHeader unset
Expect early directive you suggest. Perhaps this is sensitive to particular
releases of Apache?
That's what I was
On 2013-03-02 at 22:21 -0500, Phil Pennock wrote:
So in fact, this is not normally biting Apache. I'll update the wiki
now.
John, Daniel: thanks for getting back to me and helping pin this down.
I've confirmed the new text is accurate. Got an Apache setup running,
passing onto the same
Folks,
We now have two separate issues affecting SKS (and GnuKS) keyservers
which have nginx or Apache in front of them, affecting interop
compatibility with various versions of GnuPG (and other clients) as
deployed.
Even as changed clients roll out, we can expect to see clients which
have
On 03/01/2013 02:03 PM, Phil Pennock wrote:
I have updated
https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Peering already.
Thank you for sorting this out, Phil, and for taking it all the way to
concrete suggestions. This is really helpful and useful.
nginx
-
[...]
Hi Phil/List,
On 01/03/2013 22:03, Phil Pennock wrote:
Apache
--
By default, breaks all clients which use a real libcurl, blocking their
ability to POST (--send-key) to the server. The clients set an Expect:
100-continue HTTP/1.1 header and unfortunately Apache actually
implements the
On 2013-03-01 at 22:36 +, Daniel Austin wrote:
I've added the config to ports 80+11371 for pgpkeys.eu (using Apache
mod_proxy) and your example config from the wiki - all tests seem to
work for me, but please feel free to test for confidence.
If all works well, i'll duplicate the
10 matches
Mail list logo
