QNetworkAccessManager Class Reference

The QNetworkAccessManager class allows the application to send network requests and receive replies

  1. #include <QNetworkAccessManager>

Inherits: QObject.

Note: All functions in this class are reentrant.

This class was introduced in Qt 4.4.

Detailed Description

The QNetworkAccessManager class allows the application to send network requests and receive replies

The Network Access API is constructed around one QNetworkAccessManager object, which holds the common configuration and settings for the requests it sends. It contains the proxy and cache configuration, as well as the signals related to such issues, and reply signals that can be used to monitor the progress of a network operation. One QNetworkAccessManager should be enough for the whole Qt application.

Once a QNetworkAccessManager object has been created, the application can use it to send requests over the network. A group of standard functions are supplied that take a request and optional data, and each return a QNetworkReply object. The returned object is used to obtain any data returned in response to the corresponding request.

A simple download off the network could be accomplished with:

  1. connect(manager, SIGNAL(finished(QNetworkReply*)),
  2.         this, SLOT(replyFinished(QNetworkReply*)));
  3.  
  4. manager->get(QNetworkRequest(QUrl("http://qt.nokia.com")));

QNetworkAccessManager has an asynchronous API. When the replyFinished slot above is called, the parameter it takes is the QNetworkReply object containing the downloaded data as well as meta-data (headers, etc.).

Note: After the request has finished, it is the responsibility of the user to delete the QNetworkReply object at an appropriate time. Do not directly delete it inside the slot connected to finished(). You can use the deleteLater() function.

Note: QNetworkAccessManager queues the requests it receives. The number of requests executed in parallel is dependent on the protocol. Currently, for the HTTP protocol on desktop platforms, 6 requests are executed in parallel for one host/port combination.

A more involved example, assuming the manager is already existent, can be:

  1.                 QNetworkRequest request;
  2. request.setUrl(QUrl("http://qt.nokia.com"));
  3. request.setRawHeader("User-Agent", "MyOwnBrowser 1.0");
  4.  
  5. QNetworkReply *reply = manager->get(request);
  6. connect(reply, SIGNAL(readyRead()), this, SLOT(slotReadyRead()));
  7. connect(reply, SIGNAL(error(QNetworkReply::NetworkError)),
  8.         this, SLOT(slotError(QNetworkReply::NetworkError)));
  9. connect(reply, SIGNAL(sslErrors(QList<QSslError>)),
  10.         this, SLOT(slotSslErrors(QList<QSslError>)));

Network and Roaming support

With the addition of the Bearer Management API to Qt 4.7 QNetworkAccessManager gained the ability to manage network connections. QNetworkAccessManager can start the network interface if the device is offline and terminates the interface if the current process is the last one to use the uplink. Note that some platform utilize grace periods from when the last application stops using a uplink until the system actually terminates the connectivity link. Roaming is equally transparent. Any queued/pending network requests are automatically transferred to new access point.

Clients wanting to utilize this feature should not require any changes. In fact it is likely that existing platform specific connection code can simply be removed from the application.

Note: The network and roaming support in QNetworkAccessManager is conditional upon the platform supporting connection management. The QNetworkConfigurationManager::NetworkSessionRequired can be used to detect whether QNetworkAccessManager utilizes this feature. Currently only Meego/Harmattan and Symbian platforms provide connection management support.

Note: This feature cannot be used in combination with the Bearer Management API as provided by QtMobility. Applications have to migrate to the Qt version of Bearer Management.

Symbian Platform Security Requirements

On Symbian, processes which use this class must have the NetworkServices platform security capability. If the client process lacks this capability, operations will result in a panic.

Platform security capabilities are added via the TARGET.CAPABILITY qmake variable.

See also QNetworkRequest, QNetworkReply, and QNetworkProxy.

Public Types

Toggle detailsenum QNetworkAccessManager::

NetworkAccessibilityNetworkAccessibility { UnknownAccessibility , NotAccessible , Accessible 1 ...} { UnknownAccessibility , NotAccessible , Accessible 1 }

