> If you could capture the traffic of a successful request and one of> QNetworkAccessManager failing, it would help trying to find out what's wrong.
OK, tehere are two log files from wireshark
fail - shows the Qt app's job succes - shows firefox's jobAs I can see, there will be a problem with the method of using the proxy server. While firefox simple GETs http://www.nokia.com on the proxy address, QApplication tries to CONNECT to a forwarded (?) ip. When I telnetted to that IP-s port 3128 and I GET http://www.nokia.com, I got it.
Then I tried with nokia.com's IP, and disabled the name resolution (I uncomment the nameserver line from /etc/resolv.conf). The results ar shown in the attachment "wonameresolution". IMO that log points to the source of problem: the Qt application tries to CONNECT to the given host, with this command (147.243.3.83 is nokia.com's IP):
CONNECT 147.243.3.83:80 HTTP/1.1 in place of the "correct" GET http://147.243.3.83Now the big question: If my brainstorm is good, how to get Qt (QApplication, QNetworkProxy, whatever) to use that GET method, and don't try to CONNECT?
Two comments:1. http://147.243.3.83 / this is only something like a placeholder, don't bother this. 2. Now I can see, that if the proxy's IP is given to firefox's proxy settings, then firefox doesn't try to resolv the given page's address, but it goes to the proxy's IP and simple GETs the proper page.
fail
Description: Binary data
success
Description: Binary data
wonameresolution
Description: Binary data
_______________________________________________ Qt4-preview-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
