User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:184.108.40.206) Gecko/20071115 Iceweasel/220.127.116.11 (Debian-18.104.22.168-0etch1) Build Identifier: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:22.214.171.124) Gecko/20071115 Iceweasel/126.96.36.199 (Debian-188.8.131.52-0etch1) When Firefox displays a message like The connection has timed out The server at <host> is taking too long to respond. * The site could be temporarily unavailable or too busy. Try again in a few moments. * If you are unable to load any pages, check your computer's network connection. * If your computer or network is protected by a firewall or proxy, make sure that Iceweasel is permitted to access the Web. it should also display the IP address it tried to connect to. This would make easier to see where the problem comes from (e.g. like incorrect name resolving). Reproducible: Always Steps to Reproduce: 1. Open a URL with a valid host name but for which there is no web server. Actual Results: Firefox displays a message containing: "The server at <host> is taking too long to respond." Expected Results: It should be: "The server at <host> (<IP_address>) is taking too long to respond."
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: General → Embedding: Docshell
Product: Firefox → Core
QA Contact: general → docshell
I'm not sure we can get that information out of Necko (esp. in a round-robin situation where the hostname maps to a list of IPs).
You need to log in before you can comment on or make changes to this bug.