Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. QT5 QNetworkAccessManager only has finished signal IS NOT enough

QT5 QNetworkAccessManager only has finished signal IS NOT enough

Scheduled Pinned Locked Moved General and Desktop
3 Posts 3 Posters 1.4k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    guotie
    wrote on last edited by
    #1

    for some case, when QNetworkAccessManager has send HTTP GET request, and the http server continue send data to client, and it will never finished, so the finished signal never emit.

    I think the QNetworkAccessManager should have some signal like readyread or http header finished signal.

    1 Reply Last reply
    0
    • JKSHJ Offline
      JKSHJ Offline
      JKSH
      Moderators
      wrote on last edited by
      #2

      Use QNetworkReply::readyRead()

      Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches

      1 Reply Last reply
      0
      • C Offline
        C Offline
        ChrisW67
        wrote on last edited by
        #3

        You can hear about the HTTP response headers as they arrive with the QNetworkReply::metaDataChanged() signal. As soon as you receive the first byte of response data, i.e. the first time QNetworkReply::readyRead() is emitted, the headers are fully known and accessible through the QNetworkReply object.

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved