ClientSessionCache is a cache of ClientSessionState objects that can be used by a client to resume a TLS session with a given server. ClientSessionCache implementations should expect to be called concurrently from different goroutines. Up to TLS 1.2, only ticket-based resumption is supported, not Se
| 371 | // SessionID-based resumption. In TLS 1.3 they were merged into PSK modes, which |
| 372 | // are supported via this interface. |
| 373 | type ClientSessionCache interface { |
| 374 | // Get searches for a ClientSessionState associated with the given key. |
| 375 | // On return, ok is true if one was found. |
| 376 | Get(sessionKey string) (session *ClientSessionState, ok bool) |
| 377 | |
| 378 | // Put adds the ClientSessionState to the cache with the given key. It might |
| 379 | // get called multiple times in a connection if a TLS 1.3 server provides |
| 380 | // more than one session ticket. If called with a nil *ClientSessionState, |
| 381 | // it should remove the cache entry. |
| 382 | Put(sessionKey string, cs *ClientSessionState) |
| 383 | } |
| 384 | |
| 385 | //go:generate stringer -linecomment -type=SignatureScheme,CurveID,ClientAuthType -output=common_string.go |
| 386 |
no outgoing calls
no test coverage detected
searching dependent graphs…