W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2010

Re: Content-Disposition next steps

From: Mark Nottingham <mnot@mnot.net>
Date: Thu, 16 Dec 2010 14:36:51 +1100
Cc: "Jungshik Shin (신정식, 申政湜)" <jungshik@google.com>, Maciej Stachowiak <mjs@apple.com>, Adam Barth <ietf@adambarth.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <DB39590B-0A1A-4499-9356-24E892D1DF30@mnot.net>
To: Julian Reschke <julian.reschke@gmx.de>
Perhaps, but it depends on how Google sniffs the UAs. And I don't think it affects the spec.


On 16/12/2010, at 9:40 AM, Julian Reschke wrote:

> On 15.12.2010 21:19, Jungshik Shin (신정식, 申政湜) wrote:
>> ...
>> Before rushing to remove it (as an optional 'fallback') , I'd like to
>> have some 'numbers' about what web servers do (FYI, some Google products
>> emit RFC 2047 for Firefox and Chrome at the moment, but I guess Google
>> has to switch over to RFC 5987 for Firefox and Chrome). I'm not sure
>> whether the cost of supporting it is larger than the benefit.
>> ...
> 
> Indeed. GMail seems to use RFC2047-encoding (when saving an attachment with non-ASCII characters in the filename) for Firefox (and likely for Chrome as well).
> 
> So it's unlikely that UAs can remove this until this get fixed.
> 
> Best regards, Julian
> 

--
Mark Nottingham   http://www.mnot.net/
Received on Thursday, 16 December 2010 03:37:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:34 GMT