HLS & Vimeo

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Implement the MediaPlayer library on a Custom Cast receiver.
2. Initialize a HLS stream from Vimeo
3. Attempt to begin playback.

What is the expected output? What do you see instead?
I would hope that the video would begin playing, instead I receiver error codes.

What version of the product are you using? On what operating system?
The original Chromecast, as well as V2, running the latest IS as of 2/1/16

Please provide any additional information below.

I've been working on a custom receiver applications which utilizes the cast 
Media Player library to handle HLS playback. Unfortunately, Vimeo has a bit of 
mishandling in regard to CORS. When you make a request at the initially 
provided HLS url, Vimeo responds with a redirect to the final, actual HLS url, 
according to the best CDN server for the client. 

There are two problems with this, which Vimeo has confirmed that they don't 
intend on fixing:

 The first is that the CORS pre-flight request is met with the 302 redirect. According to the CORS protocol, an error should be thrown, which is exactly how chrome responds. Is there any way to get around this, and resolve the redirected HLS url? Currently, I am relying on the client application to resolve the redirect URL.The problem with this approach is that the resource expires, and I have no way to request an updated URL.

The second is that the redirect doesn't respond with the 
"Access-Control-Allow-Origin" set correctly. This mean that an error will be 
thrown, and the redirected URL will not be exposed. Is there any way to expose 
the redirected url? Is there any way to force an exception to this error on the 
Chromecast?

I have to imagine that we will not be the only ones trying to use Vimeo as a 
HLS CDN on Chromecast, so any help getting this resolved now would be greatly 
appreciated.

Original issue reported on code.google.com by JeffreyK...@gmail.com on 1 Feb 2016 at 9:58

[GoogleCodeExporter]

We're looking into this.

Original comment by jonathan...@google.com on 12 Feb 2016 at 12:22

• Changed state: Acknowledged

[TrueNorthTrent]

Any updates to this? Currently still observing this.