diff options
| author | Kaloyan Chehlarski <kaloyan.chehlarski@qt.io> | 2024-02-28 11:18:23 +0100 |
|---|---|---|
| committer | Kaloyan Chehlarski <kaloyan.chehlarski@qt.io> | 2024-05-17 11:39:07 +0200 |
| commit | c18dfe70f3f7adc7c88988d9a06a6a65fd509c19 (patch) | |
| tree | 68301af74d18c796419f6e4d91d7e59063184809 /src/core/renderer/render_configuration.h | |
| parent | cca9b5b8fef8b11e631a1b46fa5c6f0a262b0e5c (diff) | |
Currently, all certificate errors are handled the same way, regardless
of whether they come from the main frame or from an outside resource.
On the user side, this means that all certificate errors for resources
trigger a pop-up claiming the page is unsafe. Other browsers do not
do this, and instead automatically reject bad certificates for
resources.
This change extends the QWebEngineCertificateError API to allow
querying for whether the error comes from the main frame, or from
a resource. This information is already supplied by Chromium, but we
previously just ignored it. With this, application developers may now
choose to auto-reject resource errors just as Chrome does.
The simple and quick nano browser examples have been updated to
reject certificate errors coming from a page resource.
Task-number: QTBUG-92009
Change-Id: Id38b21f569318d7a83332d4ba69cb27d14b53430
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Diffstat (limited to 'src/core/renderer/render_configuration.h')
0 files changed, 0 insertions, 0 deletions