On 2012-01-19 00:28, Alexey Proskuryakov wrote:
18.01.2012, в 13:02, Adam Barth написал(а):
I used to hold that opinion, but folks convinced me (and the rest of
the httpbis working group) otherwise, hence the standard.
A working group that that can be convinced to specify something so out of line
with how browsers work is not one we should be following blindly.
We asked browser developers to write down what *they* think is needed,
and didn't get a proposal -- mainly because the browsers do not
interoperate on this.
It's especially so in this case, where limitations on how non-ASCII bytes are
interpreted do not solve any problem except for formal compatibility with some
universally ignored text in RFC 2616.
I agree that changing things over here doesn't help with any real-world
problems, because developers will wouldn't be able to send non-ASCII
filenames reliably (well, unless we agree on everything being UTF-8, but
that would have broken existing content as well).
On the other hand, removing unreliable options reduces
incompatibilities, untested code paths (you know what I mean), and helps
developers focus on the variants that do work predictably.
Best regards, Julian
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
