On 7/1/19 7:23 PM, Jaikiran Pai wrote:
Hello Tony,
On 01/07/19 10:28 PM, Anthony Scarpino wrote:
Hi,
You are correct this behavior is a result of stateless resumption.
The stateless servers does not keep session state information and is
currently opt-out.
Thank you for looking into this and
Hello Tony,
On 01/07/19 10:28 PM, Anthony Scarpino wrote:
> Hi,
>
> You are correct this behavior is a result of stateless resumption.
> The stateless servers does not keep session state information and is
> currently opt-out.
Thank you for looking into this and providing the details.
> The
Hi,
You are correct this behavior is a result of stateless resumption. The
stateless servers does not keep session state information and is
currently opt-out. The system property
'jdk.tls.server.enableSessionTicketExtension' set to false will return
the server to stateful. The client side
Hi
Session ids can change due to the way the way stateless operates in the RFCs,
particularly if a client doesn’t provide a session Id during resumption. I can
take a look at your test and let you know what I find.
Thanks
Tony
> On Jun 30, 2019, at 10:38 PM, Jaikiran Pai wrote:
>
> It loo
