Obsolete Members for QWebEngineProfile
The following members of class QWebEngineProfile are obsolete. They are provided to keep old source code working. We strongly advise against using them in new code.
Public Functions
(obsolete) bool | isUsedForGlobalCertificateVerification() const |
(obsolete) void | setRequestInterceptor(QWebEngineUrlRequestInterceptor *interceptor) |
(obsolete) void | setUseForGlobalCertificateVerification(bool enabled = true) |
Member Function Documentation
bool QWebEngineProfile::isUsedForGlobalCertificateVerification() const
This function is obsolete. It is provided to keep old source code working. We strongly advise against using it in new code.
Returns true
if this profile is currently being used for global certificate verification.
This function was introduced in Qt 5.13.
void QWebEngineProfile::setRequestInterceptor(QWebEngineUrlRequestInterceptor *interceptor)
This function is obsolete. It is provided to keep old source code working. We strongly advise against using it in new code.
Registers a request interceptor singleton interceptor to intercept URL requests.
The profile does not take ownership of the pointer.
Interceptors installed with this method will call QWebEngineUrlRequestInterceptor::interceptRequest on the I/O thread. Therefore the user has to provide thread-safe interaction with the other user classes. For a duration of this call ui thread is blocked. Use setUrlRequestInterceptor instead.
This function was introduced in Qt 5.6.
See also QWebEngineUrlRequestInfo.
void QWebEngineProfile::setUseForGlobalCertificateVerification(bool enabled = true)
This function is obsolete. It is provided to keep old source code working. We strongly advise against using it in new code.
Sets if this profile is to be used for downloading and caching when needed during certificate verification, for instance for OCSP, CRLs, and AIA.
Only one QWebEngineProfile can do this at a time, and it is recommended that the profile fullfilling this role has a disk HTTP cache to avoid needlessly re-downloading. If you set the option on a second profile, it will be disabled on the profile it is currently set.
As long as one profile has enabled set to true
, all other profiles will be able to use it for their certificate verification.
Originally only affected Linux/NSS installations where it enabled OCSP.
Since 5.15.3, no longer does anything. Certificate verification is done using AIO on the requesting profile.
This function was introduced in Qt 5.13.
See also isUsedForGlobalCertificateVerification() and httpCacheType().