html5 - Why is Firefox ignoring cache control on Range-based queries? -

web servers have ability stream media (audio in example) browsers. browsers use html5 controls play media. i'm discovering, however, firefox caching media, though (believe i) explicitly tell not to. have hunch has 206 partial content response regular "non-range" full 200 ok response not cached. chrome (27) handles ok, firefox (21) not:

http/1.1 206 partial content date: tue, 21 may 2013 17:24:29 gmt expires: 0 pragma: no-cache cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 content-disposition: attachment; filename="audio.wav" content-type: audio/x-wav connection: close accept-ranges: bytes content-range: bytes 0-218923/218924 

anyone got ideas how make firefox not cache this? when click play other audio files named same, firefox plays first 1 clicked (cached) in session opposed re-fetching new 1 server.

note this question seems directly ask/answer this, not work... use headers mentioned.

thanks help.

edit: tried adding etag: header, still firefox caches original response.

edit: including content-length: header match (218924 in example) not seem impact issue.

edit: have filed bug @ bugzilla.mozilla.org no activity on @ point.

your firefox implementing section 13.8 of rfc2616. behavior alright.

13.8 errors or incomplete response cache behavior

a cache receives incomplete response (for example, fewer bytes of data specified in content-length header) may store response. however, cache must treat partial response. partial responses may combined described in section 13.5.4; result might full response or might still partial. cache must not return partial response client without explicitly marking such, using 206 (partial content) status code. cache must not return partial response using status code of 200 (ok).

partial responses may(or maynot) stored. chrome , firefox both follow rules.