I have a client and Application server, that exchange certificates with each other and establishes a secure TLS connection.
At the end of such connection, after application data is transferred. The client sends a FIN packet to the server, in return the server replies with a TLSV1.2 encrypted alert packet.
This is further ack by the client and the client this time sends an RST packet. Could you help me decipher this behaviour. I am trying to baseline my traffic between these endpoints and later take these notes as input.
From this link here, https://serverfault.com/questions/854692/client-sends-rst-after-fin-ack it looks like the socket is not shut down before it is closed, which comes down to bad programming. I am curious to confirm whether this is the case.