I have successfully integrated socket.io, node.js, and express to serve real-time json data to multiple browsers except for IE (tested on version 9) over a secure connection. Everything was functioning smoothly until I switched to HTTPS. From the server's console output, it indicates that an event is received when triggered from IE:
xhr-polling received data packet 5:::{"name":"lookup_place","args":
[{"place":"Berlin"}]}
However, no response is generated and the following four lines are displayed in the console:
clearing poll timeout
xhr-polling writing 8::
set close timeout for client 27081179790885432
xhr-polling closed due to exceeded duration
When the same action is performed on FF or Chrome, the "xhr-polling writing 8::" line includes the correct response, like so:
xhr-polling writing 5:::{"name":"place_results","args":[{"a":
[{"identifier":"52156","value":"Monschau, 52156"},
{"identifier":"67590","value":"Monsheim, 67590"},
{"identifier":"04617","value":"Monstab, 04617"}]}]}
The versions of node.js, socket.io, and express used are 0.4.10, 0.7.7, and 2.4.3 respectively. These scripts were operating flawlessly in IE versions 7-9 prior to enabling HTTPS/SSL.
We would greatly appreciate any assistance in identifying the reason behind the lack of response in IE while functioning correctly in other browsers.