Entries returned by the Necko cache don't have the Accept-Ranges header, so media code treats them as non-seekable. I guess the Necko cache doesn't support range requests, so that makes sense, but it causes a big problem for the media code, which benefits from being able to do range requests. This creates the strange situation that non-cached responses work better than cached responses. I'm not sure what we should do about this. It's not currently urgent.
its a good point and I'll throw it into the hopper as we decide what features to put on top of the more robust, cache honza and michal are building.
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.