All geek questions in one place

Persistent HTTP connection and ssl session

HTTP is the application protocol, and the underlying TCP connection can be closed and open without affecting the HTTP application (other than performance).
Using HTTP1.1, we use persistent connections, but still the server or client can close the connection at any time.
For security, HTTP uses TCP over SSL / TLS.
I understand that SSL acts just like an application, at least this is how TCP “looks through” SSL.
My question is that the nearest TCP socket closes at a certain point after a secure connection is established, does this mean that the SSL session is becoming invalid, and the parties should start working on ssl acknowledgment?
Or is the underlying TCP connection not related to the TLS session?

Thank!

+3
source share
2 answers

Does this mean that the SSL session is becoming invalid and the parties should start via ssl handshake?

Yes, the SSL / TLS session has ended and the acknowledgment should be restored. TLS includes mechanisms for resuming a session (some operations will still be performed, but less than with a full handshake), but not all applications support it.

See http://ietf.org/rfc/rfc2246.txt , F.1.4 for technical details on renewal.

+3
source

http://publib.boulder.ibm.com/httpserv/ihsdiag/ihs_performance.html#SSL :

SSL - - . SSL , , . , , SSL.

. TCP-, SSL . SSL , SSL. , TCP- ( 80% ). - SSL. - .

+2

Source: https://habr.com/ru/post/1785739/

More articles:


All Articles