diff options
author | Allan Sandfeld Jensen <allan.jensen@qt.io> | 2023-03-21 09:24:51 +0100 |
---|---|---|
committer | Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> | 2023-03-24 09:15:01 +0000 |
commit | e584bbbe9ae0fe0c58bb92d541984cd0e272a298 (patch) | |
tree | 71adb016e0c6f6cd2d7a51128b780f816c3184e4 /src | |
parent | 1416afe5db193023292e09c3eafad1755ea88575 (diff) | |
download | qtwebengine-e584bbbe9ae0fe0c58bb92d541984cd0e272a298.tar.gz |
Add quotes from removed example to documentation
Task-number: QTBUG-108751
Change-Id: I5560c2104e28cb5ca753f5db3579feabf4723980
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
(cherry picked from commit fb2b93818c7ecd5c025b999b2521801da9f4fbc9)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Diffstat (limited to 'src')
-rw-r--r-- | src/core/api/qwebengineurlschemehandler.cpp | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/src/core/api/qwebengineurlschemehandler.cpp b/src/core/api/qwebengineurlschemehandler.cpp index 9e5b95ef4..e01ecef49 100644 --- a/src/core/api/qwebengineurlschemehandler.cpp +++ b/src/core/api/qwebengineurlschemehandler.cpp @@ -12,9 +12,23 @@ QT_BEGIN_NAMESPACE \brief The QWebEngineUrlSchemeHandler class is a base class for handling custom URL schemes. \since 5.6 + A custom scheme handler is, broadly speaking, similar to a web application + served over HTTP. However, because custom schemes are integrated directly + into the web engine, they have the advantage in terms of efficiency and security: + There is no need for generating and parsing HTTP messages or for transferring data + over sockets, nor any way to intercept or monitor the traffic. + To implement a custom URL scheme for QtWebEngine, you first have to create an instance of QWebEngineUrlScheme and register it using QWebEngineUrlScheme::registerScheme(). + As custom schemes are integrated directly into the web engine, they do not + necessarily need to follow the standard security rules which apply to + ordinary web content. Depending on the chosen configuration, content served + over a custom scheme may be given access to local resources, be set to + ignore Content-Security-Policy rules, or conversely, be denied access to any + other content entirely. If it is to be accessed by normal content, ensure cross-origin + access is enabled, and if accessed from HTTPS that it is marked as secure. + \note Make sure that you create and register the scheme object \e before the QGuiApplication or QApplication object is instantiated. |