https://issues.apache.org/bugzilla/show_bug.cgi?id=55741
--- Comment #6 from Dirkjan Ochtman <[email protected]> --- (In reply to Nick Kew from comment #4) > In any case, it looks like a firefox issue (or a local issue). I haven't > checked it in the latest update, but when I first worked on charset issues, > the HTTP spec *explicitly* made iso-9958-1 a default if no explicit > content-type was indicated. Hence a browser needs, at a minimum, to accept > it. That may be so, but I think a bunch of this changed with HTML5 and new-found enthusiasm for standardizing actual browser behavior. Please check the W3C table I linked to in the description. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
