- From: <bugzilla@jessica.w3.org>
- Date: Wed, 14 Nov 2012 07:27:22 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19582 --- Comment #17 from Thomas Fossati <tho@koanlogic.com> --- (In reply to comment #16) > So how is the user going to get this proxy? How is the user going to get the > proxy set up as a handler for the coap: protocol? As already said, the model here is: a web application proposes its HTTP-CoAP proxy to the user. If the user opts-in, the "coap" URIs that the web application needs to link, will be requested via the configured HTTP-CoAP proxy. > How will sites be > restricted from communicating with this coap: protocol handler without the > user's permission? The access control function is not on the user. It is on the HTTP-CoAP proxy. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 14 November 2012 07:27:26 UTC