Re: [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824)

jub0bs left a comment (whatwg/fetch#1824)

@annevk 

> It does seem weird to point out that a non-preflighted request can nevertheless be preflighted, but I guess that works.

It would indeed be unfortunate if "non-preflighted" came to mean "sometimes preflighted". But I'm not sure I'm following you. Are you referring to your earlier comment?

> a CORS-preflight request can nevertheless be forced. E.g., in `XMLHttpRequest` if you use upload event listeners or with `fetch()` if you use an upload stream.

FWIW, the term "simple request", [as used by MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS#simple_requests), covers those cases:

> - If the request is made using an [XMLHttpRequest](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) object, no event listeners are registered on the object returned by the [XMLHttpRequest.upload](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/upload) property used in the request; that is, given an [XMLHttpRequest](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) instance xhr, no code has called xhr.upload.addEventListener() to add an event listener to monitor the upload.
> - No [ReadableStream](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream) object is used in the request.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1824#issuecomment-2886056627
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1824/2886056627@github.com>