ChromeSSLHostStateDelegate::RevokeUserAllowExceptionsHard does not work correctly with the network service |
|
Issue descriptionChromeSSLHostStateDelegate::RevokeUserAllowExceptionsHard changes some settings (Which may or may not currently be passed to the network service), and then closes all idle connections for a particular URLRequestContextGetter. While I have no idea if the settings changes are correctly applied to the network service, the CloseIdleConnections() call does not. As there's no CloseIdleConnections() call in services/network, even if the settings change is passed to the network service somehow, that also does not triggering closing idle connections.
,
Oct 10
On the CloseIdleConnections side, probably the right way to solve this, long-term, would be for //net to maintain some aspect of the certificate exceptions so it can handle the socket management itself. (The issue we were previously talking about where this feature doesn't interact with socket pools right at all.) |
|
►
Sign in to add a comment |
|
Comment 1 by davidben@chromium.org
, Oct 10Labels: Team-Security-UX