Unexpected 10 seconds delay if TlsHostCertificateFingerprint is different
Hello,
I'm using WinSCP 6.5.1 COM Automation to access a FTPS server.
I found that during the session initialization, after the TLS handshake, if the given TlsHostCertificateFingerprint is wrong, WinSCP waits 10 seconds before sending an error "Peer certificate rejected. Disconnected from server. Connection failed.", without exchanging any data with the server meanwhile.
I think it should abort immediately after receiving the server certificate, without waiting 10 seconds.
I'm using WinSCP 6.5.1 COM Automation to access a FTPS server.
I found that during the session initialization, after the TLS handshake, if the given TlsHostCertificateFingerprint is wrong, WinSCP waits 10 seconds before sending an error "Peer certificate rejected. Disconnected from server. Connection failed.", without exchanging any data with the server meanwhile.
I think it should abort immediately after receiving the server certificate, without waiting 10 seconds.