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

feat: expose native handles to the underlying webview type #495

Closed
kt215 opened this issue Feb 13, 2022 · 3 comments · Fixed by #515
Closed

feat: expose native handles to the underlying webview type #495

kt215 opened this issue Feb 13, 2022 · 3 comments · Fixed by #515

Comments

@kt215
Copy link

kt215 commented Feb 13, 2022

How do I set TLSErrorsPolicy to Ignore using set_tls_errors_policy on WebContext/DataManager?

Is there a configuration setting for this?

@amrbashir
Copy link
Member

amrbashir commented Feb 13, 2022

We currently don't expose that and I don't think we should do it and I think we should expose handles to the underlying platform-specific Webview type.

We are currently exposing Webview2 Controller, so only Webkit2gtk and WkWebView handles are missing.

@amrbashir amrbashir changed the title How to set TLSErrorsPolicy to Ignore feat: expose native handles to the underlying webview type Feb 13, 2022
@kt215
Copy link
Author

kt215 commented Feb 13, 2022

Thanks for considering this. I'm trying to connect a Tauri app to a server with a self-signed SSL certificate, which fails.

This works fine with a PWA app (chromium) since I'm able to add a custom root certificate on the client side.

I barely started learning rust, but I have the latest Tauri source code, so where would be the best place to hack this for now so my Tauri client app accepts self-signed server certificates?

@amrbashir
Copy link
Member

We first need to expose the native handles and afterwards tauri can expose the same handles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants