VEVIDA allows you to create your own error pages, for example for the 404 `file not found” error message. You can make a 404.html (or .asp/.php) page and place this in the root of the /www directory.
You must then make a note of this in the communication module on MyVevida with the request to activate this as a custom error page. We will do this for you at no charge.
You can find an overview of IIS (5 and 6) status codes here.
404 pages and search engines
If a file extension other than .html / .htm is being used (such as .asp / .aspx / .php / .cgi), it is a good idea to include a”404 File not found” header in the page to ensure that it functions correctly. Otherwise it will still give a “200 OK” message in the log files because it redirects to its own 404 file in IIS.
Search engines such as Google make a major point of this, more information on this can be found at this URL.
<?php header("HTTP/1.0 404 File not Found"); ?>
<%@ Language=VBScript %> <% Response.Status="404 File not Found" %>
#!C:/Perl/bin use CGI qw/:standard/; $query = new CGI; print $query->header(-status => '404 Not Found');
This will cause you to lose the website layout in the 404 page; the standard page from the browser will be displayed. A 404 page in the website layout is only possible if the .html / .htm extension is used.
404 or 410?
From RFC2616, section 10:
404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.