This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25873 - Add a 'prefetch' context to Fetch?
Summary: Add a 'prefetch' context to Fetch?
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Fetch (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+fetchspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-23 09:40 UTC by Mike West
Modified: 2014-05-27 10:16 UTC (History)
1 user (show)

See Also:

Attachments

Description Mike West 2014-05-23 09:40:48 UTC 
http://fetch.spec.whatwg.org/#concept-request-context

[[
context
]]

It might make sense to add a "prefetch" context to cover things like `<link rel="{prefetch,subresource,...}" ...>` (do those even go through Fetch? The HTML spec is unclear about the mechanisms involved: http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#link-type-prefetch).
Comment 1 Mike West 2014-05-23 09:41:46 UTC 
I'd change the title of this bug to "Add a 'prefetch' context to Fetch?", but I'm getting lovely 408 responses. :(
Comment 2 Anne 2014-05-26 11:06:42 UTC 
These should go through Fetch in the end I guess, we only want to end up with a single fetch layer.

Chrome also had prerender and such, do we need those too?
Comment 3 Anne 2014-05-27 10:16:31 UTC 
I guess we can always add those later. https://github.com/whatwg/fetch/commit/ca784a76050352fbc4ceb61e39ae71475197398c