>It seems some browsers open three to five sockets at the same time and
then don't complete SSL negotiation on all of them, just closing them
in various states.
Yes, this is exactly what they do.
> error:140E0197:SSL routines:SSL_shutdown:shutdown while in init,
> State: SSL negotiation finished successfully
And lots more similar overnight:
error:140E0197:SSL routines:SSL_shutdown:shutdown while in init, State:
TLSv1.3 early data
It seems some browsers open three to five sockets at the
> Is it possible the browsers are trying to send early data?
I doubt it, I was not reporting the error, trying to report errors
before they disappear with clean-up code is an art, and does not always
work, so mostly I now see:
error::lib(0):func(0):reason(0), State: TLSv1.3 early data,
Is it possible the browsers are trying to send early data?
On 23/03/2020 12:06, Angus Robertson - Magenta Systems Ltd wrote:
>>> My public web servers shows several handshake failures daily
>>> due to 'TLSv1.3 early data', sometimes after a previous
>>> successful TLSv1.3 connection, but not always.
>>
>> Do you have specific error messages?
>
> I
> > My public web servers shows several handshake failures daily
> > due to 'TLSv1.3 early data', sometimes after a previous
> > successful TLSv1.3 connection, but not always.
>
> Do you have specific error messages?
I seem to only report the state rather than an error once the socket is
On 23/03/2020 11:09, Angus Robertson - Magenta Systems Ltd wrote:
> My public web servers shows several handshake failures daily due to
> 'TLSv1.3 early data', sometimes after a previous successful TLSv1.3
> connection, but not always.
Do you have specific error messages?
>
> I'm not
My public web servers shows several handshake failures daily due to
'TLSv1.3 early data', sometimes after a previous successful TLSv1.3
connection, but not always.
I'm not currently attempting to handle any early data, I thought it was
disabled by default.
Is there something I should be doing
