- From: Liam Quinn <liam@htmlhelp.com>
- Date: Tue, 13 Aug 2002 17:15:23 -0400 (EDT)
- To: Carlo Perassi <carlo@linux.it>
- cc: <www-validator@w3.org>
On Tue, 13 Aug 2002, Carlo Perassi wrote: > the default "404 Not Found" page generated by the latest version of Apache HTTP > Server (and the similar pages) doesn't pass the W3C Validator test > ( > it's a HTML 2.0 code shipped without a meta tag with charset value: try this > foo page to see it: > http://www.apache.org/doesntexist.html > ) There is no need to specify a meta charset in HTML documents if the charset is given in the Content-Type header. > "I would hope that if (the Validator) saw a good http Content-Type header, > it wouldn't need the stuff in the html meta line." That's correct. > Before trying the new Apache CVS code... I found a "problem": when your > Validator found a "404" on the response header of the server, it doesn't > parse the HTML provided anymore. I don't think it makes sense for the Validator to check unsuccessful responses since this almost always indicates an incorrect URL. To check a 404 error page, you can use the file upload form. > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>404 Not Found</title> > </head><body> > <h1>Not Found</h1> > <p>The requested URL /doesntexist.html was not found on this server.</p> > <hr /> > <address>Apache/2.0.40 Server at www.apache.org Port 80</address> > </body></html> They should change <hr /> to <hr>. <hr /> is for XHTML/XML only, but they've specified HTML 2.0. -- Liam Quinn
Received on Tuesday, 13 August 2002 17:15:24 UTC