Closed (won't fix)
Project:
Node.js integration
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
12 Oct 2011 at 03:03 UTC
Updated:
28 Apr 2013 at 23:06 UTC
Jump to comment: Most recent
Comments
Comment #1
tizzo commentedI've tested it on windows xp machiens though I don't have a windows 7 machine.
Can you be more specific about browser version? According to socket.io's own docs IE should be supported back to 5.5 and we aren't doing anything to change socket.io's normal behavior. Could it be an issue with your network, selected socket.io port, firewall, etc?
What browsers have you experimented with?
Comment #2
supermouse commentedthanks tizzo.
I using window 7 and browsers google chrome , firefox , IE.
Comment #3
Gray Fox commentedDid you try using other socket connection methods, like xhr or json polling?
Comment #4
supermouse commentedI using transports ['websocket', 'flashsocket', 'htmlfile', 'xhr-polling', 'jsonp-polling'].
Comment #5
michaeljoser commentedI just realised that i am having the same problem i suppose.
On my side, I am running Windows 7 Ultimate Edition x64 and my browsers (chrome/firefox/ie) are all x64 versions and when i log in with any of those browsers, node.js (or socket.io) does not get any events.
I load up an Xubuntu x32 on virtualbox and load my site and i see the events.
Now i think this is not specific to node.js integration but it might be a socket.io issue... i will do some more testing.
UPDATE: After some testing, found out that using the following in nodejs.config.js now works:
which means that "websocket","flashsocket" results in no activity at all from my browsers.
Anyone has any idea what is going on?
Comment #6
Anonymous (not verified) commentednope, no idea, and not interested either. socket.io bugs are not for this issue queue.
Comment #7
anmolsaraf commentedThanks Dude. This solution worked for me :)