Re: ISSUE-28 (http-mime-override): Content type rules in HTML 5 overlaps with the HTTP specification? [HTML Principles/Requirements]

Boris Zbarsky wrote:
> 
> Oh, one more note.  Gecko's sniffing behavior actually had to be changed 
> recently.  Unfortunately, the more recent Apache installs changed from 
> ISO-8859-1 to UTF-8 as the default encoding, without changing the 
> default content type behavior.  So at this point, in Gecko, data flagged 
> as "text/plain; charset=UTF-8" is also sniffed to see whether it might 
> be binary.  Since all of the byte values that trigger the "binary" 
> determination are illegal in UTF-8, as far as I can tell, this shouldn't 
> affect any actual UTF-8 text.  It might be a good idea to update the 
> tests and the spec if people agree, though.

It's also worth noting that in httpd trunk, the new default is *not* to 
send a content type at all when it is unknown. Thus, the original 
problem (in Apache) has finally been fixed.

BR, Julian