ton" <[EMAIL PROTECTED]>
To: "Marc Stern" <[EMAIL PROTECTED]>
Cc: "Apache development list"
Sent: Wednesday, March 22, 2006 2:21 PM
Subject: Re: SSL_CLIENT_CERT header bad format
On Wed, Mar 22, 2006 at 11:44:08AM +0100, Marc Stern wrote:
I use %{SSL_CLIENT_
On Wed, Mar 22, 2006 at 11:44:08AM +0100, Marc Stern wrote:
> I use %{SSL_CLIENT_CERT}e with 2.0.54 (patched to get mod_ssl headers).
> Is this the problem ? Was it fixed after 2.0.54 ?
Yes, 2.2.0 has the %{...}s support which does this properly. There's a
backport for 2.0 here:
http://people.ap
uot;
Sent: Wednesday, March 22, 2006 9:57 AM
Subject: Re: SSL_CLIENT_CERT header bad format
On Wed, Mar 22, 2006 at 08:28:35AM +0100, Marc Stern wrote:
It seems that the PEM-encoded certificate coming out of OpenSSL (0.9.8a
in
my case) contains new lines without leading space, which is int
On Wed, Mar 22, 2006 at 08:28:35AM +0100, Marc Stern wrote:
> It seems that the PEM-encoded certificate coming out of OpenSSL (0.9.8a in
> my case) contains new lines without leading space, which is interpreted as a
> new HTTP header.
In what configuration does this happen? If you are using
%{SS
It seems that the PEM-encoded certificate coming out of OpenSSL (0.9.8a in
my case) contains new lines without leading space, which is interpreted as a
new HTTP header.
Even more important, the last empty line leads to 2 new lines without
leading space, which is interpreted as the end of all HTTP
