Skip to content

PythonQt.Qt.QNetworkReply · declarations 001

Back to PythonQt.Qt.QNetworkReply

aboutToClose

aboutToClose(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.aboutToClose; argument details are not documented.

bytesWritten

bytesWritten(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.bytesWritten; argument details are not documented.

channelBytesWritten

channelBytesWritten(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.channelBytesWritten; argument details are not documented.

channelReadyRead

channelReadyRead(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.channelReadyRead; argument details are not documented.

destroyed

destroyed(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.destroyed; argument details are not documented.

downloadProgress

downloadProgress(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.downloadProgress; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QNetworkReply::downloadProgress(qint64 bytesReceived, qint64 bytesTotal)

This signal is emitted to indicate the progress of the download part of this network request, if there's any. If there's no download associated with this request, this signal will be emitted once with 0 as the value of both bytesReceived and bytesTotal.

The bytesReceived parameter indicates the number of bytes received, while bytesTotal indicates the total number of bytes expected to be downloaded. If the number of bytes to be downloaded is not known, bytesTotal will be -1.

The download is finished when bytesReceived is equal to bytesTotal. At that time, bytesTotal will not be -1.

Note that the values of both bytesReceived and bytesTotal may be different from size(), the total number of bytes obtained through read() or readAll(), or the value of the header(ContentLengthHeader). The reason for that is that there may be protocol overhead or the data may be compressed during the download.

See also uploadProgress() and bytesAvailable().

Source: https://doc.qt.io/archives/qt-5.15/qnetworkreply.html#downloadProgress

encrypted

encrypted(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.encrypted; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QNetworkReply::encrypted()

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. 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 QNetworkAccessManager::encrypted().

Source: https://doc.qt.io/archives/qt-5.15/qnetworkreply.html#encrypted

errorOccurred

errorOccurred(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.errorOccurred; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QNetworkReply::errorOccurred(QNetworkReply::NetworkError code)

This signal is emitted when the reply detects an error in processing. The finished() signal will probably follow, indicating that the connection is over.

The code parameter contains the code of the error that was detected. Call errorString() to obtain a textual representation of the error condition.

Note: Do not delete the object in the slot connected to this signal. Use deleteLater().

This function was introduced in Qt 5.15.

See also error() and errorString().

Source: https://doc.qt.io/archives/qt-5.15/qnetworkreply.html#errorOccurred

finished

finished(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.finished; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QNetworkReply::finished()

This signal is emitted when the reply has finished processing. After this signal is emitted, there will be no more updates to the reply's data or metadata.

Unless close() or abort() have been called, the reply will still be opened for reading, so the data can be retrieved by calls to read() or readAll(). In particular, if no calls to read() were made as a result of readyRead(), a call to readAll() will retrieve the full contents in a QByteArray.

This signal is emitted in tandem with QNetworkAccessManager::finished() where that signal's reply parameter is this object.

Note: Do not delete the object in the slot connected to this signal. Use deleteLater().

You can also use isFinished() to check if a QNetworkReply has finished even before you receive the finished() signal.

See also setFinished(), QNetworkAccessManager::finished(), and isFinished().

Source: https://doc.qt.io/archives/qt-5.15/qnetworkreply.html#finished

metaDataChanged

metaDataChanged(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.metaDataChanged; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QNetworkReply::metaDataChanged()

This signal is emitted whenever the metadata in this reply changes. metadata is any information that is not the content (data) itself, including the network headers. In the majority of cases, the metadata will be known fully by the time the first byte of data is received. However, it is possible to receive updates of headers or other metadata during the processing of the data.

See also header(), rawHeaderList(), rawHeader(), and hasRawHeader().

Source: https://doc.qt.io/archives/qt-5.15/qnetworkreply.html#metaDataChanged

objectNameChanged

objectNameChanged(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.objectNameChanged; argument details are not documented.

preSharedKeyAuthenticationRequired

preSharedKeyAuthenticationRequired(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.preSharedKeyAuthenticationRequired; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QNetworkReply::preSharedKeyAuthenticationRequired(QSslPreSharedKeyAuthenticator *authenticator)

This signal is emitted if the SSL/TLS handshake negotiates a PSK ciphersuite, and therefore a PSK authentication is then required.

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/qnetworkreply.html#preSharedKeyAuthenticationRequired

readChannelFinished

readChannelFinished(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.readChannelFinished; argument details are not documented.

readyRead

readyRead(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.readyRead; argument details are not documented.

redirectAllowed

redirectAllowed(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.redirectAllowed; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QNetworkReply::redirectAllowed()

When client code handling the redirected() signal has verified the new URL, it emits this signal to allow the redirect to go ahead. This protocol applies to network requests whose redirects policy is set to QNetworkRequest::UserVerifiedRedirectPolicy

This function was introduced in Qt 5.9.

See also QNetworkRequest::UserVerifiedRedirectPolicy, QNetworkAccessManager::setRedirectPolicy(), and QNetworkRequest::RedirectPolicyAttribute.

Source: https://doc.qt.io/archives/qt-5.15/qnetworkreply.html#redirectAllowed

redirected

redirected(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.redirected; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QNetworkReply::redirected(const QUrl \&url)

This signal is emitted if the QNetworkRequest::FollowRedirectsAttribute was set in the request and the server responded with a 3xx status (specifically 301, 302, 303, 305, 307 or 308 status code) with a valid url in the location header, indicating a HTTP redirect. The url parameter contains the new redirect url as returned by the server in the location header.

This function was introduced in Qt 5.6.

See also QNetworkRequest::FollowRedirectsAttribute.

Source: https://doc.qt.io/archives/qt-5.15/qnetworkreply.html#redirected

sslErrors

sslErrors(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.sslErrors; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QNetworkReply::sslErrors(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.

To indicate that the errors are not fatal and that the connection should proceed, the 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(), QNetworkAccessManager::sslErrors(), sslConfiguration(), and ignoreSslErrors().

Source: https://doc.qt.io/archives/qt-5.15/qnetworkreply.html#sslErrors

uploadProgress

uploadProgress(*args: Any, **kwargs: Any) -> Any

Native PythonQt.Qt.QNetworkReply.uploadProgress; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QNetworkReply::uploadProgress(qint64 bytesSent, qint64 bytesTotal)

This signal is emitted to indicate the progress of the upload part of this network request, if there's any. If there's no upload associated with this request, this signal will not be emitted.

The bytesSent parameter indicates the number of bytes uploaded, while bytesTotal indicates the total number of bytes to be uploaded. If the number of bytes to be uploaded could not be determined, bytesTotal will be -1.

The upload is finished when bytesSent is equal to bytesTotal. At that time, bytesTotal will not be -1.

See also downloadProgress().

Source: https://doc.qt.io/archives/qt-5.15/qnetworkreply.html#uploadProgress