- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 24 Aug 2010 17:33:14 +0200
- To: "Eric J. Bowman" <eric@bisonsystems.net>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
On 24.08.2010 17:28, Eric J. Bowman wrote: >> >> 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*"? > > " > "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". > " Indeed :-) Thanks, and looking forward to more comments, Julian
Received on Tuesday, 24 August 2010 15:33:51 UTC