On: This is a web page

[MichaelGG]

Pretty sure YouTube is transported over HTTP. Not sure about Netflix but I wouldn't be surprised.

HTTP has become a generic TCP wrapper for the common request->response pattern.

[vacri → MichaelGG]

Wireshark doesn't think so:

9792 42.750939000 74.125.109.232 10.1.1.21 TCP 1506 [TCP segment of a reassembled PDU]

[MichaelGG → vacri]

Dunno, I tried loading a YouTube page and capturing packets. Only ports in use were 443 and 80, even to the cdn-like hostnames (bla.c.youtube.com). First packet shows "GET /videoplayback?...."

[vacri → MichaelGG]

A port number is just a port number, it doesn't define what protocol is in use. You can serve different protocols across it - the limitation is that generally you can only have one service listening on a port number. A youtube page will require a couple of different protocols.

[socillion → MichaelGG]

Youtube uses RTMP on port 80.

RTMPT is RTMP over HTTP, but Youtube doesn't use it.

https://en.wikipedia.org/wiki/Real_Time_Messaging_Protocol

[tsahyt → MichaelGG]

It is not transported over HTTP, although it does make use of HTTP at the Application Layer. It is transported over TCP, which is a Transport Layer protocol.

Yes, I'm being pedantic and annyoing.

[marshray → tsahyt]

People are using HTTP as a transport layer, e.g., websockets.

[abraininavat → marshray]

Websockets are the transport layer, built over TCP. Websockets happens to use HTTP as a protocol. That doesn't mean HTTP is the transport layer.