Answer for rtmpt http proxy

Hi, I’m not sure how FMS is doing that, but I can tell you for sure that is impossible to bind on the same machine IP:PORT combination from 2 different processes unless you do fork. Since FMS!=apache/nginx/etc, I think one of them (web server or apache) is forwarding the request from one ip:port to another on the same local machine/LAN. If that is the case, than one can use a so called "protocol discriminator" which sits in front of both FMS and the web server bound on port 80. Depending on what it sees on the pipe, it is going to open a connection to either the web server or FMS and forward the traffic. But, as I said, port 80 is definitely not shared. Here is some example of such a protocol discriminator: http://bernaerts.dyndns.org/linux/210-debian-sslh The magic is simple: it accepts the connection, reads the first bytes from it to figure out what kind of connection it is and that it will forward that tcp connection to an internal server (SSH, OpenVPN, HTTPS, RTMP, etc) Another solution is to bind the web server on the public ip:80 and than, depending on mod_rewrite or other decision making algorithm, forward the relevant RTMPT connections to the EMS/FMS. This can be done from apache/nginx configuration, and has absolutely nothing to do with the streaming server. I believe (not 100% sure) that FMS, when it installs itself and the apache server on windows for example, it also has a pre-define apache configuration doing exactly that. FMS doesn’t implement any weird/magic code for doing that. Apache i doing the heavy lifting. If you try to replace that apache with IIS, I bet that is no longer going to work (you need to manually configure it) Best regards, Andrei

Offcanvas

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.