By accident I stumbled upon this Firefox somewhat equivalent of IE’s ‘Show friendly HTTP error messages’ option. Any webdeveloper should have this turned off by default. How else will you know what the problem is? So here’s how to do it:
Now you’ll get extended warnings instead of the simple warning dialogs when, for example, you accidentaly link to a non-existant domain. Or, like me, the dreaded ‘The document contains no data’.
If you don’t know where to find this in IE: ‘Tools’ > ‘Internet Options…’ > ‘Advanced’-tab > Near the end of the ‘Browsing’-section. > Uncheck.
Previous article: Google Maps expands to Europe, needs to learn more… Next article: To Watch: Microsoft to Add Ordered List support in RSS?
[…] http://www.thinklemon.com/weblog/2005/06/22/turning-off-the-friendly-http-error-messages-in-firefox/ […]
[…] http://www.thinklemon.com/weblog/2005/06/22/turning-off-the-friendly-http-error-messages-in-firefox/ […]
I tried this in Firefox and it has always been set to true, which is the default. However, I still get the friendly error messages.
On another note, if I enter a URL (i.e spike), (which runs off to my localhost spike proxy), and the proxy is down, instaed it looks up on Google and sends the request to spiketv.com (or net), which is rather sad.
Anyone know how to solve this one as well?
Cheers,s
This setting was only valid in the Fx1.0 days. When all you got was an alert box stating Firefox couldn’t do something, instead of telling exactly what went wrong. Since 1.5 it’s the other way around. Now you’ll get an error page instead of a dialog box. (Setting it to false still reverts back to the dialog.)
If Firefox cannot resolve the address (spike) it’ll do an ‘Im feeling lucky’ on Google. That’s why you’ll end up on ’spiketv’. To tell Firefox to look on your localhost no matter what, you’ll need to do some rerouting on your system (I assume). On Windows you’ll need to alter the HOSTS-file and tell the OS ’spike’ is ‘127.0.0.1:(port)’. But look that up as it’s too long a story to post here. ![]()
On a sidenote: Roachfiend.com has a post on hacking Firefox’ error pages. But that’s probably not for the faint of heart. ![]()