The class is owned by the web engine and does not need to be deleted. However, the web engine may delete the job when it is no longer needed, and therefore the signal
destroyed()must be monitored if a pointer to the object is stored.
- class PySide2.QtWebEngineCore.QWebEngineUrlRequestJob¶
This enum type holds the type of the error that occurred:
The request was successful.
The requested URL was not found.
The requested URL is invalid.
The request was canceled.
The request was denied.
The request failed.
Fails the request with the error
- Return type:
Returns the serialized origin of the content that initiated the request.
Generally, the origin consists of a scheme, hostname, and port. For example,
"http://localhost:8080"would be a valid origin. The port is omitted if it is the scheme’s default port (80 for
http, 443 for
https). The hostname is omitted for non-network schemes such as
However, there is also the special value
"null"representing a unique origin. It is, for example, the origin of a sandboxed iframe. The purpose of this special origin is to be always different from all other origins in the same-origin check. In other words, content with a unique origin should never have privileged access to any other content.
Finally, if the request was not initiated by web content, the function will return an empty
QUrl. This happens, for example, when you call
This value can be used for implementing secure cross-origin checks.
Redirects the request to
- PySide2.QtWebEngineCore.QWebEngineUrlRequestJob.reply(contentType, device)¶
Replies to the request with
deviceand the MIME type
The user has to be aware that
devicewill be used on another thread until the job is deleted. In case simultaneous access from the main thread is desired, the user is reponsible for making access to
devicethread-safe for example by using
QMutex. Note that the
deviceobject is not owned by the web engine. Therefore, the signal
QWebEngineUrlRequestJobmust be monitored.
The device should remain available at least as long as the job exists. When calling this method with a newly constructed device, one solution is to make the device as a child of the job or delete itself when job is deleted, like this:
connect(job, &QObject::destroyed, device, &QObject::deleteLater);
- Return type:
Returns any HTTP headers added to the request.
- Return type:
Returns the HTTP method of the request (for example, GET or POST).
© 2022 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.