Tcp/Ip connections broken when using v24.0.0.194, was fine with 186

Report · Jan 10, 2017

have not had time to investigate this fully, and will update tomorrow. It maybe the same thing as this report here

As I need to get set up to debug. My application is loading from a server, and the first thing it wants to do, is send a request back to the same server, to get more code loaded. So the above report could easily be the same issue.

My code is opening up a tcp/ip socket connection, and that is never being seen at the server.

Thank you for your time.

Jay

Report · Jan 11, 2017

Hi,

Thanks for reporting the issue. We are investigating it.

Report · Jan 11, 2017

Sorry for the inconvenience. Flash Player has historically blocked communication on a number of ports. As Flash and the Internet continue to grow and mature, it's important that Flash behaves as a responsible citizen in regard to the larger ecosystem. In many instances, this means ensuring that Flash Player conforms to limit its capabilities to match those available through HTML and JavaScript.

While updates to the official documentation are forthcoming, I can confirm that we've expanded the list of blocked ports to include the following:

1, 7, 9, 11, 13, 15, 17, 19, 21, 22, 23, 25, 37, 42, 43, 53, 77, 79, 87, 95, 101, 102, 103, 104, 109, 110, 111, 113, 115, 117, 119, 123, 135, 139, 143, 179, 389, 465, 512, 513, 514, 515, 526, 530, 531, 532, 540, 556, 563, 587, 601, 636, 993, 995, 1720, 1723, 2049, 3659, 4045, 5060, 6000, 6566, 6665, 6666, 6667, 6668, and 6669.

You'll need to update the Flash content and the socket server to communicate on a different port that isn't in the list above.