UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1.	Login to an HTTPS site using “chrome.sockets.tcp”. Authentication using TLS. Example..

chrome.sockets.tcp.create({}, () => {
    chrome.sockets.tcp.setPaused(this._socketId, true, () => {
        chrome.sockets.tcp.connect(that._socketId, that._host, that._port /* 443 */, () => {

            chrome.sockets.tcp.secure(this._socketId, (secureResult) => {

                chrome.sockets.tcp.setPaused(that._socketId, false, () => {

                    console.log("connection complete with TLS handshake");
                });
            });

        });

    });
});

2.	Send post

var arr = this._str2ab(httpPost + '\n');
chrome.sockets.tcp.send(this._socketId, arr, () => {

});

3.	Receive response

_onReceiveCallback(receiveInfo) {
    if (receiveInfo.socketId != this._socketId)
        return;

    if (this._callbacks.recv) {
        var str = this._ab2str(receiveInfo.data);

        if (this._parser.addData(str)) {

            // GET AUTHENTICATION COOKIE TO BE USED
            // WITH OTHER REQUESTS.
            // Access the response header Set-Cookie header
            // Get authentication  cookie value to include in request
            // headers

        }
    }
}

4.	Socket is disconnected

5.	Sometime later, start a new HTTPS request to the same server ----  go to step 1. We have already been authenticated and we include the cookie in the request header. The request will FAIL in the connection handler. It is a new request, and we are unable to get out of the connection part of the socket.

What is the expected behavior?
We should be able to send out a subsequent HTTPS POST to the same server after authentication. A failure occurs in the connection logic the second attempt to send a request

What went wrong?
The second connection seems to be all messed up with handshaking. We are assuming it might have something to do with cookies. This is a Chrome Application, so there is not document cookie support. See https://developer.chrome.com/apps/app_deprecated

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 56.0.2924.87  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 25.0 r0

The TLS handshaking correctly works for the initial login/authentication. However, the second request to that server will fail