Reply to thread

It can theoretically cache some of the certificate’s data, but there’s a handshake process used for encryption and authentication that requires key information to be sent during each connection. If you are seeing the wrong certificate, that cannot be a caching issue: that’s server-side. It’s impossible to establish a TLS connection with the wrong cached certificate; that’s just not how TLS works.

If you’re seeing the wrong certificate but are still able to establish a connection, that’s a server side issue. If the client used the wrong certificate, the server wouldn’t be able to decrypt the stream key; if you somehow managed to bypass the handshake process with the wrong certificate, you’d still be unable to receive a response.