title: How can I make Chrome use the range http header for seeking in audio?
body: <p>It looks like Chrome downloads from the beginning of a file when scrubbing past the buffered/loaded duration, even though the 'seekable' amount claims to be 100%.</p>
  
  <p>I put up a demo page hardcoded to a 59 min audio file stored on s3, but otherwise identical to the jPlayer demo:</p>
  
  <p><a href="http://beta.prx.org/jplayer_demos/demo-01-supplied-mp3-bm.htm" rel="noreferrer">http://beta.prx.org/jplayer_demos/demo-01-supplied-mp3-bm.htm</a></p>
  
  <p>I'm testing on a Mac (10.6.8):</p>
  
  <p><strong>On Safari (5.1.4)</strong>, if you scrub past the loaded/buffered duration, it initiates another request using the range header, and gets the audio from that point almost instantly.</p>
  
  <p><strong>On Chrome (17.0.963.79)</strong>, when you scrub beyond the buffered/loaded duration, it sits and spins until it can load the audio from the beginning to the duration scrubbed.</p>
  
  <p>Any idea how to make Chrome behave itself and use the range header when you scrub past the loaded part of the audio file?</p>