- From: Mike West <notifications@github.com>
- Date: Sun, 14 May 2017 00:32:49 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 14 May 2017 07:33:21 UTC
This seems like a reasonable thing to explore. I can add some metrics to Chrome. @zackw: Would you mind filing a bug at https://crbug.com/ so I remember to follow up on Monday? I think, though, that we should consider splitting the bad ports list into those that we can block completely, and those that we can block iff the top-level browsing context doesn't match. 9100, for instance, looks like it's going to be a bit too widely used for us to block entirely, but might be blockable as a subresource request from the rest of the web (which would at least make the scanning mechanism described above a little harder to implement). -- 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/544#issuecomment-301296157
Received on Sunday, 14 May 2017 07:33:21 UTC