
Not far off the influx of html5 applications. For users, this is even more interactive and new features, primarily due to local storage and websockets technologies. For developers, this is another compatibility headache. The first hit below the belt was struck by the Firefox4 and Opera11 commands, banning websockets support by default. The developers have endured, placing in their faq instructions how to turn them on and placing a lining in the form of a flash component that emulates websockets support for absolutely outdated browsers.
When translating
the Trelljack Club with the comet long polling event processing to the websockets model, we were faced with the fact that the trouble came from where it was not expected. And she came from the camp of antiviruses.
Tested on a large number of combinations of browsers and operating systems, the application refused to work for a significant layer of users. It turned out that they all used Avast antivirus in the default configuration. It includes the so-called “Web screen” mode, which decided that the ws protocol is bad and should be silently cut. Avast evangelists, in turn, vaguely
troll with links about “Web standards” without understanding their essence (this question was repeatedly discussed at habré).
According to the old Russian custom, after closing the question “who is to blame?”, They usually raise the question “what to do?”. We have already
faced with the insane behavior of antiviruses. In that case, the answer was obvious. This is much more complicated. Convincing users to turn off the "Web screen", change the antivirus / browser / operating system, as practice shows, is not particularly effective. Throwing avast support with requests to remove this check, or at least allow users to customize the list of exceptions for specific sites - akin to complaints to Sportloto and the League of Nations.
')
It only remains to wait. Wait for the heavyweights and google / facebook / ... to catch up and release the websocket applications that are very, very necessary for users. And then the producers of [anti] viruses will not get out.
In conclusion, I would like to say the following. If you suddenly stopped working some site or service, do not rush to write off all the curves hands of developers. Perhaps the suddenly updated antivirus decided to review your security policy.