title: Latest Chrome on Android plays Baseline mp4 but not when delivered with HTTP Handler with Range Request headers
body: <p>I have an mp4 file encoded with the Baseline and Constrained Baseline profiles.</p>
  
  <p>When I place the mp4 file in a folder with an HTML file which uses a <code>&lt;video&gt;</code> tag to load the video it plays no problem.</p>
  
  <p>However we have a HTTP Handler which adds Range-Request and ETag HTTP handlers to the deliver the file.  It works on Firefox running on Android, but not on Chrome. </p>
  
  <p>The Range Request was added to allow users to jump to other sections of a long video.</p>
  
  <p>Would the extra headers in the HTTP Response (which is the video file) stop Chrome on Android being able to show the video to the users?</p>
  
  <p>extra:  I got remote debugging setup on Chrome/Android.  I can now step into my content http handler.  There is a 206 partial request that is used to stream mp4 videos to iOS clients.  In the 'Network' tab of Chrome developer tools there are usually a few entries for the chunked mp4, but on Chrome on Android the 206 only shows up once.  Something seems to blow up after that 1st 206 header is sent with the MP4 video (encoded with Constrained Baseline).  As mentioned when the file is just in a folder with the html file, Chrome 32 and 36 play the file as usual, but not when it coming from the handler.  Unfortunately the handler controls all the content, so all video files must come from there.</p>