I'm having a problem with the browser caching portions of a live audio
stream in the browser's cache. If the stream is interrupted (so some
audio has played in the client) and then starts again the client is
forced to restart the stream but it will still play the cached bit until
it runs out. I've seen this manifested in a couple of ways.
I can get around it by cache-busting the URL (e.g., myfile.mp3?2529374),
but I'd rather not have to do that.
The reason this is a mystery to me is because the server response header
is:
Cache-Control: no-cache, no-store
Pragma: no-cache
Shouldn't this tell the client to not cache any of the audio stream?
Justin
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20191221/9f95bd4e/attachment.html>