Communicate ExtensionSettings policy to renderers

extensions/common/extension_messages.h

Index: extensions/common/extension_messages.h
diff --git a/extensions/common/extension_messages.h b/extensions/common/extension_messages.h
index e2a9c9172b0807f617548139fcf39486540a8ebb..092e955bc3f51c89e75720ba01b90e21f6a2e919 100644
--- a/extensions/common/extension_messages.h
+++ b/extensions/common/extension_messages.h
@@ -299,6 +299,8 @@ struct ExtensionMsg_Loaded_Params {
   ExtensionMsg_PermissionSetStruct active_permissions;
   ExtensionMsg_PermissionSetStruct withheld_permissions;
   std::map<int, ExtensionMsg_PermissionSetStruct> tab_specific_permissions;
+  extensions::URLPatternSet runtime_blocked_hosts;
+  extensions::URLPatternSet runtime_allowed_hosts;

[asargent_no_longer_on_chrome, 2016/11/23 01:19:23]

Do we have any sort of limitation on the size of these lists? I'm worried about
the cost of copying data for this IPC as currently specified if they contain
hundreds/thousands or more of entries.

If we do want to handle more than a few 10's of entries for these lists, we
probably want to rethink the design of how we share/update this data to account
for this. (For instance, something like shared memory segments or passing a
handle to a file on disk). 

[nrpeter, 2017/01/02 19:57:45]

Updated to use SharedMemoryHandle, this should let us handle huge
URLPatternSets.

 
   // We keep this separate so that it can be used in logging.
   std::string id;
@@ -423,6 +425,13 @@ IPC_STRUCT_BEGIN(ExtensionMsg_UpdatePermissions_Params)
   IPC_STRUCT_MEMBER(ExtensionMsg_PermissionSetStruct, withheld_permissions)
 IPC_STRUCT_END()
 
+// Parameters structure for ExtensionMsg_UpdatePolicy.
+IPC_STRUCT_BEGIN(ExtensionMsg_UpdatePolicy_Params)
+  IPC_STRUCT_MEMBER(std::string, extension_id)
+  IPC_STRUCT_MEMBER(extensions::URLPatternSet, runtime_blocked_hosts)
+  IPC_STRUCT_MEMBER(extensions::URLPatternSet, runtime_allowed_hosts)
+IPC_STRUCT_END()
+
 // Messages sent from the browser to the renderer:
 
 // The browser sends this message in response to all extension api calls. The
@@ -521,6 +530,10 @@ IPC_MESSAGE_ROUTED1(ExtensionMsg_SetTabId,
 IPC_MESSAGE_CONTROL1(ExtensionMsg_UpdatePermissions,
                      ExtensionMsg_UpdatePermissions_Params)
 
+// Tell the renderer to update an extension's runtime_blocked_hosts set.
+IPC_MESSAGE_CONTROL1(ExtensionMsg_UpdatePolicy,

[asargent_no_longer_on_chrome, 2016/11/23 01:19:23]

"UpdatePolicy" is a little ambiguous of a name here, since there are a lot of
policies that apply to extensions and this message is about a fairly particular
one. 

Also, we could conceivably want to at some point allow users to manually adjust
the runtime allowed/blocked hosts lists themselves in non-enterprise managed
scenarios, so it would be better to use names that are agnostic of the source of
the allowed/blocked lists. 

How about something like "UpdateAllowedAndBlockedHosts"?

[nrpeter, 2017/01/02 19:57:45]

Done.

+                     ExtensionMsg_UpdatePolicy_Params)
+
 // Tell the render view about new tab-specific permissions for an extension.
 IPC_MESSAGE_CONTROL5(ExtensionMsg_UpdateTabSpecificPermissions,
                      GURL /* url */,