I would like to better understand the implications of maintaining a long lived (hours, days) TLS connection with respect to certificate revocation. As I understand TLS, the client verifies the server's certificate during the handshake and then never again for the duration of the connection.
After establishing a long lived connection, if the server's certificate were to be revoked, I expect that a client which uses OCSP to check revocation would not discover that the server's certificate has been revoked until the next time it establishes a new connection to that server. I suppose the client could periodically check the server's certificate status in a background thread while the connection is open, but I am not familiar with any guidance that recommends checking revocation this way.
Generally, how do TLS clients with long lived connections mitigate the risk of certificate revocation? Do they periodically reestablish connections to force a new handshake?