PythonQt.Qt.QNetworkAccessManager · declarations 001
Back to PythonQt.Qt.QNetworkAccessManager
authenticationRequired
authenticationRequired(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QNetworkAccessManager.authenticationRequired; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::authenticationRequired(QNetworkReply *reply, QAuthenticator *authenticator)
This signal is emitted whenever a final server requests authentication before it delivers the requested contents. The slot connected to this signal should fill the credentials for the contents (which can be determined by inspecting the reply object) in the authenticator object.
QNetworkAccessManager will cache the credentials internally and will send the same values if the server requires authentication again, without emitting the authenticationRequired() signal. If it rejects the credentials, this signal will be emitted again.
Note: To have the request not send credentials you must not call setUser() or setPassword() on the authenticator object. This will result in the finished() signal being emitted with a QNetworkReply with error AuthenticationRequiredError.
Note: It is not possible to use a QueuedConnection to connect to this signal, as the connection will fail if the authenticator has not been filled in with new information when the signal returns.
See also proxyAuthenticationRequired(), QAuthenticator::setUser(), and QAuthenticator::setPassword().
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#authenticationRequired
destroyed
destroyed(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QNetworkAccessManager.destroyed; argument details are not documented.
encrypted
encrypted(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QNetworkAccessManager.encrypted; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::encrypted(QNetworkReply *reply)
This signal is emitted when an SSL/TLS session has successfully completed the initial handshake. At this point, no user data has been transmitted. The signal can be used to perform additional checks on the certificate chain, for example to notify users when the certificate for a website has changed. The reply parameter specifies which network reply is responsible. If the reply does not match the expected criteria then it should be aborted by calling QNetworkReply::abort() by a slot connected to this signal. The SSL configuration in use can be inspected using the QNetworkReply::sslConfiguration() method.
Internally, QNetworkAccessManager may open multiple connections to a server, in order to allow it process requests in parallel. These connections may be reused, which means that the encrypted() signal would not be emitted. This means that you are only guaranteed to receive this signal for the first connection to a site in the lifespan of the QNetworkAccessManager.
This function was introduced in Qt 5.1.
See also QSslSocket::encrypted() and QNetworkReply::encrypted().
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#encrypted
finished
finished(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QNetworkAccessManager.finished; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::finished(QNetworkReply *reply)
This signal is emitted whenever a pending network reply is finished. The reply parameter will contain a pointer to the reply that has just finished. This signal is emitted in tandem with the QNetworkReply::finished() signal.
See QNetworkReply::finished() for information on the status that the object will be in.
Note: Do not delete the reply object in the slot connected to this signal. Use deleteLater().
See also QNetworkReply::finished() and QNetworkReply::error().
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#finished
networkAccessibleChanged
networkAccessibleChanged(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QNetworkAccessManager.networkAccessibleChanged; argument details are not documented.
networkSessionConnected
networkSessionConnected(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QNetworkAccessManager.networkSessionConnected; argument details are not documented.
objectNameChanged
objectNameChanged(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QNetworkAccessManager.objectNameChanged; argument details are not documented.
preSharedKeyAuthenticationRequired
preSharedKeyAuthenticationRequired(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QNetworkAccessManager.preSharedKeyAuthenticationRequired; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::preSharedKeyAuthenticationRequired(QNetworkReply *reply, QSslPreSharedKeyAuthenticator *authenticator)
This signal is emitted if the SSL/TLS handshake negotiates a PSK ciphersuite, and therefore a PSK authentication is then required. The reply object is the QNetworkReply that is negotiating such ciphersuites.
When using PSK, the client must send to the server a valid identity and a valid pre shared key, in order for the SSL handshake to continue. Applications can provide this information in a slot connected to this signal, by filling in the passed authenticator object according to their needs.
Note: Ignoring this signal, or failing to provide the required credentials, will cause the handshake to fail, and therefore the connection to be aborted.
Note: The authenticator object is owned by the reply and must not be deleted by the application.
This function was introduced in Qt 5.5.
See also QSslPreSharedKeyAuthenticator.
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#preSharedKeyAuthenticationRequired
proxyAuthenticationRequired
proxyAuthenticationRequired(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QNetworkAccessManager.proxyAuthenticationRequired; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::proxyAuthenticationRequired(const QNetworkProxy \&proxy, QAuthenticator *authenticator)
This signal is emitted whenever a proxy requests authentication and QNetworkAccessManager cannot find a valid, cached credential. The slot connected to this signal should fill in the credentials for the proxy proxy in the authenticator object.
QNetworkAccessManager will cache the credentials internally. The next time the proxy requests authentication, QNetworkAccessManager will automatically send the same credential without emitting the proxyAuthenticationRequired signal again.
If the proxy rejects the credentials, QNetworkAccessManager will emit the signal again.
See also proxy(), setProxy(), and authenticationRequired().
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#proxyAuthenticationRequired
sslErrors
sslErrors(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QNetworkAccessManager.sslErrors; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::sslErrors(QNetworkReply *reply, const QList\<QSslError> \&errors)
This signal is emitted if the SSL/TLS session encountered errors during the set up, including certificate verification errors. The errors parameter contains the list of errors and reply is the QNetworkReply that is encountering these errors.
To indicate that the errors are not fatal and that the connection should proceed, the QNetworkReply::ignoreSslErrors() function should be called from the slot connected to this signal. If it is not called, the SSL session will be torn down before any data is exchanged (including the URL).
This signal can be used to display an error message to the user indicating that security may be compromised and display the SSL settings (see sslConfiguration() to obtain it). If the user decides to proceed after analyzing the remote certificate, the slot should call ignoreSslErrors().
See also QSslSocket::sslErrors(), QNetworkReply::sslErrors(), QNetworkReply::sslConfiguration(), and QNetworkReply::ignoreSslErrors().
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#sslErrors