Firefox:1.5 Network Error Messages: Difference between revisions
(→Open Issues & Questions: note about redirectLoop) |
|||
Line 4: | Line 4: | ||
You can see a preview of the error message rendering [http://hskupin.info/tmp/netError/v13/ltr-fx.jpg here]. | You can see a preview of the error message rendering [http://hskupin.info/tmp/netError/v13/ltr-fx.jpg here]. | ||
The latest proposed patch to the netError.dtd file is [ | The latest proposed patch to the netError.dtd file is [http://lxr.mozilla.org/seamonkey/source/dom/locales/en-US/chrome/netError.dtd here]. | ||
== Open Issues & Questions == | == Open Issues & Questions == |
Revision as of 04:49, 29 July 2005
Error message text for netError.dtd
Firefox 1.5 will feature user-friendly error messages to help users when they encounter various network errors that result in pages not loading. Due to some overlap and checkin depedencies between the rendering of the error messages (bug 280190), and the error message text (bug 301208) this wiki is being used to synchronize the error text changes until it's time to patch the file itself.
You can see a preview of the error message rendering here.
The latest proposed patch to the netError.dtd file is here.
Open Issues & Questions
will we have access to the attempted URL for use in the error messages?- Yes, the URL is available.
- ok, using %address to refer to the attempted URI. --Beltzner 14:26, 27 Jul 2005 (PDT)
- will we have access to the product name for use in the error messages?
- Not yet, but we will have (bug 302309)
- ok for now will assume "Firefox" will resolve to some environment variable that's accessable from these messaages --Beltzner 14:26, 27 Jul 2005 (PDT)
- not sure about redirectLoop's recommendation to turn on cookies; security/privacy issues?
- That does seem to be the correct solution the redirectLoop problem in my experience, security/privacy issues aside. (weather.com is/was a particularly bad offender, as blocking cookies from one of its subdomains would cause the infinite redirect loop.) --Sardisson 20:35, 28 Jul 2005 (PDT)
- not sure about deniedPortAccess's recommendation about plugins/3rd party apps; could that happen?
- I don't think so; plugins should affect protocols, not port security when browsing HTTP. Could be wrong. --Wrprice 12:27, 28 Jul 2005 (PDT)
- Should some distinction be made for firewall/proxy possibilities between the browser's settings vs. the proxy/firewall's settings? (somewhat critical distinction)
- Proxy allows Firefox, but Firefox not set to use proxy.
- Firefox set to use proxy, but proxy/firewall does not allow the browser?
- Can't reference "Preferences" as an absolute because on Windows builds it's "Tools" > "Options".
Error Page label & retry button label
- loadError.label = "Problem loading page"
- retry.label = "Try again"
connectionFailure
Can't connect to this address
Firefox can't establish a connection to the server at %address.
- The site could be temporarily unavailable or too busy. Try again in a few moments.
- If you are unable to load any addresses, check the computer's network connection.
- If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
deniedPortAccess
This port is restricted
This address (%address) specifies a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection.
- You might need to install a plugin or other software to view this address. Go back to the previous page and check the site for any special requirements.
dnsNotFound
Can't find this server
Firefox can't find the server at %address.
- Check the address for typing errors such as ww.mozilla.org instead of www.mozilla.org
- If you are unable to load any addresses, check the computer's network connection.
- If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
fileNotFound
Can't load this file
Firefox can't find the file at %address.
- Check the file name for for capitalization or other typing errors.
- Be sure that you have the required access to see the file at this address.
- Check to see if the file was moved, renamed or deleted.
generic
Can't complete the request
Firefox has experienced a problem, and can't complete the current request right now.
malformedURI
The address isn't valid
%address isn't in a recognized format.
- Web addresses are usually written like http://www.example.com
- Make sure that you're using forward slashes (i.e. /).
shouldn't that be i.e. instead of e.g.? --Biesi 06:34, 27 Jul 2005 (PDT)
yeah, I think you're right; but maybe we don't need to use either? "..backwards slashes (\)? Addresses need to use forward slashes (/)"? --Beltzner 07:52, 27 Jul 2005 (PDT)
netInterrupt
The connection was interrupted
The connection to the server at %address was interrupted while the page was loading.
- The site could be temporarily unavailable or too busy. Try again in a few moments.
- If you are unable to load any addresses, check the computer's network connection.
- If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
netOffline
Offline mode
Firefox is currently in "offline mode" and is unable to browse the Web.
- Uncheck "Work Offline" in the "File" menu to take the browser out of offline mode.
netReset
The connection was reset
The connection to the server at %address was reset while the page was loading.
- The site could be temporarily unavailable or too busy. Try again in a few moments.
- If you are unable to load any addresses, check the computer's network connection.
- If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
netTimeout
The connection timed out
Firefox got tired of waiting to hear back from the server at %address.
- The site could be temporarily unavailable or too busy. Try again in a few moments.
- If you are unable to load any addresses, check the computer's network connection.
- If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
protocolNotFound
That protocol isn't recognized
Firefox isn't sure what protocol is being specified by %address.
- You might need to install a plugin or other software to view this address. Go back to the previous page and check the site for any special requirements.
proxyConnectFailure
The proxy server is refusing connections
Firefox is configured to use a proxy server, but that proxy server is refusing connections.
- Check the proxy settings in "Preferences" to make sure they are correct.
proxyResolveFailure
The proxy server can't be found
Firefox is configured to use a proxy server, but that proxy server cannot be found.
- Check the proxy settings in "Preferences" to make sure they are correct.
- Check to make sure you computer has a working network connection.
- If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
redirectLoop
The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for %address in a way that will never complete.
- Change your cookies settings in "Preferences" to accept cookies for this site.
unknownSocketType
Unexpected response from server
The server at %address responded to the request in an unexpected way, and Firefox cannot continue.