Thanks for your patience @Toni Ljungberg, @Victor Garcia and @DDG DOCOMO Digital Germany GmbH.
I checked in again with our engineers and this is what they had to say:
The Wowza CDN Stream Target does not inherently support use of an HTTP proxy. Wowza Streaming Engine sends streams directly to Akamai based on target information received from the Wowza Streaming Cloud server (for the target that the user created in the Engine Manager UI). HTTPByteWriter is a lower-level utility class that just pushes files wherever the stream target tells it to, so is not inherently configurable.
That said there might be a couple options you could try:
-
Try manually adding a custom property to the target called “child.host” and set it to the hostname of the proxy, but this has never been tested. You can add this property on the Custom tab for the target in the WSEM UI.
-
You could put an entry in your vhosts file to map the Akami hostname to their proxy hostname and proxy it that way, but this has also never been tested.
The Akamai hostnames for Wowza CDN targets should be something like post.{hostId}.[akamaihd.net](http://akamaihd.net/) where hostId is something like wowzaprod225-i
You can actually get that from the Playback URL for your stream target after you create in the Streamimg Engine Manager, which looks something like
[https://wowzaprod225-i.akamaihd.net/hls/live/833661/1cbb6a25/playlist.m3u8](https://wowzaprod225-i.akamaihd.net/hls/live/833661/1cbb6a25/playlist.m3u8)It’s that first bit of the hostname before the first “.”
