On 8/28/20 1:18 PM, antlists wrote:
The main reason other applications use "TCP over HTTP(S)" is because
stupid network operators block everything else!
I agree that filtering is a problem.
I also think that it's something that most people can overcome when they
control the firewall between the private LAN and the Internet. (Your
typical SOHO NATing gateway.)
The few times that I have run into filtering, it has been for
uninitiated inbound connections. I've almost always been able to
initiate outbound connections to / from odd ports. The few times that I
could not do so in the last 20 years were resolved by engaging the ISP
and ... politely ... getting them to knock it off. Inbound can be more
tricky. But even inbound HTTP(S) was subject to the same problems.
Actually, inbound HTTP(S) was more of a problem than other ports.
--
Grant. . . .
unix || die
