- From: Roland Zink <roland@zinks.de>
- Date: Thu, 16 Feb 2017 22:34:16 +0100
- To: ietf-http-wg@w3.org
Received on Thursday, 16 February 2017 21:34:47 UTC
Why would be a proprietary side-channel be better? Still it is a third party which needs to be trusted and a standard proxy let me choose which service provider to use which isn't possible with a proprietary side-channel. Regards, Roland Am 16.02.2017 um 21:17 schrieb Tom Bergan: > > Yes, I'm asking why the blocking needs to happen in a proxy. For > example, Chrome's SafeBrowsing feature doesn't use a proxy. Your > client is a willing participant that will customize their software and > configuration as you ask them. Why does the protocol for deciding what > to block necessarily need to happen over a proxy, rather than a > side-channel? Maybe I'm being naive and don't know all the obvious > reasons why a proxy is needed and a side-channel won't work. Has > someone written an RFC describing why?
Received on Thursday, 16 February 2017 21:34:47 UTC