html5 Audio & client side cache-control: no-cache

[Austin France]

I noticed in a test app that chrome is going back to the server all the time to get the same audio file.  

When I analyze the network traffic, I can see that the client has requested Cache-Control: no-cache

GET /chromebug/124357__hoobtastic__ping.wav HTTP/1.1

Host: hive.borg-collective.org.uk

Connection: keep-alive

Cache-Control: no-cache

Pragma: no-cache

Accept-Encoding: identity;q=1, *;q=0

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.26 Safari/537.22

Accept: */*

Referer: http://hive.borg-collective.org.uk/chromebug/167065.html

Accept-Language: en-US,en;q=0.8

Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Cookie: __utma=200997559.1418160322.1351250958.1351250958.1351250958.1; __utmz=200997559.1351250958.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=(not%20provided)

Range: bytes=0-

HTTP/1.1 206 Partial Content

Date: Wed, 09 Jan 2013 11:13:41 GMT

Server: Apache/2.2.17 (Fedora)

Last-Modified: Fri, 04 Jan 2013 00:00:43 GMT

ETag: "a3edf-697e-4d26b2bb20bc2"

Accept-Ranges: bytes

Content-Length: 27006

Content-Range: bytes 0-27005/27006

Connection: close

Content-Type: audio/x-wav

Is this by design?  Is there a way to tell the audio object to cache the sound file?

[Austin France]

http://mindtrove.info/html5-audio-caching/ would seem to confirm what I am seeing.

Regards
Austin

--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

[Tomislav Pešut]

This is driving me nuts. Here's one possible solution: http://phoboslab.org/log/2011/03/multiple-channels-for-html5-audio

I can't believe that those problems are still present...sigh

[Tomislav Pešut]

There is also a great answer from the developer of Construct 2 here: http://stackoverflow.com/questions/9553415/how-did-scirra-get-html5-audio-so-perfect-in-construct-2