The Perfect 404

Oops. Something went wrong. You’re not sure what — was it you? Was it the website? What do you do now?

Article Continues Below

Welcome to the world of the Error 404 page. You’ve requested a page — either by typing a URL directly into the address bar or clicking on an out-of-date link and you’ve found yourself in the middle of cyberspace nowhere. A user-friendly website will give you a helping hand while many others will simply do nothing, relying on the browser’s built-in ability to explain what the problem is. We can do better than that, can’t we?

I won’t go into details about how you set your server up to deliver a custom 404 page — instead, I’ll refer you to these articles:

I will, however, suggest strategies for building a custom 404 page that makes the most of an otherwise lost cause.

To get started, we need to examine the most common reasons that people find themselves on a 404 page:

  • a mis-typed URL (or an out-of-date bookmark/favourite)
  • a search-engine link that is out-of-date
  • an internal broken link that the webmaster hasn’t noticed

They all amount to the same thing, but they need to be handled slightly differently — the 404 message needs to be customized for each eventuality. There are some tricks that you can employ that apply to all scenarios, but my first suggestion is simple…

Don’t point the finger#section2

Tell them what went wrong, by all means, but don’t admonish the user, even if you know it’s their fault! The phrases, “might have” and “possibly” are good ones to use here. Don’t get off on the wrong foot with this visitor to your site — you might yet turn this problem around.

404 Must-haves#section3

As well as the “something went wrong” text, you should ensure that your error page has the following:

  • A link to the site map (if you have one) and the home page. This is the easiest way for users to bail out. This no-brainer requires no clever scripting.
  • A search box. If you have a site search, add it to your 404 page. If you don’t have a site search and are in the habit of generating 404 errors, perhaps you should get one.
  • A distinctly minimalist look. Avoid putting all your standard site navigation on this page. You should aim to remove distractions. Besides, insisting on including a complete site navigation strip may present a maintenance overhead (your 404 page can easily lag behind the rest of the site if it is not dynamically updated with the rest of your site and the last thing you want is to have navigation on the 404 that is no longer relevant/working. Oh the irony!)

Also be sure to cut the jargon. I mean, we can talk about 404s here, right? We’re in good company. But 60-year-old Doris who got a broken link while browsing a knitting site won’t have a clue what a 404 error is. If you want to use the phrase “Error 404,” do it subtly — do it as a footnote, a nod to those who understand your freaky-deaky web speak.

Now, let’s look at how you can make the 404 work for you, instead of against you.

Let’s be intelligent about this#section4

At this point, I should point out that this may require a certain amount of JavaScript (you may not be able to use server-side scripting to do this work, depending on your server set-up). So be sure to use the <noscript> to serve up a suitable message for people who have disabled scripting. If you can use server-side scripting, that would be preferable — no accessibility or browser support issues — so adapt the suggested code as appropriate.

First, you’ll need to set up a few variables:

var strReferrer=document.referrer.toLowerCase();
var blnSearchReferral = false;
var blnInsiteReferral = false;
var str="";
var strSite = "";

Now, how are we going to use these?

The mis-typed URL#section5

A mis-typed URL (or out-of-date bookmark) will have no referrer, so your code to identify this scenario should look something this:

if (strReferrer.length==0)
  str+='We think you will find one of the following »
    links useful:<\/p>';
  str+='<a href="\/home.php"><img src="/images/ »
    home.gif" alt="Home Page" width="100" height="30" »
    \/> <\/a>';
  str+='<a href="\/site-map.php"><img src="/images/ »
    site-map.gif" alt="Site Map" width="100" height= »
    "30" \/><\/a>';
  str+='<hr \/>';
  str+='<p><strong>You may not be able to find the »
    page you were after because of:<\/strong><\/p>';
  str+='<ol type="a">';
  str+=' <li>An <strong>out-of-date bookmark\/favorite »
  str+=' <li>A search engine that has an <strong>out- »
    of-date listing for us</strong><\/li>';
  str+=' <li>A <strong>mis-typed address</strong><\/li>';

The out-of-date search engine referral#section6

If there is a referrer value, we can look for an instance of specific search engines (and you can obviously tweak this to your own taste). Then we can split the search parameters up, look for significant matches to a list of terms you want to intercept and suggest a page that is probably appropriate to that search:

