Open Bug 1350991 Opened 9 years ago Updated 5 years ago

Add an heuristic for resources that have no cache headers and no "last modified" header

Categories

(Core :: Networking: Cache, enhancement, P5)

Product:
Core
Component:
Networking: Cache
Version:
55 Branch
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox55 --- affected

People

(Reporter: julienw, Unassigned)

Details

(Whiteboard: [necko-backlog])

This favicon has no useful headers for cache: https://ad.atdmt.com/favicon.ico The headers for this file are: HTTP/2 200 content-type: image/x-icon date: Mon, 27 Mar 2017 17:36:51 GMT content-length: 1150 As a result, ComputeFreshnessLifetime [1] returns 0. I think we should have an heuristic to get some freshness for those files as it could help performance in some cases. [1] http://searchfox.org/mozilla-central/rev/7419b368156a6efa24777b21b0e5706be89a9c2f/netwerk/protocol/http/nsHttpResponseHead.cpp#680
Michal, any opinion on this topic?
Flags: needinfo?(michal.novotny)
Honza knows this code better.
Flags: needinfo?(michal.novotny) → needinfo?(honzab.moz)
Assigning to Honza for the moment.
Assignee: nobody → honzab.moz
Whiteboard: [necko-active]
Assignee: honzab.moz → nobody
Whiteboard: [necko-active] → [necko-backlog]
Flags: needinfo?(honzab.moz)
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.