playback of HSS playready stream CORS problem

[maba72]

Hi,
I have no problem playing the following live stream in the Silverlight test application(s) but unfortunately i cannot get it to play through HASPlayer, seems the issue is likely related to CORS headers. Can anyone tell me if it's even possible to play this kind of stream without Silverlight ?

https://stream.linear.yelo.prd.telenet-ops.be/eenhd.isml/manifest

[nicosang]

Hi @maba72 ,

do you try to use hasplayer.js in Chrome browser? There is a new CORB issue with the latest chrome version. Which browser do you use?

Anyway, the first answer is yes it's still possible to play MSS stream in a browser without Silverlight.

Nico

[maba72]

Hi Nicholas, I'm trying to open the stream in Edge , as far as I know Chrome doesn't support playready, am I right ?

Chrome throws the following exception
Access to XMLHttpRequest at 'https://stream.linear.yelo.prd.telenet-ops.be/eenhd.isml/manifest' from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

[nicosang]

Hi @maba72 ,

you're right about playready.....sorry.

You just have to configure cors on your IIS server. For instance, you can see here the response headers of your stream :

Accept-Ranges: bytes Age: 0 Cache-Control: max-age=2 Content-Encoding: gzip Content-Length: 1242 Content-Type: text/xml Date: Tue, 19 Feb 2019 08:16:38 GMT Etag: "fadd79f8f87457d0" Pragma: IISMS/4.1,IIS Media Services by Microsoft Server: Microsoft-IIS/7.5 IISMS/4.1 Via: 1.1 varnish, 1.1 varnish X-Powered-By: ASP.NET X-Varnish: 3257280977, 2916984509

....and headers of an accessible stream :

Access-Control-Allow-Origin: * Cache-Control: max-age=7200 Content-Length: 262588 Content-Type: text/xml Date: Tue, 19 Feb 2019 08:20:12 GMT Etag: "a31e50c9cb486601" Pragma: IISMS/4.1,IIS Media Services by Microsoft Server: Microsoft-IIS/7.0 IISMS/4.1 X-Powered-By: ASP.NET

On your side, Access-Control-Allow-Origin is missing...

Nico

[maba72]

Nicolas, Thanks for elaborating on this topic, seems like I'm stuck with this, unfortunately I have no control over cors on the server. Op di 19 feb. 2019 om 09:27 schreef Nicolas ANGOT <notifications@github.com

…

: Hi @maba72 <https://github.com/maba72> , you're right about playready.....sorry. You just have to configure cors on your IIS server. For instance, you can see here the response headers of your stream : Accept-Ranges: bytes Age: 0 Cache-Control: max-age=2 Content-Encoding: gzip Content-Length: 1242 Content-Type: text/xml Date: Tue, 19 Feb 2019 08:16:38 GMT Etag: "fadd79f8f87457d0" Pragma: IISMS/4.1,IIS Media Services by Microsoft Server: Microsoft-IIS/7.5 IISMS/4.1 Via: 1.1 varnish, 1.1 varnish X-Powered-By: ASP.NET X-Varnish: 3257280977, 2916984509 ....and headers of an accessible stream : Access-Control-Allow-Origin: * Cache-Control: max-age=7200 Content-Length: 262588 Content-Type: text/xml Date: Tue, 19 Feb 2019 08:20:12 GMT Etag: "a31e50c9cb486601" Pragma: IISMS/4.1,IIS Media Services by Microsoft Server: Microsoft-IIS/7.0 IISMS/4.1 X-Powered-By: ASP.NET On your side, Access-Control-Allow-Origin is missing... Nico — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#245 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AtijVNGj78do_3IFFqLW36lS0dS4Juv9ks5vO7VkgaJpZM4bBM7r> .

[bbert]

Hi @maba72, if you want to get around CORS issues on Edge browser, you can try using Fiddler to act as a proxy that is able to add custom headers on the fly.
Check this link: https://gist.github.com/fhfaa/4501be75121cae2da45f

BTW, you may know that smooth streaming is also supported by dash.js (https://github.com/Dash-Industry-Forum/dash.js).
If you start a new project we recommend you using dash.js (with MSS package) instead of hasplayer.js since minimal support will be provided on hasplayer.js.

[maba72]

Hi, thanks for sharing, sounds like a really interesting work-around, I'll surely give it a try ! Op ma 25 feb. 2019 om 09:22 schreef Bertrand Berthelot < notifications@github.com>:

…

Hi @maba72 <https://github.com/maba72>, if you want to get around CORS issues on Edge browser, you can try using Fiddler to act as a proxy that is able to add custom headers on the fly. Check this link: https://gist.github.com/fhfaa/4501be75121cae2da45f BTW, you may know that smooth streaming is also supported by dash.js ( https://github.com/Dash-Industry-Forum/dash.js). If you start a new project we recommend you using dash.js (with MSS package) instead of hasplayer.js since minimal support will be provided on hasplayer.js. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#245 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AtijVJO59q_ghyeo128oUlVEWiVUqid0ks5vQ502gaJpZM4bBM7r> .

[maba72]

the following might also do the trick : https://gist.github.com/chitsaou/236b6adcb3e543959a85 Op wo 27 feb. 2019 om 14:01 schreef Marc Ballegeer <marc.ballegeer@gmail.com

…

: Hi, thanks for sharing, sounds like a really interesting work-around, I'll surely give it a try ! Op ma 25 feb. 2019 om 09:22 schreef Bertrand Berthelot < ***@***.***>: > Hi @maba72 <https://github.com/maba72>, if you want to get around CORS > issues on Edge browser, you can try using Fiddler to act as a proxy that is > able to add custom headers on the fly. > Check this link: https://gist.github.com/fhfaa/4501be75121cae2da45f > > BTW, you may know that smooth streaming is also supported by dash.js ( > https://github.com/Dash-Industry-Forum/dash.js). > If you start a new project we recommend you using dash.js (with MSS > package) instead of hasplayer.js since minimal support will be provided on > hasplayer.js. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#245 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AtijVJO59q_ghyeo128oUlVEWiVUqid0ks5vQ502gaJpZM4bBM7r> > . >