Engine socket fails for createSocket() about conscrypt HOT 5 CLOSED

@yschimke still targeting 1.0.0.

from conscrypt.

@nmittler Curious if this is an expected behaviour.

Technically it is within spec, so I can workaround it instead.

public Socket createSocket() throws IOException
Creates an unconnected socket.
Throws: IOException - if the socket cannot be created

from conscrypt.

@yschimke yeah that's an artifact of the fact that our engine socket uses the socket wrapper which places a restriction on the connection state of the underlying socket (which in this case is unconnected). This seems like a bug. Thanks for reporting!

I'm working on major changes to the engine socket and have just about all of our integration tests passing with it now. I'll try to include this fix as well.

from conscrypt.

@nmittler Are these for 1.1.0 as the current SNAPSHOT indicates? or are you actually still working on 1.0?

from conscrypt.

working with latest master

from conscrypt.