manipulate session cache
adds the session c to the context
ctx. The reference count for session
c is incremented by 1. If a session with the same
session id already exists, the old session is removed by calling
removes the session c from the context
ctx and marks it as non-resumable.
SSL_SESSION_free(3) is called once for
When adding a new session to the
internal session cache, it is examined whether a session with the same
session id already exists. In this case it is assumed that both sessions are
identical. If the same session is stored in a different
SSL_SESSION object, the old session is removed and
replaced by the new session. If the session is actually identical (the
SSL_SESSION object is identical),
is a no-op, and the return value is 0.
If a server
SSL_CTX is configured with the
SSL_SESS_CACHE_NO_INTERNAL_STORE flag then the
internal cache will not be populated automatically by new sessions
negotiated by the SSL/TLS implementation, even though the internal cache
will be searched automatically for session-resume requests (the latter can
be suppressed by
So the application can use
directly to have full control over the sessions that can be resumed if
The following values are returned by all functions:
- The operation failed. In case of the add operation, it was tried to add the same (identical) session twice. In case of the remove operation, the session was not found in the cache.
- The operation succeeded.
ssl(3), SSL_CTX_set_session_cache_mode(3), SSL_SESSION_free(3)
SSL_CTX_remove_session() first appeared in SSLeay
0.8.0 and have been available since OpenBSD 2.4.