Frank Ellermann wrote:
Julian Reschke wrote:
there's also RFC2616
Yes, that's an ugly legacy exception...
<http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/issues/#i20>
...maybe 2616bis can drop this oddity in favour of a simple
"unknown text is ASCII" rule. HTTP oddities shouldn't affect
MIME registrations, there's no string "2616" in BCP13.
Indeed.
It would be nice if somebody could provide some insight why this ever
made it into HTTP. Was that just an attempt to allow text/html encoded
in latin1 to be served without charset parameter?
BR, Julian
