Closed
Bug 1898737
Opened 1 year ago
Closed 1 year ago
Add telemetry for byte-range requests, and how often they're cacheable
Categories
(Core :: Networking: Cache, enhancement, P2)
Core
Networking: Cache
Tracking
()
RESOLVED
FIXED
129 Branch
| Tracking | Status | |
|---|---|---|
| firefox129 | --- | fixed |
People
(Reporter: jesup, Assigned: sekim)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [necko-triaged][necko-priority-next])
Attachments
(1 file)
|
Bug 1898737 - Add telemetry for byte-range requests, and how often they're cacheable r=jesup,kershaw
48 bytes,
text/x-phabricator-request
|
Details | Review |
Byte-range requests aren't cacheable unless they start at offset 0; Chrome and Safari apparently cache all byte-range requests.
We should add two bits of telemetry: how often byte-range requests occur, and how often they're cacheable.
Updated•1 year ago
|
Severity: -- → N/A
Points: --- → 2
Priority: -- → P2
Whiteboard: [necko-triaged][necko-priority-next]
| Assignee | ||
Updated•1 year ago
|
Assignee: nobody → sekim
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Attachment #9405924 -
Attachment description: Bug 1898737 - Add telemetry for byte-range requests, and how often they're cacheable r=jesup,kershaw → WIP: Bug 1898737 - Add telemetry for byte-range requests, and how often they're cacheable r=jesup,kershaw
Updated•1 year ago
|
Attachment #9405924 -
Attachment description: WIP: Bug 1898737 - Add telemetry for byte-range requests, and how often they're cacheable r=jesup,kershaw → Bug 1898737 - Add telemetry for byte-range requests, and how often they're cacheable r=jesup,kershaw
| Assignee | ||
Updated•1 year ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Updated•1 year ago
|
Blocks: necko-ifndef-removal
Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e983eca7417c
Add telemetry for byte-range requests, and how often they're cacheable r=jesup,kershaw,necko-reviewers
Comment 3•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox129:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 129 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•