Indicates whether the network is accessible via this network access manager.

ConstantValueDescription
QNetworkAccessManager::UnknownAccessibility -1 The network accessibility cannot be determined.
QNetworkAccessManager::NotAccessible 0 The network is not currently accessible, either because there is currently no network coverage or network access has been explicitly disabled by a call to setNetworkAccessible().
QNetworkAccessManager::Accessible 1 The network is accessible.

See also networkAccessible.

Look up this member in the source code.

Toggle detailsenum QNetworkAccessManager::

OperationOperation { HeadOperation , GetOperation , PutOperation , PostOperation , DeleteOperation , CustomOperation , UnknownOperation 0 ...} { HeadOperation , GetOperation , PutOperation , PostOperation , DeleteOperation , CustomOperation , UnknownOperation 0 }

Indicates the operation this reply is processing.

ConstantValueDescription
QNetworkAccessManager::HeadOperation 1 retrieve headers operation (created with head())
QNetworkAccessManager::GetOperation 2 retrieve headers and download contents (created with get())
QNetworkAccessManager::PutOperation 3 upload contents operation (created with put())
QNetworkAccessManager::PostOperation 4 send the contents of an HTML form for processing via HTTP POST (created with post())
QNetworkAccessManager::DeleteOperation 5 delete contents operation (created with deleteResource())
QNetworkAccessManager::CustomOperation 6 custom operation (created with sendCustomRequest())

See also QNetworkReply::operation().

