Bug 196488

Summary: Accessing fritzbox via https:// with Konqueror 4.2.2 results in timeout error
Product: [Applications] konqueror Reporter: Klaus Layer <klaus.layer+kde>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: finex, rasasi78
Priority: NOR    
Version: 4.2.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Klaus Layer 2009-06-14 14:55:17 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

When I access my fritzbox via https i.e. https://fritzbox.local konqueror shows a timeout error:

---
The requested operation could not be completed
Timeout Error
Details of the Request:
URL: https://fritzbox.local/
Protocol: https
Date and Time: Sunday, 14. June 2009 14:42
Additional Information: fritzbox.local
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.
---

With http the same works well with konqueror. I checked with firefox 3 and it also works as expected.
Comment 1 Raúl 2009-07-10 12:20:55 UTC
Isn't this a dupe of https://bugs.kde.org/show_bug.cgi?id=188073 ?

Regards
Comment 2 Klaus Layer 2009-07-11 00:10:10 UTC
No this is only for fritzbox. I never have this issues with other websites
Comment 3 FiNeX 2009-09-08 11:38:50 UTC

*** This bug has been marked as a duplicate of bug 169911 ***