I'm having an issue playing an hls audio stream. When I make the initial manifest call I'm required to include a udid in the query string.
The problem is that this udid is being appended to the first stream m3u8 which gets it rejected by the server. Has anyone have this problem and is there a way to get around it? Or is this operator error (me). Below are the calls reported by roSystemLog. I've obfuscated the domains and ip addresses.
Thanks,
Brent
<Component: roAssociativeArray> =
{
Datetime: <Component: roDateTime>
HttpCode: 200
LogType: "http.connect"
Method: "GET"
OrigUrl: "https://mystreamserver.com/stream/7484/manifest/digitalstations/playlist.m3u8?udid=a0793427-94d3-5dc..."
Status: "ok"
TargetIp: "1.1.1.1"
Url: "https://mystreamserver.com/stream/7484/manifest/digitalstations/playlist.m3u8?udid=a0793427-94d3-5dc..."
}
<Component: roAssociativeArray> =
{
Datetime: <Component: roDateTime>
HttpCode: 400
LogType: "http.connect"
Method: "GET"
OrigUrl: "https://mystreamserver.com/stream/7484/listen/9c85256d-479b-52d3-9b18-f902567b6a21/high/stream.m3u8?..."
Status: "ok"
TargetIp: "1.1.1.1"
Url: "https://smartstreams.radio.commystreamserver.com/stream/7484/listen/9c85256d-479b-52d3-9b18-f902567b..."
}
Hi @bbonet-entercom,
Have you tried setting the Content metadata ForwardQueryStringParams flag to false? It is set to true by default. It controls whether the query string parameters from the initial HLS stream manifest requests are forwarded to subsequent segment download requests.
This flag did not work. Our solution was to allow the query string on the back end.