Websockets and HTTPS scanning

[REDACTED]

Hello,

I work for an online site which provides to customers streaming data over a websockets. We had many users complaining about streaming not working any more lately, we discovered they all had Avast installed and that removing the "Enable HTTPS scanning" tick in the web shield settings solved the issue. Our websockets was replying from port 7000, we though that could be the issue so we changed port to 80. I can replicate the issue on a laptop with Avast free installed. From the page websockets.org I can see some websockets are not affected by this issue so my question is: What Avast doesn't like about our own websockets?

Thanks in advance

Carlo

[Asyn]

You can contact Avast here: http://www.avast.com/contact-us.php

[REDACTED]

I have done that but I though a discussion here with Avast employees could benefit other developers facing the same issue. If they reply and I manage to solve the issue I will publish the outcome here.

[bob3160]

Thanks.

[REDACTED]

Just an update, no reply from them so far, I'll keep you posted