New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExoPlayer doesn't follow http->https / https->http redirects #423
Comments
Hmm. Do they work on master? Are you sure that there isn't a redirect loop (which would cause this to occur after some limit on the number of redirects is reached)? |
Only redirect once. |
HttpURLConnection doesn't follow redirects that change the protocol. See here, in particular: "This implementation doesn't follow redirects from HTTPS to HTTP or vice versa." Whether we should follow them ourselves is an open question. I suspect we probably should, but it needs more thought. |
Note that this is currently breaking the "Dizzy (https->http redirect)" sample in the ExoPlayer demo app on the dev branch. |
This is now supported, but you have to turn it on explicitly when creating a HttpDataSource or UriDataSource (there are new constructors that have an allowCrossDomainRedirects argument). |
I've created a StackOverflow post asking how exactly can I add that flag using an ExtractorMediaSource: http://stackoverflow.com/questions/41517440/exoplayer2-how-can-i-make-a-http-301-redirect-work Could any of you please help me? |
In the latest dev branch, I cannot play some dash links.
It seems the Default Http DataSource does not handle http redirect (http status code 301).
The log is as follows:
The text was updated successfully, but these errors were encountered: