Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-103185

Is 「QNetworkRequest::setDecompressedSafetyCheckThreshold(-1)」working?

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: P2: Important P2: Important
    • None
    • 6.3.0
    • Network: HTTP
    • None
    • Windows

      Even if QNetworkRequest :: setDecompressedSafetyCheckThreshold (-1) is specified, the Content-Type of the response data is prioritized and decompressed.

      As a result, even if you post to the server, if you receive data of (10 * 1024 * 1024) bytes or more, it will be decompressed without permission, and it will not be the data you expect.

      After changing to the following processing, the expected behavior was obtained.

      bool QDecompressHelper::isValid() const
      {
          return archiveBombCheckThreshold != std::numeric_limits<qint64>::max() && contentEncoding != None;
      }
      

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            manordheim Mårten Nordheim
            zattu kazuhiro ozawa
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes