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 25971 - "To perform a CORS preflight fetch using request..."
Summary: "To perform a CORS preflight fetch using request..."
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Fetch (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+fetchspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-04 07:21 UTC by Anne
Modified: 2014-06-04 12:38 UTC (History)
2 users (show)

See Also:

Attachments

Description Anne 2014-06-04 07:21:47 UTC 
http://fetch.spec.whatwg.org/#cors-preflight-fetch

Need to define client and context for CORS preflight fetches. Probably deserves its own context and client should be copied from the actual fetch.
Comment 1 Anne 2014-06-04 07:22:12 UTC 
Mike, this might be of interest to you. What context to use for CORS preflight.
Comment 2 Mike West 2014-06-04 07:31:13 UTC 
Why would you suggest a new context? If I'm requesting an image with the crossorigin flag, I think I'd expect the CORS preflight to be blocked by `img-src 'none'`. Without thinking about it too hard, I'd suggest that the context be copied from the fetch as well as the client.
Comment 3 Anne 2014-06-04 07:38:01 UTC 
Fair I guess.

I was thinking new context since some parameters (such as credentials) are different, but what you say makes much more sense.