Re: [beacon] CORS and Credentials questions.

• From: Sigbjorn Finne <sof@opera.com>
• Date: Wed, 08 Jan 2014 10:17:01 +0100
• To: "doug.turner@gmail.com" <doug.turner@gmail.com>, public-web-perf <public-web-perf@w3.org>
• CC: Jonas Sicking <sicking@mozilla.com>
• Message-ID: <52CD178D.4040505@opera.com>

Den 08.01.2014 03:53, skreiv doug.turner@gmail.com:
> Hello,
>
> 1) When using beacon against a cross origin, is it clear that we might need to do a preflight for content types that are not specified by CORS?  For example, if you send a ArrayBuffer, we are probably going to need to preflight.  This is clear when reading the CORS spec, but it isn’t obviously clear from the beacon spec that there might be two http requests for a beacon — one for the OPTIONS and one for the POST.  I am not sure if we can or should relax this or not.  Maybe we should be more explicit about which mime types in the beacon specification don’t cause the OPTIONS request.
>

The Beacon spec doesn't set "author request headers" when issuing a 
cross-origin request, so I would expect there to be no CORS preflight.

--sigbjorn

Received on Wednesday, 8 January 2014 09:33:17 UTC