Double escaping is needed in Wowza Player setup which is not intuitive.
Now, if you have video called “s+b.mp4” in your “content” folder, you need to use
_https://example.com:4443/vod/mp4:s%252Bb.mp4/playlist.m3u8
While in all other cases (JWPlayer / HTML5
_https://example.com:4443/vod/mp4:s%2Bb.mp4/playlist.m3u8
I use Wowza Streaming Engine 4.0.3.
(Interesting that for RTMP one must use no escaping: rtmps://example.com:4443/vod/mp4:s+b.mp4 - but this issue is not about Wowza Player
PS I just realized that the problem is that you unescape the whole URL before use - that’s why it will also work:
https%3A%2F%2Fexample.com%3A4443%2Fvod%2Fmp4%3As%252Bb.mp4%2Fplaylist.m3u8
So, the problem is not in the file name escaping - but in the whole string escaping. Previously, I thought that it’s a bug at you Builder - that’s why I started using “https://…” instead of suggested “https%3A%2F%2F…”
Is there any reason to unescape strings sent to WowzaPlayer.create()?
Hello,
Thanks for contacting Wowza Forums!
Thanks for the information. Playback should be in this format: https:// or http://. If the characters are being replaced that is something custom on your end that is changing that. Sometimes spaces and translate to % values, but that’s it.
Hope this helps.
regards,
Jermaine