Rip out optimistic data socks handshake variant (#3875)
Optimistic data socks handshake variant violates RFC we could to ignore except total code logic brokenness.
For something like https transport code functionality depends timing of socks proxy. If socks-proxy answer before TLS handshake can to start then browser process socks handshake as server hello therefore violates TLS session.
You can't to use code fully based on race condition. You can't to fix code so it never process any input data as soon as you start TLS handshake. Only solution to rip out that code entirely.