Manage multiple HTTP-based connections over a single TCP session with Wowza Streaming Engine

Some HTTP playback clients use a "keep-alive" (persistent) connection with the server, which allows the player to send multiple HTTP requests to the server within the same TCP session. This speeds content loading in the player because the TCP session doesn't close and reopen for each request for content from Wowza Streaming Engine™ media server software.

Wowza Streaming Engine or later supports multiple HTTP connections per TCP session through the httpMaxHTTPSessionsPerTCPSession property. If, however, you encounter a player that doesn't properly manage or close multiple sessions, you may want to disable the persistent connection. Alternatively, you may want to specify a certain number of allowable sessions in order to control the load on your server's CPU.

The httpMaxHTTPSessionsPerTCPSession property applies to all supported HTTP streaming protocols, including Apple HLS, Adobe HDS, and MPEG-DASH. To customize it, edit it in the Application.xml file.

  1. In a text editor, open [install-dir]/conf/Application.xml and add the following property in the <HTTPStreamer>/<Properties> section:

  2. For the value:
  • Specify 0 (the default) to allow unlimited HTTP connections per TCP session.
  • Specify 1 to allow only a single HTTP connection per TCP session.
  • Specify a different positive integer to allow that many HTTP connections per TCP session.

When the maximum is reached, an additional TCP session is automatically created to handle the HTTP connections.

  1. Save your changes and restart Wowza Streaming Engine so that they take effect.