You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's quite common in larger business intranets that connections are only secured by self-signed certificates. To enable secure communication inside such networks, we're currently relying on HttpClient's badCertificateCallback.
That works well - but for http2 support and honoring of proxies set on device level, we would like to switch to cronet for Android. However, in our tests, the badCertificateCallback is never invoked. Instead attempted requests simply fail with a ClientException:
It's quite common in larger business intranets that connections are only secured by self-signed certificates. To enable secure communication inside such networks, we're currently relying on
HttpClient
'sbadCertificateCallback
.That works well - but for http2 support and honoring of proxies set on device level, we would like to switch to cronet for Android. However, in our tests, the
badCertificateCallback
is never invoked. Instead attempted requests simply fail with a ClientException:Is it possible to support the
badCertificateCallback
with cronet? Or is there an alternative way to accept self-signed certificates?The text was updated successfully, but these errors were encountered: