Stream Targets API disregards playbackssl argument

Wowza Streaming Engine
1

I’m trying to create a new stream target to Akamai using REST API. Here is an example of API call (hosts and IDs edited):

curl --http1.1 -X POST --header ‘Accept:application/json; charset=utf-8’ --header ‘Content-type:application/json; charset=utf-8’ https://someaddress.com:8087/v2/servers/defaultServer/vhosts/defaultVHost/applications/webcamrecording/pushpublish/mapentries/stream_1 -d’

{

“restURI”: “https://someaddress.com:8087/v2/servers/defaultServer/vhosts/defaultVHost/applications/webcamrecording/pushpublish/mapentries/stream”,

“serverName”:“defaultServer”,

“sourceStreamName”: “stream_in”,

“entryName”: “stream_1”,

“profile”: “cupertino-akamai”,

“akamai.hostId”:“someakamaihost-i”,

“application”:“live”,

“streamName”:“stream_1”,

“akamai.streamId”:“123456”,

“playbackSSL”:“true”,

“sendSSL”:“true”

}’

It works correctly - except for “playbackSSL”:“true”. It is disregarded. As a result, on HTTPS page I get “Mixed content warning”.

If I manually edit PushPublishMap.txt file and add “playbackSSL”:“true” there it works as expected.

Anything I’m doing incorrectly? Bug in wowza?

Thanks

2

Hi,

When adding playbackSSL, you will need to add it as follows:

"extraOptions": {
    "playbackSSL":"true"
},

To initially get an idea of how to set an option through the REST API, you can configure it from the Manager UI at first, and then perform a GET request on the endpoint. The resulting JSON response can be copied and used as your JSON data for your POST or PUT request.

Michelle