(*** This bug was imported into bugs.kde.org ***) Package: kio_http Version: KDE 2.1.1 Severity: wishlist Installed from: Mandrake RPMs Compiler: Not Specified OS: Not Specified OS/Compiler notes: Not Specified On our youth hostel we have limited number of concurrent connections sometimes to 2 sometimes to 5 depends on time. It seems to me that when I try to load some page konqueror opens more connections that is allowed (e.g. when page contains frames or images). Instead of page in frame i get page from squid saying I do not have access or instead of images I get nothing :(. I think there should be some way to limit this ... I could't find no solution to it so I sent it as bug report. (Submitted via bugs.kde.org)
I'm not sure why this is marked as "unconfirmed" - kio_http still doesn't have the ability to limit the maximum connections per server, as far as I can see. It still doesn't appear to be fixed in the latest KDE 3.2 CVS. This is basic functionality which should be in every Web browser, as it is important for compatibility with certain proxy servers, as well as the Freenet client (www.freenetproject.org).
The fact that it is unconfirmed means nothing for a wishlist. Implementing this request is not trivial given the architecture behind Konqueror and the ioslaves.
I can confirm it if that helps :-)
Reassigning since kio_http has no control how many connections are opened by other slaves.
I think this control should be available for every protocol, including file:/. Example: I often start a copy task from the cdrom, and then I start another one before the first has finished. Multiplexing access from the cdrom is ugly and slooow. But I still want to navigate. This is like having a connection limit for 'bulk' transfers (of 1) and another limit (no limit or same limit or whatever) for 'interactive' transfers.
*** Bug 75634 has been marked as a duplicate of this bug. ***
See also bug #64647 for the same issue specific to the ftp ioslave.
The number of connections per server now has an upper limit (I think five or seven for HTTP), but it's not configurable. Bug 64647 (which I'm not going to close for the time being) is about a configurable limit, and it actually applies to all protocols.