[webkit-dev] Removing deprecatedFrameEncoding

Julian Reschke julian.reschke at gmx.de
Mon Jan 16 16:24:36 PST 2012

On 2012-01-17 00:57, Alexey Proskuryakov wrote:
> 16.01.2012, в 15:15, Geoffrey Garen написал(а):
>>> 1) Standards compliance.
>> To me, this seems like your strongest argument. However…
> I'm pretty sure that no major browser implements - or maybe even intends to implement - all encoding-related aspects of RFC 6266. For example, Chrome uses default encoding instead of US-ASCII to interpret Content-Disposition bytes. This is clearly a case of using external context to interpret the response, and a violation of letter and spirit of the spec.

RFC 6266 doesn't mandate US-ASCII here. It defaults to what HTTP/1.1 
defaults to, and that is ISO-8859-1.

According to <http://greenbytes.de/tech/tc2231/#attwithisofnplain>, all 
UAs do that in absence of out-of-band information, and given a valid 
ISO-8859-1 octet sequence that doesn't look like UTF-8.

Now I'm the first one to agree that ISO-8859-1 was a bad choice as 
default. It's for historical reasons. Blame those who worked on the 
specs in 90s.

> There is a long history of HTTP related specs disregarding browser needs when it comes to non-ASCII characters in headers fields, or to stateful interpretation of responses.

"There's a long history of browser makers ignoring the standards process 
and writing crappy implementations".

Not productive.

If you don't like where the specs are headed, provide feedback to the 
Working Groups producing them.

> This is a discussion that we had before, including on this list. I don't think that enough has changed to make spending time on this again very useful. The whole topic is quite isolated and inconsequential, so the intensity of argument (particularly in bug 67882 and its patch) does not appear adequate.

I support Adam in his proposal to clean up the mess. But we should keep 
in mind that what's much more important here is to actually provide 
developers with a protocol/format that is interoperable for non-ASCII. I 
note that Safari is the only current browser which doesn't implement RFC 
5987 (*). Enough said.

Best regards, Julian

(*) IE9 only supports UTF-8, but see 

More information about the webkit-dev mailing list