No longer explicitly initialize a CertVerifier in Cronet
Support for file-based persistence was removed in r571588, so its no longer necessary for Cronet to explicitly create a CertVerifier to guarantee it is a CachingCertVerifier. Bug: 590875 Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I23e9e6db12225a7474ce589d9333595729108f1c Reviewed-on: https://chromium-review.googlesource.com/1169822Reviewed-by:Helen Li <xunjieli@chromium.org> Commit-Queue: Ryan Sleevi <rsleevi@chromium.org> Cr-Commit-Position: refs/heads/master@{#582330}
Showing
Please register or sign in to comment