Content-Range working in Safari but not in Chrome
I'm streaming audio files from a Node.js Express server with Content-Range headers plus no caching headers. This works ok in latest Safari instead, but it does not in Chrome. While when streaming the full audio file with HTTP 200 , my headers were { 'Content-Length': 4724126, 'Content-Type': 'audio/mpeg', 'Access-Control-Allow-Origin': '*', 'Access-Control-Allow-Methods': 'POST, GET, OPTIONS', 'Access-Control-Allow-Headers': 'POST, GET, OPTIONS', Expires: 0, Pragma: 'no-cache', 'Cache-Control': 'no-cache, no-store, must-revalidate' } and it works on both Chrome and Safari <audio> tag. When