| Summary: | [GLib] Remove WebKitTLSErrorsPolicy | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | bugs-noreply, cgarcia, mcatanzaro |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 210100 | ||
|
Description
Michael Catanzaro
2023-02-03 08:00:43 PST
I don't think we should remove it. I'm sure people will complain and ask us to bring it back. Being FAIL the default is enough. Really don't think there exists any valid use-case for this API in 2023. What's wrong with telling applications to use webkit_network_session_allow_tls_certificate_for_host() for bypassing certificate errors? So even though I don't think apps should be using this, it's not really a big deal to expose since it's pretty small. |