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

Re: Fwd: I-D Action:draft-reschke-rfc2183-in-http-02.txt

From: Eric J. Bowman <eric@bisonsystems.net>
Date: Tue, 24 Aug 2010 09:28:27 -0600
To: Julian Reschke <julian.reschke@gmx.de>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <20100824092827.af5be569.eric@bisonsystems.net>
> this is a new revision of draft-reschke-rfc2183-in-http defining the 
> Content-Disposition header field as used in HTTP, replacing the 
> definition in RFC 2616, and building on the encoding defined in the 
> recently published RFC 5987.

Hey, Julian.  Shouldn't the last word in the following paragraph be

"filename" and "filename*" behave the same, except that "filename*"
uses the encoding defined in [RFC5987], allowing the use of non-ASCII
characters ([USASCII]).  When both "filename" and "filename*" are
present, a recipient SHOULD pick "filename*" and ignore "filename" -
this will make it possible to send the same header value to clients
that do not support "filename".

Received on Tuesday, 24 August 2010 15:28:51 UTC

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