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

Re: Content-Disposition next steps

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 15 Dec 2010 23:40:06 +0100
Message-ID: <4D0943C6.4010303@gmx.de>
To: "Jungshik Shin (신정식, 申政湜)" <jungshik@google.com>
CC: Maciej Stachowiak <mjs@apple.com>, Adam Barth <ietf@adambarth.com>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
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
Received on Wednesday, 15 December 2010 22:40:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:55 UTC