During our migration testing from 4.7.5.02 to 4.7.6 QA reported a breaking change for our Akamai PushPublish integration that is preventing us from deploying the update.
Per your notes at: https://www.wowza.com/docs/how-to-stream-to-akamai, “If no event name is specified and the target isn’t defined in an adaptive group, then the default event name defEvent is used in the stream URL.” We do not include the eventName in our workflow as Akamai has never required it.
This is a new behavior that wasn’t present in 4.7.5.02 that has ramifications on the playback URL, stream analytics and other areas of our (and I’d assume others) workflow.
While we can certainly look into re-writing the entire integration to satisfy this change, is it possible to provide the option to exclude “defEvent” from being implanted in the HLS Manifest POSTs to Akamai?
The impact of the change is reflected below:
4.7.5.02 HLS Manifest POST to Akamai:
PushPublishHTTPCupertinoAkamaiHandler.connect(go/_definst_/xxxxxx->xxxxxx) hostId:xxxxx-i streamId:xxxxx eventName:[notset] ingressURL: http://post.xxxxxxx-i.akamaihd.net:80/xxxxxx/ddac3fe04a playbackURL: https://xxxxxxx-i.akamaihd.net/hls/live/xxxxxxx/xxxxxxxx/playlist.m3u8
4.7.6 HLS Manifest POST to Akamai:
PushPublishHTTPCupertinoAkamaiHandler.connect(go/_definst_/xxxxx->xxxxx) hostId:xxxxxxx-i, streamId: 503409, eventName: defEvent, ingressURL: http://post.xxxxx-i.akamaihd.net:80/xxxx/defEvent/xxxxxxx, playbackURL: https://xxxxxxx-i.akamaihd.net/hls/live/xxxxx/defEvent/xxxxxx/playlist.m3u8
Please note the change in the playback URL in the second where ‘defEvent’ was added.
4.7.5.02: https://xxxxxxx-i.akamaihd.net/hls/live/xxxxxxx/xxxxxxxx/playlist.m3u8
4.7.6: https://xxxxxxx-i.akamaihd.net/hls/live/xxxxx/defEvent/xxxxxx/playlist.m3u8
Is it possible to have the option the exclude the inclusion of an eventName altogether in 4.7.6 and future builds?
Thanks for any help.
