source: draft-ietf-httpbis/diffs/draft-ietf-httpbis-p3-payload-13-from-12.diff.html @ 1391

Last change on this file since 1391 was 1180, checked in by julian.reschke@…, 9 years ago

prepare publication of -13

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html; charset=iso-8859-1
File size: 220.3 KB
Line 
1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
2<!-- Generated by rfcdiff 1.38: rfcdiff  --> 
3<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
4<html> 
5<head> 
6  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
7  <meta http-equiv="Content-Style-Type" content="text/css" /> 
8  <title>Diff: draft-ietf-httpbis-p3-payload-12.txt - draft-ietf-httpbis-p3-payload-13.txt</title> 
9  <style type="text/css"> 
10    body    { margin: 0.4ex; margin-right: auto; } 
11    tr      { } 
12    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
13    th      { font-size: 0.86em; } 
14    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
15    .left   { background-color: #EEE; } 
16    .right  { background-color: #FFF; } 
17    .diff   { background-color: #CCF; } 
18    .lblock { background-color: #BFB; } 
19    .rblock { background-color: #FF8; } 
20    .insert { background-color: #8FF; } 
21    .delete { background-color: #ACF; } 
22    .void   { background-color: #FFB; } 
23    .cont   { background-color: #EEE; } 
24    .linebr { background-color: #AAA; } 
25    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
26    .elipsis{ background-color: #AAA; } 
27    .left .cont { background-color: #DDD; } 
28    .right .cont { background-color: #EEE; } 
29    .lblock .cont { background-color: #9D9; } 
30    .rblock .cont { background-color: #DD6; } 
31    .insert .cont { background-color: #0DD; } 
32    .delete .cont { background-color: #8AD; } 
33    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
34  </style> 
35</head> 
36<body > 
37  <table border="0" cellpadding="0" cellspacing="0"> 
38  <tr bgcolor="orange"><th></th><th>&nbsp;draft-ietf-httpbis-p3-payload-12.txt&nbsp;</th><th> </th><th>&nbsp;draft-ietf-httpbis-p3-payload-13.txt&nbsp;</th><th></th></tr> 
39      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
40      <tr><td class="lineno" valign="top"></td><td class="left">HTTPbis Working Group                                   R. Fielding, Ed.</td><td> </td><td class="right">HTTPbis Working Group                                   R. Fielding, Ed.</td><td class="lineno" valign="top"></td></tr>
41      <tr><td><a name="diff0001" /></td></tr>
42      <tr><td class="lineno" valign="top"></td><td class="lblock">Internet-Draft                                              <span class="delete">Day Softwar</span>e</td><td> </td><td class="rblock">Internet-Draft                                              <span class="insert">       Adob</span>e</td><td class="lineno" valign="top"></td></tr>
43      <tr><td class="lineno" valign="top"></td><td class="left">Obsoletes: 2616 (if approved)                                  J. Gettys</td><td> </td><td class="right">Obsoletes: 2616 (if approved)                                  J. Gettys</td><td class="lineno" valign="top"></td></tr>
44      <tr><td class="lineno" valign="top"></td><td class="left">Intended status: Standards Track                          Alcatel-Lucent</td><td> </td><td class="right">Intended status: Standards Track                          Alcatel-Lucent</td><td class="lineno" valign="top"></td></tr>
45      <tr><td><a name="diff0002" /></td></tr>
46      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: <span class="delete">April 28, 2011    </span>                                     J. Mogul</td><td> </td><td class="rblock">Expires: <span class="insert">September 15, 2011</span>                                     J. Mogul</td><td class="lineno" valign="top"></td></tr>
47      <tr><td class="lineno" valign="top"></td><td class="left">                                                                      HP</td><td> </td><td class="right">                                                                      HP</td><td class="lineno" valign="top"></td></tr>
48      <tr><td class="lineno" valign="top"></td><td class="left">                                                              H. Frystyk</td><td> </td><td class="right">                                                              H. Frystyk</td><td class="lineno" valign="top"></td></tr>
49      <tr><td class="lineno" valign="top"></td><td class="left">                                                               Microsoft</td><td> </td><td class="right">                                                               Microsoft</td><td class="lineno" valign="top"></td></tr>
50      <tr><td class="lineno" valign="top"></td><td class="left">                                                             L. Masinter</td><td> </td><td class="right">                                                             L. Masinter</td><td class="lineno" valign="top"></td></tr>
51      <tr><td><a name="diff0003" /></td></tr>
52      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                           <span class="delete">Adobe Systems</span></td><td> </td><td class="rblock">                                                           <span class="insert">        Adobe</span></td><td class="lineno" valign="top"></td></tr>
53      <tr><td class="lineno" valign="top"></td><td class="left">                                                                P. Leach</td><td> </td><td class="right">                                                                P. Leach</td><td class="lineno" valign="top"></td></tr>
54      <tr><td class="lineno" valign="top"></td><td class="left">                                                               Microsoft</td><td> </td><td class="right">                                                               Microsoft</td><td class="lineno" valign="top"></td></tr>
55      <tr><td class="lineno" valign="top"></td><td class="left">                                                          T. Berners-Lee</td><td> </td><td class="right">                                                          T. Berners-Lee</td><td class="lineno" valign="top"></td></tr>
56      <tr><td class="lineno" valign="top"></td><td class="left">                                                                 W3C/MIT</td><td> </td><td class="right">                                                                 W3C/MIT</td><td class="lineno" valign="top"></td></tr>
57      <tr><td class="lineno" valign="top"></td><td class="left">                                                           Y. Lafon, Ed.</td><td> </td><td class="right">                                                           Y. Lafon, Ed.</td><td class="lineno" valign="top"></td></tr>
58      <tr><td class="lineno" valign="top"></td><td class="left">                                                                     W3C</td><td> </td><td class="right">                                                                     W3C</td><td class="lineno" valign="top"></td></tr>
59      <tr><td class="lineno" valign="top"></td><td class="left">                                                         J. Reschke, Ed.</td><td> </td><td class="right">                                                         J. Reschke, Ed.</td><td class="lineno" valign="top"></td></tr>
60      <tr><td class="lineno" valign="top"></td><td class="left">                                                              greenbytes</td><td> </td><td class="right">                                                              greenbytes</td><td class="lineno" valign="top"></td></tr>
61      <tr><td><a name="diff0004" /></td></tr>
62      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                        <span class="delete">October 25, 2010</span></td><td> </td><td class="rblock">                                                        <span class="insert">  March 14, 2011</span></td><td class="lineno" valign="top"></td></tr>
63      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
64      <tr><td class="lineno" valign="top"></td><td class="left">       HTTP/1.1, part 3: Message Payload and Content Negotiation</td><td> </td><td class="right">       HTTP/1.1, part 3: Message Payload and Content Negotiation</td><td class="lineno" valign="top"></td></tr>
65      <tr><td><a name="diff0005" /></td></tr>
66      <tr><td class="lineno" valign="top"></td><td class="lblock">                    draft-ietf-httpbis-p3-payload-1<span class="delete">2</span></td><td> </td><td class="rblock">                    draft-ietf-httpbis-p3-payload-1<span class="insert">3</span></td><td class="lineno" valign="top"></td></tr>
67      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
68      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
69      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
70      <tr><td class="lineno" valign="top"></td><td class="left">   The Hypertext Transfer Protocol (HTTP) is an application-level</td><td> </td><td class="right">   The Hypertext Transfer Protocol (HTTP) is an application-level</td><td class="lineno" valign="top"></td></tr>
71      <tr><td class="lineno" valign="top"></td><td class="left">   protocol for distributed, collaborative, hypermedia information</td><td> </td><td class="right">   protocol for distributed, collaborative, hypermedia information</td><td class="lineno" valign="top"></td></tr>
72      <tr><td class="lineno" valign="top"></td><td class="left">   systems.  HTTP has been in use by the World Wide Web global</td><td> </td><td class="right">   systems.  HTTP has been in use by the World Wide Web global</td><td class="lineno" valign="top"></td></tr>
73      <tr><td class="lineno" valign="top"></td><td class="left">   information initiative since 1990.  This document is Part 3 of the</td><td> </td><td class="right">   information initiative since 1990.  This document is Part 3 of the</td><td class="lineno" valign="top"></td></tr>
74      <tr><td class="lineno" valign="top"></td><td class="left">   seven-part specification that defines the protocol referred to as</td><td> </td><td class="right">   seven-part specification that defines the protocol referred to as</td><td class="lineno" valign="top"></td></tr>
75      <tr><td class="lineno" valign="top"></td><td class="left">   "HTTP/1.1" and, taken together, obsoletes RFC 2616.  Part 3 defines</td><td> </td><td class="right">   "HTTP/1.1" and, taken together, obsoletes RFC 2616.  Part 3 defines</td><td class="lineno" valign="top"></td></tr>
76      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP message content, metadata, and content negotiation.</td><td> </td><td class="right">   HTTP message content, metadata, and content negotiation.</td><td class="lineno" valign="top"></td></tr>
77      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
78      <tr><td class="lineno" valign="top"></td><td class="left">Editorial Note (To be removed by RFC Editor)</td><td> </td><td class="right">Editorial Note (To be removed by RFC Editor)</td><td class="lineno" valign="top"></td></tr>
79      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
80      <tr><td class="lineno" valign="top"></td><td class="left">   Discussion of this draft should take place on the HTTPBIS working</td><td> </td><td class="right">   Discussion of this draft should take place on the HTTPBIS working</td><td class="lineno" valign="top"></td></tr>
81      <tr><td class="lineno" valign="top"></td><td class="left">   group mailing list (ietf-http-wg@w3.org).  The current issues list is</td><td> </td><td class="right">   group mailing list (ietf-http-wg@w3.org).  The current issues list is</td><td class="lineno" valign="top"></td></tr>
82      <tr><td class="lineno" valign="top"></td><td class="left">   at &lt;http://tools.ietf.org/wg/httpbis/trac/report/3&gt; and related</td><td> </td><td class="right">   at &lt;http://tools.ietf.org/wg/httpbis/trac/report/3&gt; and related</td><td class="lineno" valign="top"></td></tr>
83      <tr><td class="lineno" valign="top"></td><td class="left">   documents (including fancy diffs) can be found at</td><td> </td><td class="right">   documents (including fancy diffs) can be found at</td><td class="lineno" valign="top"></td></tr>
84      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://tools.ietf.org/wg/httpbis/&gt;.</td><td> </td><td class="right">   &lt;http://tools.ietf.org/wg/httpbis/&gt;.</td><td class="lineno" valign="top"></td></tr>
85      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
86      <tr><td><a name="diff0006" /></td></tr>
87      <tr><td class="lineno" valign="top"></td><td class="lblock">   The changes in this draft are summarized in Appendix E.1<span class="delete">3</span>.</td><td> </td><td class="rblock">   The changes in this draft are summarized in Appendix E.1<span class="insert">4</span>.</td><td class="lineno" valign="top"></td></tr>
88      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
89      <tr><td class="lineno" valign="top"></td><td class="left">Status of This Memo</td><td> </td><td class="right">Status of This Memo</td><td class="lineno" valign="top"></td></tr>
90      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
91      <tr><td class="lineno" valign="top"></td><td class="left">   This Internet-Draft is submitted in full conformance with the</td><td> </td><td class="right">   This Internet-Draft is submitted in full conformance with the</td><td class="lineno" valign="top"></td></tr>
92      <tr><td class="lineno" valign="top"></td><td class="left">   provisions of BCP 78 and BCP 79.</td><td> </td><td class="right">   provisions of BCP 78 and BCP 79.</td><td class="lineno" valign="top"></td></tr>
93      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
94      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
95      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
96      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
97      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
98      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
99      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right">   Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno" valign="top"></td></tr>
100      <tr><td class="lineno" valign="top"></td><td class="left">   and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right">   and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno" valign="top"></td></tr>
101      <tr><td class="lineno" valign="top"></td><td class="left">   time.  It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right">   time.  It is inappropriate to use Internet-Drafts as reference</td><td class="lineno" valign="top"></td></tr>
102      <tr><td class="lineno" valign="top"></td><td class="left">   material or to cite them other than as "work in progress."</td><td> </td><td class="right">   material or to cite them other than as "work in progress."</td><td class="lineno" valign="top"></td></tr>
103      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
104      <tr><td><a name="diff0007" /></td></tr>
105      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">April 28</span>, 2011.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">September 15</span>, 2011.</td><td class="lineno" valign="top"></td></tr>
106      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
107      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
108      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
109      <tr><td><a name="diff0008" /></td></tr>
110      <tr><td class="lineno" valign="top"></td><td class="lblock">   Copyright (c) 201<span class="delete">0</span> IETF Trust and the persons identified as the</td><td> </td><td class="rblock">   Copyright (c) 201<span class="insert">1</span> IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
111      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
112      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
113      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
114      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
115      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
116      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
117      <tr><td class="lineno" valign="top"></td><td class="left">   carefully, as they describe your rights and restrictions with respect</td><td> </td><td class="right">   carefully, as they describe your rights and restrictions with respect</td><td class="lineno" valign="top"></td></tr>
118      <tr><td class="lineno" valign="top"></td><td class="left">   to this document.  Code Components extracted from this document must</td><td> </td><td class="right">   to this document.  Code Components extracted from this document must</td><td class="lineno" valign="top"></td></tr>
119      <tr><td class="lineno" valign="top"></td><td class="left">   include Simplified BSD License text as described in Section 4.e of</td><td> </td><td class="right">   include Simplified BSD License text as described in Section 4.e of</td><td class="lineno" valign="top"></td></tr>
120      <tr><td class="lineno" valign="top"></td><td class="left">   the Trust Legal Provisions and are provided without warranty as</td><td> </td><td class="right">   the Trust Legal Provisions and are provided without warranty as</td><td class="lineno" valign="top"></td></tr>
121      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
122      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 3, line 6</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 3, line 6</em></th><td></td></tr>
123      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
124      <tr><td class="lineno" valign="top"></td><td class="left">   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
125      <tr><td class="lineno" valign="top"></td><td class="left">     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
126      <tr><td class="lineno" valign="top"></td><td class="left">     1.2.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">     1.2.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
127      <tr><td class="lineno" valign="top"></td><td class="left">     1.3.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">     1.3.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
128      <tr><td class="lineno" valign="top"></td><td class="left">       1.3.1.  Core Rules . . . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">       1.3.1.  Core Rules . . . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
129      <tr><td class="lineno" valign="top"></td><td class="left">       1.3.2.  ABNF Rules defined in other Parts of the</td><td> </td><td class="right">       1.3.2.  ABNF Rules defined in other Parts of the</td><td class="lineno" valign="top"></td></tr>
130      <tr><td class="lineno" valign="top"></td><td class="left">               Specification  . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">               Specification  . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
131      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
132      <tr><td class="lineno" valign="top"></td><td class="left">   2.  Protocol Parameters  . . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">   2.  Protocol Parameters  . . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
133      <tr><td><a name="diff0009" /></td></tr>
134      <tr><td class="lineno" valign="top"></td><td class="lblock">     2.1.  Character <span class="delete">Sets . . . . . . . .</span> . . . . . . . . . . . . . .  6</td><td> </td><td class="rblock">     2.1.  Character <span class="insert">Encodings (charset) </span> . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
135      <tr><td class="lineno" valign="top"></td><td class="left">       2.1.1.  Missing Charset  . . . . . . . . . . . . . . . . . . .  7</td><td> </td><td class="right">       2.1.1.  Missing Charset  . . . . . . . . . . . . . . . . . . .  7</td><td class="lineno" valign="top"></td></tr>
136      <tr><td><a name="diff0010" /></td></tr>
137      <tr><td class="lineno" valign="top"></td><td class="lblock">     2.2.  Content Codings  . . . . . . . . . . . . . . . . . . . . .  <span class="delete">8</span></td><td> </td><td class="rblock">     2.2.  Content Codings  . . . . . . . . . . . . . . . . . . . . .  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
138      <tr><td class="lineno" valign="top"></td><td class="lblock">       2.2.1.  Content Coding Registry  . . . . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">       2.2.1.  Content Coding Registry  . . . . . . . . . . . . . . .  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
139      <tr><td class="lineno" valign="top"></td><td class="lblock">     2.3.  Media Types  . . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">     2.3.  Media Types  . . . . . . . . . . . . . . . . . . . . . . .  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
140      <tr><td class="lineno" valign="top"></td><td class="lblock">       2.3.1.  Canonicalization and Text Defaults . . . . . . . . . . <span class="delete">10</span></td><td> </td><td class="rblock">       2.3.1.  Canonicalization and Text Defaults . . . . . . . . . .  <span class="insert">9</span></td><td class="lineno" valign="top"></td></tr>
141      <tr><td class="lineno" valign="top"></td><td class="lblock">       2.3.2.  Multipart Types  . . . . . . . . . . . . . . . . . . . <span class="delete">11</span></td><td> </td><td class="rblock">       2.3.2.  Multipart Types  . . . . . . . . . . . . . . . . . . . <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr>
142      <tr><td class="lineno" valign="top"></td><td class="lblock">     2.4.  Language Tags  . . . . . . . . . . . . . . . . . . . . . . <span class="delete">11</span></td><td> </td><td class="rblock">     2.4.  Language Tags  . . . . . . . . . . . . . . . . . . . . . . <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr>
143      <tr><td class="lineno" valign="top"></td><td class="lblock">   3.  Payload  . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">12</span></td><td> </td><td class="rblock">   3.  Payload  . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">11</span></td><td class="lineno" valign="top"></td></tr>
144      <tr><td class="lineno" valign="top"></td><td class="lblock">     3.1.  Payload Header Fields  . . . . . . . . . . . . . . . . . . <span class="delete">12</span></td><td> </td><td class="rblock">     3.1.  Payload Header Fields  . . . . . . . . . . . . . . . . . . <span class="insert">11</span></td><td class="lineno" valign="top"></td></tr>
145      <tr><td class="lineno" valign="top"></td><td class="left">     3.2.  Payload Body . . . . . . . . . . . . . . . . . . . . . . . 12</td><td> </td><td class="right">     3.2.  Payload Body . . . . . . . . . . . . . . . . . . . . . . . 12</td><td class="lineno" valign="top"></td></tr>
146      <tr><td class="lineno" valign="top"></td><td class="left">   4.  Representation . . . . . . . . . . . . . . . . . . . . . . . . 12</td><td> </td><td class="right">   4.  Representation . . . . . . . . . . . . . . . . . . . . . . . . 12</td><td class="lineno" valign="top"></td></tr>
147      <tr><td><a name="diff0011" /></td></tr>
148      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.1.  Representation Header Fields . . . . . . . . . . . . . . . 1<span class="delete">3</span></td><td> </td><td class="rblock">     4.1.  Representation Header Fields . . . . . . . . . . . . . . . 1<span class="insert">2</span></td><td class="lineno" valign="top"></td></tr>
149      <tr><td class="lineno" valign="top"></td><td class="left">     4.2.  Representation Data  . . . . . . . . . . . . . . . . . . . 13</td><td> </td><td class="right">     4.2.  Representation Data  . . . . . . . . . . . . . . . . . . . 13</td><td class="lineno" valign="top"></td></tr>
150      <tr><td class="lineno" valign="top"></td><td class="left">   5.  Content Negotiation  . . . . . . . . . . . . . . . . . . . . . 14</td><td> </td><td class="right">   5.  Content Negotiation  . . . . . . . . . . . . . . . . . . . . . 14</td><td class="lineno" valign="top"></td></tr>
151      <tr><td class="lineno" valign="top"></td><td class="left">     5.1.  Server-driven Negotiation  . . . . . . . . . . . . . . . . 15</td><td> </td><td class="right">     5.1.  Server-driven Negotiation  . . . . . . . . . . . . . . . . 15</td><td class="lineno" valign="top"></td></tr>
152      <tr><td class="lineno" valign="top"></td><td class="left">     5.2.  Agent-driven Negotiation . . . . . . . . . . . . . . . . . 16</td><td> </td><td class="right">     5.2.  Agent-driven Negotiation . . . . . . . . . . . . . . . . . 16</td><td class="lineno" valign="top"></td></tr>
153      <tr><td><a name="diff0012" /></td></tr>
154      <tr><td class="lineno" valign="top"></td><td class="lblock">   6.  Header Field Definitions . . . . . . . . . . . . . . . . . . . <span class="delete">17</span></td><td> </td><td class="rblock">   6.  Header Field Definitions . . . . . . . . . . . . . . . . . . . <span class="insert">16</span></td><td class="lineno" valign="top"></td></tr>
155      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.1.  Accept . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">17</span></td><td> </td><td class="rblock">     6.1.  Accept . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">16</span></td><td class="lineno" valign="top"></td></tr>
156      <tr><td class="lineno" valign="top"></td><td class="left">     6.2.  Accept-Charset . . . . . . . . . . . . . . . . . . . . . . 19</td><td> </td><td class="right">     6.2.  Accept-Charset . . . . . . . . . . . . . . . . . . . . . . 19</td><td class="lineno" valign="top"></td></tr>
157      <tr><td><a name="diff0013" /></td></tr>
158      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.3.  Accept-Encoding  . . . . . . . . . . . . . . . . . . . . . <span class="delete">20</span></td><td> </td><td class="rblock">     6.3.  Accept-Encoding  . . . . . . . . . . . . . . . . . . . . . <span class="insert">19</span></td><td class="lineno" valign="top"></td></tr>
159      <tr><td class="lineno" valign="top"></td><td class="left">     6.4.  Accept-Language  . . . . . . . . . . . . . . . . . . . . . 21</td><td> </td><td class="right">     6.4.  Accept-Language  . . . . . . . . . . . . . . . . . . . . . 21</td><td class="lineno" valign="top"></td></tr>
160      <tr><td class="lineno" valign="top"></td><td class="left">     6.5.  Content-Encoding . . . . . . . . . . . . . . . . . . . . . 22</td><td> </td><td class="right">     6.5.  Content-Encoding . . . . . . . . . . . . . . . . . . . . . 22</td><td class="lineno" valign="top"></td></tr>
161      <tr><td class="lineno" valign="top"></td><td class="left">     6.6.  Content-Language . . . . . . . . . . . . . . . . . . . . . 23</td><td> </td><td class="right">     6.6.  Content-Language . . . . . . . . . . . . . . . . . . . . . 23</td><td class="lineno" valign="top"></td></tr>
162      <tr><td class="lineno" valign="top"></td><td class="left">     6.7.  Content-Location . . . . . . . . . . . . . . . . . . . . . 24</td><td> </td><td class="right">     6.7.  Content-Location . . . . . . . . . . . . . . . . . . . . . 24</td><td class="lineno" valign="top"></td></tr>
163      <tr><td class="lineno" valign="top"></td><td class="left">     6.8.  Content-MD5  . . . . . . . . . . . . . . . . . . . . . . . 25</td><td> </td><td class="right">     6.8.  Content-MD5  . . . . . . . . . . . . . . . . . . . . . . . 25</td><td class="lineno" valign="top"></td></tr>
164      <tr><td><a name="diff0014" /></td></tr>
165      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.9.  Content-Type . . . . . . . . . . . . . . . . . . . . . . . 2<span class="delete">7</span></td><td> </td><td class="rblock">     6.9.  Content-Type . . . . . . . . . . . . . . . . . . . . . . . 2<span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
166      <tr><td class="lineno" valign="top"></td><td class="left">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 27</td><td> </td><td class="right">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 27</td><td class="lineno" valign="top"></td></tr>
167      <tr><td class="lineno" valign="top"></td><td class="left">     7.1.  Header Field Registration  . . . . . . . . . . . . . . . . 27</td><td> </td><td class="right">     7.1.  Header Field Registration  . . . . . . . . . . . . . . . . 27</td><td class="lineno" valign="top"></td></tr>
168      <tr><td class="lineno" valign="top"></td><td class="left">     7.2.  Content Coding Registry  . . . . . . . . . . . . . . . . . 27</td><td> </td><td class="right">     7.2.  Content Coding Registry  . . . . . . . . . . . . . . . . . 27</td><td class="lineno" valign="top"></td></tr>
169      <tr><td class="lineno" valign="top"></td><td class="left">   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 28</td><td> </td><td class="right">   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 28</td><td class="lineno" valign="top"></td></tr>
170      <tr><td class="lineno" valign="top"></td><td class="left">     8.1.  Privacy Issues Connected to Accept Header Fields . . . . . 28</td><td> </td><td class="right">     8.1.  Privacy Issues Connected to Accept Header Fields . . . . . 28</td><td class="lineno" valign="top"></td></tr>
171      <tr><td class="lineno" valign="top"></td><td class="left">   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 29</td><td> </td><td class="right">   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 29</td><td class="lineno" valign="top"></td></tr>
172      <tr><td class="lineno" valign="top"></td><td class="left">   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29</td><td> </td><td class="right">   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29</td><td class="lineno" valign="top"></td></tr>
173      <tr><td class="lineno" valign="top"></td><td class="left">     10.1. Normative References . . . . . . . . . . . . . . . . . . . 29</td><td> </td><td class="right">     10.1. Normative References . . . . . . . . . . . . . . . . . . . 29</td><td class="lineno" valign="top"></td></tr>
174      <tr><td class="lineno" valign="top"></td><td class="left">     10.2. Informative References . . . . . . . . . . . . . . . . . . 31</td><td> </td><td class="right">     10.2. Informative References . . . . . . . . . . . . . . . . . . 31</td><td class="lineno" valign="top"></td></tr>
175      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix A.  Differences between HTTP and MIME . . . . . . . . . . 32</td><td> </td><td class="right">   Appendix A.  Differences between HTTP and MIME . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
176      <tr><td><a name="diff0015" /></td></tr>
177      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.1.  MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 3<span class="delete">3</span></td><td> </td><td class="rblock">     A.1.  MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 3<span class="insert">2</span></td><td class="lineno" valign="top"></td></tr>
178      <tr><td class="lineno" valign="top"></td><td class="left">     A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 33</td><td> </td><td class="right">     A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 33</td><td class="lineno" valign="top"></td></tr>
179      <tr><td class="lineno" valign="top"></td><td class="left">     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 33</td><td> </td><td class="right">     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 33</td><td class="lineno" valign="top"></td></tr>
180      <tr><td class="lineno" valign="top"></td><td class="left">     A.4.  Introduction of Content-Encoding . . . . . . . . . . . . . 34</td><td> </td><td class="right">     A.4.  Introduction of Content-Encoding . . . . . . . . . . . . . 34</td><td class="lineno" valign="top"></td></tr>
181      <tr><td class="lineno" valign="top"></td><td class="left">     A.5.  No Content-Transfer-Encoding . . . . . . . . . . . . . . . 34</td><td> </td><td class="right">     A.5.  No Content-Transfer-Encoding . . . . . . . . . . . . . . . 34</td><td class="lineno" valign="top"></td></tr>
182      <tr><td class="lineno" valign="top"></td><td class="left">     A.6.  Introduction of Transfer-Encoding  . . . . . . . . . . . . 34</td><td> </td><td class="right">     A.6.  Introduction of Transfer-Encoding  . . . . . . . . . . . . 34</td><td class="lineno" valign="top"></td></tr>
183      <tr><td class="lineno" valign="top"></td><td class="left">     A.7.  MHTML and Line Length Limitations  . . . . . . . . . . . . 34</td><td> </td><td class="right">     A.7.  MHTML and Line Length Limitations  . . . . . . . . . . . . 34</td><td class="lineno" valign="top"></td></tr>
184      <tr><td><a name="diff0016" /></td></tr>
185      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix B.  Additional Features . . . . . . . . . . . . . . . . . 3<span class="delete">5</span></td><td> </td><td class="rblock">   Appendix B.  Additional Features . . . . . . . . . . . . . . . . . 3<span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
186      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix C.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 35</td><td> </td><td class="right">   Appendix C.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 35</td><td class="lineno" valign="top"></td></tr>
187      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 35</td><td> </td><td class="right">   Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 35</td><td class="lineno" valign="top"></td></tr>
188      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix E.  Change Log (to be removed by RFC Editor before</td><td> </td><td class="right">   Appendix E.  Change Log (to be removed by RFC Editor before</td><td class="lineno" valign="top"></td></tr>
189      <tr><td class="lineno" valign="top"></td><td class="left">                publication)  . . . . . . . . . . . . . . . . . . . . 37</td><td> </td><td class="right">                publication)  . . . . . . . . . . . . . . . . . . . . 37</td><td class="lineno" valign="top"></td></tr>
190      <tr><td class="lineno" valign="top"></td><td class="left">     E.1.  Since RFC 2616 . . . . . . . . . . . . . . . . . . . . . . 37</td><td> </td><td class="right">     E.1.  Since RFC 2616 . . . . . . . . . . . . . . . . . . . . . . 37</td><td class="lineno" valign="top"></td></tr>
191      <tr><td class="lineno" valign="top"></td><td class="left">     E.2.  Since draft-ietf-httpbis-p3-payload-00 . . . . . . . . . . 37</td><td> </td><td class="right">     E.2.  Since draft-ietf-httpbis-p3-payload-00 . . . . . . . . . . 37</td><td class="lineno" valign="top"></td></tr>
192      <tr><td class="lineno" valign="top"></td><td class="left">     E.3.  Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . 38</td><td> </td><td class="right">     E.3.  Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . 38</td><td class="lineno" valign="top"></td></tr>
193      <tr><td class="lineno" valign="top"></td><td class="left">     E.4.  Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . 38</td><td> </td><td class="right">     E.4.  Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . 38</td><td class="lineno" valign="top"></td></tr>
194      <tr><td class="lineno" valign="top"></td><td class="left">     E.5.  Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . 38</td><td> </td><td class="right">     E.5.  Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . 38</td><td class="lineno" valign="top"></td></tr>
195      <tr><td class="lineno" valign="top"></td><td class="left">     E.6.  Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . 39</td><td> </td><td class="right">     E.6.  Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . 39</td><td class="lineno" valign="top"></td></tr>
196      <tr><td class="lineno" valign="top"></td><td class="left">     E.7.  Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . 39</td><td> </td><td class="right">     E.7.  Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . 39</td><td class="lineno" valign="top"></td></tr>
197      <tr><td><a name="diff0017" /></td></tr>
198      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.8.  Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . <span class="delete">40</span></td><td> </td><td class="rblock">     E.8.  Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . <span class="insert">39</span></td><td class="lineno" valign="top"></td></tr>
199      <tr><td class="lineno" valign="top"></td><td class="left">     E.9.  Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . 40</td><td> </td><td class="right">     E.9.  Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . 40</td><td class="lineno" valign="top"></td></tr>
200      <tr><td class="lineno" valign="top"></td><td class="left">     E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . 40</td><td> </td><td class="right">     E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . 40</td><td class="lineno" valign="top"></td></tr>
201      <tr><td class="lineno" valign="top"></td><td class="left">     E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . 41</td><td> </td><td class="right">     E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . 41</td><td class="lineno" valign="top"></td></tr>
202      <tr><td class="lineno" valign="top"></td><td class="left">     E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . 41</td><td> </td><td class="right">     E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . 41</td><td class="lineno" valign="top"></td></tr>
203      <tr><td class="lineno" valign="top"></td><td class="left">     E.13. Since draft-ietf-httpbis-p3-payload-11 . . . . . . . . . . 42</td><td> </td><td class="right">     E.13. Since draft-ietf-httpbis-p3-payload-11 . . . . . . . . . . 42</td><td class="lineno" valign="top"></td></tr>
204      <tr><td><a name="diff0018" /></td></tr>
205      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     E.14. Since draft-ietf-httpbis-p3-payload-12 . . . . . . . . . . 42</span></td><td class="lineno" valign="top"></td></tr>
206      <tr><td class="lineno" valign="top"></td><td class="left">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42</td><td> </td><td class="right">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42</td><td class="lineno" valign="top"></td></tr>
207      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
208      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
209      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
210      <tr><td class="lineno" valign="top"></td><td class="left">   This document defines HTTP/1.1 message payloads (a.k.a., content),</td><td> </td><td class="right">   This document defines HTTP/1.1 message payloads (a.k.a., content),</td><td class="lineno" valign="top"></td></tr>
211      <tr><td class="lineno" valign="top"></td><td class="left">   the associated metadata header fields that define how the payload is</td><td> </td><td class="right">   the associated metadata header fields that define how the payload is</td><td class="lineno" valign="top"></td></tr>
212      <tr><td class="lineno" valign="top"></td><td class="left">   intended to be interpreted by a recipient, the request header fields</td><td> </td><td class="right">   intended to be interpreted by a recipient, the request header fields</td><td class="lineno" valign="top"></td></tr>
213      <tr><td class="lineno" valign="top"></td><td class="left">   that might influence content selection, and the various selection</td><td> </td><td class="right">   that might influence content selection, and the various selection</td><td class="lineno" valign="top"></td></tr>
214      <tr><td class="lineno" valign="top"></td><td class="left">   algorithms that are collectively referred to as HTTP content</td><td> </td><td class="right">   algorithms that are collectively referred to as HTTP content</td><td class="lineno" valign="top"></td></tr>
215      <tr><td class="lineno" valign="top"></td><td class="left">   negotiation.</td><td> </td><td class="right">   negotiation.</td><td class="lineno" valign="top"></td></tr>
216      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
217      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 6, line 32</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 6, line 32</em></th><td></td></tr>
218      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
219      <tr><td class="lineno" valign="top"></td><td class="left">     token          = &lt;token, defined in [Part1], Section 1.2.2&gt;</td><td> </td><td class="right">     token          = &lt;token, defined in [Part1], Section 1.2.2&gt;</td><td class="lineno" valign="top"></td></tr>
220      <tr><td class="lineno" valign="top"></td><td class="left">     word           = &lt;word, defined in [Part1], Section 1.2.2&gt;</td><td> </td><td class="right">     word           = &lt;word, defined in [Part1], Section 1.2.2&gt;</td><td class="lineno" valign="top"></td></tr>
221      <tr><td class="lineno" valign="top"></td><td class="left">     OWS            = &lt;OWS, defined in [Part1], Section 1.2.2&gt;</td><td> </td><td class="right">     OWS            = &lt;OWS, defined in [Part1], Section 1.2.2&gt;</td><td class="lineno" valign="top"></td></tr>
222      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
223      <tr><td class="lineno" valign="top"></td><td class="left">1.3.2.  ABNF Rules defined in other Parts of the Specification</td><td> </td><td class="right">1.3.2.  ABNF Rules defined in other Parts of the Specification</td><td class="lineno" valign="top"></td></tr>
224      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
225      <tr><td class="lineno" valign="top"></td><td class="left">   The ABNF rules below are defined in other parts:</td><td> </td><td class="right">   The ABNF rules below are defined in other parts:</td><td class="lineno" valign="top"></td></tr>
226      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
227      <tr><td class="lineno" valign="top"></td><td class="left">     absolute-URI   = &lt;absolute-URI, defined in [Part1], Section 2.6&gt;</td><td> </td><td class="right">     absolute-URI   = &lt;absolute-URI, defined in [Part1], Section 2.6&gt;</td><td class="lineno" valign="top"></td></tr>
228      <tr><td><a name="diff0019" /></td></tr>
229      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     Content-Length = &lt;Content-Length, defined in [Part1], Section 9.2&gt;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
230      <tr><td class="lineno" valign="top"></td><td class="left">     partial-URI    = &lt;partial-URI, defined in [Part1], Section 2.6&gt;</td><td> </td><td class="right">     partial-URI    = &lt;partial-URI, defined in [Part1], Section 2.6&gt;</td><td class="lineno" valign="top"></td></tr>
231      <tr><td class="lineno" valign="top"></td><td class="left">     qvalue         = &lt;qvalue, defined in [Part1], Section 6.4&gt;</td><td> </td><td class="right">     qvalue         = &lt;qvalue, defined in [Part1], Section 6.4&gt;</td><td class="lineno" valign="top"></td></tr>
232      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
233      <tr><td><a name="diff0020" /></td></tr>
234      <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">Last-Modified  = &lt;Last-Modified, defined in [Part4], Section 6.6&gt;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
235      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
236      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     Content-Range  = &lt;Content-Range, defined in [Part5], Section 5.2&gt;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
237      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
238      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     Expires        = &lt;Expires, defined in [Part6], Section 3.3&gt;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
239      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
240      <tr><td class="lineno" valign="top"></td><td class="left">2.  Protocol Parameters</td><td> </td><td class="right">2.  Protocol Parameters</td><td class="lineno" valign="top"></td></tr>
241      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
242      <tr><td><a name="diff0021" /></td></tr>
243      <tr><td class="lineno" valign="top"></td><td class="lblock">2.1.  Character <span class="delete">Sets</span></td><td> </td><td class="rblock">2.1.  Character <span class="insert">Encodings (charset)</span></td><td class="lineno" valign="top"></td></tr>
244      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
245      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP uses the same definition of the term "character set" as that</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
246      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   described for MIME:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
247      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
248      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The term "character set" is used in this document to refer to a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
249      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   method used with one or more tables to convert a sequence of octets</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
250      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   into a sequence of characters.  Note that unconditional conversion in</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
251      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the other direction is not required, in that not all characters might</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
252      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   be available in a given character set and a character set might</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
253      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   provide more than one sequence of octets to represent a particular</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
254      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   character.  This definition is intended to allow various kinds of</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
255      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   character encoding, from simple single-table mappings such as US-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
256      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   ASCII to complex table switching methods such as those that use ISO-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
257      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   2022's techniques.  However, the definition associated with a MIME</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
258      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   character set name MUST fully specify the mapping to be performed</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
259      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   from octets to characters.  In particular, use of external profiling</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
260      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   information to determine the exact mapping is not permitted.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
261      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
262      <tr><td><a name="diff0022" /></td></tr>
263      <tr><td class="lineno" valign="top"></td><td class="lblock">      <span class="delete">Note: This use of the term "character set" is more commonly</span></td><td> </td><td class="rblock">   HTTP <span class="insert">uses charset names to indicate</span> the <span class="insert">character encoding of a</span></td><td class="lineno" valign="top"></td></tr>
264      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      referred to as a "character encoding".  However, since</span> HTTP <span class="delete">and</span></td><td> </td><td class="rblock"><span class="insert">   textual representation.</span></td><td class="lineno" valign="top"></td></tr>
265      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      MIME share the same registry, it is important that</span> the <span class="delete">terminology</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
266      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      also be shared.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
267      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
268      <tr><td><a name="diff0023" /></td></tr>
269      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">HTTP character sets are identified by case-insensitive tokens</span>.  The</td><td> </td><td class="rblock">   <span class="insert">A character encoding is identified by a case-insensitive token</span>.  The</td><td class="lineno" valign="top"></td></tr>
270      <tr><td class="lineno" valign="top"></td><td class="left">   complete set of tokens is defined by the IANA Character Set registry</td><td> </td><td class="right">   complete set of tokens is defined by the IANA Character Set registry</td><td class="lineno" valign="top"></td></tr>
271      <tr><td class="lineno" valign="top"></td><td class="left">   (&lt;http://www.iana.org/assignments/character-sets&gt;).</td><td> </td><td class="right">   (&lt;http://www.iana.org/assignments/character-sets&gt;).</td><td class="lineno" valign="top"></td></tr>
272      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
273      <tr><td class="lineno" valign="top"></td><td class="left">     charset = token</td><td> </td><td class="right">     charset = token</td><td class="lineno" valign="top"></td></tr>
274      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
275      <tr><td class="lineno" valign="top"></td><td class="left">   Although HTTP allows an arbitrary token to be used as a charset</td><td> </td><td class="right">   Although HTTP allows an arbitrary token to be used as a charset</td><td class="lineno" valign="top"></td></tr>
276      <tr><td class="lineno" valign="top"></td><td class="left">   value, any token that has a predefined value within the IANA</td><td> </td><td class="right">   value, any token that has a predefined value within the IANA</td><td class="lineno" valign="top"></td></tr>
277      <tr><td><a name="diff0024" /></td></tr>
278      <tr><td class="lineno" valign="top"></td><td class="lblock">   Character Set registry MUST represent the character <span class="delete">set</span> defined by</td><td> </td><td class="rblock">   Character Set registry MUST represent the character <span class="insert">encoding</span> defined</td><td class="lineno" valign="top"></td></tr>
279      <tr><td class="lineno" valign="top"></td><td class="lblock">   that registry.  Applications SHOULD limit their use of character <span class="delete">sets</span></td><td> </td><td class="rblock">   by that registry.  Applications SHOULD limit their use of character</td><td class="lineno" valign="top"></td></tr>
280      <tr><td class="lineno" valign="top"></td><td class="lblock">   to those defined <span class="delete">by</span> the IANA registry.</td><td> </td><td class="rblock">   <span class="insert">encodings</span> to those defined <span class="insert">within</span> the IANA registry.</td><td class="lineno" valign="top"></td></tr>
281      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
282      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP uses charset in two contexts: within an Accept-Charset request</td><td> </td><td class="right">   HTTP uses charset in two contexts: within an Accept-Charset request</td><td class="lineno" valign="top"></td></tr>
283      <tr><td class="lineno" valign="top"></td><td class="left">   header field (in which the charset value is an unquoted token) and as</td><td> </td><td class="right">   header field (in which the charset value is an unquoted token) and as</td><td class="lineno" valign="top"></td></tr>
284      <tr><td class="lineno" valign="top"></td><td class="left">   the value of a parameter in a Content-Type header field (within a</td><td> </td><td class="right">   the value of a parameter in a Content-Type header field (within a</td><td class="lineno" valign="top"></td></tr>
285      <tr><td class="lineno" valign="top"></td><td class="left">   request or response), in which case the parameter value of the</td><td> </td><td class="right">   request or response), in which case the parameter value of the</td><td class="lineno" valign="top"></td></tr>
286      <tr><td class="lineno" valign="top"></td><td class="left">   charset parameter can be quoted.</td><td> </td><td class="right">   charset parameter can be quoted.</td><td class="lineno" valign="top"></td></tr>
287      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
288      <tr><td class="lineno" valign="top"></td><td class="left">   Implementors need to be aware of IETF character set requirements</td><td> </td><td class="right">   Implementors need to be aware of IETF character set requirements</td><td class="lineno" valign="top"></td></tr>
289      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3629] [RFC2277].</td><td> </td><td class="right">   [RFC3629] [RFC2277].</td><td class="lineno" valign="top"></td></tr>
290      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
291      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
292      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 9, line 40</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 9, line 9</em></th><td></td></tr>
293      <tr><td class="lineno" valign="top"></td><td class="left">2.3.  Media Types</td><td> </td><td class="right">2.3.  Media Types</td><td class="lineno" valign="top"></td></tr>
294      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
295      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP uses Internet Media Types [RFC2046] in the Content-Type</td><td> </td><td class="right">   HTTP uses Internet Media Types [RFC2046] in the Content-Type</td><td class="lineno" valign="top"></td></tr>
296      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 6.9) and Accept (Section 6.1) header fields in order to</td><td> </td><td class="right">   (Section 6.9) and Accept (Section 6.1) header fields in order to</td><td class="lineno" valign="top"></td></tr>
297      <tr><td class="lineno" valign="top"></td><td class="left">   provide open and extensible data typing and type negotiation.</td><td> </td><td class="right">   provide open and extensible data typing and type negotiation.</td><td class="lineno" valign="top"></td></tr>
298      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
299      <tr><td class="lineno" valign="top"></td><td class="left">     media-type = type "/" subtype *( OWS ";" OWS parameter )</td><td> </td><td class="right">     media-type = type "/" subtype *( OWS ";" OWS parameter )</td><td class="lineno" valign="top"></td></tr>
300      <tr><td class="lineno" valign="top"></td><td class="left">     type       = token</td><td> </td><td class="right">     type       = token</td><td class="lineno" valign="top"></td></tr>
301      <tr><td class="lineno" valign="top"></td><td class="left">     subtype    = token</td><td> </td><td class="right">     subtype    = token</td><td class="lineno" valign="top"></td></tr>
302      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
303      <tr><td><a name="diff0025" /></td></tr>
304      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Parameters MAY follow the</span> type/subtype in the form of attribute/value</td><td> </td><td class="rblock">   <span class="insert">The</span> type/subtype <span class="insert">MAY be followed by parameters</span> in the form of</td><td class="lineno" valign="top"></td></tr>
305      <tr><td class="lineno" valign="top"></td><td class="lblock">   pairs.</td><td> </td><td class="rblock">   attribute/value pairs.</td><td class="lineno" valign="top"></td></tr>
306      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
307      <tr><td class="lineno" valign="top"></td><td class="left">     parameter      = attribute "=" value</td><td> </td><td class="right">     parameter      = attribute "=" value</td><td class="lineno" valign="top"></td></tr>
308      <tr><td class="lineno" valign="top"></td><td class="left">     attribute      = token</td><td> </td><td class="right">     attribute      = token</td><td class="lineno" valign="top"></td></tr>
309      <tr><td class="lineno" valign="top"></td><td class="left">     value          = word</td><td> </td><td class="right">     value          = word</td><td class="lineno" valign="top"></td></tr>
310      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
311      <tr><td class="lineno" valign="top"></td><td class="left">   The type, subtype, and parameter attribute names are case-</td><td> </td><td class="right">   The type, subtype, and parameter attribute names are case-</td><td class="lineno" valign="top"></td></tr>
312      <tr><td class="lineno" valign="top"></td><td class="left">   insensitive.  Parameter values might or might not be case-sensitive,</td><td> </td><td class="right">   insensitive.  Parameter values might or might not be case-sensitive,</td><td class="lineno" valign="top"></td></tr>
313      <tr><td class="lineno" valign="top"></td><td class="left">   depending on the semantics of the parameter name.  The presence or</td><td> </td><td class="right">   depending on the semantics of the parameter name.  The presence or</td><td class="lineno" valign="top"></td></tr>
314      <tr><td class="lineno" valign="top"></td><td class="left">   absence of a parameter might be significant to the processing of a</td><td> </td><td class="right">   absence of a parameter might be significant to the processing of a</td><td class="lineno" valign="top"></td></tr>
315      <tr><td class="lineno" valign="top"></td><td class="left">   media-type, depending on its definition within the media type</td><td> </td><td class="right">   media-type, depending on its definition within the media type</td><td class="lineno" valign="top"></td></tr>
316      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
317      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 12, line 28</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 11, line 44</em></th><td></td></tr>
318      <tr><td class="lineno" valign="top"></td><td class="left">   header fields (e.g., responses to HEAD) or only some part(s) of the</td><td> </td><td class="right">   header fields (e.g., responses to HEAD) or only some part(s) of the</td><td class="lineno" valign="top"></td></tr>
319      <tr><td class="lineno" valign="top"></td><td class="left">   representation (e.g., the 206 status code).</td><td> </td><td class="right">   representation (e.g., the 206 status code).</td><td class="lineno" valign="top"></td></tr>
320      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
321      <tr><td class="lineno" valign="top"></td><td class="left">3.1.  Payload Header Fields</td><td> </td><td class="right">3.1.  Payload Header Fields</td><td class="lineno" valign="top"></td></tr>
322      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
323      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP header fields that specifically define the payload, rather than</td><td> </td><td class="right">   HTTP header fields that specifically define the payload, rather than</td><td class="lineno" valign="top"></td></tr>
324      <tr><td class="lineno" valign="top"></td><td class="left">   the associated representation, are referred to as "payload header</td><td> </td><td class="right">   the associated representation, are referred to as "payload header</td><td class="lineno" valign="top"></td></tr>
325      <tr><td class="lineno" valign="top"></td><td class="left">   fields".  The following payload header fields are defined by</td><td> </td><td class="right">   fields".  The following payload header fields are defined by</td><td class="lineno" valign="top"></td></tr>
326      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/1.1:</td><td> </td><td class="right">   HTTP/1.1:</td><td class="lineno" valign="top"></td></tr>
327      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
328      <tr><td><a name="diff0026" /></td></tr>
329      <tr><td class="lineno" valign="top"></td><td class="lblock">      Content-Length           <span class="delete">; [Part1],</span> Section 9.2</td><td> </td><td class="rblock">   <span class="insert">+-------------------+------------------------+</span></td><td class="lineno" valign="top"></td></tr>
330      <tr><td class="lineno" valign="top"></td><td class="lblock">      Content-MD5              <span class="delete">;</span> Section 6.8</td><td> </td><td class="rblock"><span class="insert">   | Header Field Name | Defined in...          |</span></td><td class="lineno" valign="top"></td></tr>
331      <tr><td class="lineno" valign="top"></td><td class="lblock">      Content-Range            <span class="delete">; [Part5],</span> Section 5.2</td><td> </td><td class="rblock"><span class="insert">   +-------------------+------------------------+</span></td><td class="lineno" valign="top"></td></tr>
332      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   |</span> Content-Length    <span class="insert">|</span> Section 9.2 <span class="insert">of [Part1] |</span></td><td class="lineno" valign="top"></td></tr>
333      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   |</span> Content-MD5       <span class="insert">|</span> Section 6.8            <span class="insert">|</span></td><td class="lineno" valign="top"></td></tr>
334      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   |</span> Content-Range     <span class="insert">|</span> Section 5.2 <span class="insert">of [Part5] |</span></td><td class="lineno" valign="top"></td></tr>
335      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   +-------------------+------------------------+</span></td><td class="lineno" valign="top"></td></tr>
336      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
337      <tr><td class="lineno" valign="top"></td><td class="left">3.2.  Payload Body</td><td> </td><td class="right">3.2.  Payload Body</td><td class="lineno" valign="top"></td></tr>
338      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
339      <tr><td class="lineno" valign="top"></td><td class="left">   A payload body is only present in a message when a message-body is</td><td> </td><td class="right">   A payload body is only present in a message when a message-body is</td><td class="lineno" valign="top"></td></tr>
340      <tr><td class="lineno" valign="top"></td><td class="left">   present, as described in Section 3.3 of [Part1].  The payload body is</td><td> </td><td class="right">   present, as described in Section 3.3 of [Part1].  The payload body is</td><td class="lineno" valign="top"></td></tr>
341      <tr><td class="lineno" valign="top"></td><td class="left">   obtained from the message-body by decoding any Transfer-Encoding that</td><td> </td><td class="right">   obtained from the message-body by decoding any Transfer-Encoding that</td><td class="lineno" valign="top"></td></tr>
342      <tr><td class="lineno" valign="top"></td><td class="left">   might have been applied to ensure safe and proper transfer of the</td><td> </td><td class="right">   might have been applied to ensure safe and proper transfer of the</td><td class="lineno" valign="top"></td></tr>
343      <tr><td class="lineno" valign="top"></td><td class="left">   message.</td><td> </td><td class="right">   message.</td><td class="lineno" valign="top"></td></tr>
344      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
345      <tr><td class="lineno" valign="top"></td><td class="left">4.  Representation</td><td> </td><td class="right">4.  Representation</td><td class="lineno" valign="top"></td></tr>
346      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
347      <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 13, line 24</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 13, line 5</em></th><td></td></tr>
348      <tr><td class="lineno" valign="top"></td><td class="left">4.1.  Representation Header Fields</td><td> </td><td class="right">4.1.  Representation Header Fields</td><td class="lineno" valign="top"></td></tr>
349      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
350      <tr><td class="lineno" valign="top"></td><td class="left">   Representation header fields define metadata about the representation</td><td> </td><td class="right">   Representation header fields define metadata about the representation</td><td class="lineno" valign="top"></td></tr>
351      <tr><td class="lineno" valign="top"></td><td class="left">   data enclosed in the message-body or, if no message-body is present,</td><td> </td><td class="right">   data enclosed in the message-body or, if no message-body is present,</td><td class="lineno" valign="top"></td></tr>
352      <tr><td class="lineno" valign="top"></td><td class="left">   about the representation that would have been transferred in a 200</td><td> </td><td class="right">   about the representation that would have been transferred in a 200</td><td class="lineno" valign="top"></td></tr>
353      <tr><td class="lineno" valign="top"></td><td class="left">   response to a simultaneous GET request with the same effective</td><td> </td><td class="right">   response to a simultaneous GET request with the same effective</td><td class="lineno" valign="top"></td></tr>
354      <tr><td class="lineno" valign="top"></td><td class="left">   request URI.</td><td> </td><td class="right">   request URI.</td><td class="lineno" valign="top"></td></tr>
355      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
356      <tr><td class="lineno" valign="top"></td><td class="left">   The following header fields are defined as representation metadata:</td><td> </td><td class="right">   The following header fields are defined as representation metadata:</td><td class="lineno" valign="top"></td></tr>
357      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
358      <tr><td><a name="diff0027" /></td></tr>
359      <tr><td class="lineno" valign="top"></td><td class="lblock">      Content-Encoding         <span class="delete">;</span> Section 6.5</td><td> </td><td class="rblock">   <span class="insert">+-------------------+------------------------+</span></td><td class="lineno" valign="top"></td></tr>
360      <tr><td class="lineno" valign="top"></td><td class="lblock">      Content-Language         <span class="delete">;</span> Section 6.6</td><td> </td><td class="rblock"><span class="insert">   | Header Field Name | Defined in...          |</span></td><td class="lineno" valign="top"></td></tr>
361      <tr><td class="lineno" valign="top"></td><td class="lblock">      Content-Location         <span class="delete">;</span> Section 6.7</td><td> </td><td class="rblock"><span class="insert">   +-------------------+------------------------+</span></td><td class="lineno" valign="top"></td></tr>
362      <tr><td class="lineno" valign="top"></td><td class="lblock">      Content-Type             <span class="delete">;</span> Section 6.9</td><td> </td><td class="rblock"><span class="insert">   |</span> Content-Encoding  <span class="insert">|</span> Section 6.5            <span class="insert">|</span></td><td class="lineno" valign="top"></td></tr>
363      <tr><td class="lineno" valign="top"></td><td class="lblock">      Expires                  <span class="delete">; [Part6],</span> Section 3.3</td><td> </td><td class="rblock"><span class="insert">   |</span> Content-Language  <span class="insert">|</span> Section 6.6            <span class="insert">|</span></td><td class="lineno" valign="top"></td></tr>
364      <tr><td class="lineno" valign="top"></td><td class="lblock">      Last-Modified            <span class="delete">; [Part4],</span> Section 6.6</td><td> </td><td class="rblock"><span class="insert">   |</span> Content-Location  <span class="insert">|</span> Section 6.7            <span class="insert">|</span></td><td class="lineno" valign="top"></td></tr>
365      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   |</span> Content-Type      <span class="insert">|</span> Section 6.9            <span class="insert">|</span></td><td class="lineno" valign="top"></td></tr>
366      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   |</span> Expires           <span class="insert">|</span> Section 3.3 <span class="insert">of [Part6] |</span></td><td class="lineno" valign="top"></td></tr>
367      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   |</span> Last-Modified     <span class="insert">|</span> Section 6.6 <span class="insert">of [Part4] |</span></td><td class="lineno" valign="top"></td></tr>
368      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   +-------------------+------------------------+</span></td><td class="lineno" valign="top"></td></tr>
369      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
370      <tr><td class="lineno" valign="top"></td><td class="left">4.2.  Representation Data</td><td> </td><td class="right">4.2.  Representation Data</td><td class="lineno" valign="top"></td></tr>
371      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
372      <tr><td class="lineno" valign="top"></td><td class="left">   The representation body associated with an HTTP message is either</td><td> </td><td class="right">   The representation body associated with an HTTP message is either</td><td class="lineno" valign="top"></td></tr>
373      <tr><td class="lineno" valign="top"></td><td class="left">   provided as the payload body of the message or referred to by the</td><td> </td><td class="right">   provided as the payload body of the message or referred to by the</td><td class="lineno" valign="top"></td></tr>
374      <tr><td class="lineno" valign="top"></td><td class="left">   message semantics and the effective request URI.  The representation</td><td> </td><td class="right">   message semantics and the effective request URI.  The representation</td><td class="lineno" valign="top"></td></tr>
375      <tr><td class="lineno" valign="top"></td><td class="left">   data is in a format and encoding defined by the representation</td><td> </td><td class="right">   data is in a format and encoding defined by the representation</td><td class="lineno" valign="top"></td></tr>
376      <tr><td class="lineno" valign="top"></td><td class="left">   metadata header fields.</td><td> </td><td class="right">   metadata header fields.</td><td class="lineno" valign="top"></td></tr>
377      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
378      <tr><td class="lineno" valign="top"></td><td class="left">   The data type of the representation data is determined via the header</td><td> </td><td class="right">   The data type of the representation data is determined via the header</td><td class="lineno" valign="top"></td></tr>
379      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
380      <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 16, line 11</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 15, line 44</em></th><td></td></tr>
381      <tr><td class="lineno" valign="top"></td><td class="left">       can be both very inefficient (given that only a small percentage</td><td> </td><td class="right">       can be both very inefficient (given that only a small percentage</td><td class="lineno" valign="top"></td></tr>
382      <tr><td class="lineno" valign="top"></td><td class="left">       of responses have multiple representations) and a potential</td><td> </td><td class="right">       of responses have multiple representations) and a potential</td><td class="lineno" valign="top"></td></tr>
383      <tr><td class="lineno" valign="top"></td><td class="left">       violation of the user's privacy.</td><td> </td><td class="right">       violation of the user's privacy.</td><td class="lineno" valign="top"></td></tr>
384      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
385      <tr><td class="lineno" valign="top"></td><td class="left">   3.  It complicates the implementation of an origin server and the</td><td> </td><td class="right">   3.  It complicates the implementation of an origin server and the</td><td class="lineno" valign="top"></td></tr>
386      <tr><td class="lineno" valign="top"></td><td class="left">       algorithms for generating responses to a request.</td><td> </td><td class="right">       algorithms for generating responses to a request.</td><td class="lineno" valign="top"></td></tr>
387      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
388      <tr><td class="lineno" valign="top"></td><td class="left">   4.  It might limit a public cache's ability to use the same response</td><td> </td><td class="right">   4.  It might limit a public cache's ability to use the same response</td><td class="lineno" valign="top"></td></tr>
389      <tr><td class="lineno" valign="top"></td><td class="left">       for multiple user's requests.</td><td> </td><td class="right">       for multiple user's requests.</td><td class="lineno" valign="top"></td></tr>
390      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
391      <tr><td><a name="diff0028" /></td></tr>
392      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP/1.1 includes the following <span class="delete">request-header</span> fields for enabling</td><td> </td><td class="rblock">   HTTP/1.1 includes the following <span class="insert">header</span> fields for enabling <span class="insert">server-</span></td><td class="lineno" valign="top"></td></tr>
393      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">server-driven</span> negotiation through description of user agent</td><td> </td><td class="rblock"><span class="insert">   driven</span> negotiation through description of user agent capabilities and</td><td class="lineno" valign="top"></td></tr>
394      <tr><td class="lineno" valign="top"></td><td class="lblock">   capabilities and user preferences: Accept (Section 6.1), <span class="delete">Accept-</span></td><td> </td><td class="rblock">   user preferences: Accept (Section 6.1), <span class="insert">Accept-Charset</span> (Section 6.2),</td><td class="lineno" valign="top"></td></tr>
395      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Charset</span> (Section 6.2), Accept-Encoding (Section 6.3), Accept-Language</td><td> </td><td class="rblock">   Accept-Encoding (Section 6.3), Accept-Language (Section 6.4), and</td><td class="lineno" valign="top"></td></tr>
396      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section 6.4), and User-Agent (Section 9.9 of [Part2]).  However, an</td><td> </td><td class="rblock">   User-Agent (Section 9.9 of [Part2]).  However, an origin server is</td><td class="lineno" valign="top"></td></tr>
397      <tr><td class="lineno" valign="top"></td><td class="lblock">   origin server is not limited to these dimensions and MAY vary the</td><td> </td><td class="rblock">   not limited to these dimensions and MAY vary the response based on</td><td class="lineno" valign="top"></td></tr>
398      <tr><td class="lineno" valign="top"></td><td class="lblock">   response based on any aspect of the request, including <span class="delete">information</span></td><td> </td><td class="rblock">   any aspect of the request, including <span class="insert">aspects of</span> the <span class="insert">connection (e.g.,</span></td><td class="lineno" valign="top"></td></tr>
399      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   outside</span> the <span class="delete">request-header fields</span> or within extension header fields</td><td> </td><td class="rblock"><span class="insert">   IP address)</span> or <span class="insert">information</span> within extension header fields not defined</td><td class="lineno" valign="top"></td></tr>
400      <tr><td class="lineno" valign="top"></td><td class="lblock">   not defined by this specification.</td><td> </td><td class="rblock">   by this specification.</td><td class="lineno" valign="top"></td></tr>
401      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
402      <tr><td class="lineno" valign="top"></td><td class="left">      Note: In practice, User-Agent based negotiation is fragile,</td><td> </td><td class="right">      Note: In practice, User-Agent based negotiation is fragile,</td><td class="lineno" valign="top"></td></tr>
403      <tr><td class="lineno" valign="top"></td><td class="left">      because new clients might not be recognized.</td><td> </td><td class="right">      because new clients might not be recognized.</td><td class="lineno" valign="top"></td></tr>
404      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
405      <tr><td class="lineno" valign="top"></td><td class="left">   The Vary header field (Section 3.5 of [Part6]) can be used to express</td><td> </td><td class="right">   The Vary header field (Section 3.5 of [Part6]) can be used to express</td><td class="lineno" valign="top"></td></tr>
406      <tr><td class="lineno" valign="top"></td><td class="left">   the parameters the server uses to select a representation that is</td><td> </td><td class="right">   the parameters the server uses to select a representation that is</td><td class="lineno" valign="top"></td></tr>
407      <tr><td class="lineno" valign="top"></td><td class="left">   subject to server-driven negotiation.</td><td> </td><td class="right">   subject to server-driven negotiation.</td><td class="lineno" valign="top"></td></tr>
408      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
409      <tr><td class="lineno" valign="top"></td><td class="left">5.2.  Agent-driven Negotiation</td><td> </td><td class="right">5.2.  Agent-driven Negotiation</td><td class="lineno" valign="top"></td></tr>
410      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
411      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
412      <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 17, line 17</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 16, line 50</em></th><td></td></tr>
413      <tr><td class="lineno" valign="top"></td><td class="left">   the server is unwilling or unable to provide a varying response using</td><td> </td><td class="right">   the server is unwilling or unable to provide a varying response using</td><td class="lineno" valign="top"></td></tr>
414      <tr><td class="lineno" valign="top"></td><td class="left">   server-driven negotiation.</td><td> </td><td class="right">   server-driven negotiation.</td><td class="lineno" valign="top"></td></tr>
415      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
416      <tr><td class="lineno" valign="top"></td><td class="left">6.  Header Field Definitions</td><td> </td><td class="right">6.  Header Field Definitions</td><td class="lineno" valign="top"></td></tr>
417      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
418      <tr><td class="lineno" valign="top"></td><td class="left">   This section defines the syntax and semantics of HTTP/1.1 header</td><td> </td><td class="right">   This section defines the syntax and semantics of HTTP/1.1 header</td><td class="lineno" valign="top"></td></tr>
419      <tr><td class="lineno" valign="top"></td><td class="left">   fields related to the payload of messages.</td><td> </td><td class="right">   fields related to the payload of messages.</td><td class="lineno" valign="top"></td></tr>
420      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
421      <tr><td class="lineno" valign="top"></td><td class="left">6.1.  Accept</td><td> </td><td class="right">6.1.  Accept</td><td class="lineno" valign="top"></td></tr>
422      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
423      <tr><td><a name="diff0029" /></td></tr>
424      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "Accept" <span class="delete">request-header</span> field can be used by user agents to</td><td> </td><td class="rblock">   The "Accept" <span class="insert">header</span> field can be used by user agents to specify</td><td class="lineno" valign="top"></td></tr>
425      <tr><td class="lineno" valign="top"></td><td class="lblock">   specify response media types that are acceptable.  Accept header</td><td> </td><td class="rblock">   response media types that are acceptable.  Accept header fields can</td><td class="lineno" valign="top"></td></tr>
426      <tr><td class="lineno" valign="top"></td><td class="lblock">   fields can be used to indicate that the request is specifically</td><td> </td><td class="rblock">   be used to indicate that the request is specifically limited to a</td><td class="lineno" valign="top"></td></tr>
427      <tr><td class="lineno" valign="top"></td><td class="lblock">   limited to a small set of desired types, as in the case of a request</td><td> </td><td class="rblock">   small set of desired types, as in the case of a request for an <span class="insert">in-</span></td><td class="lineno" valign="top"></td></tr>
428      <tr><td class="lineno" valign="top"></td><td class="lblock">   for an <span class="delete">in-line</span> image.</td><td> </td><td class="rblock"><span class="insert">   line</span> image.</td><td class="lineno" valign="top"></td></tr>
429      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
430      <tr><td class="lineno" valign="top"></td><td class="left">     Accept   = "Accept" ":" OWS Accept-v</td><td> </td><td class="right">     Accept   = "Accept" ":" OWS Accept-v</td><td class="lineno" valign="top"></td></tr>
431      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-v = #( media-range [ accept-params ] )</td><td> </td><td class="right">     Accept-v = #( media-range [ accept-params ] )</td><td class="lineno" valign="top"></td></tr>
432      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
433      <tr><td class="lineno" valign="top"></td><td class="left">     media-range    = ( "*/*"</td><td> </td><td class="right">     media-range    = ( "*/*"</td><td class="lineno" valign="top"></td></tr>
434      <tr><td class="lineno" valign="top"></td><td class="left">                      / ( type "/" "*" )</td><td> </td><td class="right">                      / ( type "/" "*" )</td><td class="lineno" valign="top"></td></tr>
435      <tr><td class="lineno" valign="top"></td><td class="left">                      / ( type "/" subtype )</td><td> </td><td class="right">                      / ( type "/" subtype )</td><td class="lineno" valign="top"></td></tr>
436      <tr><td class="lineno" valign="top"></td><td class="left">                      ) *( OWS ";" OWS parameter )</td><td> </td><td class="right">                      ) *( OWS ";" OWS parameter )</td><td class="lineno" valign="top"></td></tr>
437      <tr><td class="lineno" valign="top"></td><td class="left">     accept-params  = OWS ";" OWS "q=" qvalue *( accept-ext )</td><td> </td><td class="right">     accept-params  = OWS ";" OWS "q=" qvalue *( accept-ext )</td><td class="lineno" valign="top"></td></tr>
438      <tr><td class="lineno" valign="top"></td><td class="left">     accept-ext     = OWS ";" OWS token [ "=" word ]</td><td> </td><td class="right">     accept-ext     = OWS ";" OWS token [ "=" word ]</td><td class="lineno" valign="top"></td></tr>
439      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
440      <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 19, line 25</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 19, line 9</em></th><td></td></tr>
441      <tr><td class="lineno" valign="top"></td><td class="left">   | text/html;level=3 | 0.7           |</td><td> </td><td class="right">   | text/html;level=3 | 0.7           |</td><td class="lineno" valign="top"></td></tr>
442      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+---------------+</td><td> </td><td class="right">   +-------------------+---------------+</td><td class="lineno" valign="top"></td></tr>
443      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
444      <tr><td class="lineno" valign="top"></td><td class="left">   Note: A user agent might be provided with a default set of quality</td><td> </td><td class="right">   Note: A user agent might be provided with a default set of quality</td><td class="lineno" valign="top"></td></tr>
445      <tr><td class="lineno" valign="top"></td><td class="left">   values for certain media ranges.  However, unless the user agent is a</td><td> </td><td class="right">   values for certain media ranges.  However, unless the user agent is a</td><td class="lineno" valign="top"></td></tr>
446      <tr><td class="lineno" valign="top"></td><td class="left">   closed system which cannot interact with other rendering agents, this</td><td> </td><td class="right">   closed system which cannot interact with other rendering agents, this</td><td class="lineno" valign="top"></td></tr>
447      <tr><td class="lineno" valign="top"></td><td class="left">   default set ought to be configurable by the user.</td><td> </td><td class="right">   default set ought to be configurable by the user.</td><td class="lineno" valign="top"></td></tr>
448      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
449      <tr><td class="lineno" valign="top"></td><td class="left">6.2.  Accept-Charset</td><td> </td><td class="right">6.2.  Accept-Charset</td><td class="lineno" valign="top"></td></tr>
450      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
451      <tr><td><a name="diff0030" /></td></tr>
452      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "Accept-Charset" <span class="delete">request-header</span> field can be used by user agents</td><td> </td><td class="rblock">   The "Accept-Charset" <span class="insert">header</span> field can be used by user agents to</td><td class="lineno" valign="top"></td></tr>
453      <tr><td class="lineno" valign="top"></td><td class="lblock">   to indicate what <span class="delete">response</span> character <span class="delete">sets</span> are <span class="delete">acceptable.</span>  This field</td><td> </td><td class="rblock">   indicate what character <span class="insert">encodings</span> are <span class="insert">acceptable in a response</span></td><td class="lineno" valign="top"></td></tr>
454      <tr><td class="lineno" valign="top"></td><td class="lblock">   allows clients capable of understanding more comprehensive or</td><td> </td><td class="rblock"><span class="insert">   payload.</span>  This field allows clients capable of understanding more</td><td class="lineno" valign="top"></td></tr>
455      <tr><td class="lineno" valign="top"></td><td class="lblock">   special-purpose character <span class="delete">sets</span> to signal that capability to a server</td><td> </td><td class="rblock">   comprehensive or special-purpose character <span class="insert">encodings</span> to signal that</td><td class="lineno" valign="top"></td></tr>
456      <tr><td class="lineno" valign="top"></td><td class="lblock">   which is capable of representing documents in those character <span class="delete">sets.</span></td><td> </td><td class="rblock">   capability to a server which is capable of representing documents in</td><td class="lineno" valign="top"></td></tr>
457      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   those character <span class="insert">encodings.</span></td><td class="lineno" valign="top"></td></tr>
458      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
459      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Charset   = "Accept-Charset" ":" OWS</td><td> </td><td class="right">     Accept-Charset   = "Accept-Charset" ":" OWS</td><td class="lineno" valign="top"></td></tr>
460      <tr><td class="lineno" valign="top"></td><td class="left">             Accept-Charset-v</td><td> </td><td class="right">             Accept-Charset-v</td><td class="lineno" valign="top"></td></tr>
461      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Charset-v = 1#( ( charset / "*" )</td><td> </td><td class="right">     Accept-Charset-v = 1#( ( charset / "*" )</td><td class="lineno" valign="top"></td></tr>
462      <tr><td class="lineno" valign="top"></td><td class="left">                            [ OWS ";" OWS "q=" qvalue ] )</td><td> </td><td class="right">                            [ OWS ";" OWS "q=" qvalue ] )</td><td class="lineno" valign="top"></td></tr>
463      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
464      <tr><td><a name="diff0031" /></td></tr>
465      <tr><td class="lineno" valign="top"></td><td class="lblock">   Character <span class="delete">set</span> values are described in Section 2.1.  Each charset MAY</td><td> </td><td class="rblock">   Character <span class="insert">encoding</span> values <span class="insert">(a.k.a., charsets)</span> are described in</td><td class="lineno" valign="top"></td></tr>
466      <tr><td class="lineno" valign="top"></td><td class="lblock">   be given an associated quality value which represents the user's</td><td> </td><td class="rblock">   Section 2.1.  Each charset MAY be given an associated quality value</td><td class="lineno" valign="top"></td></tr>
467      <tr><td class="lineno" valign="top"></td><td class="lblock">   preference for that charset.  The default value is q=1.  An example</td><td> </td><td class="rblock">   which represents the user's preference for that charset.  The default</td><td class="lineno" valign="top"></td></tr>
468      <tr><td class="lineno" valign="top"></td><td class="lblock">   is</td><td> </td><td class="rblock">   value is q=1.  An example is</td><td class="lineno" valign="top"></td></tr>
469      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
470      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Charset: iso-8859-5, unicode-1-1;q=0.8</td><td> </td><td class="right">     Accept-Charset: iso-8859-5, unicode-1-1;q=0.8</td><td class="lineno" valign="top"></td></tr>
471      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
472      <tr><td class="lineno" valign="top"></td><td class="left">   The special value "*", if present in the Accept-Charset field,</td><td> </td><td class="right">   The special value "*", if present in the Accept-Charset field,</td><td class="lineno" valign="top"></td></tr>
473      <tr><td><a name="diff0032" /></td></tr>
474      <tr><td class="lineno" valign="top"></td><td class="lblock">   matches every character <span class="delete">set</span> (including ISO-8859-1) which is not</td><td> </td><td class="rblock">   matches every character <span class="insert">encoding</span> (including ISO-8859-1) which is not</td><td class="lineno" valign="top"></td></tr>
475      <tr><td class="lineno" valign="top"></td><td class="left">   mentioned elsewhere in the Accept-Charset field.  If no "*" is</td><td> </td><td class="right">   mentioned elsewhere in the Accept-Charset field.  If no "*" is</td><td class="lineno" valign="top"></td></tr>
476      <tr><td><a name="diff0033" /></td></tr>
477      <tr><td class="lineno" valign="top"></td><td class="lblock">   present in an Accept-Charset field, then all character <span class="delete">set</span>s not</td><td> </td><td class="rblock">   present in an Accept-Charset field, then all character <span class="insert">encoding</span>s not</td><td class="lineno" valign="top"></td></tr>
478      <tr><td class="lineno" valign="top"></td><td class="left">   explicitly mentioned get a quality value of 0, except for ISO-8859-1,</td><td> </td><td class="right">   explicitly mentioned get a quality value of 0, except for ISO-8859-1,</td><td class="lineno" valign="top"></td></tr>
479      <tr><td class="lineno" valign="top"></td><td class="left">   which gets a quality value of 1 if not explicitly mentioned.</td><td> </td><td class="right">   which gets a quality value of 1 if not explicitly mentioned.</td><td class="lineno" valign="top"></td></tr>
480      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
481      <tr><td class="lineno" valign="top"></td><td class="left">   If no Accept-Charset header field is present, the default is that any</td><td> </td><td class="right">   If no Accept-Charset header field is present, the default is that any</td><td class="lineno" valign="top"></td></tr>
482      <tr><td><a name="diff0034" /></td></tr>
483      <tr><td class="lineno" valign="top"></td><td class="lblock">   character <span class="delete">set</span> is acceptable.  If an Accept-Charset header field is</td><td> </td><td class="rblock">   character <span class="insert">encoding</span> is acceptable.  If an Accept-Charset header field</td><td class="lineno" valign="top"></td></tr>
484      <tr><td class="lineno" valign="top"></td><td class="lblock">   present, and if the server cannot send a response which is acceptable</td><td> </td><td class="rblock">   is present, and if the server cannot send a response which is</td><td class="lineno" valign="top"></td></tr>
485      <tr><td class="lineno" valign="top"></td><td class="lblock">   according to the Accept-Charset header field, then the server SHOULD</td><td> </td><td class="rblock">   acceptable according to the Accept-Charset header field, then the</td><td class="lineno" valign="top"></td></tr>
486      <tr><td class="lineno" valign="top"></td><td class="lblock">   send an error response with the 406 (Not Acceptable) status code,</td><td> </td><td class="rblock">   server SHOULD send an error response with the 406 (Not Acceptable)</td><td class="lineno" valign="top"></td></tr>
487      <tr><td class="lineno" valign="top"></td><td class="lblock">   though the sending of an unacceptable response is also allowed.</td><td> </td><td class="rblock">   status code, though the sending of an unacceptable response is also</td><td class="lineno" valign="top"></td></tr>
488      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   allowed.</td><td class="lineno" valign="top"></td></tr>
489      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
490      <tr><td class="lineno" valign="top"></td><td class="left">6.3.  Accept-Encoding</td><td> </td><td class="right">6.3.  Accept-Encoding</td><td class="lineno" valign="top"></td></tr>
491      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
492      <tr><td><a name="diff0035" /></td></tr>
493      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "Accept-Encoding" <span class="delete">request-header</span> field can be used by user agents</td><td> </td><td class="rblock">   The "Accept-Encoding" <span class="insert">header</span> field can be used by user agents to</td><td class="lineno" valign="top"></td></tr>
494      <tr><td class="lineno" valign="top"></td><td class="lblock">   to indicate what response content-codings (Section 2.2) are</td><td> </td><td class="rblock">   indicate what response content-codings (Section 2.2) are acceptable</td><td class="lineno" valign="top"></td></tr>
495      <tr><td class="lineno" valign="top"></td><td class="lblock">   acceptable in the response.</td><td> </td><td class="rblock">   in the response.</td><td class="lineno" valign="top"></td></tr>
496      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
497      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Encoding    = "Accept-Encoding" ":" OWS</td><td> </td><td class="right">     Accept-Encoding    = "Accept-Encoding" ":" OWS</td><td class="lineno" valign="top"></td></tr>
498      <tr><td class="lineno" valign="top"></td><td class="left">                        Accept-Encoding-v</td><td> </td><td class="right">                        Accept-Encoding-v</td><td class="lineno" valign="top"></td></tr>
499      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Encoding-v  =</td><td> </td><td class="right">     Accept-Encoding-v  =</td><td class="lineno" valign="top"></td></tr>
500      <tr><td class="lineno" valign="top"></td><td class="left">                        #( codings [ OWS ";" OWS "q=" qvalue ] )</td><td> </td><td class="right">                        #( codings [ OWS ";" OWS "q=" qvalue ] )</td><td class="lineno" valign="top"></td></tr>
501      <tr><td class="lineno" valign="top"></td><td class="left">     codings            = ( content-coding / "*" )</td><td> </td><td class="right">     codings            = ( content-coding / "*" )</td><td class="lineno" valign="top"></td></tr>
502      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
503      <tr><td class="lineno" valign="top"></td><td class="left">   Each codings value MAY be given an associated quality value which</td><td> </td><td class="right">   Each codings value MAY be given an associated quality value which</td><td class="lineno" valign="top"></td></tr>
504      <tr><td class="lineno" valign="top"></td><td class="left">   represents the preference for that encoding.  The default value is</td><td> </td><td class="right">   represents the preference for that encoding.  The default value is</td><td class="lineno" valign="top"></td></tr>
505      <tr><td class="lineno" valign="top"></td><td class="left">   q=1.</td><td> </td><td class="right">   q=1.</td><td class="lineno" valign="top"></td></tr>
506      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
507      <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 21, line 32</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 21, line 22</em></th><td></td></tr>
508      <tr><td class="lineno" valign="top"></td><td class="left">      messages sent with other content-codings.  The server might also</td><td> </td><td class="right">      messages sent with other content-codings.  The server might also</td><td class="lineno" valign="top"></td></tr>
509      <tr><td class="lineno" valign="top"></td><td class="left">      make this decision based on information about the particular user-</td><td> </td><td class="right">      make this decision based on information about the particular user-</td><td class="lineno" valign="top"></td></tr>
510      <tr><td class="lineno" valign="top"></td><td class="left">      agent or client.</td><td> </td><td class="right">      agent or client.</td><td class="lineno" valign="top"></td></tr>
511      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
512      <tr><td class="lineno" valign="top"></td><td class="left">      Note: Most HTTP/1.0 applications do not recognize or obey qvalues</td><td> </td><td class="right">      Note: Most HTTP/1.0 applications do not recognize or obey qvalues</td><td class="lineno" valign="top"></td></tr>
513      <tr><td class="lineno" valign="top"></td><td class="left">      associated with content-codings.  This means that qvalues will not</td><td> </td><td class="right">      associated with content-codings.  This means that qvalues will not</td><td class="lineno" valign="top"></td></tr>
514      <tr><td class="lineno" valign="top"></td><td class="left">      work and are not permitted with x-gzip or x-compress.</td><td> </td><td class="right">      work and are not permitted with x-gzip or x-compress.</td><td class="lineno" valign="top"></td></tr>
515      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
516      <tr><td class="lineno" valign="top"></td><td class="left">6.4.  Accept-Language</td><td> </td><td class="right">6.4.  Accept-Language</td><td class="lineno" valign="top"></td></tr>
517      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
518      <tr><td><a name="diff0036" /></td></tr>
519      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "Accept-Language" <span class="delete">request-header</span> field can be used by user agents</td><td> </td><td class="rblock">   The "Accept-Language" <span class="insert">header</span> field can be used by user agents to</td><td class="lineno" valign="top"></td></tr>
520      <tr><td class="lineno" valign="top"></td><td class="lblock">   to indicate the set of natural languages that are preferred in the</td><td> </td><td class="rblock">   indicate the set of natural languages that are preferred in the</td><td class="lineno" valign="top"></td></tr>
521      <tr><td class="lineno" valign="top"></td><td class="left">   response.  Language tags are defined in Section 2.4.</td><td> </td><td class="right">   response.  Language tags are defined in Section 2.4.</td><td class="lineno" valign="top"></td></tr>
522      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
523      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Language   = "Accept-Language" ":" OWS</td><td> </td><td class="right">     Accept-Language   = "Accept-Language" ":" OWS</td><td class="lineno" valign="top"></td></tr>
524      <tr><td class="lineno" valign="top"></td><td class="left">                       Accept-Language-v</td><td> </td><td class="right">                       Accept-Language-v</td><td class="lineno" valign="top"></td></tr>
525      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Language-v =</td><td> </td><td class="right">     Accept-Language-v =</td><td class="lineno" valign="top"></td></tr>
526      <tr><td class="lineno" valign="top"></td><td class="left">                       1#( language-range [ OWS ";" OWS "q=" qvalue ] )</td><td> </td><td class="right">                       1#( language-range [ OWS ";" OWS "q=" qvalue ] )</td><td class="lineno" valign="top"></td></tr>
527      <tr><td class="lineno" valign="top"></td><td class="left">     language-range    =</td><td> </td><td class="right">     language-range    =</td><td class="lineno" valign="top"></td></tr>
528      <tr><td class="lineno" valign="top"></td><td class="left">               &lt;language-range, defined in [RFC4647], Section 2.1&gt;</td><td> </td><td class="right">               &lt;language-range, defined in [RFC4647], Section 2.1&gt;</td><td class="lineno" valign="top"></td></tr>
529      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
530      <tr><td class="lineno" valign="top"></td><td class="left">   Each language-range can be given an associated quality value which</td><td> </td><td class="right">   Each language-range can be given an associated quality value which</td><td class="lineno" valign="top"></td></tr>
531      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
532      <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 22, line 50</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 22, line 41</em></th><td></td></tr>
533      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
534      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Encoding   = "Content-Encoding" ":" OWS Content-Encoding-v</td><td> </td><td class="right">     Content-Encoding   = "Content-Encoding" ":" OWS Content-Encoding-v</td><td class="lineno" valign="top"></td></tr>
535      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Encoding-v = 1#content-coding</td><td> </td><td class="right">     Content-Encoding-v = 1#content-coding</td><td class="lineno" valign="top"></td></tr>
536      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
537      <tr><td class="lineno" valign="top"></td><td class="left">   Content codings are defined in Section 2.2.  An example of its use is</td><td> </td><td class="right">   Content codings are defined in Section 2.2.  An example of its use is</td><td class="lineno" valign="top"></td></tr>
538      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
539      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Encoding: gzip</td><td> </td><td class="right">     Content-Encoding: gzip</td><td class="lineno" valign="top"></td></tr>
540      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
541      <tr><td class="lineno" valign="top"></td><td class="left">   The content-coding is a characteristic of the representation.</td><td> </td><td class="right">   The content-coding is a characteristic of the representation.</td><td class="lineno" valign="top"></td></tr>
542      <tr><td class="lineno" valign="top"></td><td class="left">   Typically, the representation body is stored with this encoding and</td><td> </td><td class="right">   Typically, the representation body is stored with this encoding and</td><td class="lineno" valign="top"></td></tr>
543      <tr><td><a name="diff0037" /></td></tr>
544      <tr><td class="lineno" valign="top"></td><td class="lblock">   is only decoded before rendering or analogous usage.  However, a <span class="delete">non-</span></td><td> </td><td class="rblock">   is only decoded before rendering or analogous usage.  However, a</td><td class="lineno" valign="top"></td></tr>
545      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   transparent</span> proxy MAY modify the content-coding if the new coding is</td><td> </td><td class="rblock">   <span class="insert">transforming</span> proxy MAY modify the content-coding if the new coding is</td><td class="lineno" valign="top"></td></tr>
546      <tr><td class="lineno" valign="top"></td><td class="left">   known to be acceptable to the recipient, unless the "no-transform"</td><td> </td><td class="right">   known to be acceptable to the recipient, unless the "no-transform"</td><td class="lineno" valign="top"></td></tr>
547      <tr><td class="lineno" valign="top"></td><td class="left">   cache-control directive is present in the message.</td><td> </td><td class="right">   cache-control directive is present in the message.</td><td class="lineno" valign="top"></td></tr>
548      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
549      <tr><td class="lineno" valign="top"></td><td class="left">   If the content-coding of a representation is not "identity", then the</td><td> </td><td class="right">   If the content-coding of a representation is not "identity", then the</td><td class="lineno" valign="top"></td></tr>
550      <tr><td class="lineno" valign="top"></td><td class="left">   representation metadata MUST include a Content-Encoding header field</td><td> </td><td class="right">   representation metadata MUST include a Content-Encoding header field</td><td class="lineno" valign="top"></td></tr>
551      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 6.5) that lists the non-identity content-coding(s) used.</td><td> </td><td class="right">   (Section 6.5) that lists the non-identity content-coding(s) used.</td><td class="lineno" valign="top"></td></tr>
552      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
553      <tr><td class="lineno" valign="top"></td><td class="left">   If the content-coding of a representation in a request message is not</td><td> </td><td class="right">   If the content-coding of a representation in a request message is not</td><td class="lineno" valign="top"></td></tr>
554      <tr><td class="lineno" valign="top"></td><td class="left">   acceptable to the origin server, the server SHOULD respond with a</td><td> </td><td class="right">   acceptable to the origin server, the server SHOULD respond with a</td><td class="lineno" valign="top"></td></tr>
555      <tr><td class="lineno" valign="top"></td><td class="left">   status code of 415 (Unsupported Media Type).</td><td> </td><td class="right">   status code of 415 (Unsupported Media Type).</td><td class="lineno" valign="top"></td></tr>
556      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
557      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 24, line 37</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 24, line 30</em></th><td></td></tr>
558      <tr><td class="lineno" valign="top"></td><td class="left">   It has the same syntax and semantics as the header field of the same</td><td> </td><td class="right">   It has the same syntax and semantics as the header field of the same</td><td class="lineno" valign="top"></td></tr>
559      <tr><td class="lineno" valign="top"></td><td class="left">   name defined for MIME body parts in Section 4 of [RFC2557].  However,</td><td> </td><td class="right">   name defined for MIME body parts in Section 4 of [RFC2557].  However,</td><td class="lineno" valign="top"></td></tr>
560      <tr><td class="lineno" valign="top"></td><td class="left">   its appearance in an HTTP message has some special implications for</td><td> </td><td class="right">   its appearance in an HTTP message has some special implications for</td><td class="lineno" valign="top"></td></tr>
561      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP recipients.</td><td> </td><td class="right">   HTTP recipients.</td><td class="lineno" valign="top"></td></tr>
562      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
563      <tr><td class="lineno" valign="top"></td><td class="left">   If Content-Location is included in a response message and its value</td><td> </td><td class="right">   If Content-Location is included in a response message and its value</td><td class="lineno" valign="top"></td></tr>
564      <tr><td class="lineno" valign="top"></td><td class="left">   is the same as the effective request URI, then the response payload</td><td> </td><td class="right">   is the same as the effective request URI, then the response payload</td><td class="lineno" valign="top"></td></tr>
565      <tr><td class="lineno" valign="top"></td><td class="left">   SHOULD be considered the current representation of that resource.</td><td> </td><td class="right">   SHOULD be considered the current representation of that resource.</td><td class="lineno" valign="top"></td></tr>
566      <tr><td class="lineno" valign="top"></td><td class="left">   For a GET or HEAD request, this is the same as the default semantics</td><td> </td><td class="right">   For a GET or HEAD request, this is the same as the default semantics</td><td class="lineno" valign="top"></td></tr>
567      <tr><td class="lineno" valign="top"></td><td class="left">   when no Content-Location is provided by the server.  For a state-</td><td> </td><td class="right">   when no Content-Location is provided by the server.  For a state-</td><td class="lineno" valign="top"></td></tr>
568      <tr><td><a name="diff0038" /></td></tr>
569      <tr><td class="lineno" valign="top"></td><td class="lblock">   changing <span class="delete">method</span> like PUT or POST, it implies that the server's</td><td> </td><td class="rblock">   changing <span class="insert">request</span> like PUT or POST, it implies that the server's</td><td class="lineno" valign="top"></td></tr>
570      <tr><td class="lineno" valign="top"></td><td class="left">   response contains the new representation of that resource, thereby</td><td> </td><td class="right">   response contains the new representation of that resource, thereby</td><td class="lineno" valign="top"></td></tr>
571      <tr><td class="lineno" valign="top"></td><td class="left">   distinguishing it from representations that might only report about</td><td> </td><td class="right">   distinguishing it from representations that might only report about</td><td class="lineno" valign="top"></td></tr>
572      <tr><td class="lineno" valign="top"></td><td class="left">   the action (e.g., "It worked!").  This allows authoring applications</td><td> </td><td class="right">   the action (e.g., "It worked!").  This allows authoring applications</td><td class="lineno" valign="top"></td></tr>
573      <tr><td class="lineno" valign="top"></td><td class="left">   to update their local copies without the need for a subsequent GET</td><td> </td><td class="right">   to update their local copies without the need for a subsequent GET</td><td class="lineno" valign="top"></td></tr>
574      <tr><td class="lineno" valign="top"></td><td class="left">   request.</td><td> </td><td class="right">   request.</td><td class="lineno" valign="top"></td></tr>
575      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
576      <tr><td class="lineno" valign="top"></td><td class="left">   If Content-Location is included in a response message and its value</td><td> </td><td class="right">   If Content-Location is included in a response message and its value</td><td class="lineno" valign="top"></td></tr>
577      <tr><td class="lineno" valign="top"></td><td class="left">   differs from the effective request URI, then the origin server is</td><td> </td><td class="right">   differs from the effective request URI, then the origin server is</td><td class="lineno" valign="top"></td></tr>
578      <tr><td class="lineno" valign="top"></td><td class="left">   informing recipients that this representation has its own, presumably</td><td> </td><td class="right">   informing recipients that this representation has its own, presumably</td><td class="lineno" valign="top"></td></tr>
579      <tr><td class="lineno" valign="top"></td><td class="left">   more specific, identifier.  For a GET or HEAD request, this is an</td><td> </td><td class="right">   more specific, identifier.  For a GET or HEAD request, this is an</td><td class="lineno" valign="top"></td></tr>
580      <tr><td class="lineno" valign="top"></td><td class="left">   indication that the effective request URI identifies a resource that</td><td> </td><td class="right">   indication that the effective request URI identifies a resource that</td><td class="lineno" valign="top"></td></tr>
581      <tr><td class="lineno" valign="top"></td><td class="left">   is subject to content negotiation and the representation selected for</td><td> </td><td class="right">   is subject to content negotiation and the representation selected for</td><td class="lineno" valign="top"></td></tr>
582      <tr><td class="lineno" valign="top"></td><td class="left">   this response can also be found at the identified URI.  For other</td><td> </td><td class="right">   this response can also be found at the identified URI.  For other</td><td class="lineno" valign="top"></td></tr>
583      <tr><td class="lineno" valign="top"></td><td class="left">   methods, such a Content-Location indicates that this representation</td><td> </td><td class="right">   methods, such a Content-Location indicates that this representation</td><td class="lineno" valign="top"></td></tr>
584      <tr><td class="lineno" valign="top"></td><td class="left">   contains a report on the action's status and the same report is</td><td> </td><td class="right">   contains a report on the action's status and the same report is</td><td class="lineno" valign="top"></td></tr>
585      <tr><td class="lineno" valign="top"></td><td class="left">   available (for future access with GET) at the given URI.  For</td><td> </td><td class="right">   available (for future access with GET) at the given URI.  For</td><td class="lineno" valign="top"></td></tr>
586      <tr><td><a name="diff0039" /></td></tr>
587      <tr><td class="lineno" valign="top"></td><td class="lblock">   example, a purchase transaction made via <span class="delete">the</span> POST <span class="delete">method</span> might</td><td> </td><td class="rblock">   example, a purchase transaction made via <span class="insert">a</span> POST <span class="insert">request</span> might include</td><td class="lineno" valign="top"></td></tr>
588      <tr><td class="lineno" valign="top"></td><td class="lblock">   include a receipt document as the payload of the 200 response; the</td><td> </td><td class="rblock">   a receipt document as the payload of the 200 response; the <span class="insert">Content-</span></td><td class="lineno" valign="top"></td></tr>
589      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Content-Location</span> value provides an identifier for retrieving a copy</td><td> </td><td class="rblock"><span class="insert">   Location</span> value provides an identifier for retrieving a copy of that</td><td class="lineno" valign="top"></td></tr>
590      <tr><td class="lineno" valign="top"></td><td class="lblock">   of that same receipt in the future.</td><td> </td><td class="rblock">   same receipt in the future.</td><td class="lineno" valign="top"></td></tr>
591      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
592      <tr><td class="lineno" valign="top"></td><td class="left">   If Content-Location is included in a request message, then it MAY be</td><td> </td><td class="right">   If Content-Location is included in a request message, then it MAY be</td><td class="lineno" valign="top"></td></tr>
593      <tr><td class="lineno" valign="top"></td><td class="left">   interpreted by the origin server as an indication of where the user</td><td> </td><td class="right">   interpreted by the origin server as an indication of where the user</td><td class="lineno" valign="top"></td></tr>
594      <tr><td class="lineno" valign="top"></td><td class="left">   agent originally obtained the content of the enclosed representation</td><td> </td><td class="right">   agent originally obtained the content of the enclosed representation</td><td class="lineno" valign="top"></td></tr>
595      <tr><td class="lineno" valign="top"></td><td class="left">   (prior to any subsequent modification of the content by that user</td><td> </td><td class="right">   (prior to any subsequent modification of the content by that user</td><td class="lineno" valign="top"></td></tr>
596      <tr><td class="lineno" valign="top"></td><td class="left">   agent).  In other words, the user agent is providing the same</td><td> </td><td class="right">   agent).  In other words, the user agent is providing the same</td><td class="lineno" valign="top"></td></tr>
597      <tr><td class="lineno" valign="top"></td><td class="left">   representation metadata that it received with the original</td><td> </td><td class="right">   representation metadata that it received with the original</td><td class="lineno" valign="top"></td></tr>
598      <tr><td class="lineno" valign="top"></td><td class="left">   representation.  However, such interpretation MUST NOT be used to</td><td> </td><td class="right">   representation.  However, such interpretation MUST NOT be used to</td><td class="lineno" valign="top"></td></tr>
599      <tr><td class="lineno" valign="top"></td><td class="left">   alter the semantics of the method requested by the client.  For</td><td> </td><td class="right">   alter the semantics of the method requested by the client.  For</td><td class="lineno" valign="top"></td></tr>
600      <tr><td class="lineno" valign="top"></td><td class="left">   example, if a client makes a PUT request on a negotiated resource and</td><td> </td><td class="right">   example, if a client makes a PUT request on a negotiated resource and</td><td class="lineno" valign="top"></td></tr>
601      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
602      <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 26, line 8</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 25, line 48</em></th><td></td></tr>
603      <tr><td class="lineno" valign="top"></td><td class="left">   transfer-coding is decoded).  Note that a MIC is good for detecting</td><td> </td><td class="right">   transfer-coding is decoded).  Note that a MIC is good for detecting</td><td class="lineno" valign="top"></td></tr>
604      <tr><td class="lineno" valign="top"></td><td class="left">   accidental modification of the payload body in transit, but is not</td><td> </td><td class="right">   accidental modification of the payload body in transit, but is not</td><td class="lineno" valign="top"></td></tr>
605      <tr><td class="lineno" valign="top"></td><td class="left">   proof against malicious attacks.</td><td> </td><td class="right">   proof against malicious attacks.</td><td class="lineno" valign="top"></td></tr>
606      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
607      <tr><td class="lineno" valign="top"></td><td class="left">     Content-MD5   = "Content-MD5" ":" OWS Content-MD5-v</td><td> </td><td class="right">     Content-MD5   = "Content-MD5" ":" OWS Content-MD5-v</td><td class="lineno" valign="top"></td></tr>
608      <tr><td class="lineno" valign="top"></td><td class="left">     Content-MD5-v = &lt;base64 of 128 bit MD5 digest as per [RFC1864]&gt;</td><td> </td><td class="right">     Content-MD5-v = &lt;base64 of 128 bit MD5 digest as per [RFC1864]&gt;</td><td class="lineno" valign="top"></td></tr>
609      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
610      <tr><td class="lineno" valign="top"></td><td class="left">   The Content-MD5 header field MAY be generated by an origin server or</td><td> </td><td class="right">   The Content-MD5 header field MAY be generated by an origin server or</td><td class="lineno" valign="top"></td></tr>
611      <tr><td class="lineno" valign="top"></td><td class="left">   client to function as an integrity check of the payload body.  Only</td><td> </td><td class="right">   client to function as an integrity check of the payload body.  Only</td><td class="lineno" valign="top"></td></tr>
612      <tr><td class="lineno" valign="top"></td><td class="left">   origin servers or user agents MAY generate the Content-MD5 header</td><td> </td><td class="right">   origin servers or user agents MAY generate the Content-MD5 header</td><td class="lineno" valign="top"></td></tr>
613      <tr><td><a name="diff0040" /></td></tr>
614      <tr><td class="lineno" valign="top"></td><td class="lblock">   field; proxies <span class="delete">and gateways</span> MUST NOT generate it, as this would</td><td> </td><td class="rblock">   field; proxies MUST NOT generate it, as this would defeat its value</td><td class="lineno" valign="top"></td></tr>
615      <tr><td class="lineno" valign="top"></td><td class="lblock">   defeat its value as an end-to-end integrity check.  Any recipient MAY</td><td> </td><td class="rblock">   as an end-to-end integrity check.  Any recipient MAY check that the</td><td class="lineno" valign="top"></td></tr>
616      <tr><td class="lineno" valign="top"></td><td class="lblock">   check that the digest value in this header field matches a</td><td> </td><td class="rblock">   digest value in this header field matches a corresponding digest</td><td class="lineno" valign="top"></td></tr>
617      <tr><td class="lineno" valign="top"></td><td class="lblock">   corresponding digest calculated on payload body as received.</td><td> </td><td class="rblock">   calculated on payload body as received.</td><td class="lineno" valign="top"></td></tr>
618      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
619      <tr><td class="lineno" valign="top"></td><td class="left">   The MD5 digest is computed based on the content of the payload body,</td><td> </td><td class="right">   The MD5 digest is computed based on the content of the payload body,</td><td class="lineno" valign="top"></td></tr>
620      <tr><td class="lineno" valign="top"></td><td class="left">   including any content-coding, but not including any transfer-coding</td><td> </td><td class="right">   including any content-coding, but not including any transfer-coding</td><td class="lineno" valign="top"></td></tr>
621      <tr><td class="lineno" valign="top"></td><td class="left">   applied to the message-body because such transfer-codings might be</td><td> </td><td class="right">   applied to the message-body because such transfer-codings might be</td><td class="lineno" valign="top"></td></tr>
622      <tr><td class="lineno" valign="top"></td><td class="left">   applied or removed anywhere along the request/response chain.  If the</td><td> </td><td class="right">   applied or removed anywhere along the request/response chain.  If the</td><td class="lineno" valign="top"></td></tr>
623      <tr><td class="lineno" valign="top"></td><td class="left">   message is received with a transfer-coding, that encoding MUST be</td><td> </td><td class="right">   message is received with a transfer-coding, that encoding MUST be</td><td class="lineno" valign="top"></td></tr>
624      <tr><td class="lineno" valign="top"></td><td class="left">   decoded prior to checking the Content-MD5 value against the received</td><td> </td><td class="right">   decoded prior to checking the Content-MD5 value against the received</td><td class="lineno" valign="top"></td></tr>
625      <tr><td class="lineno" valign="top"></td><td class="left">   payload.</td><td> </td><td class="right">   payload.</td><td class="lineno" valign="top"></td></tr>
626      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
627      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP extends RFC 1864 to permit the digest to be computed for MIME</td><td> </td><td class="right">   HTTP extends RFC 1864 to permit the digest to be computed for MIME</td><td class="lineno" valign="top"></td></tr>
628      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
629      <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 28, line 32</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 28, line 30</em></th><td></td></tr>
630      <tr><td class="lineno" valign="top"></td><td class="left">8.  Security Considerations</td><td> </td><td class="right">8.  Security Considerations</td><td class="lineno" valign="top"></td></tr>
631      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
632      <tr><td class="lineno" valign="top"></td><td class="left">   This section is meant to inform application developers, information</td><td> </td><td class="right">   This section is meant to inform application developers, information</td><td class="lineno" valign="top"></td></tr>
633      <tr><td class="lineno" valign="top"></td><td class="left">   providers, and users of the security limitations in HTTP/1.1 as</td><td> </td><td class="right">   providers, and users of the security limitations in HTTP/1.1 as</td><td class="lineno" valign="top"></td></tr>
634      <tr><td class="lineno" valign="top"></td><td class="left">   described by this document.  The discussion does not include</td><td> </td><td class="right">   described by this document.  The discussion does not include</td><td class="lineno" valign="top"></td></tr>
635      <tr><td class="lineno" valign="top"></td><td class="left">   definitive solutions to the problems revealed, though it does make</td><td> </td><td class="right">   definitive solutions to the problems revealed, though it does make</td><td class="lineno" valign="top"></td></tr>
636      <tr><td class="lineno" valign="top"></td><td class="left">   some suggestions for reducing security risks.</td><td> </td><td class="right">   some suggestions for reducing security risks.</td><td class="lineno" valign="top"></td></tr>
637      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
638      <tr><td class="lineno" valign="top"></td><td class="left">8.1.  Privacy Issues Connected to Accept Header Fields</td><td> </td><td class="right">8.1.  Privacy Issues Connected to Accept Header Fields</td><td class="lineno" valign="top"></td></tr>
639      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
640      <tr><td><a name="diff0041" /></td></tr>
641      <tr><td class="lineno" valign="top"></td><td class="lblock">   Accept <span class="delete">request-headers</span> fields can reveal information about the user</td><td> </td><td class="rblock">   Accept <span class="insert">headers</span> fields can reveal information about the user to all</td><td class="lineno" valign="top"></td></tr>
642      <tr><td class="lineno" valign="top"></td><td class="lblock">   to all servers which are accessed.  The Accept-Language header field</td><td> </td><td class="rblock">   servers which are accessed.  The Accept-Language header field in</td><td class="lineno" valign="top"></td></tr>
643      <tr><td class="lineno" valign="top"></td><td class="lblock">   in particular can reveal information the user would consider to be of</td><td> </td><td class="rblock">   particular can reveal information the user would consider to be of a</td><td class="lineno" valign="top"></td></tr>
644      <tr><td class="lineno" valign="top"></td><td class="lblock">   a private nature, because the understanding of particular languages</td><td> </td><td class="rblock">   private nature, because the understanding of particular languages is</td><td class="lineno" valign="top"></td></tr>
645      <tr><td class="lineno" valign="top"></td><td class="lblock">   is often strongly correlated to the membership of a particular ethnic</td><td> </td><td class="rblock">   often strongly correlated to the membership of a particular ethnic</td><td class="lineno" valign="top"></td></tr>
646      <tr><td class="lineno" valign="top"></td><td class="left">   group.  User agents which offer the option to configure the contents</td><td> </td><td class="right">   group.  User agents which offer the option to configure the contents</td><td class="lineno" valign="top"></td></tr>
647      <tr><td class="lineno" valign="top"></td><td class="left">   of an Accept-Language header field to be sent in every request are</td><td> </td><td class="right">   of an Accept-Language header field to be sent in every request are</td><td class="lineno" valign="top"></td></tr>
648      <tr><td class="lineno" valign="top"></td><td class="left">   strongly encouraged to let the configuration process include a</td><td> </td><td class="right">   strongly encouraged to let the configuration process include a</td><td class="lineno" valign="top"></td></tr>
649      <tr><td class="lineno" valign="top"></td><td class="left">   message which makes the user aware of the loss of privacy involved.</td><td> </td><td class="right">   message which makes the user aware of the loss of privacy involved.</td><td class="lineno" valign="top"></td></tr>
650      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
651      <tr><td class="lineno" valign="top"></td><td class="left">   An approach that limits the loss of privacy would be for a user agent</td><td> </td><td class="right">   An approach that limits the loss of privacy would be for a user agent</td><td class="lineno" valign="top"></td></tr>
652      <tr><td class="lineno" valign="top"></td><td class="left">   to omit the sending of Accept-Language header fields by default, and</td><td> </td><td class="right">   to omit the sending of Accept-Language header fields by default, and</td><td class="lineno" valign="top"></td></tr>
653      <tr><td class="lineno" valign="top"></td><td class="left">   to ask the user whether or not to start sending Accept-Language</td><td> </td><td class="right">   to ask the user whether or not to start sending Accept-Language</td><td class="lineno" valign="top"></td></tr>
654      <tr><td class="lineno" valign="top"></td><td class="left">   header fields to a server if it detects, by looking for any Vary</td><td> </td><td class="right">   header fields to a server if it detects, by looking for any Vary</td><td class="lineno" valign="top"></td></tr>
655      <tr><td><a name="diff0042" /></td></tr>
656      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">response-header</span> fields generated by the server, that such sending</td><td> </td><td class="rblock">   <span class="insert">header</span> fields generated by the server, that such sending could</td><td class="lineno" valign="top"></td></tr>
657      <tr><td class="lineno" valign="top"></td><td class="lblock">   could improve the quality of service.</td><td> </td><td class="rblock">   improve the quality of service.</td><td class="lineno" valign="top"></td></tr>
658      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
659      <tr><td class="lineno" valign="top"></td><td class="left">   Elaborate user-customized accept header fields sent in every request,</td><td> </td><td class="right">   Elaborate user-customized accept header fields sent in every request,</td><td class="lineno" valign="top"></td></tr>
660      <tr><td class="lineno" valign="top"></td><td class="left">   in particular if these include quality values, can be used by servers</td><td> </td><td class="right">   in particular if these include quality values, can be used by servers</td><td class="lineno" valign="top"></td></tr>
661      <tr><td class="lineno" valign="top"></td><td class="left">   as relatively reliable and long-lived user identifiers.  Such user</td><td> </td><td class="right">   as relatively reliable and long-lived user identifiers.  Such user</td><td class="lineno" valign="top"></td></tr>
662      <tr><td class="lineno" valign="top"></td><td class="left">   identifiers would allow content providers to do click-trail tracking,</td><td> </td><td class="right">   identifiers would allow content providers to do click-trail tracking,</td><td class="lineno" valign="top"></td></tr>
663      <tr><td class="lineno" valign="top"></td><td class="left">   and would allow collaborating content providers to match cross-server</td><td> </td><td class="right">   and would allow collaborating content providers to match cross-server</td><td class="lineno" valign="top"></td></tr>
664      <tr><td class="lineno" valign="top"></td><td class="left">   click-trails or form submissions of individual users.  Note that for</td><td> </td><td class="right">   click-trails or form submissions of individual users.  Note that for</td><td class="lineno" valign="top"></td></tr>
665      <tr><td class="lineno" valign="top"></td><td class="left">   many users not behind a proxy, the network address of the host</td><td> </td><td class="right">   many users not behind a proxy, the network address of the host</td><td class="lineno" valign="top"></td></tr>
666      <tr><td class="lineno" valign="top"></td><td class="left">   running the user agent will also serve as a long-lived user</td><td> </td><td class="right">   running the user agent will also serve as a long-lived user</td><td class="lineno" valign="top"></td></tr>
667      <tr><td class="lineno" valign="top"></td><td class="left">   identifier.  In environments where proxies are used to enhance</td><td> </td><td class="right">   identifier.  In environments where proxies are used to enhance</td><td class="lineno" valign="top"></td></tr>
668      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
669      <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 29, line 32</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 29, line 29</em></th><td></td></tr>
670      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
671      <tr><td class="lineno" valign="top"></td><td class="left">   [ISO-8859-1]  International Organization for Standardization,</td><td> </td><td class="right">   [ISO-8859-1]  International Organization for Standardization,</td><td class="lineno" valign="top"></td></tr>
672      <tr><td class="lineno" valign="top"></td><td class="left">                 "Information technology -- 8-bit single-byte coded</td><td> </td><td class="right">                 "Information technology -- 8-bit single-byte coded</td><td class="lineno" valign="top"></td></tr>
673      <tr><td class="lineno" valign="top"></td><td class="left">                 graphic character sets -- Part 1: Latin alphabet No.</td><td> </td><td class="right">                 graphic character sets -- Part 1: Latin alphabet No.</td><td class="lineno" valign="top"></td></tr>
674      <tr><td class="lineno" valign="top"></td><td class="left">                 1", ISO/IEC 8859-1:1998, 1998.</td><td> </td><td class="right">                 1", ISO/IEC 8859-1:1998, 1998.</td><td class="lineno" valign="top"></td></tr>
675      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
676      <tr><td class="lineno" valign="top"></td><td class="left">   [Part1]       Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,</td><td> </td><td class="right">   [Part1]       Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,</td><td class="lineno" valign="top"></td></tr>
677      <tr><td class="lineno" valign="top"></td><td class="left">                 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,</td><td> </td><td class="right">                 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,</td><td class="lineno" valign="top"></td></tr>
678      <tr><td class="lineno" valign="top"></td><td class="left">                 Ed., and J. Reschke, Ed., "HTTP/1.1, part 1: URIs,</td><td> </td><td class="right">                 Ed., and J. Reschke, Ed., "HTTP/1.1, part 1: URIs,</td><td class="lineno" valign="top"></td></tr>
679      <tr><td class="lineno" valign="top"></td><td class="left">                 Connections, and Message Parsing",</td><td> </td><td class="right">                 Connections, and Message Parsing",</td><td class="lineno" valign="top"></td></tr>
680      <tr><td><a name="diff0043" /></td></tr>
681      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p1-messaging-12</span> (work in progress),</td><td> </td><td class="rblock">                 <span class="insert">draft-ietf-httpbis-p1-messaging-13</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
682      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">October 2010.</span></td><td> </td><td class="rblock">                 <span class="insert">March 2011.</span></td><td class="lineno" valign="top"></td></tr>
683      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
684      <tr><td class="lineno" valign="top"></td><td class="left">   [Part2]       Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,</td><td> </td><td class="right">   [Part2]       Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,</td><td class="lineno" valign="top"></td></tr>
685      <tr><td class="lineno" valign="top"></td><td class="left">                 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,</td><td> </td><td class="right">                 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,</td><td class="lineno" valign="top"></td></tr>
686      <tr><td class="lineno" valign="top"></td><td class="left">                 Ed., and J. Reschke, Ed., "HTTP/1.1, part 2: Message</td><td> </td><td class="right">                 Ed., and J. Reschke, Ed., "HTTP/1.1, part 2: Message</td><td class="lineno" valign="top"></td></tr>
687      <tr><td><a name="diff0044" /></td></tr>
688      <tr><td class="lineno" valign="top"></td><td class="lblock">                 Semantics", <span class="delete">draft-ietf-httpbis-p2-semantics-12</span> (work in</td><td> </td><td class="rblock">                 Semantics", <span class="insert">draft-ietf-httpbis-p2-semantics-13</span> (work in</td><td class="lineno" valign="top"></td></tr>
689      <tr><td class="lineno" valign="top"></td><td class="lblock">                 progress), <span class="delete">October 2010.</span></td><td> </td><td class="rblock">                 progress), <span class="insert">March 2011.</span></td><td class="lineno" valign="top"></td></tr>
690      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
691      <tr><td class="lineno" valign="top"></td><td class="left">   [Part4]       Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,</td><td> </td><td class="right">   [Part4]       Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,</td><td class="lineno" valign="top"></td></tr>
692      <tr><td class="lineno" valign="top"></td><td class="left">                 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,</td><td> </td><td class="right">                 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,</td><td class="lineno" valign="top"></td></tr>
693      <tr><td class="lineno" valign="top"></td><td class="left">                 Ed., and J. Reschke, Ed., "HTTP/1.1, part 4:</td><td> </td><td class="right">                 Ed., and J. Reschke, Ed., "HTTP/1.1, part 4:</td><td class="lineno" valign="top"></td></tr>
694      <tr><td class="lineno" valign="top"></td><td class="left">                 Conditional Requests",</td><td> </td><td class="right">                 Conditional Requests",</td><td class="lineno" valign="top"></td></tr>
695      <tr><td><a name="diff0045" /></td></tr>
696      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p4-conditional-12</span> (work in</td><td> </td><td class="rblock">                 <span class="insert">draft-ietf-httpbis-p4-conditional-13</span> (work in</td><td class="lineno" valign="top"></td></tr>
697      <tr><td class="lineno" valign="top"></td><td class="lblock">                 progress), <span class="delete">October 2010.</span></td><td> </td><td class="rblock">                 progress), <span class="insert">March 2011.</span></td><td class="lineno" valign="top"></td></tr>
698      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
699      <tr><td class="lineno" valign="top"></td><td class="left">   [Part5]       Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,</td><td> </td><td class="right">   [Part5]       Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,</td><td class="lineno" valign="top"></td></tr>
700      <tr><td class="lineno" valign="top"></td><td class="left">                 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,</td><td> </td><td class="right">                 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,</td><td class="lineno" valign="top"></td></tr>
701      <tr><td class="lineno" valign="top"></td><td class="left">                 Ed., and J. Reschke, Ed., "HTTP/1.1, part 5: Range</td><td> </td><td class="right">                 Ed., and J. Reschke, Ed., "HTTP/1.1, part 5: Range</td><td class="lineno" valign="top"></td></tr>
702      <tr><td class="lineno" valign="top"></td><td class="left">                 Requests and Partial Responses",</td><td> </td><td class="right">                 Requests and Partial Responses",</td><td class="lineno" valign="top"></td></tr>
703      <tr><td><a name="diff0046" /></td></tr>
704      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p5-range-12</span> (work in progress),</td><td> </td><td class="rblock">                 <span class="insert">draft-ietf-httpbis-p5-range-13</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
705      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">October 2010.</span></td><td> </td><td class="rblock">                 <span class="insert">March 2011.</span></td><td class="lineno" valign="top"></td></tr>
706      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
707      <tr><td class="lineno" valign="top"></td><td class="left">   [Part6]       Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,</td><td> </td><td class="right">   [Part6]       Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,</td><td class="lineno" valign="top"></td></tr>
708      <tr><td class="lineno" valign="top"></td><td class="left">                 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,</td><td> </td><td class="right">                 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,</td><td class="lineno" valign="top"></td></tr>
709      <tr><td class="lineno" valign="top"></td><td class="left">                 Ed., Nottingham, M., Ed., and J. Reschke, Ed.,</td><td> </td><td class="right">                 Ed., Nottingham, M., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr>
710      <tr><td class="lineno" valign="top"></td><td class="left">                 "HTTP/1.1, part 6: Caching",</td><td> </td><td class="right">                 "HTTP/1.1, part 6: Caching",</td><td class="lineno" valign="top"></td></tr>
711      <tr><td><a name="diff0047" /></td></tr>
712      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p6-cache-12</span> (work in progress),</td><td> </td><td class="rblock">                 <span class="insert">draft-ietf-httpbis-p6-cache-13</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
713      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">October 2010.</span></td><td> </td><td class="rblock">                 <span class="insert">March 2011.</span></td><td class="lineno" valign="top"></td></tr>
714      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
715      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC1864]     Myers, J. and M. Rose, "The Content-MD5 Header Field",</td><td> </td><td class="right">   [RFC1864]     Myers, J. and M. Rose, "The Content-MD5 Header Field",</td><td class="lineno" valign="top"></td></tr>
716      <tr><td class="lineno" valign="top"></td><td class="left">                 RFC 1864, October 1995.</td><td> </td><td class="right">                 RFC 1864, October 1995.</td><td class="lineno" valign="top"></td></tr>
717      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
718      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC1950]     Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data</td><td> </td><td class="right">   [RFC1950]     Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data</td><td class="lineno" valign="top"></td></tr>
719      <tr><td class="lineno" valign="top"></td><td class="left">                 Format Specification version 3.3", RFC 1950, May 1996.</td><td> </td><td class="right">                 Format Specification version 3.3", RFC 1950, May 1996.</td><td class="lineno" valign="top"></td></tr>
720      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
721      <tr><td class="lineno" valign="top"></td><td class="left">                 RFC 1950 is an Informational RFC, thus it might be less</td><td> </td><td class="right">                 RFC 1950 is an Informational RFC, thus it might be less</td><td class="lineno" valign="top"></td></tr>
722      <tr><td class="lineno" valign="top"></td><td class="left">                 stable than this specification.  On the other hand,</td><td> </td><td class="right">                 stable than this specification.  On the other hand,</td><td class="lineno" valign="top"></td></tr>
723      <tr><td class="lineno" valign="top"></td><td class="left">                 this downward reference was present since the</td><td> </td><td class="right">                 this downward reference was present since the</td><td class="lineno" valign="top"></td></tr>
724      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
725      <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 33, line 8</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 32, line 50</em></th><td></td></tr>
726      <tr><td class="lineno" valign="top"></td><td class="left">   This appendix describes specific areas where HTTP differs from MIME.</td><td> </td><td class="right">   This appendix describes specific areas where HTTP differs from MIME.</td><td class="lineno" valign="top"></td></tr>
727      <tr><td class="lineno" valign="top"></td><td class="left">   Proxies and gateways to strict MIME environments SHOULD be aware of</td><td> </td><td class="right">   Proxies and gateways to strict MIME environments SHOULD be aware of</td><td class="lineno" valign="top"></td></tr>
728      <tr><td class="lineno" valign="top"></td><td class="left">   these differences and provide the appropriate conversions where</td><td> </td><td class="right">   these differences and provide the appropriate conversions where</td><td class="lineno" valign="top"></td></tr>
729      <tr><td class="lineno" valign="top"></td><td class="left">   necessary.  Proxies and gateways from MIME environments to HTTP also</td><td> </td><td class="right">   necessary.  Proxies and gateways from MIME environments to HTTP also</td><td class="lineno" valign="top"></td></tr>
730      <tr><td class="lineno" valign="top"></td><td class="left">   need to be aware of the differences because some conversions might be</td><td> </td><td class="right">   need to be aware of the differences because some conversions might be</td><td class="lineno" valign="top"></td></tr>
731      <tr><td class="lineno" valign="top"></td><td class="left">   required.</td><td> </td><td class="right">   required.</td><td class="lineno" valign="top"></td></tr>
732      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
733      <tr><td class="lineno" valign="top"></td><td class="left">A.1.  MIME-Version</td><td> </td><td class="right">A.1.  MIME-Version</td><td class="lineno" valign="top"></td></tr>
734      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
735      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP is not a MIME-compliant protocol.  However, HTTP/1.1 messages</td><td> </td><td class="right">   HTTP is not a MIME-compliant protocol.  However, HTTP/1.1 messages</td><td class="lineno" valign="top"></td></tr>
736      <tr><td><a name="diff0048" /></td></tr>
737      <tr><td class="lineno" valign="top"></td><td class="lblock">   MAY include a single MIME-Version <span class="delete">general-header</span> field to indicate</td><td> </td><td class="rblock">   MAY include a single MIME-Version <span class="insert">header</span> field to indicate what</td><td class="lineno" valign="top"></td></tr>
738      <tr><td class="lineno" valign="top"></td><td class="lblock">   what version of the MIME protocol was used to construct the message.</td><