Re: [w3c/ServiceWorker] OPTIONS request reported as GET (#1498)

monica-ch left a comment (w3c/ServiceWorker#1498)

> > [Bug triage] Working as expected, closing the issue
> 
> Was this successfully tested on a specific browser(s)? Did the test successfully execute the following test originally reported:
> 
> console.log(event.request.method, event.request.url);

Fair question. I hadn't captured that reasoning in the close comment. 

Let me explain the spec basis so you can verify independently: This behavior is defined in the Fetch spec, not the SW spec:

Service workers are invoked from [HTTP fetch step 3.1](https://fetch.spec.whatwg.org/#http-fetch)
CORS preflights are dispatched via [CORS-preflight fetch step 3](https://fetch.spec.whatwg.org/#cors-preflight-fetch), which calls HTTP-network-or-cache fetch directly and bypasses the HTTP-fetch (SW dispatch) layer.
So preflight OPTIONS requests are intentionally not visible to service workers; only the actual request (GET in your example) is. This is consistent across Chromium, Firefox, and WebKit implementations.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1498#issuecomment-5547034548
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1498/5547034548@github.com>