I think that the browser waits to see what happens with the connection.
As I use my own DNS server I think I could give a bit of light to that, guenter, as I've seen several times happening.
The example explained is, as said, about DNS resolving, some other variables could affect to the timeout.
When you request a page, K-meleon calls the tcp stack, the tcp stack routes to the DNS server, the server starts to resolve the domain to an IP, then, the result goes back to K-meleon. If found, K-meleon loads the page, if the dns server can't resolve, K-meleon, immediately, displays an error.
But, wait, there is a paradox. In the DNS server I can configure the minimum timeout for domain resolving, or, in other words I can expand the timeout limit. Here you can see the system-level timout working.
But, wait, we haven't finished. I'm talking under Windows 2000. In OSs like XP, where you have a configurable DNS client service, does it behave the same way? how is that service configured? does it have a windows registry setting as, maybe, the whole connection timeout?
I haven't searched, but probably, the solution could be in the registry.
[Kleon just answered while I was composing this message
Anyway, going on topic again, we have to know first if the proxy is just slow, or if it really can't resolve and find the page through the proxy. Why I say this? because I haven't had such timeout problems with proxies. Usually, when a proxy displays an error (free proxies out there, at least) is because it really can't handle the request at any level and, usually, it displays an standard pre-configured error, not a K-meleon error.
What error does k-meleon show? Can you provide a screen capture, maybe?
Edited 1 time(s). Last edit at 03/25/2012 09:29PM by JohnHell.