if (strReferrer.length!=0) {
  if ((strReferrer.indexOf("")>0)||
    //get site domain — split at the first forward-slash
    var arrSite=strReferrer.split("/");
    // now find search parameters
    var arrParams=strReferrer.split("?"); 
    var strSearchTerms = arrParams[1];
    var sQryStr="";
    //define what search terms are in use by the different engines
    var arrQueryStrings = new Array();
    arrQueryStrings[0]="q=";  //google, altavista, msn
    arrQueryStrings[1]="p=";  //yahoo
    arrQueryStrings[2]="ask=";  //ask jeeves
    arrQueryStrings[3]="key=";  //looksmart
    for (i=0;i<arrParams.length;i++)
    //loop through all the parameters in the referring page’s URL
      for (q=0;q.indexOf(sQryStr)==0)
      {//we’ve found a search term!
      strSearchTerms = arrParams<i>;
      strSearchTerms = strSearchTerms.split(sQryStr);
      strSearchTerms = strSearchTerms[1];
      strSearchTerms = strSearchTerms.replace("+", " ");
  //Tell the visitor what site is at fault, what the 
  //search terms were
  document.write ("<p>You did a search on <strong> <a href='" + strReferrer + "' target='_blank'>" + strSite + "</a> </strong> for "<strong>"+ strSearchTerms + "</strong>". However, their index appears to be out of date.</p> 
  <h2>All is not lost!</h2>
  <p>We think that the following page(s)on our site will be able to help you:</p>");

You can now add in some lines to identify key search phrases that you don’t want to be lost. For example, say you’re getting good search results for the words “electronics” and “widgets” but you’ve just moved pages around in your site — no good losing all those existing Gooogle referrals, is it?

if (
    document.write("<a href='/cool-widgets.htm'>Our excellent widgets page</a><br />");

Of course, if you have an internal site search, you could use the search parameters found in the URL to generate a search automatically, rather than this very manual process. However, the manual approach may be preferred (otherwise you may only be adding another hit-and-miss search process to one that already failed).

The broken (in-site) link#section7

With the errant search engine referrals taken care of, we now need to look at referrals that are not from a search engine (or at least not a search engine you’ve chosen to look for). We’ll need to add some more conditions:

if (!blnSearchReferral) {
  strSite = strReferrer;
  strSite = strSite.split("/");
  strSite = strSite[2];
  document.write("<p>You were incorrectly referred to this page by: <strong><a href='" + strReferrer + " 'target='_blank'>" + strSite + "</a></strong> <br />We suggest you try one of the links below: </p>");

… those links being the site map and home page mentioned right up front.

What if your own site is the problem?#section8

You cannot say in your 404 page “This site had an incorrect link” when the errant referrer is actually one of your own. In this instance, you might need to change the language to admit some guilt!

blnInsiteReferral =((strReferrer.indexOf("")>=0)||
(strReferrer.indexOf("") >=0))
if (blnInsiteReferral) {
  document.write("<p>This one’s down to us! Please accept our apologies for this — we’ll see to it that the developer responsible for this broken link is given 20 lashes (but only after he or she has fixed this problem).</p>");

Fixing the problem#section9

>So, we’ve provided routes out of the 404 black hole. But have we actually fixed anything? No. We do have some options though, as we know the page requested and the referring page (if indeed there was a referrer). We could capture this information in a database, either automatically or via a manual “report this broken link” button offered to the user when they hit the 404 page. The latter should cut down on noise, and the hope is that you’ll only get to hear about the most important broken links. How you go about fixing them from here on in is up to you.

Related links#section10

To see this advice in action, try the following examples hosted at Accessify and A List Apart:

[Note: the pages seem to have been lost to time. —Ed.]

  • paste this in to your address bar to show the behavior for an out-of-date bookmark:
  • a broken link
  • mimicking a Google search [intermediate page required to trigger]

Download the example error 404 page described above (and amend to suit your own needs).

About the Author

Ian Lloyd

Ian Lloyd runs, a site dedicated to promoting web accessibility, and is an active member of the Web Standards Project. Not long after you read this, he’ll be fleeing UK for a year around the world, so be prepared for delays in him answering emails — we hear the Fijian internet cafés have some catching up to do.

57 Reader Comments

  1. Ian Lloyd is out and about in Australia and will have intermittent Internet access for a few days after the publication of this article. Should you have any questions for him, please be patient. All will be answered in the fullness of time.

  2. The best way to deal with 404s is not to have them in the first place. Every time I move a page on my site I leave behind a file in the same place with the same filename that tells the user the page has been moved, and gives them the new link.

    The alternate method is to use .htaccess files to automatically redirect the user to the correct place. You can redirect based on wildcards, so whole directories can be catered for. No more 404s.

  3. Arg!

    I’ve stated this before, but I’ll say it again, as it seems that people overlook this.

    “expired links” ie. links that used to exist but now exist in a new location [vs. mis-typed links] should be redirected via an HTTP ERROR 301 “file permanently moved” or an HTTP ERROR 302 “file temporarily moved”. These are seamless re-directs and will automatically update personal bookmarks *and* allow search engine crawlers to update their entries.

    301 and 302 errors are obviously a better choice than presenting the visitor with a page telling them that something doesn’t exist, with the bonus of “fixing” old search engines without begging Google et al to change them for you. 404s should only be used in cases where the URLs are totally invalid due to human typographic errors, or the content doesn’t exist on the site anymore

  4. Actually, if the URL used to be valid but isn’t anymore, and the content does not exist at any other location, the proper HTTP status code is 410, not 404.

    Also, Ian, the sample links to attempt to download the page rather than displaying it. I’m using the latest nightly build of Firebird. It works properly in IE6.

  5. i didn’t think this would be a very informative article, since error pages are very easy and basic, but there were some pretty useful tidbits stashed.


  6. If your site is running on top Apache and you’re allowed to use .htaccess files, create a file called, ‘.htaccess’ and put the below (between the snips)in there:

    Redirect Permanent /the/old/page.html

    (all on one line, mind)

    Save this file in your root public_html directory (the same place you put, say, a robots.txt file)

    That way, the user will never see an error page, which is what a “404” is (an error smarty) Yes, a visitor will never know that they need to, “update their bookmarks”, but when’s the last time you did that? That’s what I thought…

    If you want to get really techy, you can use the “RedirectMatch” thingy, like this:

    RedirectMatch ^/the/old/directory

    If you have some sort of odd fetish and know regex’s like the back of your hand (hairy hands up!), you’ll know that the caret (^) means: “match the beginning of a line”.

    We follow that with a directory. That means, any request to the directory will be redirected to a different directory.

    Finally, notice that you can use ANY url for,””. For instance, if you move your entire site, or, a portion of your site – say your knitting tips are REALLY taking off and deserve their own site, it’s really no problem now, init?


    Justin Simoni

  7. That’s because the server returns Content-Type: application/octet-stream instead of text/html in the HTTP headers. Mozilla doesn’t know what to do with an octet-steam, so it pops up a Save to Disk box.
    I’ve sent a bug report to

  8. .htaccess

    I have updated .htaccess when moving files and directories around, but I ususally do it in the old subdirectory so as to reduce the load on the root .htaccess; perhaps this is overkill, and may be harder to maintain.


    Not sure how to make Apache spit this out. I’d still probably want to show the same error page. Actually, we show the same error page for 403 as for 404, simply to keep the content simple for the end-user.

    If we can’t find a trace of the file, I wonder whether it would make sense to offer to search for the page at, with the warning that the page is presumably out of date.

  9. Sorry, didn’t know what was kosher for link making in comments here on ALA. Perhaps a short description would be useful, much like a good 404.

  10. << Sorry, didn't know what was kosher for link making in comments here on ALA. Perhaps a short description would be useful, much like a good 404. >>

    At the top of every page of the forum is this short description:

    Discuss this article. HTML tags and entities display as source; they do not render. To create a live link, simply type the URL (including http://).

  11. Scripting to enhance the error page is a good idea, especially when you have limited control over the server configuration and cannot implement custom error pages on the server.

    The examples seem to be vulernable to cross-site scripting, though, with referrer information written out unescaped, which may have some undesirable side effects …

  12. At Virgin Radio, we worked hard on our 404 errors. I liked this article, but think we’re ahead of the crowd here, and we’ve some more examples you might like.
    – this page doesn’t exist, but we automatically search for possible results from the URL you gave us. Why not? It makes sense.

    But if you’re going to run searches automatically, you need to make sure this doesn’t happen on non-HTML requests – it’ll kill your server otherwise! A graphics file, like
    …returns a much simpler error page.
    (As does a multimedia file, like )

    We also use our 404 error code for simpler URLs for use in advertising. properly directs to the correct file at

    Here’s hoping these ideas are useful. If you want to contact me further, I’m at

  13. Another addition worthy of note is that if your site is running on Apache (version 1.3 or greater) then you can enable mod_speling.

    This module allows for capitilisation issues (only a problem on non-windows servers) and also allows for one spelling error.

    An as example if you typed in instead if index.htm, or statd instead of stats, Apache will attempt to track down the right file or directory before issuing you the appropriate error.

  14. Just to add to what Josh L posted above, mod_speling can be good for taking care of some of the typos, though obviously is not ideal for those worried about performance. It does, however, check both spelling and capitalisation.

    In addition, if you are do use a server side language to serve up your 404 pages (and other error docs), it can be extremely beneficial to have the page email you whenever an error doc is served. Ideally, include all request headers with it too, so you can track down the cause of the error.

  15. Thanks for everyone who has commented so far. It has caught me off guard a little though, and as editor Erin pointed out, it’s also happening while I’m on travels and so I might not be able to respond in as timely a fashion as I’d like.

    Thanks to James Cridland for building on the ideas I had in the article. I knew there would many other great ideas, so thanks for sharing.

    As many have pointed it, there is an irony that in a piece about 404 errors, there has been another error in one of the example 404 pages, that being that the 404 page being served up is coming through as an octet stream. In IE it renders fine but on Firebird it prompts to save the custom 404 page as a file. If anyone knows how to remedy this, please add to the discussion.

    Thanks also to Klaus for pointing out that Cross-site scripting was a potential problem. I don’t know how much of a problem this is – I do not have the mind of a hacker! – but I am not married to the notion that the script must be client-side. If the server config allows, I would favour server-side scripting which should, as I understand it, stop (or at least reduce) the spectre of cross-site scripting. If’ I’m wrong, please do tell ASAP.

  16. Depending on your setup, it is helpful to add some server-side code into the custom 404 page to eMail the administrator information about the offending link. With PHP it is easy to create a mail message containing the URL (if they mis-typed it you can see what it was) the Referrer (so you can see if google has an outdated link or fix a link within yourown site), and other information like date/time, etc.

    If you don’t have the ability to put this code in your custom 404 page, that’s OK. You can create a php file with just the mail function. Then in the HTML of the custom 404 page add a something like this in the head tag.

    This contains the PHP mail function. If done properly, it will be called when ever someone hits the 404 page.

    This will eMail you a heads-up that there is an error. If the offending link is from within the site, you can fix it. If the link comes from a search engine, you can temporarily re-create the link and point it somewhere else. You can even add a snippit of code to the top to tell the search engine the content has permenantly moved

    header(“Status : 301 Moved Permanently”);
    header(“Location: correct_link/”); /* Redirect browser */

    Having a well designed custom 404 page is great, but after one person gets there, you should be making every effort that no one else does. Without any information about what caused the 404, someone is doomed to repeat the error.

  17. I have built a custom 404 page with some of the ideas here and toyed with the idea of an automatic email but a glance at my log files put me off the idea – most of the 404 errors come from script kiddies and worms looking for vulnerable web servers. Instead I plan to add an optional ‘Tell the webmaster’ form. Clicking submit without doing anything else will send the URL but they will have the option to add a comment and a return email.

    Back to our current 404 page – Its all server-side using vbscript on an MS box. I use a text file that holds possible matches for the error URL. These include names for our larger directories, URLs for pages that have been moved, wrong URLs that published elsewhere.

    If someone has a dud URL that points to somewhere in our ‘rules’ directory, they will be offered a link to the ‘Current rules and regulations’ contents page.

    If its a known problem, eg a magazine has published a URL with a typo, we can offer the exact page.

    The same idea on our search page gives ‘recommended links’ for our most common search terms.

    I’ll have to look at the idea of dealing separately with typos and wrong referrals. What happens when people just chop off the end of the URL looking for an index page? We get a few of those.

    If you have to deal with a Microsoft IIS server and would like the code, I’m happy to supply it.

  18. If you are scripting a custom 404 page then it is critical to send appropriate headers. For example:

    This will inform user agents (such as Googlebot) that the page is a 404.

  19. Does anybody have a good way of going to a URL and specifying a false referrer? Not sure how to test drive all the different pieces of this without, for example, convincing a search engine to link to a nonexistent page in my site…

  20. One thing that is not mentioned in this otherwise good article is that you should have your system set up to send mails or other forms of data to your webmaster/system everytime a 404 fault is registered. This ensures a proactive approach if something is wrong and needs to be fixed i.e. someone in the marketing department has done a mailing with a wrong URL.

  21. Nate, you can just have a link to a non-existant page from another site. Just post it in a forum or something and click on it. That should work for testing purposes.

    In response to the article, I think it has some good ideas. I will not use Javascript to implement this, but I undertsnad why the author did so. Thanks for taking the time to write this article, good ideas!

  22. 1. The comment delimeters for Javascript have not really been needed since Netscape 1.0 died – they were there to prevent browsers that were not aware of the

    .. there are also cases where this theoretically could fail (e.g. if you serve this to a client that doesn't understand what a CDATA section is, it could throw script errors). If you wanted to satisfy both the pseudo-xhtml-crowd, and the old-browser-crowd, you could use something insanely complex like

    In the end - you'd really be better off using an external script that modifies the source of the document - which would also do away with the need for a

  23. Hello… I’ve done a tentative converstion of this to php for those of you who may want it.

    It’s kind of tough to debug because I can only check it through so there may be a few slight errors, but I think it’s pretty close to done. If anyone out there wants to do a double-check of my conversion please do!

    Keep in mind that this code will still need to be modified a bit to suit your specific needs.

  24. It’s also posssible to tailor the content of a 404 page based on the file or file type requested (James Cridland hinted at this in an earlier post). For example I cooked up a little something becuase I wanted to offer mp3 downloads for a limited time period, then just delete the files and forget about them (yes, yes, I know, moving/changing urls is very bad practice but sometimes you just can’t help it. I can’t anyway).

    I did something like this in php:

    if(preg_match(‘/mp3$/’ $_SERVER[‘REQUEST_URI’]))
    echo ‘‘;

    // custom error message

    } else {

    // standard 404 error message


    It at least allows you to offer a little explanation. Trivial demo:

    There’s probably a dozen better ways to do the same thing, but that seemed to work for me.

  25. Or, if you prefer your php to parse correctly subsitute:

    if(preg_match(‘/mp3$/’, $_SERVER[‘REQUEST_URI’]))

    * sigh *

  26. I screwed up my 404 page once; hopefully others might benefit from my mistake.

    My host offered “missing.html” as the 404 handler, and I had a basic 404 page done some time ago. Later I converted my site to PHP, and added a directive with mod_rewrite to redirect *.html to *.php. I noticed this stopped loading my 404 page, so I thought I’d just rename missing.html to missing.php.

    After a very long time I began to notice my custom 404 page was appearing in search engine results. Turns out my PHP redirect was making errors return a 301 (moved permanently) message instead of 404.

  27. If you mistype the WAP url above, the server will send a 404 status followed by a nice little HTML page.

    But WAP phones can’t read HTML, so all the user will see, is “INVALID FILE TYPE”.

    Conclusion 1: The WAP gateway should intercept the 404 message, and supply its own WML error page.

    Conclusion 2: The WAP gateway doesn’t, so if your site has WAP pages, it should send WML error pages to WAP user agents.

    In general, we should always try to send a MIME type that the UA says it will accept. But IE doesn’t say that it accepts text/html, so forget it, see

  28. Bruce – I agree entirely, it seems like a good idea to include an auto email facility (if you can do this) to notify the webmaster, but it can get out of hand too quickly. Many of these ideas were used in the error 404 for Nationwide Building Society (my place of employment when I’m not slacking around the world!) and the key thing was not to overload some poor admin person. Hence, the technique was an opt-in one – if the page they wanted was important, they’d probably report it otherwise it gets ignored. Or at least that’s the theory!

  29. An error is an error. An exception should not be replaced by anything!

    If I download a web-document using a spider or robot I *WANT* the 404 as an error, not as a page. The ‘invention’ you show us here also break link-checkers, since they simply will find: aha, there is a document on this link, so all is fine.

    Usability is to be enhanced by applications, not by data-files. If the data is missing it is missing. If the programmer of the web-server wants to analyze the user-agent-string and send a special document: ok. If the browser does offer a better option: ok. But if the server sends a search- and report-form to the robot: bad!

  30. Read the provided links. This is not a hack, this is an encouraged standard by Apache.

    ErrorDocument is an Apache directive that only customizes a standard Apache response containing important HTTP header information (404/301/etc). The URL is not going to be written to your browser’s address bar.

    Apache will serve the appropriate header information, i.e. the 404, and then provide this page in place of the incorrectly requested one. Google does not catalog pages that give the appropriate 404 header information, nor 301, etc. You can deny direct access to those files by simply adding a ‘Deny From All’ htaccess file in the error directory itself.

    The page that is served in conjunction with ErrorDocument is exactly the same as what you *WANT* and *GET*, this is only Apache’s way of allowing you to customize it’s look, feel, & functionality.

    If you’re still not convinced, read this:

    Excerpt ::

    If all attempts to locate the content fail, Apache returns an error page with HTTP status code 404 (file not found). The appearance of this page is controlled with the ErrorDocument directive and can be customized in a flexible manner as discussed in the Custom error responses and International Server Error Responses documents.

  31. Better late than never.
    Ian and Andrew inspired me to write an ASP custom 404 page based on their ideas/design/style. Which is useful because I can actually use it for the health systems’ website that I manage. I believe simple and consistent options for all platforms could make 404 error pages useful across the board.

    eh – eNjoy…

  32. from experience…

    if you use apache’s mod spelling then that’s it for server side (untill apache 2).

    if your isp has mod spelling turned on, you can turn it off with .htaccess but your error page (php etc) will still not run as the page has already been sent to mod spelling.

  33. MSIE/PC is per default set to
    “Show friendly HTTP Error Messages”
    thus making it impossible for ca. 95% of all users to benefit from the article’s idea as they are presented with what MSIE thinks is a good 404. (or 401 or the like)

    The default setting can be overruled easily but most users don’t (and wouldn’t know about it anyway).

    Web developers tend not to use MSIE for private surfing, (quite OK) so I guess that’s how the article came into beeing; good idea, but not fitting reality.

    By the way, I don’t see the point for relaying on client side scripting, server side offers the same possibilities here and wouldn’t exclude ca. 10% of all users.
    (some stats state that number for JS-less users)

  34. octet-stream solution (re Ian’s page 3 post)

    “…there has been another error in one of the example 404 pages, that being that the 404 page being served up is coming through as an octet stream. In IE it renders fine but on Firebird it prompts to save the custom 404 page as a file. If anyone knows how to remedy this, please add to the discussion.”

    IE violates the W3C rule of using MIME-type to determine how to handle a file; it uses the dot-extension instead. So IE will work fine with application/octet-stream (a default MIME type for some servers) while standards-compliant browsers will attempt to download the file. The solution is to send .asp files out with the proper MIME type.

    In Apache, you would put this line in the .htaccess file of the root folder of your Web site (if you are the server master, you would put it in httpd.conf in /www/conf instead):

    AddType text/html .asp

    Other Web servers may use other syntax and files.


    re: MSIE 404 default

    The MSIE default page for 404’s and other server errors only shows if the site-supplied 404 page is shorter than a certain number of bytes, 512 I believe. If you want to show a custom page, you need to make sure it is longer than that length, so don’t be *too* terse.

  35. >The MSIE default page for 404’s and other
    >server errors only shows if the site-
    >supplied 404 page is shorter than a certain
    >number of bytes, 512 I believe.

    I tried this with MSIE6/WinXP, works well, 512b is the exact threshold.

    Thanks for the info, calling the article “useless for 95% of all users” was rash, I apologize.

  36. One thing that annoys me almost everyday:

    Some people redirect every 404 Error to their Main 404 page. So I loose the original URL in the case I’d like to debug my incorrectly typed URL or to hack it in order to look what I can find around.

    So, whatever 404 page you put, please, don’t redirect the user somewhere else.

  37. There is no reason for 404 error pages.

    In the years I am browsing the web, no single 404 page has helped me and your approach does not help either.

    The site is either searchable or not. If so, what does it cost to return to the top or the previous page and access a search box there ?

    404 is an error. An exception. It means: No document at given location.

    This is important ! Robots, Spiders, Downloaders use this to compute results. And these programs are the ‘other’ users of the web. You simply let them not read.

    Whenever I mirror a site with ‘wget’ I am very angry for all those 404-error-pages, that mean nothing to me. Even worse, this way sepcialized programs are not able to determine “holes” in a web-document.

    How with an error is being dealt is solely up to the clients programmer and user, not (!) to the web-designer.

    The web would be much nicer, if more web-designers would realize, that the internet is not a human-only territory.

Got something to say?

We have turned off comments, but you can see what folks had to say before we did so.

More from ALA