Since the issue was also reported as a bug for IO::Socket::SSL: You can find a detailed explanation what the reason for the behavior is and why this is not a bug in IO::Socket::SSL but a bug in the application at the github repository for IO::Socket::SSL.