Real Time Messaging Protocol - HTTP Tunneling (RTMPT)

HTTP Tunneling (RTMPT)

This refers to the HTTP tunneled version of the protocol. It communicates over port 80 and passes the AMF data inside HTTP POST request and responses. The sequence for connection is as follows:

POST /fcs/ident2 HTTP/1.1 Content-Type: application/x-fcs\r\n HTTP/1.0 404 Not Found POST /open/1 HTTP/1.1 Content-Type: application/x-fcs\r\n HTTP/1.1 200 OK Content-Type: application/x-fcs\r\n 1728724019

The first request has an /fcs/ident2 path and the correct reply is a 404 Not Found error. The client then sends an /open/1 request where the server must reply with a 200 ok appending a random number that will be used as the session identifier for the said communication. In this example 1728724019 is returned in the response body.

POST /idle/1728724019/0 HTTP/1.1 HTTP/1.1 200 OK 0x01

From now on the /idle// is a polling request where the session id has been generated and returned from the server and the sequence is just a number that increments by one for every request. The appropriate response is a 200 OK with an integer returned in the body signifying the interval time. AMF data is sent through /send//