RawHeaderPair is a QPair<QByteArray, QByteArray> where the first QByteArray is the header name and the second is the header.

Indicates all possible error conditions found during the processing of the request.

See also

error()

Disposes of this reply and frees any resources associated with it. If any network connections are still open, they will be closed.

See also

abort(), close()

Creates a QNetworkReply object with the given parent.

You can not directly instantiate QNetworkReply objects. Use QNetworkAccessManager functions to do that.

Aborts the operation immediately and close down any network connections still open. Uploads still in progress are also aborted.

See also

close()

Returns the attribute associated with the given code. If the attribute has not been set it returns an invalid QVariant (type QVariant::Null). You can expect the default values listed in QNetworkRequest::Attribute to be applied to the values returned by this method.

See also

setAttribute(), QNetworkRequest::Attribute

Closes this device for reading. Unread data is discarded, but the network resources are not discarded until they are finished. In particular, if any upload is in progress, it will continue until it is done.

The finished() signal is emitted when all operations are over and the network resources are freed.

See also

abort(), finished()

Reimplemented from QIODevice::close()

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(), bytesAvailable()

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.

See also

QSslSocket::encrypted(), QNetworkAccessManager::encrypted()

Returns the error that was found during the processing of this request. If no error was found, returns NoError.

See also

setError()

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.

Do not delete the object in the slot connected to this signal, use deleteLater().

See also

error(), errorString()

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() has been called, the reply will be 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.

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

Do not delete the object in the slot connected to this signal, use deleteLater().

See also

setFinished(), QNetworkAccessManager::finished(), isFinished()

Returns true if the raw header of name headerName was sent by the remote server

See also

rawHeader()

Returns the value of the known header, if that header was sent by the remote server. If the header was not sent, returns an invalid QVariant.

See also

rawHeader(), setHeader(), QNetworkRequest::header()

If this methods is called, SSL errors related to network connection will be ignored, including certificate validation errors.

Be sure to always let the user inspect the errors reported by the sslErrors() signal, and only call this method upon confirmation from the user that proceeding is ok. If there are unexpected errors, the reply should be aborted. Calling this method without inspecting the actual errors will most likely pose a security risk for your application. Use it with great care.

This method can be called from the slot connected to the sslErrors() signal, which indicates which errors were found.

See also

sslConfiguration(), sslErrors(), QSslSocket::ignoreSslErrors()

This method configures QSslSocket to ignore a specific set of errors given in errors. Multiple calls to this method will replace the list of errors that were passed in previous calls. You can clear the list of errors you want to ignore by calling this function with an empty list.

For example, if you want to connect to a Server and allow a self signed certificate use code similar to the following.

Multiple calls to this method will replace the list of errors that were passed in previous calls. You can clear the list of errors you want to ignore by calling this function with an empty list.

See also

sslConfiguration(), sslErrors(), QSslSocket::ignoreSslErrors()

This virtual method is provided to enable overriding the behavior of ignoreSslErrors(). ignoreSslErrors() is a public wrapper for this method. The value for errors contains the errors the user wants to ignore.

See also

ignoreSslErrors()

Returns true when the reply has finished or was aborted.

See also

isRunning()

Returns true when the request is still processing and the reply has not finished or was aborted yet.

See also

isFinished()

Returns true if this device is sequential, otherwise returns false.

Sequential devices, as opposed to a random-access devices, have no concept of a start, an end, a size, or a current position, and they do not support seeking. You can only read from the device when it reports that data is available. The most common example of a sequential device is a network socket. On Unix, special files such as /dev/zero and fifo pipes are sequential.

Regular files, on the other hand, do support random access. They have both a size and a current position, and they also support seeking backwards and forwards in the data stream. Regular files are non-sequential.

The QIODevice implementation returns false.

See also

bytesAvailable()

Reimplemented from QIODevice::isSequential()

Returns the QNetworkAccessManager that was used to create this QNetworkReply object. Initially, it is also the parent object.

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(), hasRawHeader()

Returns the operation that was posted for this reply.

See also

setOperation()

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.

Ignoring this signal, or failing to provide the required credentials, will cause the handshake to fail, and therefore the connection to be aborted.

The authenticator object is owned by the reply and must not be deleted by the application.

See also

QSslPreSharedKeyAuthenticator

