Home > Uncategorized > RTMP – how it make YouTube?

RTMP – how it make YouTube?

There is a problem with RTMP. It works on 1935 port. In fact it’s not a problem with RTMP but with ISP. ISP like filtering internet traffic and like packets queuing. That’s why connections on port 1935 – which is not wheel – known in Internet – work worse than connection on port 80. Adobe know that and have introduced RTMPT, which is an encapsulation of RTMP in HTTP, which works on port 80.

YouTube does something else. You see, You Tube allows recording from web cam. It uses RTMP to do that, but RTMP works on HTTP (80) port. I noticed it by using NetLimiter.

I decided to check it carefully. Is it RTMP on its unusual port or is it usual RTMPT? Using Wireshark as my oxygen supply, I dove deep in the hidden depths of the system. Wireshark allows me to sniff internet traffic. I was wondering what exactly my laptop send to YouTube. I would have expected many POST requests for RTMPT. There weren’t. It was something like

instead. rtmp:/…webcam.youtube:80/ – 99% YouTube use RTMP on port 80.

It’s an interesting idea. I can check it out to give me an idea of how to write similar routines.


Categories: Uncategorized Tags: ,
  1. Enrique
    September 2nd, 2010 at 06:23 | #1

    Hi!, did you find more info about this?
    How can be used RTMP with port 80? I’m confused…


  2. March 1st, 2011 at 17:49 | #2

    1. You can just run RTMP server on port 80.
    2. You can also RTMPT (RTMP encapsulated with HTTP).

    Both this techniques have pluses and minuses.

  1. March 25th, 2011 at 07:27 | #1