Look up this member in the source code.

    Properties

    Toggle detailsnetworkAccessiblenetworkAccessible : NetworkAccessibility

    This property holds whether the network is currently accessible via this network access manager.

    If the network is not accessible the network access manager will not process any new network requests, all such requests will fail with an error. Requests with URLs with the file:// scheme will still be processed.

    By default the value of this property reflects the physical state of the device. Applications may override it to disable all network requests via this network access manager by calling

    1. networkAccessManager->setNetworkAccessible(QNetworkAccessManager::NotAccessible);

    Network requests can be reenabled again by calling

    1. networkAccessManager->setNetworkAccessible(QNetworkAccessManager::Accessible);

    Note: Calling setNetworkAccessible() does not change the network state.

    Access functions:

    Look up this member in the source code.

      Public Functions

      Toggle details QNetworkAccessManager

      QNetworkAccessManagerQNetworkAccessManager ( QObject *parent=0 ) ( QObject *parent=0 )

      Constructs a QNetworkAccessManager object that is the center of the Network Access API and sets parent as the parent object.

      Look up this member in the source code.

      Toggle details QNetworkAccessManager

      ~QNetworkAccessManager~QNetworkAccessManager () ()

      Destroys the QNetworkAccessManager object and frees up any resources. Note that QNetworkReply objects that are returned from this class have this object set as their parents, which means that they will be deleted along with it if you don't call QObject::setParent() on them.

      Look up this member in the source code.

      Toggle details QNetworkConfiguration QNetworkAccessManager

      activeConfigurationactiveConfiguration () ()const

      Returns the current active network configuration.

      If the network configuration returned by configuration() is of type QNetworkConfiguration::ServiceNetwork this function will return the current active child network configuration of that configuration. Otherwise returns the same network configuration as configuration().

      Use this function to return the actual network configuration currently in use by the network session.

      See also configuration().

      Look up this member in the source code.

      Toggle details QAbstractNetworkCache * QNetworkAccessManager

      cachecache () ()const

      Returns the cache that is used to store data obtained from the network.

      See also setCache().

      Look up this member in the source code.

      Toggle details QNetworkConfiguration QNetworkAccessManager

      configurationconfiguration () ()const

      Returns the network configuration that will be used to create the network session which will be used when processing network requests.

      See also setConfiguration() and activeConfiguration().

      Look up this member in the source code.

      Toggle details QNetworkCookieJar * QNetworkAccessManager

      cookieJarcookieJar () ()const

      Returns the QNetworkCookieJar that is used to store cookies obtained from the network as well as cookies that are about to be sent.

      See also setCookieJar().

      Look up this member in the source code.

      Toggle details QNetworkReply * QNetworkAccessManager

      createRequestcreateRequest ( Operation op , const QNetworkRequest &req , QIODevice *outgoingData=0 ...) ( Operation op , const QNetworkRequest &req , QIODevice *outgoingData=0 ) [virtual protected]

      Returns a new QNetworkReply object to handle the operation op and request req. The device outgoingData is always 0 for Get and Head requests, but is the value passed to post() and put() in those operations (the QByteArray variants will pass a QBuffer object).

      The default implementation calls QNetworkCookieJar::cookiesForUrl() on the cookie jar set with setCookieJar() to obtain the cookies to be sent to the remote server.

      The returned object must be in an open state.

      Look up this member in the source code.

      Toggle details QNetworkReply * QNetworkAccessManager

      deleteResourcedeleteResource ( const QNetworkRequest &request ...) ( const QNetworkRequest &request )

      Sends a request to delete the resource identified by the URL of request.

      Note: This feature is currently available for HTTP only, performing an HTTP DELETE request.

      See also get(), post(), put(), and sendCustomRequest().

      Look up this member in the source code.

      Toggle details QNetworkReply * QNetworkAccessManager

      getget ( const QNetworkRequest &request ...) ( const QNetworkRequest &request )

      Posts a request to obtain the contents of the target request and returns a new QNetworkReply object opened for reading which emits the readyRead() signal whenever new data arrives.

      The contents as well as associated headers will be downloaded.

      See also post(), put(), deleteResource(), and sendCustomRequest().

      Look up this member in the source code.

      Toggle details QNetworkReply * QNetworkAccessManager

      headhead ( const QNetworkRequest &request ...) ( const QNetworkRequest &request )

      Posts a request to obtain the network headers for request and returns a new QNetworkReply object which will contain such headers.

      The function is named after the HTTP request associated (HEAD).

      Look up this member in the source code.

      Toggle details QNetworkReply * QNetworkAccessManager

      postpost ( const QNetworkRequest &request , QIODevice *data ...) ( const QNetworkRequest &request , QIODevice *data )

      Sends an HTTP POST request to the destination specified by request and returns a new QNetworkReply object opened for reading that will contain the reply sent by the server. The contents of the data device will be uploaded to the server.

      data must be open for reading and must remain valid until the finished() signal is emitted for this reply.

      Note: Sending a POST request on protocols other than HTTP and HTTPS is undefined and will probably fail.

      See also get(), put(), deleteResource(), and sendCustomRequest().

      Look up this member in the source code.

      Toggle details QNetworkReply * QNetworkAccessManager

      postpost ( const QNetworkRequest &request , const QByteArray &data ...) ( const QNetworkRequest &request , const QByteArray &data )

      This is an overloaded function.

      Sends the contents of the data byte array to the destination specified by request.

      Look up this member in the source code.

      Toggle details QNetworkProxy QNetworkAccessManager

      proxyproxy () ()const

      Returns the QNetworkProxy that the requests sent using this QNetworkAccessManager object will use. The default value for the proxy is QNetworkProxy::DefaultProxy.

      See also setProxy(), setProxyFactory(), and proxyAuthenticationRequired().

      Look up this member in the source code.

      Toggle details QNetworkProxyFactory * QNetworkAccessManager

      proxyFactoryproxyFactory () ()const

      Returns the proxy factory that this QNetworkAccessManager object is using to determine the proxies to be used for requests.

      Note that the pointer returned by this function is managed by QNetworkAccessManager and could be deleted at any time.

      See also setProxyFactory() and proxy().

      Look up this member in the source code.

      Toggle details QNetworkReply * QNetworkAccessManager

      putput ( const QNetworkRequest &request , QIODevice *data ...) ( const QNetworkRequest &request , QIODevice *data )

      Uploads the contents of data to the destination request and returnes a new QNetworkReply object that will be open for reply.

      data must be opened for reading when this function is called and must remain valid until the finished() signal is emitted for this reply.

      Whether anything will be available for reading from the returned object is protocol dependent. For HTTP, the server may send a small HTML page indicating the upload was successful (or not). Other protocols will probably have content in their replies.

      Note: For HTTP, this request will send a PUT request, which most servers do not allow. Form upload mechanisms, including that of uploading files through HTML forms, use the POST mechanism.

      See also get(), post(), deleteResource(), and sendCustomRequest().

      Look up this member in the source code.

      Toggle details QNetworkReply * QNetworkAccessManager

      putput ( const QNetworkRequest &request , const QByteArray &data ...) ( const QNetworkRequest &request , const QByteArray &data )

      This is an overloaded function.

      Sends the contents of the data byte array to the destination specified by request.

      Look up this member in the source code.

      Toggle details QNetworkReply * QNetworkAccessManager

      sendCustomRequestsendCustomRequest ( const QNetworkRequest &request , const QByteArray &verb , QIODevice *data=0 ...) ( const QNetworkRequest &request , const QByteArray &verb , QIODevice *data=0 )

      Sends a custom request to the server identified by the URL of request.

      It is the user's responsibility to send a verb to the server that is valid according to the HTTP specification.

      This method provides means to send verbs other than the common ones provided via get() or post() etc., for instance sending an HTTP OPTIONS command.

      If data is not empty, the contents of the data device will be uploaded to the server; in that case, data must be open for reading and must remain valid until the finished() signal is emitted for this reply.

      Note: This feature is currently available for HTTP(S) only.

      See also get(), post(), put(), and deleteResource().

      Look up this member in the source code.

      Toggle details void QNetworkAccessManager

      setCachesetCache ( QAbstractNetworkCache *cache ) ( QAbstractNetworkCache *cache )

      Sets the manager's network cache to be the cache specified. The cache is used for all requests dispatched by the manager.

      Use this function to set the network cache object to a class that implements additional features, like saving the cookies to permanent storage.

      Note: QNetworkAccessManager takes ownership of the cache object.

      QNetworkAccessManager by default does not have a set cache. Qt provides a simple disk cache, QNetworkDiskCache, which can be used.

      See also cache() and QNetworkRequest::CacheLoadControl.

      Look up this member in the source code.

      Toggle details void QNetworkAccessManager

      setConfigurationsetConfiguration ( const QNetworkConfiguration &config ...) ( const QNetworkConfiguration &config )

      Sets the network configuration that will be used when creating the network session to config.

      The network configuration is used to create and open a network session before any request that requires network access is process. If no network configuration is explicitly set via this function the network configuration returned by QNetworkConfigurationManager::defaultConfiguration() will be used.

      To restore the default network configuration set the network configuration to the value returned from QNetworkConfigurationManager::defaultConfiguration().

      1.                     QNetworkConfigurationManager manager;
      2. networkAccessManager->setConfiguration(manager.defaultConfiguration());

      If an invalid network configuration is set, a network session will not be created. In this case network requests will be processed regardless, but may fail. For example:

      1. networkAccessManager->setConfiguration(QNetworkConfiguration());

      See also configuration() and QNetworkSession.

      Look up this member in the source code.

      Toggle details void QNetworkAccessManager

      setCookieJarsetCookieJar ( QNetworkCookieJar *cookieJar ) ( QNetworkCookieJar *cookieJar )

      Sets the manager's cookie jar to be the cookieJar specified. The cookie jar is used by all requests dispatched by the manager.

      Use this function to set the cookie jar object to a class that implements additional features, like saving the cookies to permanent storage.

      Note: QNetworkAccessManager takes ownership of the cookieJar object.

      If cookieJar is in the same thread as this QNetworkAccessManager, it will set the parent of the cookieJar so that the cookie jar is deleted when this object is deleted as well. If you want to share cookie jars between different QNetworkAccessManager objects, you may want to set the cookie jar's parent to 0 after calling this function.

      QNetworkAccessManager by default does not implement any cookie policy of its own: it accepts all cookies sent by the server, as long as they are well formed and meet the minimum security requirements (cookie domain matches the request's and cookie path matches the request's). In order to implement your own security policy, override the QNetworkCookieJar::cookiesForUrl() and QNetworkCookieJar::setCookiesFromUrl() virtual functions. Those functions are called by QNetworkAccessManager when it detects a new cookie.

      See also cookieJar(), QNetworkCookieJar::cookiesForUrl(), and QNetworkCookieJar::setCookiesFromUrl().

      Look up this member in the source code.

      Toggle details void QNetworkAccessManager

      setProxysetProxy ( const QNetworkProxy &proxy ) ( const QNetworkProxy &proxy )

      Sets the proxy to be used in future requests to be proxy. This does not affect requests that have already been sent. The proxyAuthenticationRequired() signal will be emitted if the proxy requests authentication.

      A proxy set with this function will be used for all requests issued by QNetworkAccessManager. In some cases, it might be necessary to select different proxies depending on the type of request being sent or the destination host. If that's the case, you should consider using setProxyFactory().

      See also proxy() and proxyAuthenticationRequired().

      Look up this member in the source code.

      Toggle details void QNetworkAccessManager

      setProxyFactorysetProxyFactory ( QNetworkProxyFactory *factory ...) ( QNetworkProxyFactory *factory )

      Sets the proxy factory for this class to be factory. A proxy factory is used to determine a more specific list of proxies to be used for a given request, instead of trying to use the same proxy value for all requests.

      All queries sent by QNetworkAccessManager will have type QNetworkProxyQuery::UrlRequest.

      For example, a proxy factory could apply the following rules:

      • if the target address is in the local network (for example, if the hostname contains no dots or if it's an IP address in the organization's range), return QNetworkProxy::NoProxy
      • if the request is FTP, return an FTP proxy
      • if the request is HTTP or HTTPS, then return an HTTP proxy
      • otherwise, return a SOCKSv5 proxy server

      The lifetime of the object factory will be managed by QNetworkAccessManager. It will delete the object when necessary.

      Note: If a specific proxy is set with setProxy(), the factory will not be used.

      See also proxyFactory(), setProxy(), and QNetworkProxyQuery.

      Look up this member in the source code.

        Signals

        Toggle details void QNetworkAccessManager

        authenticationRequiredauthenticationRequired ( QNetworkReply *reply , QAuthenticator *authenticator ...) ( QNetworkReply *reply , QAuthenticator *authenticator ) [signal]

        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.

        See also proxyAuthenticationRequired().

        Look up this member in the source code.

        Toggle details void QNetworkAccessManager

        finishedfinished ( QNetworkReply *reply ) ( QNetworkReply *reply ) [signal]

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

        Look up this member in the source code.

        Toggle details void QNetworkAccessManager

        networkAccessibleChangednetworkAccessibleChanged ( QNetworkAccessManager::NetworkAccessibility accessible ...) ( QNetworkAccessManager::NetworkAccessibility accessible ) [signal]

        This signal is emitted when the value of the networkAccessible property changes. accessible is the new network accessibility.

        Look up this member in the source code.

        Toggle details void QNetworkAccessManager

        proxyAuthenticationRequiredproxyAuthenticationRequired ( const QNetworkProxy &proxy , QAuthenticator *authenticator ...) ( const QNetworkProxy &proxy , QAuthenticator *authenticator ) [signal]

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

        Look up this member in the source code.

        Toggle details void QNetworkAccessManager

        sslErrorssslErrors ( QNetworkReply *reply , const QList <QSslError > &errors ...) ( QNetworkReply *reply , const QList <QSslError > &errors ) [signal]

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

        Look up this member in the source code.

          Notes provided by the Qt Community
          Informative
          • 5

          Votes: 7

          Coverage: Qt library 4.7, 4.8, 5.0

          Picture of Volker Volker

          Ant Farmer
          35 notes

          Nokia Certified Qt Developer

          Don't use QThread to run network operations in the background

          There is no need to use QThread in order to make your network operations in the background!

          Every now and then someone pops up in the forums doing exactly this and having problems to make it work correctly or not to crash at all.

          QNetworkAccessManger and its related classes work asynchronously by design! Just connect to the appropriate signals and keep track of your QNetworkReply objects and you’re done!

          [Revisions]

          Cool Hack
          • 5

          Votes: 9

          Coverage: Qt library 4.7, Qt 4.8

          Picture of Smar Smar

          Lab Rat
          3 notes

          Creating valid POST request

          post() functions (atleast QByteArray one) does send the data as given: URL escaping is up to you.

          You could manually populate a QByteArray and send it, but QUrl gives better syntax while offering request construction, and so validation, and URL encoding for you.

          1. QUrl params;
          2. params.addQueryItem("key", "value");
          3. params.addQueryItem("another_key", "äöutf8-value");
          4.  
          5. QNetworkRequest request(url);
          6. manager->post(request, params.encodedQuery());

          EDIT for 4.8:
          In 4.8 creating POST request without explicitly setting content type results into warning:

          content-type missing in HTTP POST, defaulting to application/octet-stream

          This warning can be muted by setting this header for QNetworkRequest:

          1. networkRequest.setHeader(QNetworkRequest::ContentTypeHeader, "application/octet-stream");

          Content type used by for example browsers to do requests would be “application/x-www-form-urlencoded”, in case you need it.

          [Revisions]

          Best Practice
          • 5

          Votes: 1

          Coverage: Qt library 4.7, Qt 4.8

          Picture of Code_ReaQtor Code_ReaQtor

          Ant Farmer
          1 note

          POST with QIODevice*

          Don’t forget to “open” QIODevice* when using QNetworkAccessManager::post [qt-project.org] ! For example, when uploading a QFile through POST:

          1. QFile *file = new QFile(fileName); //QString fileName
          2. file->open(QIODevice::ReadOnly)); //<--- It is needed!
          3.  
          4. QUrl url(...); //server address
          5. url.addQueryItem("key", "value"); //optional, if the server needs it
          6.  
          7. request.setUrl(url);
          8. request.setHeader(QNetworkRequest::ContentTypeHeader,"application/octet-stream"); //Required!
          9. request.setRawHeader("headerName", "headerValue"); //optional, if the server needs it
          10.  
          11. QNetworkReply *reply = manager->post(request, file);
          12. file->setParent(reply); //if file is too big, it will be deleted after reply is destroyed
          13.  
          14. //signal-slot
          15. QObject::connect(reply, SIGNAL(uploadProgress(qint64,qint64)), this, SLOT(onUploadProgress(qint64,qint64)));
          16. QObject::connect(reply, SIGNAL(finished()), this, SLOT(onFinished()));
          17. QObject::connect(reply, SIGNAL(error(QNetworkReply::NetworkError)), this, SLOT(onNetworkError(QNetworkReply::NetworkError)));

          For the above code, error occurs when:

          • file is not opened for “reading”
          • “application/octet-stream” is not used (for uploading QFile)

          [Revisions]

          Best Practice
          • 4

          Votes: 10

          Coverage: Qt library 4.7, 4.8, 5.0

          Picture of minimoog77 minimoog77

          Lab Rat
          2 notes

          Typical use of network access manager

          1. QUrl url("http://mymagicurl.com");
          2. QNetworkRequest req(url);
          3.  
          4. QNetworkReply *reply = netManager->get(req);
          5. connect(reply, SIGNAL(finished()), this, SLOT(reply()));
          6.  
          7. void MyNetClass::reply()
          8. {
          9.    QNetworkReply *reply = qobject_cast<QNetworkReply*>(sender());
          10.  
          11.    if (reply) {
          12.        if (reply->error()) == QNetworkReply::NoError) {
          13.            //read data from reply
          14.        } else {
          15.            //get http status code
          16.            int httpStatus = reply->attribute(QNetworkRequest::HttpStatusCodeAttribute).toInt();
          17.            //do some error management
          18.        }
          19.        reply->deleteLater();
          20.    }
          21. }

          [Revisions]