Content-Disposition (new issue?)
Julian Reschke <julian.reschke@gmx.de> Fri, 20 June 2008 10:00 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 0FD373A69E0 for <ietfarch-httpbisa-archive-bis2Juki@core3.amsl.com>; Fri, 20 Jun 2008 03:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 FyMuRkhM9pX8 for <ietfarch-httpbisa-archive-bis2Juki@core3.amsl.com>; Fri, 20 Jun 2008 03:00:22 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by core3.amsl.com (Postfix) with ESMTP id C2BF83A6913 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 20 Jun 2008 03:00:22 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.63) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1K9dOp-0005PK-5p for ietf-http-wg-dist@listhub.w3.org; Fri, 20 Jun 2008 09:59:19 +0000
Received: from maggie.w3.org ([193.51.208.68]) by frink.w3.org with esmtp (Exim 4.63) (envelope-from <julian.reschke@gmx.de>) id 1K9dOi-0005OF-Jk for ietf-http-wg@listhub.w3.org; Fri, 20 Jun 2008 09:59:12 +0000
Received: from mail.gmx.net ([213.165.64.20]) by maggie.w3.org with smtp (Exim 4.63) (envelope-from <julian.reschke@gmx.de>) id 1K9dOX-0000MD-90 for ietf-http-wg@w3.org; Fri, 20 Jun 2008 09:59:12 +0000
Received: (qmail invoked by alias); 20 Jun 2008 09:58:30 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.106]) [217.91.35.233] by mail.gmx.net (mp044) with SMTP; 20 Jun 2008 11:58:30 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19a/gheXYxaJtUtb9KwKmLwuknw4htaNit98bob++ 2JME9bggM3XklH
Message-ID: <485B7F45.3090804@gmx.de>
Date: Fri, 20 Jun 2008 11:58:29 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: ietf-http-wg@w3.org
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: maggie.w3.org 1K9dOX-0000MD-90 adc8443d0527b44e67d7d6fa5fabc3a2
X-Original-To: ietf-http-wg@w3.org
Subject: Content-Disposition (new issue?)
Archived-At: <http://www.w3.org/mid/485B7F45.3090804@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/4802
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: <E1K9dOp-0005PK-5p@frink.w3.org>
Resent-Date: Fri, 20 Jun 2008 09:59:19 +0000
Hi, looking at <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p3-payload-03.html#content-disposition>: ---- B.1 Content-Disposition The Content-Disposition response-header field has been proposed as a means for the origin server to suggest a default filename if the user requests that the content is saved to a file. This usage is derived from the definition of Content-Disposition in [RFC1806]. content-disposition = "Content-Disposition" ":" disposition-type *( ";" disposition-parm ) disposition-type = "attachment" | disp-extension-token disposition-parm = filename-parm | disp-extension-parm filename-parm = "filename" "=" quoted-string disp-extension-token = token disp-extension-parm = token "=" ( token | quoted-string ) An example is Content-Disposition: attachment; filename="fname.ext" The receiving user agent SHOULD NOT respect any directory path information present in the filename-parm parameter, which is the only parameter believed to apply to HTTP implementations at this time. The filename SHOULD be treated as a terminal component only. If this header is used in a response with the application/octet-stream content-type, the implied suggestion is that the user agent should not display the response, but directly enter a `save response as...' dialog. See Section 8.2 for Content-Disposition security issues. ---- It seems that certain vendors do not "get" that RFC1806 was updated by RFC2183, which in turn was updated by RFC2231 (defining I18N). So I think we need to 1) s/1806/2183/g (this is editorial, methinks) 2) Clarify that I18N is defined in by RFC2231 3) Specify a profile of RFC2231 that makes sense for Content-Disposition as used over HTTP (as opposed to mail), such as: 3a) No Continuations (<http://greenbytes.de/tech/webdav/rfc2231.html#rfc.section.3>) 3b) Support <http://greenbytes.de/tech/webdav/rfc2231.html#rfc.section.3>, but only use UTF-8 encoding in producers. Feedback appreciated, Julian
- Content-Disposition (new issue?) Julian Reschke
- Re: Content-Disposition (new issue?) Frank Ellermann
- Re: Content-Disposition (new issue?) Julian Reschke
- Re: Content-Disposition (new issue?) Frank Ellermann
- Re: Content-Disposition (new issue?) Julian Reschke
- Re: Content-Disposition (new issue?) Julian Reschke
- Issue 121 (RFC 1806 vs RFC2183), was: Content-Dis… Julian Reschke
- Re: Content-Disposition (new issue?) Julian Reschke
- RE: Content-Disposition (new issue?) Brian Smith
- Re: Content-Disposition (new issue?) Julian Reschke
- RE: Content-Disposition (new issue?) Brian Smith
- Re: Content-Disposition (new issue?) Julian Reschke
- Re: Content-Disposition (new issue?) Julian Reschke
- Re: Content-Disposition (new issue?) Julian Reschke
- Re: Content-Disposition (new issue?) Frank Ellermann
- Re: Content-Disposition (new issue?) Julian Reschke
- Re: Content-Disposition (new issue?) Henrik Nordstrom
- Re: Content-Disposition (new issue?) Julian Reschke
- Factoring out Content-Disposition (i123), was: Co… Julian Reschke
- Re: Factoring out Content-Disposition (i123), was… Julian Reschke
- RE: Factoring out Content-Disposition (i123), was… Brian Smith
- Re: Factoring out Content-Disposition (i123), was… Julian Reschke
- Re: Factoring out Content-Disposition (i123), was… Roy T. Fielding
- RE: Factoring out Content-Disposition (i123), was… Brian Smith
- Re: Factoring out Content-Disposition (i123), was… William A. Rowe, Jr.
- Re: Factoring out Content-Disposition (i123) Frank Ellermann
- Re: Factoring out Content-Disposition (i123), was… Frank Ellermann
- Re: Factoring out Content-Disposition (i123), was… Julian Reschke
- Re: Factoring out Content-Disposition (i123) William A. Rowe, Jr.
- Re: Factoring out Content-Disposition (i123), was… William A. Rowe, Jr.
- Re: Factoring out Content-Disposition (i123), was… Julian Reschke
- Re: Factoring out Content-Disposition (i123) Julian Reschke
- Re: Factoring out Content-Disposition (i123), was… Julian Reschke
- Re: Factoring out Content-Disposition (i123) Frank Ellermann
- Re: Factoring out Content-Disposition (i123) Henrik Nordstrom
- RE: Factoring out Content-Disposition (i123), was… Brian Smith
- RE: Factoring out Content-Disposition (i123), was… Brian Smith
- Re: Factoring out Content-Disposition (i123), was… Julian Reschke
- RE: Factoring out Content-Disposition (i123), was… Brian Smith
- RE: Factoring out Content-Disposition (i123), was… Brian Smith
- RE: Factoring out Content-Disposition (i123) Brian Smith
- Re: Factoring out Content-Disposition (i123), was… Julian Reschke
- Re: Factoring out Content-Disposition (i123) Frank Ellermann
- Re: Factoring out Content-Disposition (i123) William A. Rowe, Jr.
- Re: Factoring out Content-Disposition (i123) Julian Reschke
- Re: Factoring out Content-Disposition (i123) William A. Rowe, Jr.
- Re: Factoring out Content-Disposition (i123) Julian Reschke
- RE: Factoring out Content-Disposition (i123) Brian Smith
- Re: Factoring out Content-Disposition (i123) Frank Ellermann
- OT: historical file systems (was: Factoring out C… Frank Ellermann
- Re: Factoring out Content-Disposition (i123) Julian Reschke