Comment 9 for bug 1865900

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Bug #1834671 also has this possible workaround:
Another workaround is to move the SSLVerifyClient config to the vhost level. It it applied to the whole vhost, and there are no exceptions in specific blocks, then a re-negotiation isn't triggered and the problem doesn't happen.

i.e., it's the change in ssl configuration inside a vhost that triggers the PHA, from my understanding.