atom feed51 messages in org.w3.ietf-http-wgContent-Disposition (new issue?)
FromSent OnAttachments
Julian ReschkeJun 20, 2008 2:58 am 
Frank EllermannJun 20, 2008 4:32 am 
Julian ReschkeJun 20, 2008 4:41 am 
Frank EllermannJun 20, 2008 5:14 am 
Julian ReschkeJun 20, 2008 5:38 am 
Julian ReschkeJun 20, 2008 6:00 am 
Brian SmithJun 20, 2008 6:52 am 
Julian ReschkeJun 20, 2008 6:59 am 
Julian ReschkeJun 20, 2008 7:07 am 
Brian SmithJun 20, 2008 7:54 am 
Julian ReschkeJun 20, 2008 8:06 am 
Julian ReschkeJun 20, 2008 9:50 am 
Julian ReschkeJun 25, 2008 9:18 am 
Julian ReschkeJul 20, 2008 9:36 am 
Frank EllermannJul 20, 2008 10:23 am 
Julian ReschkeJul 20, 2008 10:41 am 
Henrik NordstromJul 21, 2008 4:29 pm 
Julian ReschkeJul 25, 2008 4:21 am 
Julian ReschkeAug 14, 2008 2:01 pm 
Julian ReschkeAug 15, 2008 9:43 am 
Brian SmithAug 15, 2008 12:53 pm 
Julian ReschkeAug 15, 2008 2:00 pm 
Roy T. FieldingAug 15, 2008 2:02 pm 
Brian SmithAug 15, 2008 3:32 pm 
William A. Rowe, Jr.Aug 15, 2008 3:44 pm 
Frank EllermannAug 15, 2008 7:42 pm 
Frank EllermannAug 15, 2008 8:12 pm 
Julian ReschkeAug 16, 2008 12:45 am 
William A. Rowe, Jr.Aug 16, 2008 12:50 am 
William A. Rowe, Jr.Aug 16, 2008 12:56 am 
Julian ReschkeAug 16, 2008 12:56 am 
Julian ReschkeAug 16, 2008 1:00 am 
Julian ReschkeAug 16, 2008 1:18 am 
Frank EllermannAug 16, 2008 1:20 am 
Henrik NordstromAug 17, 2008 2:01 am 
Brian SmithAug 17, 2008 8:23 am 
Brian SmithAug 17, 2008 9:45 am 
Julian ReschkeAug 17, 2008 9:59 am 
Brian SmithAug 17, 2008 9:08 pm 
Brian SmithAug 17, 2008 9:45 pm 
Brian SmithAug 17, 2008 10:53 pm 
Julian ReschkeAug 18, 2008 5:42 am 
Frank EllermannAug 18, 2008 5:08 pm 
William A. Rowe, Jr.Aug 18, 2008 8:12 pm 
Julian ReschkeAug 18, 2008 11:29 pm 
William A. Rowe, Jr.Aug 19, 2008 12:28 am 
Julian ReschkeAug 19, 2008 1:03 am 
Brian SmithAug 19, 2008 7:17 am 
Frank EllermannAug 19, 2008 12:30 pm 
Frank EllermannAug 19, 2008 12:42 pm 
Julian ReschkeAug 20, 2008 4:23 am 
Subject:Content-Disposition (new issue?)
From:Julian Reschke (juli@gmx.de)
Date:Jun 20, 2008 2:58:06 am
List:org.w3.ietf-http-wg

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