Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support badCertificateCallback in cronet #1314

Open
komaxx opened this issue Oct 7, 2024 · 0 comments
Open

Support badCertificateCallback in cronet #1314

komaxx opened this issue Oct 7, 2024 · 0 comments
Assignees
Labels
package:cronet_http type-enhancement A request for a change that isn't a bug

Comments

@komaxx
Copy link

komaxx commented Oct 7, 2024

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:

ClientException: Cronet exception: m.mb: Exception in CronetUrlRequest: net::ERR_CERT_AUTHORITY_INVALID, ErrorCode=11, InternalErrorCode=-202, Retryable=false, uri=https://self-signed.badssl.com/

Is it possible to support the badCertificateCallback with cronet? Or is there an alternative way to accept self-signed certificates?

@komaxx komaxx added package:cronet_http type-enhancement A request for a change that isn't a bug labels Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
package:cronet_http type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

2 participants