Re: [whatwg/fetch] More informative error types (#526)

Nobody is working on this, though it seems like necessary infrastructure, e.g., for Network Error Logging. If someone wants to take this on, there are roughly three parts here:

1. Identify all the places where we create a "network error" today, annotate them with a private slot regarding the type of error and ensure that annotation makes it all the way to the caller. (E.g., there might be places where we return a new network error at some point as currently there is no distinction.) This should not be too hard, although when we get to the HTTP layer there might be some difficulty in identifying all the appropriate types. (Perhaps Network Error Logging can help.)
2. Figure out what from 1 we can reasonably expose to JavaScript, without giving attackers more information than they have today.
3. Figure out out how to expose what remains in 2 to JavaScript.

-- 
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/526#issuecomment-499988664