- From: sleevi <notifications@github.com>
- Date: Fri, 16 Dec 2016 08:40:29 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 16 December 2016 16:41:30 UTC
> > @sleevi <https://github.com/sleevi> fair, didn't realize support was > limited to Fx. Isn't there some fetching related to certificates though > that everyone implements and needs to bypass service workers? > That's AIA, which FF doesn't support, on macOS/iOS/Win are handled by OS (and an out of process network stack shared with all users and processes). Chrome uses its "not at all web/fetch" network stack for it on Linux/CrOS. So fetch never sees them, even to begin with. Given architectures today, I *think* only FF is at risk of ever "accidentally" sending a request for certs/OneCRL/SafeBrowsing/spelling/etc through Fetch-enabled/compliant networking - for all other UAs, happens well, well below where Fetch spec is implemented, in bowels of other systems, not the "UA" per se. -- 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/303#issuecomment-267636385
Received on Friday, 16 December 2016 16:41:30 UTC