|
|
|
|
|
by Buge
3323 days ago
|
|
I don't think Keep-Alive = true would be enough. The article also mentions TLS session tickets would be necessary. And it's hard to call this a coding problem if the requirements of the API never specified that session tickets and keep alive were necessary. |
|
keep-alive keeps the HTTP/TLS socket open.
TLS session tickets allow to close and "cheaply" reopen TLS session on a new socket for a new HTTP connection.
Using both keep-alive and TLS session tickets is optimal.