37597 2010-04-14 12:38:57 -0700 [Qt] Cannot download files from websites 2010-05-06 00:36:27 -0700 1 1 1 Unclassified WebKit Page Loading 528+ (Nightly build) PC All RESOLVED INVALID Qt P3 Normal --- 1 jturcotte webkit-qt-unassigned markus oldest_to_newest 212500 0 jturcotte 2010-04-14 12:38:57 -0700 It happens often, each time I have to click the link in another browser instead. I get it when downloading attachments from GMail. I can download xml or txt attached files, but if I try to download a bigger pdf or power point file, it hangs in Arora and the progress bar don't increase. Trying to open the attachment in QtLauncher gives me the following message: "Frame load interrupted by policy change" I gets this on maybe 1/5 the files I try to download from web sites. I'll add other examples here when I encounter them. Got this on the webkit-2.0 branch on Windows. 212858 1 jturcotte 2010-04-15 08:13:13 -0700 Raising to P1 since there is 240 P2s and I think this would benefit visibility. Please re-lower if the problem gets revealed less critical. 215297 2 jturcotte 2010-04-21 07:11:53 -0700 Another example, try downloading the attachment from this bug report: https://bugs.webkit.org/show_bug.cgi?id=18461 217667 3 jturcotte 2010-04-27 06:07:34 -0700 The bugs seems to be present on Windows when downloading a file over https. I tried on Linux and it works as expected both http and https. 217670 4 markus 2010-04-27 06:38:07 -0700 Did you also try that on different Windows versions with probably different OpenSSL versions? 221073 5 jturcotte 2010-05-05 06:04:36 -0700 What is happening is that we push the encrypted bytes to OpenSSL however they never come back to Qt in some cases. I couldn't reproduce the problem on other machines, this problem seems very local. I'm closing it as invalid, I'll reopen if I find a real problem around this. 221075 6 markus 2010-05-05 06:06:27 -0700 It would still be interesting to see the windows + OpenSSL + Qt versions you tried that it worked with. 221538 7 jturcotte 2010-05-06 00:36:27 -0700 (In reply to comment #6) > It would still be interesting to see the windows + OpenSSL + Qt versions you > tried that it worked with. The same as on the problematic machine: Windows7 + 0.9.8.12 + Qt 4.7 trunk