Re: %encoding in filename parameters. Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 from Julian Reschke on 2010-10-03 (ietf-http-wg@w3.org from October to December 2010)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sun, 03 Oct 2010 22:15:52 +0200
To: Adam Barth <w3c@adambarth.com>
CC: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <4CA8E478.1080501@gmx.de>

On 03.10.2010 21:21, Adam Barth wrote:
> On Sun, Oct 3, 2010 at 12:03 PM, Julian Reschke<julian.reschke@gmx.de>  wrote:
>> The site I worked on (an SAP content management system) indeed will not work
>> with Chrome, unless it has been fixed since Chrome came out (which I doubt
>> because that system is in "maintenance mode"). It will send the
>> RFC2231-encoded parameter, and Chrome will not "get" the "filename*"
>> parameter. If RFC 2231 support was added in Chrome, the problem would simply
>> go away with no server change being required.
>
> I don't think anyone has opposed adding RFC 2231 support.
> ...

Well, IE has since 2003, and Chrome since it came out.

Best regards, Julian

Received on Sunday, 3 October 2010 20:16:31 UTC