c0e70558d0
See: https://chromium-review.googlesource.com/c/chromium/src/+/4200660 This CL adds a new enum attribute to the ProtocolHandlerRegistry to operate under a mode where it will automatically simulate a user either accepting or rejecting a registration confirmation prompt dialog. Bug: 1359103 Change-Id: I9f99b82eee08a0b249ce79c1db5463ffc58e9dae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4203529 Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Reviewed-by: Danil Somsikov <dsv@chromium.org> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Dominick Ng <dominickn@chromium.org> Reviewed-by: Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/main@{#1100903}
Custom Handlers
The custom handlers component provides a way to register custom protocol handlers for specific URL schemes. This is part of the implementation of the System state and capabilities defined in the HTML spec. Specifically, it implements the interface NavigatorContentUtils from which the Navigator object derives.
These handlers may be used to translate the http request's URL so that it is redirected to the appropriated service (e.g. email, apps) or a different http(s) site.
All the component's code is intended to be run by the Browser process, in the UI thread.
Security and privacy
The component addresses the security and privacy considerations described in the HTML spec.
A protocol handler is only valid if it passes all protocol handler parameters normalization steps. These security and privacy checks are:
-
The handler's url must be HTTP or HTTPS; 'chrome-extension' schemes may be allowed depending on the
security level. -
Ensure the handler's url fulfills the potentially trustworthy criteria defined in the Secure Context spec. This logic is implemented by the
IsUrlPotentiallyTrustworthyin the//services/networkmodule. -
The protocol being handled must be on the safelisted scheme described in the spec. The
IsValidCustomHandlerSchemefunction inblinkimplements this check.
Chromium defines a hierarchy of security levels to relax the
restrictions imposed by the spec and allow the implementation of
certain features. Being strict the default behavior and the one
defined in the spec, there are levels for allowing untrusted-origins
and schemes not listed in the mentioned safelist defined in the spec.
For instance, on order to make possible for extensions to register
their own pages as handlers, the chrome-extension scheme is also
allowed when security level is
blink::ProtocolHandlerSecurityLevel::kExtensionFeatures.
It's also worth mentioned that Chromium defines its own
kProtocolSafelist that includes some additional decentralized schemes
that are not being explicitly defined in the mentioned.
High-level architecture
Browser
+--------------------------------------------------------------------+
| //components/custom_handlers |
| |
| +------------------------------------------+ |
| | RegisterProtocolHandlerPermissionRequest | |
| +------------------------------------------+ |
| / \ |
| +-----------------+ | |
| | ProtocolHandler | <-------------+ | |
| +-----------------+ | | |
| / \ | | |
| | | | |
| | | | |
| | | | |
| +-------------------------+ | | |
| | ProtocolHandlerRegistry | <--------+ | |
| +-------------------------+ | | |
| / \ | | |
| | | | |
| | | | |
+--------------------------------------------------------------------+
| | |
| | |
+--------------------------------------------------------------------+
| //chrome | | | |
| | | | |
| +--------------------------------+ | +---------+ | +--------------------------+
| | ProtocolHandlerRegistryFactory | <----- | Browser | ----------------> | PermissionRequestManager |
| +--------------------------------+ +---------+ | +--------------------------+
| / \ |
| | |
+--------------------------------------------------------------------+
|
+--------------------------------------------------------------------+
| //content | |
| | |
| +-----------------+ +---------------------+ |
| | WebContentsImpl | ---------> | WebContentsDelegate | |
| +-----------------+ +---------------------+ |
| / \ |
| | |
| | |
| | |
| +-------------------------+ +---------------------+ |
| | RenderFrameHostDelegate | <--------- | RenderFrameHostImpl | |
| +-------------------------+ +---------------------+ |
| | |
| | |
+--------------------------------------------------------------------+
|
|
+--------------------------------------------------------------------------------------------------------+
Renderer |
|
+--------------------------------------------------------------------+
| //blink | |
| V |
| +-----------------------+ +------------------------------+ |
| | NavigatorContentUtils | ----> | mojom::blink::LocalFrameHost | |
| +-----------------------+ +------------------------------+ |
| |
+--------------------------------------------------------------------+
Here is a summary of the core responsibilities of the classes and interfaces:
-
It's the class responsible of the security and privacy validation mentioned before, and eventually of the http request's URL translation, using the protocol handler's url spec.
-
This class is implemented as a
KeyedServicewhich means it is attached to aBrowserContext.The registry holds different kind of protocol handlers lists, depending on their source during the registration: user or internal policies. The registry also provides an API to selectively ignore protocol handlers, which are managed in an independent list.
There are also some predefined-handlers, which are automatically registered by the registry factory during the service's initialization.
Finally there is a list of the default handlers for each protocol.
All the protocol handlers managed by the registry are stored in the user preference storage, based on the user profile (the Browser Context) used to initialize the keyed service. This makes possible to guarantee the persistence of the protocol handlers state.
-
It implements the blink's
blink::URLLoaderThrottleinterface to manage the http request. It holds a pointer to a ProtocolHandlerRegistry instance to performs the URL translation if there is a custom handler for the protocol used for the request. -
RegisterProtocolHandlerPermissionRequestIt implements the
PermissionRequestinterface to manage user authorization for the requests issued by the Navigator object'sregisterProtocolHandler()method. An instance of this class holds a pointer to a ProtocolHandlerRegistry instance and a ProtocolHandler reference to be registered.It performs the handler registration of granted, or adds it to the ignored list if denied.