Re: channel4 validator failure [The error was "".]

Hi David,

Thank you for your quick response.

[...]
> No, the <meta> tag is a (very) poor mans way to specify HTTP headers,
> and real HTTP headers always take precedence. If I request those
> headers I get:
> 
> [david@cyberman ~/]$ lynx -head -dump "http://www.channel4.com/news/special-reports/special-reports-storypage.jsp?id=67"
> HTTP/1.1 200 OK
> Date: Tue, 26 Apr 2005 17:59:16 GMT
> Server: Apache
> Set-Cookie: JSESSIONID=CuP90nVOjbVQCzSrtM83cXtk2zcHTWTOiIVy29ZWnlOorhYCr1FZ!616
> 296125!c4wlgnode001!8888!-1; path=/
> Keep-Alive: timeout=15, max=81
> Connection: Keep-Alive
> Content-Type: ??/html; charset=UTF8
> Set-Cookie: NSC_d43e13d40050=c0a808170050;path=/
> 
> Note the Content-Type header. 
> 
> The content type should be "text/html" but comes out as "??/html"
> where "??" are characters that my terminal appears to have decided
> mean "Ctrl+End". The character encoded is specified as "UTF8" and is
> missing the "-"
> 
> If I repeat the request, the "??" part of the content type comes out
> as something different every time. Something is *very* broken with
> either the JSP script or the server.
>  
>> In addition, could a clearer error message be displayed by the validator?
> 
> Could you make a suggestion?

Ok, sure.  Certainly verbose shoudl display similar output to your dump
from lynx as above.

In addition this text would be nice:

=====================
Sorry! A fatal error occurred when attempting to transcode the character
encoding of the document. Either we do not support this character
encoding yet, or you have specified a non-existent character encoding
(often a misspelling).

Error: Invalid characters found in HTTP Content-Type: "??/html; 
charset=UTF8"
(Server likely has a configuration fault. Contact the hosts' webmaster.)

Error: Invalid charset: UTF8. Valid charsets are <link to valid list>
(Server likely has a configuration fault. Contact the hosts' webmaster.)
===============

Note I did not lower-case the "utf8" as the present web page seems to.
If it is "UTF8" in its broken form I think it should remain as that in
the error.

I am not on this list, please include my email address in any replies.

Kind regards
JG
-- 
Homepage: http://jguk.org/
Blog: http://jguk.org/blog.rss
Radio: http://jguk.org/#radio

Received on Tuesday, 26 April 2005 19:24:43 UTC