draft-ietf-httpbis-content-disp-01.txt   draft-ietf-httpbis-content-disp-02.txt 
HTTPbis Working Group J. Reschke HTTPbis Working Group J. Reschke
Internet-Draft greenbytes Internet-Draft greenbytes
Updates: 2616 (if approved) September 16, 2010 Updates: 2616 (if approved) September 22, 2010
Intended status: Standards Track Intended status: Standards Track
Expires: March 20, 2011 Expires: March 26, 2011
Use of the Content-Disposition Header Field in the Use of the Content-Disposition Header Field in the
Hypertext Transfer Protocol (HTTP) Hypertext Transfer Protocol (HTTP)
draft-ietf-httpbis-content-disp-01 draft-ietf-httpbis-content-disp-02
Abstract Abstract
HTTP/1.1 defines the Content-Disposition response header field, but 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 points out that it is not part of the HTTP/1.1 Standard. This
specification takes over the definition and registration of Content- specification takes over the definition and registration of Content-
Disposition, as used in HTTP, and clarifies internationalization Disposition, as used in HTTP, and clarifies internationalization
aspects. aspects.
Editorial Note (To be removed by RFC Editor before publication) Editorial Note (To be removed by RFC Editor before publication)
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Disposition in the HTTP/1.1 specification, as currently revised by Disposition in the HTTP/1.1 specification, as currently revised by
the IETF HTTPbis working group. See also the IETF HTTPbis working group. See also
<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123>. <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123>.
Discussion of this draft should take place on the HTTPBIS working Discussion of this draft should take place on the HTTPBIS working
group mailing list (ietf-http-wg@w3.org). The current issues list is group mailing list (ietf-http-wg@w3.org). The current issues list is
at <http://trac.tools.ietf.org/wg/httpbis/trac/ at <http://trac.tools.ietf.org/wg/httpbis/trac/
query?component=content-disp> and related documents (including fancy query?component=content-disp> and related documents (including fancy
diffs) can be found at <http://tools.ietf.org/wg/httpbis/>. diffs) can be found at <http://tools.ietf.org/wg/httpbis/>.
The changes in this draft are summarized in Appendix D.5. The changes in this draft are summarized in Appendix D.6.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 20, 2011. This Internet-Draft will expire on March 26, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 40 skipping to change at page 3, line 40
C.3. Encoding Sniffing . . . . . . . . . . . . . . . . . . . . 11 C.3. Encoding Sniffing . . . . . . . . . . . . . . . . . . . . 11
C.4. Implementations (to be removed by RFC Editor before C.4. Implementations (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . . . . 11 publication) . . . . . . . . . . . . . . . . . . . . . . . 11
Appendix D. Change Log (to be removed by RFC Editor before Appendix D. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 12 publication) . . . . . . . . . . . . . . . . . . . . 12
D.1. Since draft-reschke-rfc2183-in-http-00 . . . . . . . . . . 12 D.1. Since draft-reschke-rfc2183-in-http-00 . . . . . . . . . . 12
D.2. Since draft-reschke-rfc2183-in-http-01 . . . . . . . . . . 12 D.2. Since draft-reschke-rfc2183-in-http-01 . . . . . . . . . . 12
D.3. Since draft-reschke-rfc2183-in-http-02 . . . . . . . . . . 12 D.3. Since draft-reschke-rfc2183-in-http-02 . . . . . . . . . . 12
D.4. Since draft-reschke-rfc2183-in-http-03 . . . . . . . . . . 12 D.4. Since draft-reschke-rfc2183-in-http-03 . . . . . . . . . . 12
D.5. Since draft-ietf-httpbis-content-disp-00 . . . . . . . . . 12 D.5. Since draft-ietf-httpbis-content-disp-00 . . . . . . . . . 12
D.6. Since draft-ietf-httpbis-content-disp-01 . . . . . . . . . 13
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
HTTP/1.1 defines the Content-Disposition response header field in HTTP/1.1 defines the Content-Disposition response header field in
Section 19.5.1 of [RFC2616], but points out that it is not part of Section 19.5.1 of [RFC2616], but points out that it is not part of
the HTTP/1.1 Standard (Section 15.5): the HTTP/1.1 Standard (Section 15.5):
Content-Disposition is not part of the HTTP standard, but since it Content-Disposition is not part of the HTTP standard, but since it
is widely implemented, we are documenting its use and risks for is widely implemented, we are documenting its use and risks for
skipping to change at page 4, line 35 skipping to change at page 4, line 35
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This specification uses the augmented BNF notation defined in Section This specification uses the augmented BNF notation defined in Section
2.1 of [RFC2616], including its rules for linear whitespace (LWS). 2.1 of [RFC2616], including its rules for linear whitespace (LWS).
3. Header Field Definition 3. Header Field Definition
The Content-Disposition response header field is used to convey The Content-Disposition response header field is used to convey
additional information about how to process the response payload, and additional information about how to process the response payload, and
also can be used to attach additional metadata, such as the filename. also can be used to attach additional metadata, such as the filename
to use when saving the response payload locally.
3.1. Grammar 3.1. Grammar
content-disposition = "Content-Disposition" ":" content-disposition = "Content-Disposition" ":"
disposition-type *( ";" disposition-parm ) disposition-type *( ";" disposition-parm )
disposition-type = "inline" | "attachment" | disp-ext-type disposition-type = "inline" | "attachment" | disp-ext-type
; case-insensitive ; case-insensitive
disp-ext-type = token disp-ext-type = token
skipping to change at page 5, line 35 skipping to change at page 5, line 35
token = <token, defined in [RFC2616], Section 2.2> token = <token, defined in [RFC2616], Section 2.2>
value = <value, defined in [RFC2616], Section 3.6> value = <value, defined in [RFC2616], Section 3.6>
Defined in [RFC5987]: Defined in [RFC5987]:
ext-value = <ext-value, defined in [RFC5987], Section 3.2> ext-value = <ext-value, defined in [RFC5987], Section 3.2>
3.2. Disposition Type 3.2. Disposition Type
If the disposition type matches "attachment" (case-insensitively), If the disposition type matches "attachment" (case-insensitively),
this indicates that the user agent should not display the response, this indicates that the user agent should prompt the user to save the
but directly enter a "save as..." dialog. response locally, rather than process it normally (as per its media
type).
On the other hand, if it matches "inline" (case-insensitively), this On the other hand, if it matches "inline" (case-insensitively), this
implies default processing. implies default processing.
Unknown or unhandled disposition types SHOULD be handled the same way Unknown or unhandled disposition types SHOULD be handled the same way
as "attachment" (see also [RFC2183], Section 2.8). as "attachment" (see also [RFC2183], Section 2.8).
3.3. Disposition Parameter: 'Filename' 3.3. Disposition Parameter: 'Filename'
The parameters "filename" and "filename*", to be matched case- The parameters "filename" and "filename*", to be matched case-
skipping to change at page 6, line 33 skipping to change at page 6, line 34
information. In particular: information. In particular:
o When the value contains path separator characters, all but the o When the value contains path separator characters, all but the
last segment SHOULD be ignored. This prevents unintentional last segment SHOULD be ignored. This prevents unintentional
overwriting of well-known file system location (such as "/etc/ overwriting of well-known file system location (such as "/etc/
passwd"). passwd").
o Many platforms do not use Internet Media Types ([RFC2046]) to hold o Many platforms do not use Internet Media Types ([RFC2046]) to hold
type information in the file system, but rely on filename type information in the file system, but rely on filename
extensions instead. Trusting the server-provided file extension extensions instead. Trusting the server-provided file extension
could introduce a privilege escalation when later on the file is could introduce a privilege escalation when the saved file is
opened locally (consider ".exe"). Thus, recipients need to ensure later opened (consider ".exe"). Thus, recipients need to ensure
that a file extension is used that is safe, optimally matching the that a file extension is used that is safe, optimally matching the
media type of the received payload. media type of the received payload.
o Other aspects recipients need to be aware of are names that have a o Other aspects recipients need to be aware of are names that have a
special meaning in the file system or in shell commands, such as special meaning in the file system or in shell commands, such as
"." and "..", "~", "|", and also device names. "." and "..", "~", "|", and also device names.
3.4. Disposition Parameter: Extensions 3.4. Disposition Parameter: Extensions
To enable future extensions, unknown parameters SHOULD be ignored To enable future extensions, unknown parameters SHOULD be ignored
skipping to change at page 8, line 51 skipping to change at page 8, line 51
Status: standard Status: standard
Author/Change controller: IETF Author/Change controller: IETF
Specification document: this specification (Section 3) Specification document: this specification (Section 3)
8. Acknowledgements 8. Acknowledgements
Thanks to Rolf Eike Beer, Bjoern Hoehrmann, Alfred Hoenes, Roar Thanks to Rolf Eike Beer, Bjoern Hoehrmann, Alfred Hoenes, Roar
Lauritzsen, and Henrik Nordstrom for their valuable feedback. Lauritzsen, Henrik Nordstrom, and Mark Nottingham for their valuable
feedback.
9. References 9. References
9.1. Normative References 9.1. Normative References
[ISO-8859-1] International Organization for Standardization, [ISO-8859-1] International Organization for Standardization,
"Information technology -- 8-bit single-byte coded "Information technology -- 8-bit single-byte coded
graphic character sets -- Part 1: Latin alphabet No. graphic character sets -- Part 1: Latin alphabet No.
1", ISO/IEC 8859-1:1998, 1998. 1", ISO/IEC 8859-1:1998, 1998.
skipping to change at page 13, line 10 skipping to change at page 13, line 10
D.5. Since draft-ietf-httpbis-content-disp-00 D.5. Since draft-ietf-httpbis-content-disp-00
Closed issues: Closed issues:
o <http://tools.ietf.org/wg/httpbis/trac/ticket/242>: "handling of o <http://tools.ietf.org/wg/httpbis/trac/ticket/242>: "handling of
unknown disposition types" unknown disposition types"
Slightly updated the notes about the proposed fallback behavior. Slightly updated the notes about the proposed fallback behavior.
D.6. Since draft-ietf-httpbis-content-disp-01
None yet.
Index Index
C C
Content-Disposition header 4 Content-Disposition header 4
H H
Headers Headers
Content-Disposition 4 Content-Disposition 4
Author's Address Author's Address
 End of changes. 11 change blocks. 
11 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.39. The latest version is available from http://tools.ietf.org/tools/rfcdiff/