Obtain the following information from the operator at the upstream system:
-
The locations (URLs) on the upstream server where the M3U8 manifest files are stored.
There are two URLs for a standard-class input, or one URL for a single-class input. For information about input classes and their uses, see Choosing the channel class and input class.
See the tables later in this section for the URL format and for examples.
Make a note of the full URLs.
-
The user name and password (credentials) to access the upstream server, if the upstream system requires authenticated requests, and to access the license server, if the HLS source is encrypted. You might need credentials for the upstream system, or for the license server, or both.
If you need credentials for both, the credentials must be identical for both servers. When you discussed any encryption requirements with the upstream system, you should have made sure that the license server uses the same credentials as the upstream system.
Note that these user credentials relate to user authentication, not to the protocol. User authentication is about whether the upstream system or license server will accept your request. The protocol is about whether the request is sent over a secure connection.
Upstream server is an HTTP or HTTPS server
Format of URL | http//:<web
server>[:port]/<path>/<file>.m3u8 or https//:<web
server>[:port]/<path>/<file>.m3u8 |
Example | https://203.0.113.13/sports/curling.m3u8
and
|
Upstream server is AWS Elemental MediaStore
Format of URL | mediastoressl://<data endpoint
for
container>/<path>/<file>.m3u8 |
Example |
Assume that the data endpoint for the container for one of the content sources is the following:
Assume that the The URL for one of the content sources would be:
|