- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 25 Feb 2011 11:11:35 +0100
- To: Mark Nottingham <mnot@mnot.net>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
On 24.02.2011 08:54, Julian Reschke wrote:
> On 24.02.2011 06:39, Mark Nottingham wrote:
>> I wouldn't say we break FireFox by recommending this ("breaking" means
>> that C-D doesn't work at all, or produces garbage), and I wouldn't say
>> they've been doing the right thing (because they implemented to prefer
>> the non-internationalised filename).
>
> When I said "break" I mean that sending a I18Nized filename will not
> have the desired effect.
> ...
Looking at <https://bugzilla.mozilla.org/show_bug.cgi?id=588781#c21>,
the fix will go into Firefox 5, which is planned to be 3 months behind
Firefox 4.
Optimally, this would be ~July 2011.
On the other hand, to get to RFC we need
- to do the IETF LC -> two weeks
- get it through the IESG (I expect at least minimally one revision to
be requested) -> ~ two months
Once it's in the RFC publication queue, it'll take at least another six
weeks... Which would be around the same time.
Still, I'm very uncomfortable recommending something we're not sure will
work when the RFC is published.
Related to this; I just updated the notes with respect to the
filename*/filename fallback behavior; see
<http://trac.tools.ietf.org/wg/httpbis/trac/changeset/1140>.
Best regards, Julian
Received on Friday, 25 February 2011 10:12:20 UTC