Hook up WebView.clearSslPreferences() for the Chromium HTTP stack
Note that this is an incomplete fix, as we do not clear the responses for connections currently in use, as they maintain their own cache. See http:/b/5324235. Bug: 5287216 Change-Id: I18f6638efeff0bee1e7ffed606be1444d683bebd
This commit is contained in:
committed by
Steve Block
parent
9a0cd15eec
commit
d9151bf1cc
@@ -46,4 +46,8 @@ final class SslCertLookupTable {
|
||||
public boolean isAllowed(SslError sslError) {
|
||||
return table.getBoolean(sslError.toString());
|
||||
}
|
||||
|
||||
public void clear() {
|
||||
table.clear();
|
||||
}
|
||||
}
|
||||
|
||||
@@ -1349,8 +1349,14 @@ public final class WebViewCore {
|
||||
}
|
||||
|
||||
case CLEAR_SSL_PREF_TABLE:
|
||||
Network.getInstance(mContext)
|
||||
.clearUserSslPrefTable();
|
||||
if (JniUtil.useChromiumHttpStack()) {
|
||||
// FIXME: This will not work for connections currently in use, as
|
||||
// they cache the certificate responses. See http://b/5324235.
|
||||
SslCertLookupTable.getInstance().clear();
|
||||
nativeCloseIdleConnections();
|
||||
} else {
|
||||
Network.getInstance(mContext).clearUserSslPrefTable();
|
||||
}
|
||||
break;
|
||||
|
||||
case TOUCH_UP:
|
||||
|
||||
Reference in New Issue
Block a user