The new version of Chrome errors out with "Unexpected Code 200" -- apparently the latest update now requires a protocol transfer code "101 Switching Protocols" instead of "200 OK" to be sent in the response or else Chrome will reject the websocket connection.
I've been searching through the CFC but I'm beginning to fear that the handshake is in the JAR somewhere (although I will be the first to tell you I know very little about how this all works, I'm probably totally off base). Any suggestions?
The new version of Chrome errors out with "Unexpected Code 200" -- apparently the latest update now requires a protocol transfer code "101 Switching Protocols" instead of "200 OK" to be sent in the response or else Chrome will reject the websocket connection.
I've been searching through the CFC but I'm beginning to fear that the handshake is in the JAR somewhere (although I will be the first to tell you I know very little about how this all works, I'm probably totally off base). Any suggestions?