"Accept-Ranges" header and Blink Browsers

[Zack Krida]

Hi folks! I work on the Openverse project, a non profit project part of the WordPress ecosystem which displays image and audio results. We collect and share results from Jamendo. We've noticed that audio responses from Jamendo lack the "Accept-Ranges" HTTP header, which prevents Jamendo tracks from being seeked in browsers using the Blink engine.

I believe if Jamendo audio responses had the 'Accept-Ranges: bytes' header set this wouldn't be an issue. Here's some issues relevant to this problem:

- https://stackoverflow.com/questions/7380532/browser-audio-playback-fails-when-accept-ranges-not-set-in-http-headers-why

- https://github.com/WordPress/openverse-frontend/issues/680