ffplayout built-in player has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource about ffplayout

[jb-alvarado]

Let's discuss this in the other issue.

[JunioCalu]

If I change the player_url value from "http://10.145.123.117:8787/live/stream.m3u8 " to http://bntv.space:8787/live/stream.m3u8, the problem is solved. The real problem is that without setting the Access-Control-Allow-Origin header, the browser cannot recognize that 10.145.123.117 and bntv.space is the same host with different "names", so the browser expects that the view stream source address must be the same address that loaded the ffplayout-frontend page to avoid "security" problem.

However there is a network performance issue with this approach, the preview stream will have to be externally routed over the internet before reaching my server, i.e. the preview stream would have to go through an external protocol stack and this results in in delays and dependency on internet connection. I think creating an internal virtual host in /etc/hosts to associate bntv.site with 127.0.0.1 should theoretically solve the problem more efficiently.

[JunioCalu]

Implementation screen template suggestion for ffplayout's CORS policy.

[jb-alvarado]

Sorry @JunioCalu, I will not integrate this, because to me this is more a workaround then a real solution. I don't think there is any way to dynamically update a cors setting from ffpapi. And when it goes to production and people wants to use a proxy (which is still the recommend way), it can leads to confusion and multiple cors settings on different places.

When you use ffplayout only locally, you can use IP or DNS from your local network. When you use ffplayout public setup a proxy for ssl termination and serving of hls playlists. I don't see any need mixing IP and DNS, but if you need it, use a proxy and setup there your cors rule.

[JunioCalu]

Good decision. I think maybe it would be useful when the IP of a server has more than one domain name. The example screen was implemented by datarhei/restreamer, in this case they implemented another menu to identify multiple domain names for the same server.

And by the way ffplayout and datarhei/restreamer make a good combination.