Re: I-D Action:draft-ietf-httpbis-content-disp-00.txt
Julian Reschke <julian.reschke@gmx.de> Sat, 04 September 2010 10:19 UTC
Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@core3.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FAF83A6403 for <ietfarch-httpbisa-archive-bis2Juki@core3.amsl.com>; Sat, 4 Sep 2010 03:19:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.643
X-Spam-Level:
X-Spam-Status: No, score=-7.643 tagged_above=-999 required=5 tests=[AWL=2.956, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jpa2w0J27Xs0 for <ietfarch-httpbisa-archive-bis2Juki@core3.amsl.com>; Sat, 4 Sep 2010 03:19:24 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by core3.amsl.com (Postfix) with ESMTP id C8F303A6802 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 4 Sep 2010 03:19:22 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1OrppY-0000QG-BP for ietf-http-wg-dist@listhub.w3.org; Sat, 04 Sep 2010 10:18:40 +0000
Received: from bart.w3.org ([128.30.52.63]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <julian.reschke@gmx.de>) id 1OrppO-0000OW-IS for ietf-http-wg@listhub.w3.org; Sat, 04 Sep 2010 10:18:30 +0000
Received: from mailout-de.gmx.net ([213.165.64.22] helo=mail.gmx.net) by bart.w3.org with smtp (Exim 4.69) (envelope-from <julian.reschke@gmx.de>) id 1OrppM-00009r-9K for ietf-http-wg@w3.org; Sat, 04 Sep 2010 10:18:30 +0000
Received: (qmail invoked by alias); 04 Sep 2010 10:17:53 -0000
Received: from p508FBD5F.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.189.95] by mail.gmx.net (mp062) with SMTP; 04 Sep 2010 12:17:53 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX185RkMtpAM53haSoCdrT54e0FeC5mfBuoMz4qRty7 xWZ1Q7W1MCOynI
Message-ID: <4C821CBF.8060507@gmx.de>
Date: Sat, 04 Sep 2010 12:17:35 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: ietf-http-wg@w3.org
CC: Rolf Eike Beer <eike@sf-mail.de>, Roar Lauritzsen <roarl@opera.com>
References: <20100904000001.C400D3A67B2@core3.amsl.com>
In-Reply-To: <20100904000001.C400D3A67B2@core3.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Received-SPF: pass
X-SPF-Guess: pass
X-W3C-Hub-Spam-Status: No, score=-2.6
X-W3C-Hub-Spam-Report: BAYES_00=-2.599, SPF_PASS=-0.001
X-W3C-Scan-Sig: bart.w3.org 1OrppM-00009r-9K 5cdad63ded8b802d14efc12de615d86c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: I-D Action:draft-ietf-httpbis-content-disp-00.txt
Archived-At: <http://www.w3.org/mid/4C821CBF.8060507@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/9165
X-Loop: ietf-http-wg@w3.org
Sender: ietf-http-wg-request@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Resent-Message-Id: <E1OrppY-0000QG-BP@frink.w3.org>
Resent-Date: Sat, 04 Sep 2010 10:18:40 +0000
Hi, the draft below is essentially identical with draft-reschke-rfc2183-in-http-03 (<http://greenbytes.de/tech/webdav/draft-reschke-rfc2183-in-http-03.html>), except for a boilerplate change with respect to the changed status (such as the issue tracker URI). I think this draft can go to WG LC soon. In the meantime I'm looking for feedback specifically on: 1) Section 3.3, Security Considerations (<http://tools.ietf.org/html/draft-ietf-httpbis-content-disp-00#section-3.3>): I'm sure more can be added. 2) Section 3.5, Extensibility (<http://tools.ietf.org/html/draft-ietf-httpbis-content-disp-00#section-3.5>): the original MIME spec for Content-Disposition defines a registry for values and parameters, which has been used in other protocols as well. I *think* the registry procedure should be updated to clarify this, but this seems to be a job for a future RFC2183bis. 3) Appendix C.4, Implementations (<http://tools.ietf.org/html/draft-ietf-httpbis-content-disp-00#appendix-C.4>): this reports on the behavior of existing implementations; at some point we'll need to make a conscious decision about whether this should go into the final spec. UA implementers: <http://tools.ietf.org/html/draft-ietf-httpbis-content-disp-00#section-3.3> proposes: "filename" and "filename*" behave the same, except that "filename*" uses the encoding defined in [RFC5987], allowing the use of characters not present in the ISO-8859-1 character set ([ISO-8859-1]). 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*". Unfortunately, UAs are very shaky here, so they'll need fixes to make this possible. See <http://greenbytes.de/tech/tc2231/#attfnboth>: - FF3 and Opera pick "filename" over "filename*" (Konqueror gets this right) and <http://greenbytes.de/tech/tc2231/#attfnboth2>: - MSIE8 and Chrome fail to pick "filename", apparently being confused by "filename*". For all of these, I have reported the bugs already (the ones with public bug trackers have the issue links in the test document). Best regards, Julian On 04.09.2010 02:00, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Hypertext Transfer Protocol Bis Working Group of the IETF. > > > Title : Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) > Author(s) : J. Reschke > Filename : draft-ietf-httpbis-content-disp-00.txt > Pages : 13 > Date : 2010-09-03 > > HTTP/1.1 defines the Content-Disposition response header field, but > points out that it is not part of the HTTP/1.1 Standard. This > specification takes over the definition and registration of Content- > Disposition, as used in HTTP, and clarifies internationalization > aspects. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-httpbis-content-disp-00.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft.
- I-D Action:draft-ietf-httpbis-content-disp-00.txt Internet-Drafts
- Re: I-D Action:draft-ietf-httpbis-content-disp-00… Julian Reschke
- Issue 123 (factor out Content-Disposition), was: … Julian Reschke
- Re: I-D Action:draft-ietf-httpbis-content-disp-00… Henrik Nordström
- Re: I-D Action:draft-ietf-httpbis-content-disp-00… Julian Reschke
- Re: I-D Action:draft-ietf-httpbis-content-disp-00… Henrik Nordström