https://bz.apache.org/bugzilla/show_bug.cgi?id=57600

--- Comment #4 from Yann Ylavic <[email protected]> ---
(In reply to Kaspar Brand from comment #3)
> No, as it only applies to the Certificate*Request* message, not to the
> Certificate message (and CertificateRequest only comes into play when
> SSLVerifyClient isn't set to "none" [which is the default]).

Hmm ok, maybe your trick from [1] with SSLCertificateChainFile then?
The directive is deprecated in 2.4.8+ though, but it used to override
SSLCACertificate{File,Path} for the (expected) Certificate message in 2.2.
I can't tell if it still works for this purpose in 2.4 (beside the startup
warning).
Could that be an (ugly) workaround?

[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=56073#c1

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to