Direct post from Battlelog devs....
Following this fixed my issues using Avast security.
First up:
Visit http://www.adobe.com/software/flash/about/ [adobe.com] and make sure you have version 11 or later installed. Upgrade flash if there is an update available.
Update your anti-virus to the latest version
AVG, Bitdefender, Avast, and most other anti-virus programs offer free upgrades to the latest version. Do it!
Old versions are not up to date and may block legit connections.
Test websocket connections in Chrome
1. Go to http://websocket.org/echo.html [websocket.org]
2. Click on Connect. Do you get a line saying CONNECTED in the Log window?
3. Click on Send. Do you get SENT and RESPONSE lines in the Log window?
4. If you answered "No" to 2 or 3, check Use secure WebSocket (TLS) and try 2 and 3 again. Different result?
* Could you connect with/without TLS?
* Could you send messages with/without TLS?
* Could you receive messages with/without TLS?
Tested Anti-virus programs so far
LATEST version available and DEFAULT settings if not stated otherwise:
Comodo Internet Security 2011 Pro
Works.
Works also with advanced, more strict, settings such as Custom Policy chosen in Firewall settings and/or "Do protocol analysis" enabled.
Microsoft Security Essentials
Works
Norton Antivirus
Reported by users to work. Not tested by Battlelog developers.
Avast
* Avast Free Antivirus works
* Avast Pro Antivirus works
* Avast Internet Security works if web shield is disabled/stopped.
Reported to work with web shield on if you add Battlelog to the list of exceptions in the web shield. Make sure you use a asterisk at the end.
Example: *battlelog.battlefield.com/*
Also reported to work if you go into the settings and check the box "Scan known processes only". Then everything else can be left on.
Ask Avast why they block legit websocket connections here:
http://forum.avast.com/index.php?board=2.0 [forum.avast.com]
AVG
Works
Older versions block websocket connections. Upgrade!
Bitdefender
Receiving events works (with our automatic SSL workaround)
Sending chat messages etc might fail due to javascript injects by Bitdefender.
Problem:
Bitdefender injects javascript code into the page which interfere with Battlelog code.
Bitdefender blocks legit websocket connections on port 80 but accepts websocket connections using SSL.
Battlelog is forced to use SSL connections for websockets to work around the issue with receiving events.
Ask Bitdefender why they block legit websocket connections and inject javascripts that interfere with Battlelog code here:
http://forum.bitdefender.com/index.php?showforum=243 [forum.bitdefender.com]
If you use advanced settings, make sure to disable Scan SSL
If you have problems and are using version 2010 or 2011, try upgrading to the latest version. It is free of charge. See this url: http://www.bitdefender.com/support/How-to-Upgrade-from-BitDefender-2009-2010-2011-to-BitDefender-2012-711.html [bitdefender.com]
Users have reported that turning these features off makes Battlelog work with Bitdefender:
* bitdefender toolbar
* search advisor
* protection against fraud
* protection against instant messaging
Update from Bitdefender: New version out.
http://forum.bitdefender.com/index.php?showtopic=28172&st=0&p=124814&#entry124814 [forum.bitdefender.com]
Let us know if you still experience problems with the latest version.
Kaspersky
Works but we have reports about it blocking websocket connections. Update on this coming as soon as more testing has been made.
ESET NOD32
Works but you might need to turn off "advanced integration"
Trend Micro Internet Security
Works
Vipre Antivirus
Not tested by the Battlelog team, but a user reports that the "Bad Website Filtering" setting is making Battlelog not function properly, and can be disabled without disabling your anti virus or fire wall. Another user reports that full disabling of Vipre is the only working solution right now.
Other programs known to cause problems
Internet Download Manager
Plugin/addon for firefox that interferes with normal web connections and cause websocket connections to receive broken or no data.
We are working on a getting a work-around out to detect this plugin and prevent it from sending rubbish on websocket connections.