Persistent HTTP connections: use same TCP/TLS connection for all messages of a transaction

mpeylo / cmpossl

An OpenSSL-based implementation of the Certificate Management Protocol (CMP), defined in IETF RFCs 4210, 4211, and 6712. It is being extended according to the emerging RFCs 'CMP Updates' (CMPv3), 'CMP Algorithms', and 'Lightweight CMP Profile'.

https://github.com/mpeylo/cmpossl/wiki

Other

35 stars 13 forks source link

Persistent HTTP connections: use same TCP/TLS connection for all messages of a transaction #217

Closed DDvO closed 3 years ago

DDvO commented 3 years ago

When using HTTP(S) as message transfer mechanism, currently the TCP connection is closed after each request-response round-trip. It would be more efficient to keep it open for all parts of the same transaction. At HTTP level this is known as persistent connections: https://tools.ietf.org/html/rfc7230#section-6.3 .

This is relevant only for more complex transaction that use confirmation or polling.

DDvO commented 3 years ago

Persistent HTTP connections is also of more general interest for the OpenSSL HTTP client: https://github.com/openssl/openssl/issues/14004 and will be tackled soon.

DDvO commented 3 years ago

Done by https://github.com/openssl/openssl/pull/15053.