Closed Bug 159044 Opened 22 years ago Closed 22 years ago

Honor and precache LINK REL=NEXT

Categories

(Core :: Networking: HTTP, defect, P3)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
Windows 2000
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 12274
Milestone:
mozilla1.2alpha

People

(Reporter: dougt, Assigned: darin.moz)

Details

Per our conversation today, we should implement the LINK tag to enable precaching of web content.
Summary: Honor and precache LINK tag → Honor and precache LINK tag
Status: NEW → ASSIGNED
Priority: -- → P3
Summary: Honor and precache LINK tag → Honor and precache LINK tag
Target Milestone: --- → mozilla1.2alpha
Just some clarification. Link tag (and header) is already implemented. We need the REL=NEXT implementation to do a prefetch. More importantly this would need a way to prioritize connections. Darin do we already have a bug for that or should a new one be created?
Summary: Honor and precache LINK tag → Honor and precache LINK REL=NEXT
that may just end up being part of the patch for this bug.
Well... as we talked about in the meeting, the prioritizing may help other cases too (like background download, or even deferring download of content elements that is not visible immediately on a long page, etc.) So while you may wrap it all in one patch keeping these as separate bugs may still be useful. What do you think?
yeah, that makes sense... especially if we end up filing bugs for those other features.
*** Bug 12274 has been marked as a duplicate of this bug. ***
reversing duplicate... *** This bug has been marked as a duplicate of 12274 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Verified dupe.
Status: RESOLVED → VERIFIED
QA Contact: tever → junruh
You need to log in before you can comment on or make changes to this bug.