63696 2011-06-30 02:40:21 -0700 Custom Accept-Encoding header prevents autoDecompress 2022-07-29 10:53:33 -0700 1 1 1 Unclassified WebKit WebKit Qt 528+ (Nightly build) All All RESOLVED INVALID http://developer.qt.nokia.com/forums/viewthread/2357/ P3 Enhancement --- 0 ttf11 webkit-unassigned markus oldest_to_newest 430294 0 ttf11 2011-06-30 02:40:21 -0700 When you set a custom "Accept-Encoding" raw header on a QNetworkRequest object (for example via an overridden QNetworkAccessManager::createRequest() ), QtWebKit will never decompress the reply anymore: source code of qhttpnetworkconnection.cpp : ==================== value = request.headerField("accept-encoding"); if (value.isEmpty()) { #ifndef QT_NO_COMPRESS request.setHeaderField("Accept-Encoding", "gzip"); request.d->autoDecompress = true; #else // if zlib is not available set this to false always request.d->autoDecompress = false; #endif } ==================== If the "accept-encoding" header was already set, request.d->autoDecompress is never set to true. This is even true if you manually set the header to "gzip" for example. The solution consists of two parts: 1) If the current value contains "gzip", also set autoDecompress to true 2) add a custom method to manually set autoDecompress to true (useful if you do not want gzipped data, but if the server still sends it, then decode it anyway as a fallback method) 430300 1 markus 2011-06-30 02:59:37 -0700 That's not a bug. If you set the header on the QNetworkRequest you are basically telling QNetworkAccessManager "I know what I'm doing, please don't do any content encoding processing". 430302 2 ttf11 2011-06-30 03:13:17 -0700 (In reply to comment #1) > That's not a bug. If you set the header on the QNetworkRequest you are basically telling QNetworkAccessManager "I know what I'm doing, please don't do any content encoding processing". If that's true, then the documentation should clearly point this out. It doesn't mention anywhere that if you set the Accept-Encoding manually, you will not get auto-decompression anymore. Especially if you set "gzip" (same as Qt does), this is very surprising. 430324 3 ttf11 2011-06-30 04:39:33 -0700 Changed from "bug" to "enhancement" request 1887694 4 ap 2022-07-29 10:53:33 -0700 The Qt port has been removed from WebKit, resolving this bug.