Version: 4.2.1 (KDE 4.2.1) "release 106" (using 4.2.1 (KDE 4.2.1) "release 106", KDE:KDE4:Factory:Desktop / openSUSE_11.1) Compiler: gcc OS: Linux (i686) release 2.6.27.19-3.2-default Very often I get HTTPS connection timeouts using Konqueror over a HTTP proxy. This happens for instance here at https://bugs.kde.org during using the bug report wizard, or at https://sourceforge.net/account/login.php and similar sites. After a few reloads the site can be accessed after the problem has occured. Firefox 3.0 doesn't have any problems on the mentioned sites at all. Konqueror shows in such cases: ________ The requested operation could not be completed Timeout Error Details of the Request: URL: https://bugs.kde.org/show_bug.cgi?id=182629 Protocol: https Date and Time: Wednesday 25 March 2009 12:37 Additional Information: bugs.kde.org Description: Although contact was made with the server, a response was not received within the amount of time allocated for the request as follows: Timeout for establishing a connection: 20 seconds Timeout for receiving a response: 600 seconds Timeout for accessing proxy servers: 10 seconds Please note that you can alter these timeout settings in the KDE Control Center, by selecting Network -> Preferences. Possible Causes: There may have been a problem at some point along the network path between the server and this computer. The server was too busy responding to other requests to respond. Possible Solutions: Try again, either now or at a later time. Contact the administrator of the server for further assistance.
Note: The timeout occurs immediately on site access, not after 10 or more seconds.
Still present in KDE 4.2.2
I have the same problem with konqueror/proxy/https. using kde 4.2.2 from kubuntu jaunty repositories. in my case i see the followign output: QPainter::begin: Widget painting can only begin as a result of a paintEvent QPainter::translate: Painter not active QPainter::setClipRect: Painter not active QPainter::hasClipping: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::drawRects: Painter not active QPainter::hasClipping: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::drawRects: Painter not active QPainter::hasClipping: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::drawRects: Painter not active QPainter::hasClipping: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::drawRects: Painter not active QPainter::hasClipping: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::drawRects: Painter not active QPainter::hasClipping: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::drawRects: Painter not active QPainter::setPen: Painter not active QPainter::worldTransform: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active
I am not sure it's proxy related.. I experience this bug even without it. Could you please try and disable them temporarily? This bug could be a duplicate of #183989
(In reply to comment #4) > I am not sure it's proxy related.. I experience this bug even without it. > Could you please try and disable them temporarily? > This bug could be a duplicate of #183989 Could be, but then it's a *lot* less frequent without proxy. If you're behind a proxy (like I am at work), then konq is unusable to report bugs here. I have a timeout on almost *all* clicks. At home (no corporate proxy) I don't have the problem, or it's not frequent enough to be a hindrance. HTH, Romain
The bug is still here: Konqueror Version 4.2.4 (KDE 4.2.4) Using KDE 4.2.4 (KDE 4.2.4) Error appear imediatelly and not within 10 seconds of timeout. Increasing timeout lead sometime to crash. Few times I also get (after numerous refreshes) default page instead of requested. But I cannot recreate this behavior any more. Sometimes it works though. Without proxy configured in it seems to work correctly.
Same here on OpenSUSE 11.1 KDE4.2.4 behind a proxy. I get the error message immediately.
still present in 4.2.98 RC3 IMHO all https sites suffer from this
Same here with 4.2.4 on Fedora. Like comment #5, I see this for almost all sites from work (corporate proxy) and almost never at home (no proxy). As with the OP, I find bugs.kde.org is nearly impossible to use due to this bug.
same here on OpenSuSE 11.1 x86_64 KDE 4.3.0 konqueror is simply not corporate (proxy) ready may be a work around is to set no proxy for https
"no proxy for https" works for me
I don't access through a proxy and I get instantaneous timeout errors on about 5% of pages - too many for me.
I run into the same problem here, on KDE 4.3.1. Accessing a https url is impossible with a corporate http proxy. Seems like https://bugs.kde.org/show_bug.cgi?id=177432 is about the same bug.
Does the proxy require authentication? If so this looks like a duplicate.
I encountered this bug, too. The proxy did not require authentication.
Still there in KDE 4.3.2. No authorization required for the proxy.
*** Bug 216217 has been marked as a duplicate of this bug. ***
I am observing a similar (though maybe not the same) problem. When trying to connect to https://vpn.uconn.edu , I always and immediately get the konqueror Timeout Error page. Using kubuntu karmic, konqueror 4.3.2; I am NOT using a proxy.
The problem is still there in version 4.3.85 (KDE 4.4 Beta2) with Qt 4.6.0+4.6.20091222. Browsing at https://bugs.kde.org under my account gives me approximately 1 of 4 successful connections without a https timeout behind the proxy.
Still there in 4.4.1...
Bug still present in KDE 4.4.0 To reproduce, simply send the https protocol via a proxy and try to use Amazon or your favourite bank. Watch it fail with broken images, "instant" timeout errors and a lot of stuff in ~/.xsession-errors about "KIO::TransferJob::slotMimetype: mimetype() emitted again, or after sending first data!" It works OK with a mostly-text site like (say) your personal Squirrelmail installation, but anything which embeds many images will collapse in a big smelly heap.
...though actually from the looks of it this is a bug in kio_http rather than konqueror per se...
Good news: I can't reproduce it with konqueror/kdelibs 4.5.3 (from debian experimental) and qt 4.6.3 (from debian unstable) so this bug may have been fixed at some point.
I ran into this bug again, yesterday, while I was using a http proxy with rekonq...
Joel: which KDE and Qt version?
I'm using kde 4.5.4 and qt 4.7.1, with ArchLinux.
So I'm updating the version because the bug is still present.
This has already been fixed. See https://projects.kde.org/projects/kde/kdelibs/repository/revisions/8a2929b2dd8b7fe166053aed51a5def3c6565844 If the problem persists for any of you for KDE 4.6.2 and up, feel free to reopen this ticket.
Hi Dawit, I have Konqueror 4.7.1 and I still have this issue. Can't reopen the ticket, I don't seem to have enough rights... Regards, Atanas
(In reply to comment #29) > Hi Dawit, > > I have Konqueror 4.7.1 and I still have this issue. Can't reopen the ticket, I > don't seem to have enough rights... What proxy server are you using and what distribution ? Does your problem go away if you increase the "Proxy connect" timeout value under System Settings-> Network Settings-> Connection Preferences ?
I was finally able to reproduce this bug and discovered what causes it. It is a bug in how we deal with keep alive in kio_http. A patch will be forth coming soon.