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

"Eric J. Bowman" <eric@bisonsystems.net> Tue, 24 August 2010 15:28 UTC

Date: Tue, 24 Aug 2010 09:28:27 -0600
From: "Eric J. Bowman" <eric@bisonsystems.net>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <20100824092827.af5be569.eric@bisonsystems.net>
In-Reply-To: <4C73DD78.3070700@gmx.de>
References: <4C73DD78.3070700@gmx.de>
Organization: Bison Systems Corporation
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Received-SPF: pass
Subject: Re: Fwd: I-D Action:draft-reschke-rfc2183-in-http-02.txt
Archived-At: <http://www.w3.org/mid/20100824092827.af5be569.eric@bisonsystems.net>
Resent-From: ietf-http-wg@w3.org
Sender: ietf-http-wg-request@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
Resent-Message-Id: <E1OnvQn-00087t-Bz@frink.w3.org>
Resent-Date: Tue, 24 Aug 2010 15:28:57 +0000

> 
> 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".
"

-Eric

Fwd: I-D Action:draft-reschke-rfc2183-in-http-02.… Julian Reschke
Re: Fwd: I-D Action:draft-reschke-rfc2183-in-http… Eric J. Bowman
Re: Fwd: I-D Action:draft-reschke-rfc2183-in-http… Julian Reschke
Re: Fwd: I-D Action:draft-reschke-rfc2183-in-http… Julian Reschke