draft-ietf-httpbis-p3-payload-11.txt   draft-ietf-httpbis-p3-payload-latest.txt 
HTTPbis Working Group R. Fielding, Ed. HTTPbis Working Group R. Fielding, Ed.
Internet-Draft Day Software Internet-Draft Day Software
Obsoletes: 2616 (if approved) J. Gettys Obsoletes: 2616 (if approved) J. Gettys
Intended status: Standards Track Alcatel-Lucent Intended status: Standards Track Alcatel-Lucent
Expires: February 5, 2011 J. Mogul Expires: March 6, 2011 J. Mogul
HP HP
H. Frystyk H. Frystyk
Microsoft Microsoft
L. Masinter L. Masinter
Adobe Systems Adobe Systems
P. Leach P. Leach
Microsoft Microsoft
T. Berners-Lee T. Berners-Lee
W3C/MIT W3C/MIT
Y. Lafon, Ed. Y. Lafon, Ed.
W3C W3C
J. Reschke, Ed. J. Reschke, Ed.
greenbytes greenbytes
August 4, 2010 September 2, 2010
HTTP/1.1, part 3: Message Payload and Content Negotiation HTTP/1.1, part 3: Message Payload and Content Negotiation
draft-ietf-httpbis-p3-payload-11 draft-ietf-httpbis-p3-payload-latest
Abstract Abstract
The Hypertext Transfer Protocol (HTTP) is an application-level The Hypertext Transfer Protocol (HTTP) is an application-level
protocol for distributed, collaborative, hypermedia information protocol for distributed, collaborative, hypermedia information
systems. HTTP has been in use by the World Wide Web global systems. HTTP has been in use by the World Wide Web global
information initiative since 1990. This document is Part 3 of the information initiative since 1990. This document is Part 3 of the
seven-part specification that defines the protocol referred to as seven-part specification that defines the protocol referred to as
"HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines
HTTP message content, metadata, and content negotiation. HTTP message content, metadata, and content negotiation.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
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://tools.ietf.org/wg/httpbis/trac/report/3> and related at <http://tools.ietf.org/wg/httpbis/trac/report/3> and related
documents (including fancy diffs) can be found at documents (including fancy diffs) can be found at
<http://tools.ietf.org/wg/httpbis/>. <http://tools.ietf.org/wg/httpbis/>.
The changes in this draft are summarized in Appendix E.12. The changes in this draft are summarized in Appendix E.13.
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 February 5, 2011. This Internet-Draft will expire on March 6, 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 4, line 21 skipping to change at page 4, line 21
E.3. Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . 39 E.3. Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . 39
E.4. Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . 39 E.4. Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . 39
E.5. Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . 40 E.5. Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . 40
E.6. Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . 40 E.6. Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . 40
E.7. Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . 40 E.7. Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . 40
E.8. Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . 41 E.8. Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . 41
E.9. Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . 41 E.9. Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . 41
E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . 42 E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . 42
E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . 42 E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . 42
E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . 42 E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . 42
E.13. Since draft-ietf-httpbis-p3-payload-11 . . . . . . . . . . 43
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1. Introduction 1. Introduction
This document defines HTTP/1.1 message payloads (a.k.a., content), This document defines HTTP/1.1 message payloads (a.k.a., content),
the associated metadata header fields that define how the payload is the associated metadata header fields that define how the payload is
intended to be interpreted by a recipient, the request header fields intended to be interpreted by a recipient, the request header fields
that might influence content selection, and the various selection that might influence content selection, and the various selection
algorithms that are collectively referred to as HTTP content algorithms that are collectively referred to as HTTP content
negotiation. negotiation.
This document is currently disorganized in order to minimize the This document is currently disorganized in order to minimize the
changes between drafts and enable reviewers to see the smaller errata changes between drafts and enable reviewers to see the smaller errata
changes. The next draft will reorganize the sections to better changes. A future draft will reorganize the sections to better
reflect the content. In particular, the sections on entities will be reflect the content. In particular, the sections on entities will be
renamed payload and moved to the first half of the document, while renamed payload and moved to the first half of the document, while
the sections on content negotiation and associated request header the sections on content negotiation and associated request header
fields will be moved to the second half. The current mess reflects fields will be moved to the second half. The current mess reflects
how widely dispersed these topics and associated requirements had how widely dispersed these topics and associated requirements had
become in [RFC2616]. become in [RFC2616].
1.1. Terminology 1.1. Terminology
This specification uses a number of terms to refer to the roles This specification uses a number of terms to refer to the roles
skipping to change at page 6, line 34 skipping to change at page 6, line 34
token = <token, defined in [Part1], Section 1.2.2> token = <token, defined in [Part1], Section 1.2.2>
word = <word, defined in [Part1], Section 1.2.2> word = <word, defined in [Part1], Section 1.2.2>
OWS = <OWS, defined in [Part1], Section 1.2.2> OWS = <OWS, defined in [Part1], Section 1.2.2>
1.3.2. ABNF Rules defined in other Parts of the Specification 1.3.2. ABNF Rules defined in other Parts of the Specification
The ABNF rules below are defined in other parts: The ABNF rules below are defined in other parts:
absolute-URI = <absolute-URI, defined in [Part1], Section 2.6> absolute-URI = <absolute-URI, defined in [Part1], Section 2.6>
Content-Length = <Content-Length, defined in [Part1], Section 9.2> Content-Length = <Content-Length, defined in [Part1], Section 9.2>
header-field = <header-field, defined in [Part1], Section 3.2>
partial-URI = <partial-URI, defined in [Part1], Section 2.6> partial-URI = <partial-URI, defined in [Part1], Section 2.6>
qvalue = <qvalue, defined in [Part1], Section 6.4> qvalue = <qvalue, defined in [Part1], Section 6.4>
Last-Modified = <Last-Modified, defined in [Part4], Section 6.6> Last-Modified = <Last-Modified, defined in [Part4], Section 6.6>
Content-Range = <Content-Range, defined in [Part5], Section 5.2> Content-Range = <Content-Range, defined in [Part5], Section 5.2>
Expires = <Expires, defined in [Part6], Section 3.3> Expires = <Expires, defined in [Part6], Section 3.3>
2. Protocol Parameters 2. Protocol Parameters
skipping to change at page 29, line 42 skipping to change at page 29, line 42
[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.
[Part1] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., [Part1] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,
Ed., and J. Reschke, Ed., "HTTP/1.1, part 1: URIs, Ed., and J. Reschke, Ed., "HTTP/1.1, part 1: URIs,
Connections, and Message Parsing", Connections, and Message Parsing",
draft-ietf-httpbis-p1-messaging-11 (work in progress), draft-ietf-httpbis-p1-messaging-latest (work in
August 2010. progress), September 2010.
[Part2] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., [Part2] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,
Ed., and J. Reschke, Ed., "HTTP/1.1, part 2: Message Ed., and J. Reschke, Ed., "HTTP/1.1, part 2: Message
Semantics", draft-ietf-httpbis-p2-semantics-11 (work in Semantics", draft-ietf-httpbis-p2-semantics-latest
progress), August 2010. (work in progress), September 2010.
[Part4] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., [Part4] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,
Ed., and J. Reschke, Ed., "HTTP/1.1, part 4: Ed., and J. Reschke, Ed., "HTTP/1.1, part 4:
Conditional Requests", Conditional Requests",
draft-ietf-httpbis-p4-conditional-11 (work in draft-ietf-httpbis-p4-conditional-latest (work in
progress), August 2010. progress), September 2010.
[Part5] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., [Part5] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,
Ed., and J. Reschke, Ed., "HTTP/1.1, part 5: Range Ed., and J. Reschke, Ed., "HTTP/1.1, part 5: Range
Requests and Partial Responses", Requests and Partial Responses",
draft-ietf-httpbis-p5-range-11 (work in progress), draft-ietf-httpbis-p5-range-latest (work in progress),
August 2010. September 2010.
[Part6] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., [Part6] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,
Ed., Nottingham, M., Ed., and J. Reschke, Ed., Ed., Nottingham, M., Ed., and J. Reschke, Ed.,
"HTTP/1.1, part 6: Caching", "HTTP/1.1, part 6: Caching",
draft-ietf-httpbis-p6-cache-11 (work in progress), draft-ietf-httpbis-p6-cache-latest (work in progress),
August 2010. September 2010.
[RFC1864] Myers, J. and M. Rose, "The Content-MD5 Header Field", [RFC1864] Myers, J. and M. Rose, "The Content-MD5 Header Field",
RFC 1864, October 1995. RFC 1864, October 1995.
[RFC1950] Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data [RFC1950] Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data
Format Specification version 3.3", RFC 1950, May 1996. Format Specification version 3.3", RFC 1950, May 1996.
RFC 1950 is an Informational RFC, thus it might be less RFC 1950 is an Informational RFC, thus it might be less
stable than this specification. On the other hand, stable than this specification. On the other hand,
this downward reference was present since the this downward reference was present since the
skipping to change at page 37, line 40 skipping to change at page 37, line 40
content-disposition-v = disposition-type *( OWS ";" OWS content-disposition-v = disposition-type *( OWS ";" OWS
disposition-parm ) disposition-parm )
disp-extension-parm = token "=" word disp-extension-parm = token "=" word
disp-extension-token = token disp-extension-token = token
disposition-parm = filename-parm / disp-extension-parm disposition-parm = filename-parm / disp-extension-parm
disposition-type = "attachment" / disp-extension-token disposition-type = "attachment" / disp-extension-token
filename-parm = "filename=" quoted-string filename-parm = "filename=" quoted-string
header-field = <header-field, defined in [Part1], Section 3.2>
language-range = <language-range, defined in [RFC4647], Section 2.1> language-range = <language-range, defined in [RFC4647], Section 2.1>
language-tag = <Language-Tag, defined in [RFC5646], Section 2.1> language-tag = <Language-Tag, defined in [RFC5646], Section 2.1>
media-range = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS media-range = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
";" OWS parameter ) ";" OWS parameter )
media-type = type "/" subtype *( OWS ";" OWS parameter ) media-type = type "/" subtype *( OWS ";" OWS parameter )
parameter = attribute "=" value parameter = attribute "=" value
partial-URI = <partial-URI, defined in [Part1], Section 2.6> partial-URI = <partial-URI, defined in [Part1], Section 2.6>
quoted-string = <quoted-string, defined in [Part1], Section 1.2.2> quoted-string = <quoted-string, defined in [Part1], Section 1.2.2>
qvalue = <qvalue, defined in [Part1], Section 6.4> qvalue = <qvalue, defined in [Part1], Section 6.4>
subtype = token subtype = token
token = <token, defined in [Part1], Section 1.2.2> token = <token, defined in [Part1], Section 1.2.2>
type = token type = token
value = word value = word
word = <word, defined in [Part1], Section 1.2.2> word = <word, defined in [Part1], Section 1.2.2>
ABNF diagnostics: ABNF diagnostics:
skipping to change at page 38, line 33 skipping to change at page 38, line 30
; Content-Language defined but not used ; Content-Language defined but not used
; Content-Length defined but not used ; Content-Length defined but not used
; Content-Location defined but not used ; Content-Location defined but not used
; Content-MD5 defined but not used ; Content-MD5 defined but not used
; Content-Range defined but not used ; Content-Range defined but not used
; Content-Type defined but not used ; Content-Type defined but not used
; Expires defined but not used ; Expires defined but not used
; Last-Modified defined but not used ; Last-Modified defined but not used
; MIME-Version defined but not used ; MIME-Version defined but not used
; content-disposition defined but not used ; content-disposition defined but not used
; header-field defined but not used
Appendix E. Change Log (to be removed by RFC Editor before publication) Appendix E. Change Log (to be removed by RFC Editor before publication)
E.1. Since RFC2616 E.1. Since RFC2616
Extracted relevant partitions from [RFC2616]. Extracted relevant partitions from [RFC2616].
E.2. Since draft-ietf-httpbis-p3-payload-00 E.2. Since draft-ietf-httpbis-p3-payload-00
Closed issues: Closed issues:
skipping to change at page 43, line 28 skipping to change at page 43, line 25
resource' in content-encoding definition" resource' in content-encoding definition"
o <http://tools.ietf.org/wg/httpbis/trac/ticket/220>: "consider o <http://tools.ietf.org/wg/httpbis/trac/ticket/220>: "consider
removing the 'changes from 2068' sections" removing the 'changes from 2068' sections"
Partly resolved issues: Partly resolved issues:
o <http://tools.ietf.org/wg/httpbis/trac/ticket/178>: "Content-MD5 o <http://tools.ietf.org/wg/httpbis/trac/ticket/178>: "Content-MD5
and partial responses" and partial responses"
E.13. Since draft-ietf-httpbis-p3-payload-11
None yet.
Index Index
A A
Accept header 17 Accept header 17
Accept-Charset header 19 Accept-Charset header 19
Accept-Encoding header 20 Accept-Encoding header 20
Accept-Language header 21 Accept-Language header 21
C C
Coding Format Coding Format
 End of changes. 18 change blocks. 
21 lines changed or deleted 22 lines changed or added

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