Bug 251689
| 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 | ||
Michael Catanzaro
I don't think we need WebKitTLSErrorsPolicy anymore since the web is a better place than it was 15 years ago. Applications that want to ignore a particular error can still use webkit_network_session_allow_tls_certificate_for_host(), which should suffice.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Carlos Garcia Campos
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.
Michael Catanzaro
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?
Michael Catanzaro
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.