Cross-domain redirects fail on Android L about exoplayer HOT 10 CLOSED

Thanks for the report. You're correct in thinking that this relates to Android L rather than ExoPlayer. I've routed the issue internally.

from exoplayer.

Does it work if you set the "android-allow-cross-domain-redirect" header to "1" or "true"? You can pass the header into FrameworkSampleSource. For a quick and dirty test, you could try adding it directly in that class.

from exoplayer.

Sorry @ojw28, I only just saw your message. I've tried as you suggested, with both "1" and "true", and neither work. I continue to get:

MediaHTTPConnection﹕ readAt 0 / 32768 => java.net.NoRouteToHostException: Cross-domain redirects are disallowed

from exoplayer.

Could you send me a link to the test video (or a link to a branch that has it as a sample)?

from exoplayer.

Unfortunately not :( The content i'm using to test includes a private API key along with a URL which expires after a few minutes. It would be possible for you to setup our software and go through a lot of manual steps to reproduce although it might just be easier for you to setup a local webserver and a simple redirect from a local address to something online.

from exoplayer.

Actually, it might just be as easy as using a URL shortener against one of the Sample videos. I'll test to confirm.

from exoplayer.

Ok, so I took one of the sample MP4s (http://html5demos.com/assets/dizzy.mp4) and created a shorten version (http://goo.gl/MtUDEj). I was hoping that this would demonstrate the issue, but playback works fine. I guess that the main difference between this and the test files i'm using, is that my addresses redirect from HTTP to HTTPS then back to HTTP. Could this potentially be causing the issue?

from exoplayer.

Yes. My understanding is that there's a bug in the L developer preview where cross-protocol redirects are accidentally blocked. I'm mainly looking for a very low cost way to triple check that it's been fixed for the case you're hitting.

from exoplayer.

Thanks, it does look to be cross protocol specific. I don't know why I didn't think of this earlier, but the Google shortened URL also works with HTTPS. This means that the following redirect URL can be used to reproduce the issue: https://goo.gl/MtUDEj

This will redirect from goo.gl (HTTPS) to html5demos.com (HTTP).

from exoplayer.

Confirmed to be the same issue. Thanks!

from exoplayer.