H.264 Streamed Video works in Chrome 23 but not Chrome 24, different request headers ... same cherry backend

On the site I'm currently working on, we are using html5 video with h.264. If it is not available, we use flash reserve. The flash fires fine in both chrome 23 and 24, but html5 video only works in chrome 23.

I opened the video file in my own tab (in which chrome then has a simple chrome bootable html file snippet to play) in each chrome version and saved the request and response information. There are actually three queries, but I find the first one to be the most interesting. Here is the header information for request and response for both.

Chrome 23:

Request:
URL:http://localhost:8040/media/preview/ab0eca40ffee4f/c268a6240b08ff/MP4_360
Request Method:GET
Status Code:200 OK
Request Headersview source
Accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Cache-Control:no-cache
Connection:keep-alive
Cookie:beaker.session.id=c59137ff184428045f317d6b2385aa384    4c30f
Host:localhost:8040
Pragma:no-cache
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.11 (KHTML, like Gecko)     Chrome/23.0.1271.97 Safari/537.11
-------------------------------
Response Headersview source
Accept-Ranges:bytes
Content-Disposition:inline; filename="2af3dc86e4fae33370c268a6240b08ff"
Content-Length:5817287
Content-Type:video/mp4
Date:Wed, 06 Feb 2013 15:51:25 GMT
Last-Modified:Fri, 07 Dec 2012 19:47:51 GMT
Server:CherryPy/3.2.0

      

Chrome 24:

Request URL:http://localhost:8040/media/preview/ef5a0220219b8e0/a4fe5f21c26f/MP4_360
Request Method:GET
Status Code:200 OK
Request Headersview source
Accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Cache-Control:max-age=0
Connection:keep-alive
Cookie:beaker.session.id=5c080dc2b3343dc725ea368dae30cb1bc324
Host:localhost:8040
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.68 Safari/537.17
-----------------------------------
Response Headersview source
Accept-Ranges:bytes
Content-Disposition:inline; filename="e10cce5997514651851aa4fe5f21c26f"
Content-Length:3632612
Content-Type:video/mp4
Date:Wed, 06 Feb 2013 18:45:04 GMT
Last-Modified:Tue, 05 Feb 2013 20:15:20 GMT
Server:CherryPy/3.2.0

      

Has anyone else expanded on this? I would also like to conduct further testing upon request.

+3


source to share


1 answer


You can fix this problem by following these steps: There is an option in chrome: // flags called "Disable hardware accelerated video decoding".

https://productforums.google.com/forum/?fromgroups=#!searchin/chrome/mp4/chrome/ilqhiTTZcaY/hkPGA3GK6BIJ



And this is a bug filed three weeks ago: http://src.chromium.org/viewvc/chrome?view=rev&revision=178906 . According to his status, he is "corrected". However, later in the comments it says that the fix can be ported to the M25 version and fixed with the 26.0.1395.1 version.

As a test, I downloaded version 26 of Chrome (developer version), (re) disabled "Disable hardware video decode acceleration" and everything works fine. If you'd like to do the same, visit the Chromes release page and select the Windows Dev Channel.

+3


source







All Articles