Lines Matching refs:sessions

9 TLS specifies logical "sessions" that get "established" on both sides when the
15 so multiple connections to the same endpoint each negotiate fresh sessions from
18 However tls servers typically maintain a cache of recent sessions, and where
23 ### Re-use of validated sessions
36 ### Multiple concurrent use of validated sessions
45 TLS also supports sessions as bearer tokens, but these are generally considered
54 MRU-sorted list of established sessions.
56 It's also possible to serialize sessions and save and load them, but this has to
78 Internally sessions are referred to by a vhostname.hostname.port tuple.
89 The Time-To-Live policy for sessions at the client can be set in seconds at
99 Trying to make sessions really persistent is supported but requires extra
112 sessions stored that way.
114 For openssl, Public APIs are provided in `libwebsockets/lws-tls-sessions.h` to