Tyrusclient handles same 401 not authorize response twice

Looks like Tyrus client handles same 401 not authorize response twice.

Socket acquisition is protected with OAuth2 on server side.

Firs time client tries to obtain web socket server returns "401 not Authorized".
Client sends another request with token.
Server returns "101 protocol change" but sometimes client handles the same 401 response that was sent previously and closes connection

See logs from client and Wirwshark capture in attach
#### Affected Versions
[1.13]