On Sat, Oct 01, 2016 at 04:12:56PM +, Salz, Rich wrote:
> Sessions are the server holds the state and the client sends a session-id.
The client always holds (the client side of the) state. What varies
is how much (server) state is also stored at the server.
> Tickets are the client holds th
On Sat, Oct 01, 2016 at 04:05:32PM +, Daniel Janzon wrote:
> Hm... Thanks, but I think I miss some piece of the puzzle. How does client
> and server side session differ and how do they interact? I thought the TLS
> session was always cached on the server side and all the client would have
> to
Sessions are the server holds the state and the client sends a session-id.
Tickets are the client holds the state and sends it to the server.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hm... Thanks, but I think I miss some piece of the puzzle. How does client
and server side session differ and how do they interact? I thought the TLS
session was always cached on the server side and all the client would have
to do was to send its session ID.
On Fri, Sep 30, 2016 at 12:00 AM Viktor
> On Sep 29, 2016, at 11:55 AM, Daniel Janzon wrote:
>
> For performance testing purposes, I would like to turn off session reuse in
> the (homegrown) client I use for testing. Is there a function in the openssl
> library to do it?
>
> I tried googling for "openssl client don't send session i
Hi!
For performance testing purposes, I would like to turn off session reuse in
the (homegrown) client I use for testing. Is there a function in the
openssl library to do it?
I tried googling for "openssl client don't send session id" but I didn't
find anything useful.
Cheers,
Daniel
--
openssl
