Using the HTTP protocol
Applies To: Windows Server 2008, Windows Server 2008 R2
You can use HTTP to stream content from an encoder to a Windows Media server, to distribute streams between computers running different versions of Windows Media Services or computers that are separated by a firewall, and to download dynamically-generated playlists from a Web server. HTTP is especially useful for clients that receive streaming content through a firewall because HTTP is usually set up to use port 80, which is not blocked by most firewalls.
You can use HTTP to deliver streams to all Windows Media Player versions and to other Windows Media servers. If a client uses HTTP to connect to the server, protocol rollover is not used.
Windows Media Services uses the WMS HTTP Server Control Protocol plug-in to control HTTP-based client connections. You must enable this plug-in for Windows Media Services to use HTTP to stream content to clients or to receive streams from an encoder.
When you enable the WMS HTTP Server Control Protocol plug-in, it tries to bind to port 80. If another service, such as Internet Information Services (IIS), is using port 80 on the same IP address, then you cannot enable the plug-in. You can resolve the port conflict by either adding IP addresses to your server or by changing the port that Windows Media Services uses for HTTP streaming.
When setting up distribution servers to use Fast Streaming, use either the RTSPT or HTTP protocols to connect to the origin server.
Clients that receive a HTTP broadcast stream may not be able to reconnect to the stream for a period of up to 90 seconds after the stream ends. This delay occurs because the Windows Media server holds the data path open after the content ends to receive logging data.
The HTTP protocol is also used when a server running Windows Media Services is streaming a dynamic playlist generated by an ASP page or Web script.