> It would seem supplying any sort of > Accept-Encoding header is adequate to prevent QNetworkAccessManager > from doing its thing, but I have no way of verifying this in all > cases.
That does seem to be it. In this QT bug report, https://bugreports.qt-project.org/browse/QTBUG-18239 they address the opposite bug, that it isn't automatically decompressed. "Don't set the Accept-Encoding header. QNetworkAccessManager will [decompress] automatically for you" > It's probably OK, but I'm always apprehensive about relying > on undocumented behavior to make something work. Yes, I fully understand. Given how QT worked around the opposite behavior, I don't think it's too likely to fail suddenly. If they do offer a real fix, we'll only need to erase one line of code. Tom Breton (Tehom) ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
