Cannot play HLS video based on source tag with an HTTP redirection.
Reported by
florian....@mediatech.fr,
May 3 2018
|
|||||||||
Issue descriptionSteps to reproduce the problem: 1. Set-up a basic video tag with a HLS source behind a 302 redirection 2. Or go to this sample : http://recette4.streamlike.com/hosting/test/flo/hlshttps.html 3. Try to play the video in a Android Chrome webpage What is the expected behavior? 2 possibilities : - ideally, the browser should lookup once for the source redirection, and then use the final URL. - Or as of desktop version, the browser should fallback to the second source, which it can play as the final redirection is a MP4 file. What went wrong? When I click on the play button, the player try to load the video, and then I loose Chrome. Sometimes I even have to reboot the device. When I look at server logs, I have a lot of malformed calls : /secure/Medias/5/0e58646f34d84fb8/hls/https://recette4-cdn.streamlike.com/secure/Medias/5/0e58646f34d84fb8/hls/0e58646f34d84fb8_648_270_425_32_baseline.m3u8 Did this work before? N/A Does this work in other browsers? N/A Chrome version: 66.0.3359.126 Channel: stable OS Version: 5.16/7/8 Flash Version: I found the previous issue #670086 which is a bit similar to my problem. I tried for a test the given hint, to disable CORS header, but it did not help.
,
May 3 2018
,
May 4 2018
,
May 4 2018
Tested the issue using #66.0.3359.126 on Android Samsung J7; 7.0.0 and could not reproduce the issue as per the steps mentioned below. Steps: 1. Launched Browser 2. Navigated to http://recette4.streamlike.com/hosting/test/flo/hlshttps.html 3. Able to play the video. @florian.vilpoix: Could you please help us with the device details, a sample Crash I'd from chrome://crashes for further triaging? Thanks!!
,
May 4 2018
I confirm the incident, we cannot play this video. 1. Launched Browser 2. Navigated to http://recette4.streamlike.com/hosting/test/flo/hlshttps.html 3. NOT able to play the video. Huawei Mate 8 Android 7.0.0 Huawei NXT-L29 Build/HUAWEINXT-L29 Chrome 66,0,3359,126 Same problem on Samsung Galaxy S2, Samsung S9, google (tablet and smartphone) etc. We spread the test to many users and none of them could be able to launch video.
,
May 4 2018
Hello, Thank you for your answer. I tested on 2 more devices, and the 2 has the problems : - Wiko Pulp 4G / Android 5.1 / Chrome 66.0.3359.126 - Nexus 5X / Android 8.1 / Chrome 66.0.3359.126 I've just sent a report after a crash, but it does not appear in chrome://crashes. Maybe you can find it with my email address. Thanks !
,
May 4 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 7 2018
Tested the issue using #66.0.3359.126 on Android Pixel 2; 8.1.0 and could reproduce the issue as per the steps mentioned below. Steps: 1. Launched Browser 2. Navigated to http://recette4.streamlike.com/hosting/test/flo/hlshttps.html 3. Unable to play the video, No Browser Crash is seen. Unable to provide the bisect info as observing inconsistent behavior in old builds (M60). Hence marking this issue as Non-Regression and Untriaging for further inputs. Please navigate to below link for screenshot-- go/chrome-androidlogs/839365 Thanks!!
,
May 25 2018
Hello, We're delivering millions of videos -for many in hls- that are not seen under chromium and generates tons of 404 in logs we have to process (x60 logs). This incident is not flagged as important and I understand this. But if anyone having sufficient visibility on the problem has an alternative under chrome, he is really really welcome :o) Question: I'm a bit lost in chromium triage rules. Will this page be updated in case of patching/solving?
,
Aug 21
,
Oct 11
,
Oct 29
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by florian....@mediatech.fr
, May 3 2018