> I think it is the first time we see your patches around here. > Welcome to Git developer community. First time, yes thank you. I'm also not able to use a client that normally allows setting headers like in-reply-to (I am hoping mailto: works here), so I am hoping this works, and I will take any advice on that situation if possible. > I wonder if we can add some tests for the feature, though. I would love if there was a way to test it. But my historical understanding of this issue is that it has been repeatedly not merged in due to lack of anyone knowing how to test it, given the nature of a hardware token (what this is especially focused at explicitly enabling) generally being hardware. Technically, I am sure pkcs11 can apply to software tokens, but I have never ventured the topic. I'm also aware KVM+Qemu+Libvirt allows creating virtual smart cards, but I also have not ventured that topic. I have been following this issue since May of last year in private support tickets, and I do not feel I am able to contribute anything that has not already been pondered over this issue. I strongly welcome ideas, though. 0a01d41e (http: add support for different sslcert and sslkey types., 2023-03-20) does solve our main issues (which is absolutely wonderful), and this is only to finish it up with documentation, and proxySSLCertType does not personally affect me, so I am not bothered with the wait associated first consulting on proper testing. Although, it would be a shame to see this fail to get pushed in again. Thanks, Ricky Davidson