Returns the raw contents of the header headerName as sent by the remote server. If there is no such header, returns an empty byte array, which may be indistinguishable from an empty header. Use hasRawHeader() to verify if the server sent such header field.

See also

setRawHeader(), hasRawHeader(), header()

Returns a list of headers fields that were sent by the remote server, in the order that they were sent. Duplicate headers are merged together and take place of the latter duplicate.

Returns a list of raw header pairs.

Returns the size of the read buffer, in bytes.

See also

setReadBufferSize()

This signal is only emitted if the setAttribute() method has been called with the enum value of QNetworkRequest::FollowRedirectsAttribute. The signal indicates the server responded with a 3xx status 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.

See also

QNetworkRequest::Attribute

Returns the request that was posted for this reply. In special, note that the URL for the request may be different than that of the reply.

See also

QNetworkRequest::url(), url(), setRequest()

Sets the attribute code to the given value. If code was previously set, it will be overridden. If value is an invalid QVariant the attribute will be unset.

See also

attribute(), QNetworkRequest::setAttribute()

Sets the error condition to be errorCode. The human readable message is set with errorString. Calling setError() does not emit the error(QNetworkReply::NetworkError) signal.

See also

error(), errorString()

Sets the reply as finished. After having this set the replies data must not change.

See also

finished(), isFinished()

Sets the known header to the given value. The corresponding raw form of the header will be set as well.

See also

header(), setRawHeader(), QNetworkRequest::setHeader()

Sets the associated operation for this object to be operation. This value will be returned by operation(). The operation should be set when this object is created and not changed again.

See also

operation(), setRequest()

Sets the raw header headerName to be the given value. If headerName was previously set it is overridden. Multiple HTTP headers of the same name are functionally equivalent to one single header with the values concatenated, separated by commas.

If headerName matches a known header, the value will be parsed and the corresponding parsed form will also be set.

See also

rawHeader(), header(), setHeader(), QNetworkRequest::setRawHeader()

Sets the size of the read buffer to be size bytes. The read buffer is the buffer that holds data that is being downloaded off the network, before it is read with QIODevice::read(). Setting the buffer size to 0 will make the buffer unlimited in size.

QNetworkReply will try to stop reading from the network once this buffer is full (i.e., bytesAvailable() returns size or more), thus causing the download to throttle down as well. If the buffer is not limited in size, QNetworkReply will try to download as fast as possible from the network.

Unlike QAbstractSocket::setReadBufferSize(), QNetworkReply can not guarantee precision in the read buffer size. That is, bytesAvailable() can return more than size.

See also

readBufferSize()

Sets the associated request for this object to be request. This value will be returned by request().

Note: the request should be set when this object is created and not changed again.

See also

request(), setOperation()

Sets the SSL configuration for the network connection associated with this request, if possible, to be that of configuration.

See also

sslConfiguration()

This virtual method is provided to enable overriding the behavior of setSslConfiguration(). setSslConfiguration() is a public wrapper for this method. If you override this method use configuration to set the SSL configuration.

See also

sslConfigurationImplementation(), setSslConfiguration()

Sets the URL being processed to be url. Normally, the URL matches that of the request that was posted, but for a variety of reasons it can be different (for example, a file path being made absolute or canonical).

See also

url(), request(), QNetworkRequest::url()

Returns the SSL configuration and state associated with this reply, if SSL was used. It will contain the remote server's certificate, its certificate chain leading to the Certificate Authority as well as the encryption ciphers in use.

The peer's certificate and its certificate chain will be known by the time sslErrors() is emitted, if it's emitted.

See also

setSslConfiguration()

This virtual method is provided to enable overriding the behavior of sslConfiguration(). sslConfiguration() is a public wrapper for this method. The configuration will be returned in configuration.

See also

sslConfiguration()

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(), ignoreSslErrors()

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()

Returns the URL of the content downloaded or uploaded. Note that the URL may be different from that of the original request.

See also

request(), setUrl(), QNetworkRequest::url()

Writes up to maxSize bytes from data to the device. Returns the number of bytes written, or -1 if an error occurred.

This method is called by QIODevice. Reimplement when creating a subclass of QIODevice. When reimplementing it is important that this method writes all the data available before returning. This is required in order for QDataStream to be able to operate on the class. QDataStream assumes all the information was written and therefore does not retry writing if there was a problem.

See also

read(), write()

Implements QIODevice::writeData()