Stockguy22.com WebSocket Test Information

General Information

For everything to work properly on the Stockguy22.com website you will need a modern browser that supports WebSockets. Certain firewalls will block the ports required for WebSockets to function properly.

 

Test Link for Stockguy22

https://members.stockguy22.com:843/interface

If you see the following response;

{
“message”: “ok”
}

then you should be able to connect to all services.

 

General WebSocket Test

You can visit this link below to check the functionality of your browser and firewall.

http://websocketstest.com/

 

Firewall Information and Testing

 

Windows Defender

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port

Microsoft Security Essentials

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port

Avast Internet Security

The only change I made was removing the local network from the friends list. Production sites tend to be outside that range as well.

With no firewall active, all browsers connect to port 4000
FF / IE, firewall blocks 4000: both 80 and 843 work
Chrome, FW: Oh dear, Avast eats our WebSocket at port 80, port 843 works.
Note, this research was done using avast 6.0.1289 or older. The version 6.0.1367 seems to fix at least some of the issues.

McAfee Total Protection 2011

Interestingly enough, McAfee notified me of a Trojan my VM appeared to have, and that Windows Defender and Avast never mentioned. Interesting.

With no firewall active, all browsers connect to port 4000.
Firewall on: Both 80 and 843 work, for all browsers.

Norton Internet Security 2011

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port

ESET Smart Security 5

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port
It does however block WebSocket connections from localhost

ZoneAlarm Extreme Security

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port

Panda Internet Security

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port

Comodo Internet Security Pro 2011

Interestingly enough, Comodo cried wolf about the entries in the hosts file that Parallels put there, classing it as a trojan. It also claimed to find a worm in Silverlight that no other package had found.

I assume Comodo’s free firewall is the same as the one included in this package, so I didn’t test it separately.

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port

Kaspersky Internet Security 2011

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port

AVG Internet Security 2012

The first one to ask questions about the browser opening connections to Node on port 4000. After that it’s smooth sailing.

No questions asked about port 80 or 843 under Firefox
WebSockets get blocked on all ports, despite AVG’s logs showing the connection was allowed.
Non-websocket transports work fine, apart from the initial question whether the user wants to allow their browser to connect to the internet.

Avira Antivirus Premium

The trial version wouldn’t let me enable the firewall… There is some web protection stuff in there, but it doesn’t block any connectivity.

Bitdefender Total Security 2012

Bitdefender has a fair bit of options to make the firewall super paranoid. Wonderful, let’s switch on ALL the options… =]

Allows Firefox to connect on any port
WebSockets are blocked, but Chrome falls back to XHR-polling. Bitdefender logs it as stealth traffic.

Trend Micro Titanium Maximum Security 2012

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port

Online Armor++

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port

Privoxy

I used Privoxy’s default settings. Since the user can cook up any rule they want, it would be possible to block the handshake, I think, but I don’t consider it very likely.

Chrome can do its WebSockets magic through any available port
Other browsers can connect through any available port