Open
Bug 899851
Opened 12 years ago
Updated 2 years ago
Entries returned by the Necko cache aren't seekable
Categories
(Core :: Networking: Cache, defect, P5)
Tracking
()
NEW
People
(Reporter: roc, Unassigned)
Details
(Whiteboard: [necko-would-take])
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.
|
||
Comment 1•12 years ago
|
||
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.
|
|
||
Updated•9 years ago
|
Whiteboard: [necko-would-take]
|
||
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•