Re: [fetch] error types too vague for TLS certificate error (#205)

There's been some speculation among some folks about letting the network describe its "shape" to the browser; e.g., "this address range is private, that address range is not. That subdomain is private..." If there were such a positive signal, it could be used to expose more information about requests where the browser knows they're public. 

That's just speculation now, however, and a lot of questions would need to be answered to make it feasible.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/205#issuecomment-196522255