Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299)

Thanks for the response.

> Since response's status is 0 per https://fetch.spec.whatwg.org/#concept-filtered-response-opaque, response.ok will be false (only true if status is 2xx). It automatically follows from that.

Sure, this makes sense and is per-spec currently. My point is that I feel that this definition feels a little misleading since it doesn't account explicitly for this special case where the meaning of `response.status` changes. By that I mean that `response.status = 0` essentially means _N/A_ (if I understand correctly), which is unlike the meaning of any other status code.

So following the current definition seems to imply that `response.ok == false` can become ambiguous, as it can mean 'response failed' or 'response may or may not have failed' depending on the context. I guess it might just be a good idea to clearly caveat this somewhere (maybe a note)?

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