[webkit-dev] Removing deprecatedFrameEncoding

Julian Reschke julian.reschke at gmx.de
Tue Jan 24 14:33:17 PST 2012

On 2012-01-24 23:28, Alexey Proskuryakov wrote:
> 24.01.2012, в 14:03, Julian Reschke написал(а):
>>> Having UTF-8 Content-Disposition served by all Web sites that offer downloads would be the ideal outcome from higher principles. RFC 5987 style gobbledygook really has no purpose here, and only complicates life for implementors, site authors and admins alike.
>> RFC 5987 "gobbledygook" works in all recent browsers except the one you're working on. It's the only thing that currently works almost everywhere.
> You chose to overlook the part about "ideal outcome" and "higher principles".
> A header value that can be sent, consumed and observed (with tools like tcpdump) directly without turning it into unreadable gobbledygook is superior to one that can not be.

Yes. If it worked.

>> I know you don't like it but please stop spreading FUD. RFC 5987 allows senders to send the same thing to all clients without UA sniffing. If you have a different proposal for which this is true please go ahead and write it down.
> What exactly am I spreading FUD about?

"has no purpose here"

>>> We know that it works in practice.
>> No, it does not "work". See<http://greenbytes.de/tech/tc2231/#attwithutf8fnplain>. So IE, Opera, and Konqueror decode as ISO-8859-1.
> It works with servers and intermediaries. Internet infrastructure would not collapse if UTF-8 was sent in a response header.

And I never said that.

But sending UTF-8 does not work with two major browsers, so how exactly 
does it "work"?

Again, please make a proposal that is deployable and works without UA 
sniffing. I'm listening.

Best regards, Julian

More information about the webkit-dev mailing list