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: Thu, 16 Dec 2010 19:59:27 +0100
Message-ID: <4D0A618F.8090606@gmx.de>
To: "Jungshik Shin (신정식, 申政湜)" <jungshik@google.com>
CC: Maciej Stachowiak <mjs@apple.com>, Mark Nottingham <mnot@mnot.net>, Adam Barth <ietf@adambarth.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 16.12.2010 19:29, Jungshik Shin (신정식, 申政湜) wrote:
>
>
> On Wed, Dec 15, 2010 at 10:58 PM, Maciej Stachowiak <mjs@apple.com
> <mailto:mjs@apple.com>> wrote:
>
>
>     On Dec 15, 2010, at 10:46 PM, Mark Nottingham wrote:
>
>      > Because (if I read the original message correctly -- please
>     correct me if I'm wrong) they're sniffing the UA to do it, and if
>     they do that, they'll presumably adapt their sniffing based upon
>     changes in the browser market (as anyone who sniffs and believes
>     that they don't have to monitor the market tends to get bitten, hard).
>
>
> Yes, gmail sniffs the UA and emits RFC 2047 for Firefox and Chrome and
> RFC 5987 (RFC 2231) for Opera. The change to emit RFC 5987 for Opera was
> made rather recently (before that, non-ASCII characters were just tunred
> to question marks for Opera). Anyway, in case of gmail, it's relatively
> easy to make (at least I used to know where the code is and I hope it's
> still there for me to make a quick change).  Some other google products
> just turns non-ASCII characters to question marks for all the UAs (e.g.
> Google Docs) :-)   Obviously, it's a rather embarrasing bug to fix.

That would be great.

Actually, I'd change to emit RFC5987 for all UAs *except* those which do 
not support it yet (IE, Chrome, Safari).

>     Typically in cases like this you want to get sites to change before
>     breaking them. Often it takes surprisingly long for changes like
>     this to get implemented and pushed in a large-scale site, even for a
>     seemingly simple change.
>
>
> Yes, sites have to change before RFC 2047 support is dropped in Chrome
> and Firefox.

Do we happen to know *which* other sites?

Best regards, Julian
Received on Thursday, 16 December 2010 19:00:07 GMT

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