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

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

prepare publication of -12 drafts on 2010-10-25

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html; charset=iso-8859-1
File size: 202.4 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-11.txt - draft-ietf-httpbis-p3-payload-12.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-11.txt&nbsp;</th><th> </th><th>&nbsp;draft-ietf-httpbis-p3-payload-12.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 class="lineno" valign="top"></td><td class="left">Internet-Draft                                              Day Software</td><td> </td><td class="right">Internet-Draft                                              Day Software</td><td class="lineno" valign="top"></td></tr>
42      <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>
43      <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>
44      <tr><td><a name="diff0001" /></td></tr>
45      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: <span class="delete">February 5, 2011</span>                                       J. Mogul</td><td> </td><td class="rblock">Expires: <span class="insert">April 28, 2011  </span>                                       J. Mogul</td><td class="lineno" valign="top"></td></tr>
46      <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>
47      <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>
48      <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>
49      <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>
50      <tr><td class="lineno" valign="top"></td><td class="left">                                                           Adobe Systems</td><td> </td><td class="right">                                                           Adobe Systems</td><td class="lineno" valign="top"></td></tr>
51      <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>
52      <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>
53      <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>
54      <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>
55      <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>
56      <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>
57      <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>
58      <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>
59      <tr><td><a name="diff0002" /></td></tr>
60      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                        <span class="delete">  August 4</span>, 2010</td><td> </td><td class="rblock">                                                        <span class="insert">October 25</span>, 2010</td><td class="lineno" valign="top"></td></tr>
61      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
62      <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>
63      <tr><td><a name="diff0003" /></td></tr>
64      <tr><td class="lineno" valign="top"></td><td class="lblock">                    draft-ietf-httpbis-p3-payload-1<span class="delete">1</span></td><td> </td><td class="rblock">                    draft-ietf-httpbis-p3-payload-1<span class="insert">2</span></td><td class="lineno" valign="top"></td></tr>
65      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
66      <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>
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">   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>
69      <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>
70      <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>
71      <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>
72      <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>
73      <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>
74      <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>
75      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
76      <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>
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">   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>
79      <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>
80      <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>
81      <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>
82      <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>
83      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
84      <tr><td><a name="diff0004" /></td></tr>
85      <tr><td class="lineno" valign="top"></td><td class="lblock">   The changes in this draft are summarized in Appendix E.1<span class="delete">2</span>.</td><td> </td><td class="rblock">   The changes in this draft are summarized in Appendix E.1<span class="insert">3</span>.</td><td class="lineno" valign="top"></td></tr>
86      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
87      <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>
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">   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>
90      <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>
91      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
92      <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>
93      <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>
94      <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>
95      <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>
96      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
97      <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>
98      <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>
99      <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>
100      <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>
101      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
102      <tr><td><a name="diff0005" /></td></tr>
103      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">February 5</span>, 2011.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">April 28</span>, 2011.</td><td class="lineno" valign="top"></td></tr>
104      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
105      <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>
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 (c) 2010 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2010 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
108      <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>
109      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
110      <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>
111      <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>
112      <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>
113      <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>
114      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
115      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 3, line 37</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 3, line 37</em></th><td></td></tr>
116      <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>
117      <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>
118      <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>
119      <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>
120      <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>
121      <tr><td class="lineno" valign="top"></td><td class="left">     6.9.  Content-Type . . . . . . . . . . . . . . . . . . . . . . . 27</td><td> </td><td class="right">     6.9.  Content-Type . . . . . . . . . . . . . . . . . . . . . . . 27</td><td class="lineno" valign="top"></td></tr>
122      <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>
123      <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>
124      <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>
125      <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>
126      <tr><td><a name="diff0006" /></td></tr>
127      <tr><td class="lineno" valign="top"></td><td class="lblock">     8.1.  Privacy Issues Connected to Accept <span class="delete">Headers . . .</span> . . . . . 28</td><td> </td><td class="rblock">     8.1.  Privacy Issues Connected to Accept <span class="insert">Header Fields</span> . . . . . 28</td><td class="lineno" valign="top"></td></tr>
128      <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">8.2.  Content-Disposition Issues . . . . . . . . . . . . . . . . 29</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
129      <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>
130      <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>
131      <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>
132      <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>
133      <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>
134      <tr><td class="lineno" valign="top"></td><td class="left">     A.1.  MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 33</td><td> </td><td class="right">     A.1.  MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 33</td><td class="lineno" valign="top"></td></tr>
135      <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>
136      <tr><td><a name="diff0007" /></td></tr>
137      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 3<span class="delete">4</span></td><td> </td><td class="rblock">     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 3<span class="insert">3</span></td><td class="lineno" valign="top"></td></tr>
138      <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>
139      <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>
140      <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>
141      <tr><td><a name="diff0008" /></td></tr>
142      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.7.  MHTML and Line Length Limitations  . . . . . . . . . . . . 3<span class="delete">5</span></td><td> </td><td class="rblock">     A.7.  MHTML and Line Length Limitations  . . . . . . . . . . . . 3<span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
143      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix B.  Additional Features . . . . . . . . . . . . . . . . . 35</td><td> </td><td class="right">   Appendix B.  Additional Features . . . . . . . . . . . . . . . . . 35</td><td class="lineno" valign="top"></td></tr>
144      <tr><td><a name="diff0009" /></td></tr>
145      <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">B.1.  Content-Disposition  . . . . . . . . . . . . . . . . . . . 35</span></td><td> </td><td class="rblock">   Appendix C.  Changes from RFC 2616 . . . . . . . . . . . . . . . . <span class="insert">35</span></td><td class="lineno" valign="top"></td></tr>
146      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock">   Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . <span class="insert">35</span></td><td class="lineno" valign="top"></td></tr>
147      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix C.  Changes from RFC 2616 . . . . . . . . . . . . . . . . <span class="delete">36</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
148      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . <span class="delete">36</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
149      <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>
150      <tr><td><a name="diff0010" /></td></tr>
151      <tr><td class="lineno" valign="top"></td><td class="lblock">                publication)  . . . . . . . . . . . . . . . . . . . . <span class="delete">38</span></td><td> </td><td class="rblock">                publication)  . . . . . . . . . . . . . . . . . . . . <span class="insert">37</span></td><td class="lineno" valign="top"></td></tr>
152      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.1.  Since <span class="delete">RFC2616</span>  . . . . . . . . . . . . . . . . . . . . . . <span class="delete">38</span></td><td> </td><td class="rblock">     E.1.  Since <span class="insert">RFC 2616</span> . . . . . . . . . . . . . . . . . . . . . . <span class="insert">37</span></td><td class="lineno" valign="top"></td></tr>
153      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.2.  Since draft-ietf-httpbis-p3-payload-00 . . . . . . . . . . <span class="delete">38</span></td><td> </td><td class="rblock">     E.2.  Since draft-ietf-httpbis-p3-payload-00 . . . . . . . . . . <span class="insert">37</span></td><td class="lineno" valign="top"></td></tr>
154      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.3.  Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . <span class="delete">39</span></td><td> </td><td class="rblock">     E.3.  Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . <span class="insert">38</span></td><td class="lineno" valign="top"></td></tr>
155      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.4.  Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . <span class="delete">39</span></td><td> </td><td class="rblock">     E.4.  Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . <span class="insert">38</span></td><td class="lineno" valign="top"></td></tr>
156      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.5.  Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . <span class="delete">40</span></td><td> </td><td class="rblock">     E.5.  Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . <span class="insert">38</span></td><td class="lineno" valign="top"></td></tr>
157      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.6.  Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . <span class="delete">40</span></td><td> </td><td class="rblock">     E.6.  Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . <span class="insert">39</span></td><td class="lineno" valign="top"></td></tr>
158      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.7.  Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . <span class="delete">40</span></td><td> </td><td class="rblock">     E.7.  Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . <span class="insert">39</span></td><td class="lineno" valign="top"></td></tr>
159      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.8.  Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . <span class="delete">41</span></td><td> </td><td class="rblock">     E.8.  Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
160      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.9.  Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . <span class="delete">41</span></td><td> </td><td class="rblock">     E.9.  Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
161      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . <span class="delete">42</span></td><td> </td><td class="rblock">     E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
162      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . <span class="delete">42</span></td><td> </td><td class="rblock">     E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . <span class="insert">41</span></td><td class="lineno" valign="top"></td></tr>
163      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . 42</td><td> </td><td class="rblock">     E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . <span class="insert">41</span></td><td class="lineno" valign="top"></td></tr>
164      <tr><td class="lineno" valign="top"></td><td class="lblock">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">43</span></td><td> </td><td class="rblock"><span class="insert">     E.13. Since draft-ietf-httpbis-p3-payload-11 . . . . . . . . . .</span> 42</td><td class="lineno" valign="top"></td></tr>
165      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">42</span></td><td class="lineno" valign="top"></td></tr>
166      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
167      <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>
168      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
169      <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>
170      <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>
171      <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>
172      <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>
173      <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>
174      <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>
175      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
176      <tr><td class="lineno" valign="top"></td><td class="left">   This document is currently disorganized in order to minimize the</td><td> </td><td class="right">   This document is currently disorganized in order to minimize the</td><td class="lineno" valign="top"></td></tr>
177      <tr><td class="lineno" valign="top"></td><td class="left">   changes between drafts and enable reviewers to see the smaller errata</td><td> </td><td class="right">   changes between drafts and enable reviewers to see the smaller errata</td><td class="lineno" valign="top"></td></tr>
178      <tr><td><a name="diff0011" /></td></tr>
179      <tr><td class="lineno" valign="top"></td><td class="lblock">   changes.  <span class="delete">The next</span> draft will reorganize the sections to better</td><td> </td><td class="rblock">   changes.  <span class="insert">A future</span> draft will reorganize the sections to better</td><td class="lineno" valign="top"></td></tr>
180      <tr><td class="lineno" valign="top"></td><td class="left">   reflect the content.  In particular, the sections on entities will be</td><td> </td><td class="right">   reflect the content.  In particular, the sections on entities will be</td><td class="lineno" valign="top"></td></tr>
181      <tr><td class="lineno" valign="top"></td><td class="left">   renamed payload and moved to the first half of the document, while</td><td> </td><td class="right">   renamed payload and moved to the first half of the document, while</td><td class="lineno" valign="top"></td></tr>
182      <tr><td class="lineno" valign="top"></td><td class="left">   the sections on content negotiation and associated request header</td><td> </td><td class="right">   the sections on content negotiation and associated request header</td><td class="lineno" valign="top"></td></tr>
183      <tr><td class="lineno" valign="top"></td><td class="left">   fields will be moved to the second half.  The current mess reflects</td><td> </td><td class="right">   fields will be moved to the second half.  The current mess reflects</td><td class="lineno" valign="top"></td></tr>
184      <tr><td class="lineno" valign="top"></td><td class="left">   how widely dispersed these topics and associated requirements had</td><td> </td><td class="right">   how widely dispersed these topics and associated requirements had</td><td class="lineno" valign="top"></td></tr>
185      <tr><td class="lineno" valign="top"></td><td class="left">   become in [RFC2616].</td><td> </td><td class="right">   become in [RFC2616].</td><td class="lineno" valign="top"></td></tr>
186      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
187      <tr><td class="lineno" valign="top"></td><td class="left">1.1.  Terminology</td><td> </td><td class="right">1.1.  Terminology</td><td class="lineno" valign="top"></td></tr>
188      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
189      <tr><td class="lineno" valign="top"></td><td class="left">   This specification uses a number of terms to refer to the roles</td><td> </td><td class="right">   This specification uses a number of terms to refer to the roles</td><td class="lineno" valign="top"></td></tr>
190      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
191      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 6, line 23</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 6, line 23</em></th><td></td></tr>
192      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5234], Appendix B.1: ALPHA (letters), CR (carriage return), CRLF</td><td> </td><td class="right">   [RFC5234], Appendix B.1: ALPHA (letters), CR (carriage return), CRLF</td><td class="lineno" valign="top"></td></tr>
193      <tr><td class="lineno" valign="top"></td><td class="left">   (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote),</td><td> </td><td class="right">   (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote),</td><td class="lineno" valign="top"></td></tr>
194      <tr><td class="lineno" valign="top"></td><td class="left">   HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit</td><td> </td><td class="right">   HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit</td><td class="lineno" valign="top"></td></tr>
195      <tr><td class="lineno" valign="top"></td><td class="left">   sequence of data), SP (space), VCHAR (any visible USASCII character),</td><td> </td><td class="right">   sequence of data), SP (space), VCHAR (any visible USASCII character),</td><td class="lineno" valign="top"></td></tr>
196      <tr><td class="lineno" valign="top"></td><td class="left">   and WSP (whitespace).</td><td> </td><td class="right">   and WSP (whitespace).</td><td class="lineno" valign="top"></td></tr>
197      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
198      <tr><td class="lineno" valign="top"></td><td class="left">1.3.1.  Core Rules</td><td> </td><td class="right">1.3.1.  Core Rules</td><td class="lineno" valign="top"></td></tr>
199      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
200      <tr><td class="lineno" valign="top"></td><td class="left">   The core rules below are defined in Section 1.2.2 of [Part1]:</td><td> </td><td class="right">   The core rules below are defined in Section 1.2.2 of [Part1]:</td><td class="lineno" valign="top"></td></tr>
201      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
202      <tr><td><a name="diff0012" /></td></tr>
203      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     quoted-string  = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
204      <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>
205      <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>
206      <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>
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.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>
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">   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>
211      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
212      <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>
213      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Length = &lt;Content-Length, defined in [Part1], Section 9.2&gt;</td><td> </td><td class="right">     Content-Length = &lt;Content-Length, defined in [Part1], Section 9.2&gt;</td><td class="lineno" valign="top"></td></tr>
214      <tr><td><a name="diff0013" /></td></tr>
215      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     header-field   = &lt;header-field, defined in [Part1], Section 3.2&gt;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
216      <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>
217      <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>
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">     Last-Modified  = &lt;Last-Modified, defined in [Part4], Section 6.6&gt;</td><td> </td><td class="right">     Last-Modified  = &lt;Last-Modified, defined in [Part4], Section 6.6&gt;</td><td class="lineno" valign="top"></td></tr>
220      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
221      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Range  = &lt;Content-Range, defined in [Part5], Section 5.2&gt;</td><td> </td><td class="right">     Content-Range  = &lt;Content-Range, defined in [Part5], Section 5.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">     Expires        = &lt;Expires, defined in [Part6], Section 3.3&gt;</td><td> </td><td class="right">     Expires        = &lt;Expires, defined in [Part6], Section 3.3&gt;</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">2.  Protocol Parameters</td><td> </td><td class="right">2.  Protocol Parameters</td><td class="lineno" valign="top"></td></tr>
226      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
227      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 7, line 37</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 7, line 35</em></th><td></td></tr>
228      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
229      <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>
230      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
231      <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>
232      <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>
233      <tr><td class="lineno" valign="top"></td><td class="left">   Character Set registry MUST represent the character set defined by</td><td> </td><td class="right">   Character Set registry MUST represent the character set defined by</td><td class="lineno" valign="top"></td></tr>
234      <tr><td class="lineno" valign="top"></td><td class="left">   that registry.  Applications SHOULD limit their use of character sets</td><td> </td><td class="right">   that registry.  Applications SHOULD limit their use of character sets</td><td class="lineno" valign="top"></td></tr>
235      <tr><td class="lineno" valign="top"></td><td class="left">   to those defined by the IANA registry.</td><td> </td><td class="right">   to those defined by the IANA registry.</td><td class="lineno" valign="top"></td></tr>
236      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
237      <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>
238      <tr><td><a name="diff0014" /></td></tr>
239      <tr><td class="lineno" valign="top"></td><td class="lblock">   header (in which the charset value is an unquoted token) and as the</td><td> </td><td class="rblock">   header <span class="insert">field</span> (in which the charset value is an unquoted token) and as</td><td class="lineno" valign="top"></td></tr>
240      <tr><td class="lineno" valign="top"></td><td class="lblock">   value of a parameter in a Content-Type header (within a request or</td><td> </td><td class="rblock">   the value of a parameter in a Content-Type header <span class="insert">field</span> (within a</td><td class="lineno" valign="top"></td></tr>
241      <tr><td class="lineno" valign="top"></td><td class="lblock">   response), in which case the parameter value of the charset parameter</td><td> </td><td class="rblock">   request or response), in which case the parameter value of the</td><td class="lineno" valign="top"></td></tr>
242      <tr><td class="lineno" valign="top"></td><td class="lblock">   can be quoted.</td><td> </td><td class="rblock">   charset parameter can be quoted.</td><td class="lineno" valign="top"></td></tr>
243      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
244      <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>
245      <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>
246      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
247      <tr><td class="lineno" valign="top"></td><td class="left">2.1.1.  Missing Charset</td><td> </td><td class="right">2.1.1.  Missing Charset</td><td class="lineno" valign="top"></td></tr>
248      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
249      <tr><td><a name="diff0015" /></td></tr>
250      <tr><td class="lineno" valign="top"></td><td class="lblock">   Some HTTP/1.0 software has interpreted a Content-Type header without</td><td> </td><td class="rblock">   Some HTTP/1.0 software has interpreted a Content-Type header <span class="insert">field</span></td><td class="lineno" valign="top"></td></tr>
251      <tr><td class="lineno" valign="top"></td><td class="lblock">   charset parameter incorrectly to mean "recipient should guess".</td><td> </td><td class="rblock">   without charset parameter incorrectly to mean "recipient should</td><td class="lineno" valign="top"></td></tr>
252      <tr><td class="lineno" valign="top"></td><td class="lblock">   Senders wishing to defeat this behavior MAY include a charset</td><td> </td><td class="rblock">   guess".  Senders wishing to defeat this behavior MAY include a</td><td class="lineno" valign="top"></td></tr>
253      <tr><td class="lineno" valign="top"></td><td class="lblock">   parameter even when the charset is ISO-8859-1 ([ISO-8859-1]) and</td><td> </td><td class="rblock">   charset parameter even when the charset is ISO-8859-1 ([ISO-8859-1])</td><td class="lineno" valign="top"></td></tr>
254      <tr><td class="lineno" valign="top"></td><td class="lblock">   SHOULD do so when it is known that it will not confuse the recipient.</td><td> </td><td class="rblock">   and SHOULD do so when it is known that it will not confuse the</td><td class="lineno" valign="top"></td></tr>
255      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   recipient.</td><td class="lineno" valign="top"></td></tr>
256      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
257      <tr><td class="lineno" valign="top"></td><td class="left">   Unfortunately, some older HTTP/1.0 clients did not deal properly with</td><td> </td><td class="right">   Unfortunately, some older HTTP/1.0 clients did not deal properly with</td><td class="lineno" valign="top"></td></tr>
258      <tr><td class="lineno" valign="top"></td><td class="left">   an explicit charset parameter.  HTTP/1.1 recipients MUST respect the</td><td> </td><td class="right">   an explicit charset parameter.  HTTP/1.1 recipients MUST respect the</td><td class="lineno" valign="top"></td></tr>
259      <tr><td class="lineno" valign="top"></td><td class="left">   charset label provided by the sender; and those user agents that have</td><td> </td><td class="right">   charset label provided by the sender; and those user agents that have</td><td class="lineno" valign="top"></td></tr>
260      <tr><td class="lineno" valign="top"></td><td class="left">   a provision to "guess" a charset MUST use the charset from the</td><td> </td><td class="right">   a provision to "guess" a charset MUST use the charset from the</td><td class="lineno" valign="top"></td></tr>
261      <tr><td class="lineno" valign="top"></td><td class="left">   content-type field if they support that charset, rather than the</td><td> </td><td class="right">   content-type field if they support that charset, rather than the</td><td class="lineno" valign="top"></td></tr>
262      <tr><td class="lineno" valign="top"></td><td class="left">   recipient's preference, when initially displaying a document.  See</td><td> </td><td class="right">   recipient's preference, when initially displaying a document.  See</td><td class="lineno" valign="top"></td></tr>
263      <tr><td class="lineno" valign="top"></td><td class="left">   Section 2.3.1.</td><td> </td><td class="right">   Section 2.3.1.</td><td class="lineno" valign="top"></td></tr>
264      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
265      <tr><td class="lineno" valign="top"></td><td class="left">2.2.  Content Codings</td><td> </td><td class="right">2.2.  Content Codings</td><td class="lineno" valign="top"></td></tr>
266      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
267      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 8, line 48</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 8, line 48</em></th><td></td></tr>
268      <tr><td class="lineno" valign="top"></td><td class="left">      See Section 6.2.2.2 of [Part1].</td><td> </td><td class="right">      See Section 6.2.2.2 of [Part1].</td><td class="lineno" valign="top"></td></tr>
269      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
270      <tr><td class="lineno" valign="top"></td><td class="left">   gzip</td><td> </td><td class="right">   gzip</td><td class="lineno" valign="top"></td></tr>
271      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
272      <tr><td class="lineno" valign="top"></td><td class="left">      See Section 6.2.2.3 of [Part1].</td><td> </td><td class="right">      See Section 6.2.2.3 of [Part1].</td><td class="lineno" valign="top"></td></tr>
273      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
274      <tr><td class="lineno" valign="top"></td><td class="left">   identity</td><td> </td><td class="right">   identity</td><td class="lineno" valign="top"></td></tr>
275      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
276      <tr><td class="lineno" valign="top"></td><td class="left">      The default (identity) encoding; the use of no transformation</td><td> </td><td class="right">      The default (identity) encoding; the use of no transformation</td><td class="lineno" valign="top"></td></tr>
277      <tr><td class="lineno" valign="top"></td><td class="left">      whatsoever.  This content-coding is used only in the Accept-</td><td> </td><td class="right">      whatsoever.  This content-coding is used only in the Accept-</td><td class="lineno" valign="top"></td></tr>
278      <tr><td><a name="diff0016" /></td></tr>
279      <tr><td class="lineno" valign="top"></td><td class="lblock">      Encoding <span class="delete">header,</span> and SHOULD NOT be used in the <span class="delete">Content-Encoding</span></td><td> </td><td class="rblock">      Encoding <span class="insert">header field,</span> and SHOULD NOT be used in the <span class="insert">Content-</span></td><td class="lineno" valign="top"></td></tr>
280      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      header.</span></td><td> </td><td class="rblock"><span class="insert">      Encoding header field.</span></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">2.2.1.  Content Coding Registry</td><td> </td><td class="right">2.2.1.  Content Coding Registry</td><td class="lineno" valign="top"></td></tr>
283      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
284      <tr><td class="lineno" valign="top"></td><td class="left">   The HTTP Content Coding Registry defines the name space for the</td><td> </td><td class="right">   The HTTP Content Coding Registry defines the name space for the</td><td class="lineno" valign="top"></td></tr>
285      <tr><td class="lineno" valign="top"></td><td class="left">   content coding names.</td><td> </td><td class="right">   content coding names.</td><td class="lineno" valign="top"></td></tr>
286      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
287      <tr><td class="lineno" valign="top"></td><td class="left">   Registrations MUST include the following fields:</td><td> </td><td class="right">   Registrations MUST include the following fields:</td><td class="lineno" valign="top"></td></tr>
288      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
289      <tr><td class="lineno" valign="top"></td><td class="left">   o  Name</td><td> </td><td class="right">   o  Name</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-l6" /><small>skipping to change at</small><em> page 17, line 18</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 17, line 18</em></th><td></td></tr>
293      <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>
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">6.  Header Field Definitions</td><td> </td><td class="right">6.  Header Field Definitions</td><td class="lineno" valign="top"></td></tr>
296      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
297      <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>
298      <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>
299      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
300      <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>
301      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
302      <tr><td class="lineno" valign="top"></td><td class="left">   The "Accept" request-header field can be used by user agents to</td><td> </td><td class="right">   The "Accept" request-header field can be used by user agents to</td><td class="lineno" valign="top"></td></tr>
303      <tr><td><a name="diff0017" /></td></tr>
304      <tr><td class="lineno" valign="top"></td><td class="lblock">   specify response media types that are acceptable.  Accept <span class="delete">headers</span> can</td><td> </td><td class="rblock">   specify response media types that are acceptable.  Accept <span class="insert">header</span></td><td class="lineno" valign="top"></td></tr>
305      <tr><td class="lineno" valign="top"></td><td class="lblock">   be used to indicate that the request is specifically limited to a</td><td> </td><td class="rblock"><span class="insert">   fields</span> can be used to indicate that the request is specifically</td><td class="lineno" valign="top"></td></tr>
306      <tr><td class="lineno" valign="top"></td><td class="lblock">   small set of desired types, as in the case of a request for an <span class="delete">in-</span></td><td> </td><td class="rblock">   limited to a small set of desired types, as in the case of a request</td><td class="lineno" valign="top"></td></tr>
307      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   line</span> image.</td><td> </td><td class="rblock">   for an <span class="insert">in-line</span> image.</td><td class="lineno" valign="top"></td></tr>
308      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
309      <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>
310      <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>
311      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
312      <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>
313      <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>
314      <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>
315      <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>
316      <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>
317      <tr><td><a name="diff0018" /></td></tr>
318      <tr><td class="lineno" valign="top"></td><td class="lblock">     accept-ext     = OWS ";" OWS token</td><td> </td><td class="rblock">     accept-ext     = OWS ";" OWS token [ "=" word ]</td><td class="lineno" valign="top"></td></tr>
319      <tr><td class="lineno" valign="top"></td><td class="lblock">                      [ "=" word ]</td><td> </td><td class="rblock"></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">   The asterisk "*" character is used to group media types into ranges,</td><td> </td><td class="right">   The asterisk "*" character is used to group media types into ranges,</td><td class="lineno" valign="top"></td></tr>
322      <tr><td class="lineno" valign="top"></td><td class="left">   with "*/*" indicating all media types and "type/*" indicating all</td><td> </td><td class="right">   with "*/*" indicating all media types and "type/*" indicating all</td><td class="lineno" valign="top"></td></tr>
323      <tr><td class="lineno" valign="top"></td><td class="left">   subtypes of that type.  The media-range MAY include media type</td><td> </td><td class="right">   subtypes of that type.  The media-range MAY include media type</td><td class="lineno" valign="top"></td></tr>
324      <tr><td class="lineno" valign="top"></td><td class="left">   parameters that are applicable to that range.</td><td> </td><td class="right">   parameters that are applicable to that range.</td><td class="lineno" valign="top"></td></tr>
325      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
326      <tr><td class="lineno" valign="top"></td><td class="left">   Each media-range MAY be followed by one or more accept-params,</td><td> </td><td class="right">   Each media-range MAY be followed by one or more accept-params,</td><td class="lineno" valign="top"></td></tr>
327      <tr><td class="lineno" valign="top"></td><td class="left">   beginning with the "q" parameter for indicating a relative quality</td><td> </td><td class="right">   beginning with the "q" parameter for indicating a relative quality</td><td class="lineno" valign="top"></td></tr>
328      <tr><td class="lineno" valign="top"></td><td class="left">   factor.  The first "q" parameter (if any) separates the media-range</td><td> </td><td class="right">   factor.  The first "q" parameter (if any) separates the media-range</td><td class="lineno" valign="top"></td></tr>
329      <tr><td class="lineno" valign="top"></td><td class="left">   parameter(s) from the accept-params.  Quality factors allow the user</td><td> </td><td class="right">   parameter(s) from the accept-params.  Quality factors allow the user</td><td class="lineno" valign="top"></td></tr>
330      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
331      <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 19, line 50</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 19, line 50</em></th><td></td></tr>
332      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
333      <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>
334      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
335      <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>
336      <tr><td class="lineno" valign="top"></td><td class="left">   matches every character set (including ISO-8859-1) which is not</td><td> </td><td class="right">   matches every character set (including ISO-8859-1) which is not</td><td class="lineno" valign="top"></td></tr>
337      <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>
338      <tr><td class="lineno" valign="top"></td><td class="left">   present in an Accept-Charset field, then all character sets not</td><td> </td><td class="right">   present in an Accept-Charset field, then all character sets not</td><td class="lineno" valign="top"></td></tr>
339      <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>
340      <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>
341      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
342      <tr><td><a name="diff0019" /></td></tr>
343      <tr><td class="lineno" valign="top"></td><td class="lblock">   If no Accept-Charset header is present, the default is that any</td><td> </td><td class="rblock">   If no Accept-Charset header <span class="insert">field</span> is present, the default is that any</td><td class="lineno" valign="top"></td></tr>
344      <tr><td class="lineno" valign="top"></td><td class="lblock">   character set is acceptable.  If an Accept-Charset header is present,</td><td> </td><td class="rblock">   character set is acceptable.  If an Accept-Charset header <span class="insert">field</span> is</td><td class="lineno" valign="top"></td></tr>
345      <tr><td class="lineno" valign="top"></td><td class="lblock">   and if the server cannot send a response which is acceptable</td><td> </td><td class="rblock">   present, and if the server cannot send a response which is acceptable</td><td class="lineno" valign="top"></td></tr>
346      <tr><td class="lineno" valign="top"></td><td class="lblock">   according to the Accept-Charset <span class="delete">header,</span> then the server SHOULD send</td><td> </td><td class="rblock">   according to the Accept-Charset <span class="insert">header field,</span> then the server SHOULD</td><td class="lineno" valign="top"></td></tr>
347      <tr><td class="lineno" valign="top"></td><td class="lblock">   an error response with the 406 (Not Acceptable) status code, though</td><td> </td><td class="rblock">   send an error response with the 406 (Not Acceptable) status code,</td><td class="lineno" valign="top"></td></tr>
348      <tr><td class="lineno" valign="top"></td><td class="lblock">   the sending of an unacceptable response is also allowed.</td><td> </td><td class="rblock">   though the sending of an unacceptable response is also allowed.</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">6.3.  Accept-Encoding</td><td> </td><td class="right">6.3.  Accept-Encoding</td><td class="lineno" valign="top"></td></tr>
351      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
352      <tr><td class="lineno" valign="top"></td><td class="left">   The "Accept-Encoding" request-header field can be used by user agents</td><td> </td><td class="right">   The "Accept-Encoding" request-header field can be used by user agents</td><td class="lineno" valign="top"></td></tr>
353      <tr><td class="lineno" valign="top"></td><td class="left">   to indicate what response content-codings (Section 2.2) are</td><td> </td><td class="right">   to indicate what response content-codings (Section 2.2) are</td><td class="lineno" valign="top"></td></tr>
354      <tr><td class="lineno" valign="top"></td><td class="left">   acceptable in the response.</td><td> </td><td class="right">   acceptable in the response.</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">     Accept-Encoding    = "Accept-Encoding" ":" OWS</td><td> </td><td class="right">     Accept-Encoding    = "Accept-Encoding" ":" OWS</td><td class="lineno" valign="top"></td></tr>
357      <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>
358      <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>
359      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
360      <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 21, line 8</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 21, line 8</em></th><td></td></tr>
361      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
362      <tr><td class="lineno" valign="top"></td><td class="left">   4.  The "identity" content-coding is always acceptable, unless</td><td> </td><td class="right">   4.  The "identity" content-coding is always acceptable, unless</td><td class="lineno" valign="top"></td></tr>
363      <tr><td class="lineno" valign="top"></td><td class="left">       specifically refused because the Accept-Encoding field includes</td><td> </td><td class="right">       specifically refused because the Accept-Encoding field includes</td><td class="lineno" valign="top"></td></tr>
364      <tr><td class="lineno" valign="top"></td><td class="left">       "identity;q=0", or because the field includes "*;q=0" and does</td><td> </td><td class="right">       "identity;q=0", or because the field includes "*;q=0" and does</td><td class="lineno" valign="top"></td></tr>
365      <tr><td class="lineno" valign="top"></td><td class="left">       not explicitly include the "identity" content-coding.  If the</td><td> </td><td class="right">       not explicitly include the "identity" content-coding.  If the</td><td class="lineno" valign="top"></td></tr>
366      <tr><td class="lineno" valign="top"></td><td class="left">       Accept-Encoding field-value is empty, then only the "identity"</td><td> </td><td class="right">       Accept-Encoding field-value is empty, then only the "identity"</td><td class="lineno" valign="top"></td></tr>
367      <tr><td class="lineno" valign="top"></td><td class="left">       encoding is acceptable.</td><td> </td><td class="right">       encoding is acceptable.</td><td class="lineno" valign="top"></td></tr>
368      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
369      <tr><td class="lineno" valign="top"></td><td class="left">   If an Accept-Encoding field is present in a request, and if the</td><td> </td><td class="right">   If an Accept-Encoding field is present in a request, and if the</td><td class="lineno" valign="top"></td></tr>
370      <tr><td class="lineno" valign="top"></td><td class="left">   server cannot send a response which is acceptable according to the</td><td> </td><td class="right">   server cannot send a response which is acceptable according to the</td><td class="lineno" valign="top"></td></tr>
371      <tr><td><a name="diff0020" /></td></tr>
372      <tr><td class="lineno" valign="top"></td><td class="lblock">   Accept-Encoding <span class="delete">header,</span> then the server SHOULD send an error response</td><td> </td><td class="rblock">   Accept-Encoding <span class="insert">header field,</span> then the server SHOULD send an error</td><td class="lineno" valign="top"></td></tr>
373      <tr><td class="lineno" valign="top"></td><td class="lblock">   with the 406 (Not Acceptable) status code.</td><td> </td><td class="rblock">   response with the 406 (Not Acceptable) status code.</td><td class="lineno" valign="top"></td></tr>
374      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
375      <tr><td class="lineno" valign="top"></td><td class="left">   If no Accept-Encoding field is present in a request, the server MAY</td><td> </td><td class="right">   If no Accept-Encoding field is present in a request, the server MAY</td><td class="lineno" valign="top"></td></tr>
376      <tr><td class="lineno" valign="top"></td><td class="left">   assume that the client will accept any content coding.  In this case,</td><td> </td><td class="right">   assume that the client will accept any content coding.  In this case,</td><td class="lineno" valign="top"></td></tr>
377      <tr><td class="lineno" valign="top"></td><td class="left">   if "identity" is one of the available content-codings, then the</td><td> </td><td class="right">   if "identity" is one of the available content-codings, then the</td><td class="lineno" valign="top"></td></tr>
378      <tr><td class="lineno" valign="top"></td><td class="left">   server SHOULD use the "identity" content-coding, unless it has</td><td> </td><td class="right">   server SHOULD use the "identity" content-coding, unless it has</td><td class="lineno" valign="top"></td></tr>
379      <tr><td class="lineno" valign="top"></td><td class="left">   additional information that a different content-coding is meaningful</td><td> </td><td class="right">   additional information that a different content-coding is meaningful</td><td class="lineno" valign="top"></td></tr>
380      <tr><td class="lineno" valign="top"></td><td class="left">   to the client.</td><td> </td><td class="right">   to the client.</td><td class="lineno" valign="top"></td></tr>
381      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
382      <tr><td class="lineno" valign="top"></td><td class="left">      Note: If the request does not include an Accept-Encoding field,</td><td> </td><td class="right">      Note: If the request does not include an Accept-Encoding field,</td><td class="lineno" valign="top"></td></tr>
383      <tr><td class="lineno" valign="top"></td><td class="left">      and if the "identity" content-coding is unavailable, then content-</td><td> </td><td class="right">      and if the "identity" content-coding is unavailable, then content-</td><td class="lineno" valign="top"></td></tr>
384      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
385      <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 22, line 13</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 22, line 13</em></th><td></td></tr>
386      <tr><td class="lineno" valign="top"></td><td class="left">   other types of English". (see also Section 2.3 of [RFC4647])</td><td> </td><td class="right">   other types of English". (see also Section 2.3 of [RFC4647])</td><td class="lineno" valign="top"></td></tr>
387      <tr><td class="lineno" valign="top"></td><td class="left">   For matching, Section 3 of [RFC4647] defines several matching</td><td> </td><td class="right">   For matching, Section 3 of [RFC4647] defines several matching</td><td class="lineno" valign="top"></td></tr>
388      <tr><td class="lineno" valign="top"></td><td class="left">   schemes.  Implementations can offer the most appropriate matching</td><td> </td><td class="right">   schemes.  Implementations can offer the most appropriate matching</td><td class="lineno" valign="top"></td></tr>
389      <tr><td class="lineno" valign="top"></td><td class="left">   scheme for their requirements.</td><td> </td><td class="right">   scheme for their requirements.</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 class="lineno" valign="top"></td><td class="left">      Note: The "Basic Filtering" scheme ([RFC4647], Section 3.3.1) is</td><td> </td><td class="right">      Note: The "Basic Filtering" scheme ([RFC4647], Section 3.3.1) is</td><td class="lineno" valign="top"></td></tr>
392      <tr><td class="lineno" valign="top"></td><td class="left">      identical to the matching scheme that was previously defined in</td><td> </td><td class="right">      identical to the matching scheme that was previously defined in</td><td class="lineno" valign="top"></td></tr>
393      <tr><td class="lineno" valign="top"></td><td class="left">      Section 14.4 of [RFC2616].</td><td> </td><td class="right">      Section 14.4 of [RFC2616].</td><td class="lineno" valign="top"></td></tr>
394      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
395      <tr><td class="lineno" valign="top"></td><td class="left">   It might be contrary to the privacy expectations of the user to send</td><td> </td><td class="right">   It might be contrary to the privacy expectations of the user to send</td><td class="lineno" valign="top"></td></tr>
396      <tr><td><a name="diff0021" /></td></tr>
397      <tr><td class="lineno" valign="top"></td><td class="lblock">   an Accept-Language header with the complete linguistic preferences of</td><td> </td><td class="rblock">   an Accept-Language header <span class="insert">field</span> with the complete linguistic</td><td class="lineno" valign="top"></td></tr>
398      <tr><td class="lineno" valign="top"></td><td class="lblock">   the user in every request.  For a discussion of this issue, see</td><td> </td><td class="rblock">   preferences of the user in every request.  For a discussion of this</td><td class="lineno" valign="top"></td></tr>
399      <tr><td class="lineno" valign="top"></td><td class="lblock">   Section 8.1.</td><td> </td><td class="rblock">   issue, see Section 8.1.</td><td class="lineno" valign="top"></td></tr>
400      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
401      <tr><td class="lineno" valign="top"></td><td class="left">   As intelligibility is highly dependent on the individual user, it is</td><td> </td><td class="right">   As intelligibility is highly dependent on the individual user, it is</td><td class="lineno" valign="top"></td></tr>
402      <tr><td class="lineno" valign="top"></td><td class="left">   recommended that client applications make the choice of linguistic</td><td> </td><td class="right">   recommended that client applications make the choice of linguistic</td><td class="lineno" valign="top"></td></tr>
403      <tr><td class="lineno" valign="top"></td><td class="left">   preference available to the user.  If the choice is not made</td><td> </td><td class="right">   preference available to the user.  If the choice is not made</td><td class="lineno" valign="top"></td></tr>
404      <tr><td class="lineno" valign="top"></td><td class="left">   available, then the Accept-Language header field MUST NOT be given in</td><td> </td><td class="right">   available, then the Accept-Language header field MUST NOT be given in</td><td class="lineno" valign="top"></td></tr>
405      <tr><td class="lineno" valign="top"></td><td class="left">   the request.</td><td> </td><td class="right">   the request.</td><td class="lineno" valign="top"></td></tr>
406      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
407      <tr><td class="lineno" valign="top"></td><td class="left">      Note: When making the choice of linguistic preference available to</td><td> </td><td class="right">      Note: When making the choice of linguistic preference available to</td><td class="lineno" valign="top"></td></tr>
408      <tr><td class="lineno" valign="top"></td><td class="left">      the user, we remind implementors of the fact that users are not</td><td> </td><td class="right">      the user, we remind implementors of the fact that users are not</td><td class="lineno" valign="top"></td></tr>
409      <tr><td class="lineno" valign="top"></td><td class="left">      familiar with the details of language matching as described above,</td><td> </td><td class="right">      familiar with the details of language matching as described above,</td><td class="lineno" valign="top"></td></tr>
410      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
411      <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 26, line 28</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 26, line 28</em></th><td></td></tr>
412      <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>
413      <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>
414      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
415      <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>
416      <tr><td class="lineno" valign="top"></td><td class="left">   composite media-types (e.g., multipart/* and message/rfc822), but</td><td> </td><td class="right">   composite media-types (e.g., multipart/* and message/rfc822), but</td><td class="lineno" valign="top"></td></tr>
417      <tr><td class="lineno" valign="top"></td><td class="left">   this does not change how the digest is computed as defined in the</td><td> </td><td class="right">   this does not change how the digest is computed as defined in the</td><td class="lineno" valign="top"></td></tr>
418      <tr><td class="lineno" valign="top"></td><td class="left">   preceding paragraph.</td><td> </td><td class="right">   preceding paragraph.</td><td class="lineno" valign="top"></td></tr>
419      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
420      <tr><td class="lineno" valign="top"></td><td class="left">   There are several consequences of this.  The payload for composite</td><td> </td><td class="right">   There are several consequences of this.  The payload for composite</td><td class="lineno" valign="top"></td></tr>
421      <tr><td class="lineno" valign="top"></td><td class="left">   types MAY contain many body-parts, each with its own MIME and HTTP</td><td> </td><td class="right">   types MAY contain many body-parts, each with its own MIME and HTTP</td><td class="lineno" valign="top"></td></tr>
422      <tr><td><a name="diff0022" /></td></tr>
423      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">headers</span> (including Content-MD5, Content-Transfer-Encoding, and</td><td> </td><td class="rblock">   <span class="insert">header fields</span> (including Content-MD5, Content-Transfer-Encoding, and</td><td class="lineno" valign="top"></td></tr>
424      <tr><td class="lineno" valign="top"></td><td class="lblock">   Content-Encoding <span class="delete">headers).</span>  If a body-part has a <span class="delete">Content-Transfer-</span></td><td> </td><td class="rblock">   Content-Encoding <span class="insert">header fields).</span>  If a body-part has a <span class="insert">Content-</span></td><td class="lineno" valign="top"></td></tr>
425      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Encoding</span> or Content-Encoding <span class="delete">header,</span> it is assumed that the content</td><td> </td><td class="rblock"><span class="insert">   Transfer-Encoding</span> or Content-Encoding <span class="insert">header field,</span> it is assumed</td><td class="lineno" valign="top"></td></tr>
426      <tr><td class="lineno" valign="top"></td><td class="lblock">   of the body-part has had the encoding applied, and the body-part is</td><td> </td><td class="rblock">   that the content of the body-part has had the encoding applied, and</td><td class="lineno" valign="top"></td></tr>
427      <tr><td class="lineno" valign="top"></td><td class="lblock">   included in the Content-MD5 digest as is -- i.e., after the</td><td> </td><td class="rblock">   the body-part is included in the Content-MD5 digest as is -- i.e.,</td><td class="lineno" valign="top"></td></tr>
428      <tr><td class="lineno" valign="top"></td><td class="lblock">   application.  The Transfer-Encoding header field is not allowed</td><td> </td><td class="rblock">   after the application.  The Transfer-Encoding header field is not</td><td class="lineno" valign="top"></td></tr>
429      <tr><td class="lineno" valign="top"></td><td class="lblock">   within body-parts.</td><td> </td><td class="rblock">   allowed within body-parts.</td><td class="lineno" valign="top"></td></tr>
430      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
431      <tr><td class="lineno" valign="top"></td><td class="left">   Conversion of all line breaks to CRLF MUST NOT be done before</td><td> </td><td class="right">   Conversion of all line breaks to CRLF MUST NOT be done before</td><td class="lineno" valign="top"></td></tr>
432      <tr><td class="lineno" valign="top"></td><td class="left">   computing or checking the digest: the line break convention used in</td><td> </td><td class="right">   computing or checking the digest: the line break convention used in</td><td class="lineno" valign="top"></td></tr>
433      <tr><td class="lineno" valign="top"></td><td class="left">   the text actually transmitted MUST be left unaltered when computing</td><td> </td><td class="right">   the text actually transmitted MUST be left unaltered when computing</td><td class="lineno" valign="top"></td></tr>
434      <tr><td class="lineno" valign="top"></td><td class="left">   the digest.</td><td> </td><td class="right">   the digest.</td><td class="lineno" valign="top"></td></tr>
435      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
436      <tr><td class="lineno" valign="top"></td><td class="left">      Note: While the definition of Content-MD5 is exactly the same for</td><td> </td><td class="right">      Note: While the definition of Content-MD5 is exactly the same for</td><td class="lineno" valign="top"></td></tr>
437      <tr><td class="lineno" valign="top"></td><td class="left">      HTTP as in RFC 1864 for MIME entity-bodies, there are several ways</td><td> </td><td class="right">      HTTP as in RFC 1864 for MIME entity-bodies, there are several ways</td><td class="lineno" valign="top"></td></tr>
438      <tr><td class="lineno" valign="top"></td><td class="left">      in which the application of Content-MD5 to HTTP entity-bodies</td><td> </td><td class="right">      in which the application of Content-MD5 to HTTP entity-bodies</td><td class="lineno" valign="top"></td></tr>
439      <tr><td class="lineno" valign="top"></td><td class="left">      differs from its application to MIME entity-bodies.  One is that</td><td> </td><td class="right">      differs from its application to MIME entity-bodies.  One is that</td><td class="lineno" valign="top"></td></tr>
440      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
441      <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 27, line 29</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 27, line 29</em></th><td></td></tr>
442      <tr><td class="lineno" valign="top"></td><td class="left">   Further discussion of Content-Type is provided in Section 4.2.</td><td> </td><td class="right">   Further discussion of Content-Type is provided in Section 4.2.</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">7.  IANA Considerations</td><td> </td><td class="right">7.  IANA Considerations</td><td class="lineno" valign="top"></td></tr>
445      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
446      <tr><td class="lineno" valign="top"></td><td class="left">7.1.  Header Field Registration</td><td> </td><td class="right">7.1.  Header Field Registration</td><td class="lineno" valign="top"></td></tr>
447      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
448      <tr><td class="lineno" valign="top"></td><td class="left">   The Message Header Field Registry located at &lt;http://www.iana.org/</td><td> </td><td class="right">   The Message Header Field Registry located at &lt;http://www.iana.org/</td><td class="lineno" valign="top"></td></tr>
449      <tr><td class="lineno" valign="top"></td><td class="left">   assignments/message-headers/message-header-index.html&gt; shall be</td><td> </td><td class="right">   assignments/message-headers/message-header-index.html&gt; shall be</td><td class="lineno" valign="top"></td></tr>
450      <tr><td class="lineno" valign="top"></td><td class="left">   updated with the permanent registrations below (see [RFC3864]):</td><td> </td><td class="right">   updated with the permanent registrations below (see [RFC3864]):</td><td class="lineno" valign="top"></td></tr>
451      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
452      <tr><td><a name="diff0023" /></td></tr>
453      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+---------------------+----------+----------+--------------+</span></td><td> </td><td class="rblock">   <span class="insert">+-------------------+----------+----------+--------------+</span></td><td class="lineno" valign="top"></td></tr>
454      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Header Field Name   | Protocol | Status   | Reference    |</td><td> </td><td class="rblock">   | Header Field Name | Protocol | Status   | Reference    |</td><td class="lineno" valign="top"></td></tr>
455      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+---------------------+----------+----------+--------------+</span></td><td> </td><td class="rblock">   <span class="insert">+-------------------+----------+----------+--------------+</span></td><td class="lineno" valign="top"></td></tr>
456      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Accept              | http     | standard | Section 6.1  |</td><td> </td><td class="rblock">   | Accept            | http     | standard | Section 6.1  |</td><td class="lineno" valign="top"></td></tr>
457      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Accept-Charset      | http     | standard | Section 6.2  |</td><td> </td><td class="rblock">   | Accept-Charset    | http     | standard | Section 6.2  |</td><td class="lineno" valign="top"></td></tr>
458      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Accept-Encoding     | http     | standard | Section 6.3  |</td><td> </td><td class="rblock">   | Accept-Encoding   | http     | standard | Section 6.3  |</td><td class="lineno" valign="top"></td></tr>
459      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Accept-Language     | http     | standard | Section 6.4  |</td><td> </td><td class="rblock">   | Accept-Language   | http     | standard | Section 6.4  |</td><td class="lineno" valign="top"></td></tr>
460      <tr><td class="lineno" valign="top"></td><td class="lblock">   | <span class="delete">Content-Disposition | http     | standard | Appendix B.1 |</span></td><td> </td><td class="rblock">   | Content-Encoding  | http     | standard | Section 6.5  |</td><td class="lineno" valign="top"></td></tr>
461      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   |</span> Content-Encoding    | http     | standard | Section 6.5  |</td><td> </td><td class="rblock">   | Content-Language  | http     | standard | Section 6.6  |</td><td class="lineno" valign="top"></td></tr>
462      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Content-Language    | http     | standard | Section 6.6  |</td><td> </td><td class="rblock">   | Content-Location  | http     | standard | Section 6.7  |</td><td class="lineno" valign="top"></td></tr>
463      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Content-Location    | http     | standard | Section 6.7  |</td><td> </td><td class="rblock">   | Content-MD5       | http     | standard | Section 6.8  |</td><td class="lineno" valign="top"></td></tr>
464      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Content-MD5         | http     | standard | Section 6.8  |</td><td> </td><td class="rblock">   | Content-Type      | http     | standard | Section 6.9  |</td><td class="lineno" valign="top"></td></tr>
465      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Content-Type        | http     | standard | Section 6.9  |</td><td> </td><td class="rblock">   | MIME-Version      | http     | standard | Appendix A.1 |</td><td class="lineno" valign="top"></td></tr>
466      <tr><td class="lineno" valign="top"></td><td class="lblock">   | MIME-Version        | http     | standard | Appendix A.1 |</td><td> </td><td class="rblock">   <span class="insert">+-------------------+----------+----------+--------------+</span></td><td class="lineno" valign="top"></td></tr>
467      <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>
468      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
469      <tr><td class="lineno" valign="top"></td><td class="left">   The change controller is: "IETF (iesg@ietf.org) - Internet</td><td> </td><td class="right">   The change controller is: "IETF (iesg@ietf.org) - Internet</td><td class="lineno" valign="top"></td></tr>
470      <tr><td class="lineno" valign="top"></td><td class="left">   Engineering Task Force".</td><td> </td><td class="right">   Engineering Task Force".</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">7.2.  Content Coding Registry</td><td> </td><td class="right">7.2.  Content Coding Registry</td><td class="lineno" valign="top"></td></tr>
473      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
474      <tr><td class="lineno" valign="top"></td><td class="left">   The registration procedure for HTTP Content Codings is now defined by</td><td> </td><td class="right">   The registration procedure for HTTP Content Codings is now defined by</td><td class="lineno" valign="top"></td></tr>
475      <tr><td class="lineno" valign="top"></td><td class="left">   Section 2.2.1 of this document.</td><td> </td><td class="right">   Section 2.2.1 of this document.</td><td class="lineno" valign="top"></td></tr>
476      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
477      <tr><td class="lineno" valign="top"></td><td class="left">   The HTTP Content Codings Registry located at</td><td> </td><td class="right">   The HTTP Content Codings Registry located at</td><td class="lineno" valign="top"></td></tr>
478      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
479      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 28, line 32</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 28, line 30</em></th><td></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"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
482      <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>
483      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
484      <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>
485      <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>
486      <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>
487      <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>
488      <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>
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><a name="diff0024" /></td></tr>
491      <tr><td class="lineno" valign="top"></td><td class="lblock">8.1.  Privacy Issues Connected to Accept Headers</td><td> </td><td class="rblock">8.1.  Privacy Issues Connected to Accept Header<span class="insert"> Field</span>s</td><td class="lineno" valign="top"></td></tr>
492      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
493      <tr><td><a name="diff0025" /></td></tr>
494      <tr><td class="lineno" valign="top"></td><td class="lblock">   Accept request-headers can reveal information about the user to all</td><td> </td><td class="rblock">   Accept request-headers <span class="insert">fields</span> can reveal information about the user</td><td class="lineno" valign="top"></td></tr>
495      <tr><td class="lineno" valign="top"></td><td class="lblock">   servers which are accessed.  The Accept-Language header in particular</td><td> </td><td class="rblock">   to all servers which are accessed.  The Accept-Language header <span class="insert">field</span></td><td class="lineno" valign="top"></td></tr>
496      <tr><td class="lineno" valign="top"></td><td class="lblock">   can reveal information the user would consider to be of a private</td><td> </td><td class="rblock">   in particular can reveal information the user would consider to be of</td><td class="lineno" valign="top"></td></tr>
497      <tr><td class="lineno" valign="top"></td><td class="lblock">   nature, because the understanding of particular languages is often</td><td> </td><td class="rblock">   a private nature, because the understanding of particular languages</td><td class="lineno" valign="top"></td></tr>
498      <tr><td class="lineno" valign="top"></td><td class="lblock">   strongly correlated to the membership of a particular ethnic group.</td><td> </td><td class="rblock">   is often strongly correlated to the membership of a particular ethnic</td><td class="lineno" valign="top"></td></tr>
499      <tr><td class="lineno" valign="top"></td><td class="lblock">   User agents which offer the option to configure the contents of an</td><td> </td><td class="rblock">   group.  User agents which offer the option to configure the contents</td><td class="lineno" valign="top"></td></tr>
500      <tr><td class="lineno" valign="top"></td><td class="lblock">   Accept-Language header to be sent in every request are strongly</td><td> </td><td class="rblock">   of an Accept-Language header <span class="insert">field</span> to be sent in every request are</td><td class="lineno" valign="top"></td></tr>
501      <tr><td class="lineno" valign="top"></td><td class="lblock">   encouraged to let the configuration process include a message which</td><td> </td><td class="rblock">   strongly encouraged to let the configuration process include a</td><td class="lineno" valign="top"></td></tr>
502      <tr><td class="lineno" valign="top"></td><td class="lblock">   makes the user aware of the loss of privacy involved.</td><td> </td><td class="rblock">   message which makes the user aware of the loss of privacy involved.</td><td class="lineno" valign="top"></td></tr>
503      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
504      <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>
505      <tr><td><a name="diff0026" /></td></tr>
506      <tr><td class="lineno" valign="top"></td><td class="lblock">   to omit the sending of Accept-Language <span class="delete">headers</span> by default, and to ask</td><td> </td><td class="rblock">   to omit the sending of Accept-Language <span class="insert">header fields</span> by default, and</td><td class="lineno" valign="top"></td></tr>
507      <tr><td class="lineno" valign="top"></td><td class="lblock">   the user whether or not to start sending Accept-Language <span class="delete">headers</span> to a</td><td> </td><td class="rblock">   to ask the user whether or not to start sending Accept-Language</td><td class="lineno" valign="top"></td></tr>
508      <tr><td class="lineno" valign="top"></td><td class="lblock">   server if it detects, by looking for any Vary response-header fields</td><td> </td><td class="rblock">   <span class="insert">header fields</span> to a server if it detects, by looking for any Vary</td><td class="lineno" valign="top"></td></tr>
509      <tr><td class="lineno" valign="top"></td><td class="lblock">   generated by the server, that such sending could improve the quality</td><td> </td><td class="rblock">   response-header fields generated by the server, that such sending</td><td class="lineno" valign="top"></td></tr>
510      <tr><td class="lineno" valign="top"></td><td class="lblock">   of service.</td><td> </td><td class="rblock">   could improve the quality of service.</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">   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>
513      <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>
514      <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>
515      <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>
516      <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>
517      <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>
518      <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>
519      <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>
520      <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>
521      <tr><td class="lineno" valign="top"></td><td class="left">   privacy, user agents ought to be conservative in offering accept</td><td> </td><td class="right">   privacy, user agents ought to be conservative in offering accept</td><td class="lineno" valign="top"></td></tr>
522      <tr><td class="lineno" valign="top"></td><td class="left">   header configuration options to end users.  As an extreme privacy</td><td> </td><td class="right">   header configuration options to end users.  As an extreme privacy</td><td class="lineno" valign="top"></td></tr>
523      <tr><td><a name="diff0027" /></td></tr>
524      <tr><td class="lineno" valign="top"></td><td class="lblock">   measure, proxies could filter the accept <span class="delete">headers</span> in relayed requests.</td><td> </td><td class="rblock">   measure, proxies could filter the accept <span class="insert">header fields</span> in relayed</td><td class="lineno" valign="top"></td></tr>
525      <tr><td class="lineno" valign="top"></td><td class="lblock">   General purpose user agents which provide a high degree of header</td><td> </td><td class="rblock">   requests.  General purpose user agents which provide a high degree of</td><td class="lineno" valign="top"></td></tr>
526      <tr><td class="lineno" valign="top"></td><td class="lblock">   configurability SHOULD warn users about the loss of privacy which can</td><td> </td><td class="rblock">   header configurability SHOULD warn users about the loss of privacy</td><td class="lineno" valign="top"></td></tr>
527      <tr><td class="lineno" valign="top"></td><td class="lblock">   be involved.</td><td> </td><td class="rblock">   which can be involved.</td><td class="lineno" valign="top"></td></tr>
528      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
529      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">8.2.  Content-Disposition Issues</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
530      <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>
531      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   [RFC2183], from which the often implemented Content-Disposition (see</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
532      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Appendix B.1) header in HTTP is derived, has a number of very serious</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
533      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   security considerations.  Content-Disposition is not part of the HTTP</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
534      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   standard, but since it is widely implemented, we are documenting its</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
535      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   use and risks for implementors.  See Section 5 of [RFC2183] for</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
536      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   details.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
537      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
538      <tr><td class="lineno" valign="top"></td><td class="left">9.  Acknowledgments</td><td> </td><td class="right">9.  Acknowledgments</td><td class="lineno" valign="top"></td></tr>
539      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
540      <tr><td class="lineno" valign="top"></td><td class="left">10.  References</td><td> </td><td class="right">10.  References</td><td class="lineno" valign="top"></td></tr>
541      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
542      <tr><td class="lineno" valign="top"></td><td class="left">10.1.  Normative References</td><td> </td><td class="right">10.1.  Normative References</td><td class="lineno" valign="top"></td></tr>
543      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
544      <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>
545      <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>
546      <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>
547      <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>
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">   [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>
550      <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>
551      <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>
552      <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>
553      <tr><td><a name="diff0028" /></td></tr>
554      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p1-messaging-11</span> (work in progress),</td><td> </td><td class="rblock">                 <span class="insert">draft-ietf-httpbis-p1-messaging-12</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
555      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">August</span> 2010.</td><td> </td><td class="rblock">                 <span class="insert">October</span> 2010.</td><td class="lineno" valign="top"></td></tr>
556      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
557      <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>
558      <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>
559      <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>
560      <tr><td><a name="diff0029" /></td></tr>
561      <tr><td class="lineno" valign="top"></td><td class="lblock">                 Semantics", <span class="delete">draft-ietf-httpbis-p2-semantics-11</span> (work in</td><td> </td><td class="rblock">                 Semantics", <span class="insert">draft-ietf-httpbis-p2-semantics-12</span> (work in</td><td class="lineno" valign="top"></td></tr>
562      <tr><td class="lineno" valign="top"></td><td class="lblock">                 progress), <span class="delete">August</span> 2010.</td><td> </td><td class="rblock">                 progress), <span class="insert">October</span> 2010.</td><td class="lineno" valign="top"></td></tr>
563      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
564      <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>
565      <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>
566      <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>
567      <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>
568      <tr><td><a name="diff0030" /></td></tr>
569      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p4-conditional-11</span> (work in</td><td> </td><td class="rblock">                 <span class="insert">draft-ietf-httpbis-p4-conditional-12</span> (work in</td><td class="lineno" valign="top"></td></tr>
570      <tr><td class="lineno" valign="top"></td><td class="lblock">                 progress), <span class="delete">August</span> 2010.</td><td> </td><td class="rblock">                 progress), <span class="insert">October</span> 2010.</td><td class="lineno" valign="top"></td></tr>
571      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
572      <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>
573      <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>
574      <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>
575      <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>
576      <tr><td><a name="diff0031" /></td></tr>
577      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p5-range-11</span> (work in progress),</td><td> </td><td class="rblock">                 <span class="insert">draft-ietf-httpbis-p5-range-12</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
578      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">August</span> 2010.</td><td> </td><td class="rblock">                 <span class="insert">October</span> 2010.</td><td class="lineno" valign="top"></td></tr>
579      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
580      <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>
581      <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>
582      <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>
583      <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>
584      <tr><td><a name="diff0032" /></td></tr>
585      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p6-cache-11</span> (work in progress),</td><td> </td><td class="rblock">                 <span class="insert">draft-ietf-httpbis-p6-cache-12</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
586      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">August</span> 2010.</td><td> </td><td class="rblock">                 <span class="insert">October</span> 2010.</td><td class="lineno" valign="top"></td></tr>
587      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
588      <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>
589      <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>
590      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
591      <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>
592      <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>
593      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
594      <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>
595      <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>
596      <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>
597      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
598      <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 32, line 5</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 31, line 44</em></th><td></td></tr>
599      <tr><td class="lineno" valign="top"></td><td class="left">                 Mail Extensions (MIME) Part Five: Conformance Criteria</td><td> </td><td class="right">                 Mail Extensions (MIME) Part Five: Conformance Criteria</td><td class="lineno" valign="top"></td></tr>
600      <tr><td class="lineno" valign="top"></td><td class="left">                 and Examples", RFC 2049, November 1996.</td><td> </td><td class="right">                 and Examples", RFC 2049, November 1996.</td><td class="lineno" valign="top"></td></tr>
601      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
602      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2068]     Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and</td><td> </td><td class="right">   [RFC2068]     Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and</td><td class="lineno" valign="top"></td></tr>
603      <tr><td class="lineno" valign="top"></td><td class="left">                 T. Berners-Lee, "Hypertext Transfer Protocol --</td><td> </td><td class="right">                 T. Berners-Lee, "Hypertext Transfer Protocol --</td><td class="lineno" valign="top"></td></tr>
604      <tr><td class="lineno" valign="top"></td><td class="left">                 HTTP/1.1", RFC 2068, January 1997.</td><td> </td><td class="right">                 HTTP/1.1", RFC 2068, January 1997.</td><td class="lineno" valign="top"></td></tr>
605      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
606      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2076]     Palme, J., "Common Internet Message Headers", RFC 2076,</td><td> </td><td class="right">   [RFC2076]     Palme, J., "Common Internet Message Headers", RFC 2076,</td><td class="lineno" valign="top"></td></tr>
607      <tr><td class="lineno" valign="top"></td><td class="left">                 February 1997.</td><td> </td><td class="right">                 February 1997.</td><td class="lineno" valign="top"></td></tr>
608      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
609      <tr><td><a name="diff0033" /></td></tr>
610      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">[RFC2183]     Troost, R., Dorner, S., and K. Moore, "Communicating</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
611      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 Presentation Information in Internet Messages: The</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
612      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 Content-Disposition Header Field", RFC 2183,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
613      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 August 1997.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
614      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
615      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2277]     Alvestrand, H., "IETF Policy on Character Sets and</td><td> </td><td class="right">   [RFC2277]     Alvestrand, H., "IETF Policy on Character Sets and</td><td class="lineno" valign="top"></td></tr>
616      <tr><td class="lineno" valign="top"></td><td class="left">                 Languages", BCP 18, RFC 2277, January 1998.</td><td> </td><td class="right">                 Languages", BCP 18, RFC 2277, January 1998.</td><td class="lineno" valign="top"></td></tr>
617      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
618      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2295]     Holtman, K. and A. Mutz, "Transparent Content</td><td> </td><td class="right">   [RFC2295]     Holtman, K. and A. Mutz, "Transparent Content</td><td class="lineno" valign="top"></td></tr>
619      <tr><td class="lineno" valign="top"></td><td class="left">                 Negotiation in HTTP", RFC 2295, March 1998.</td><td> </td><td class="right">                 Negotiation in HTTP", RFC 2295, March 1998.</td><td class="lineno" valign="top"></td></tr>
620      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
621      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2388]     Masinter, L., "Returning Values from Forms:  multipart/</td><td> </td><td class="right">   [RFC2388]     Masinter, L., "Returning Values from Forms:  multipart/</td><td class="lineno" valign="top"></td></tr>
622      <tr><td class="lineno" valign="top"></td><td class="left">                 form-data", RFC 2388, August 1998.</td><td> </td><td class="right">                 form-data", RFC 2388, August 1998.</td><td class="lineno" valign="top"></td></tr>
623      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
624      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2557]     Palme, F., Hopmann, A., Shelness, N., and E. Stefferud,</td><td> </td><td class="right">   [RFC2557]     Palme, F., Hopmann, A., Shelness, N., and E. Stefferud,</td><td class="lineno" valign="top"></td></tr>
625      <tr><td class="lineno" valign="top"></td><td class="left">                 "MIME Encapsulation of Aggregate Documents, such as</td><td> </td><td class="right">                 "MIME Encapsulation of Aggregate Documents, such as</td><td class="lineno" valign="top"></td></tr>
626      <tr><td class="lineno" valign="top"></td><td class="left">                 HTML (MHTML)", RFC 2557, March 1999.</td><td> </td><td class="right">                 HTML (MHTML)", RFC 2557, March 1999.</td><td class="lineno" valign="top"></td></tr>
627      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
628      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2616]     Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,</td><td> </td><td class="right">   [RFC2616]     Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,</td><td class="lineno" valign="top"></td></tr>
629      <tr><td class="lineno" valign="top"></td><td class="left">                 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext</td><td> </td><td class="right">                 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext</td><td class="lineno" valign="top"></td></tr>
630      <tr><td class="lineno" valign="top"></td><td class="left">                 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.</td><td> </td><td class="right">                 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.</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">   [RFC3629]     Yergeau, F., "UTF-8, a transformation format of ISO</td><td> </td><td class="right">   [RFC3629]     Yergeau, F., "UTF-8, a transformation format of ISO</td><td class="lineno" valign="top"></td></tr>
633      <tr><td><a name="diff0034" /></td></tr>
634      <tr><td class="lineno" valign="top"></td><td class="lblock">                 10646", <span class="delete">RFC 3629, STD 63</span>, November 2003.</td><td> </td><td class="rblock">                 10646", <span class="insert">STD 63, RFC 3629</span>, November 2003.</td><td class="lineno" valign="top"></td></tr>
635      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
636      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3864]     Klyne, G., Nottingham, M., and J. Mogul, "Registration</td><td> </td><td class="right">   [RFC3864]     Klyne, G., Nottingham, M., and J. Mogul, "Registration</td><td class="lineno" valign="top"></td></tr>
637      <tr><td class="lineno" valign="top"></td><td class="left">                 Procedures for Message Header Fields", BCP 90,</td><td> </td><td class="right">                 Procedures for Message Header Fields", BCP 90,</td><td class="lineno" valign="top"></td></tr>
638      <tr><td class="lineno" valign="top"></td><td class="left">                 RFC 3864, September 2004.</td><td> </td><td class="right">                 RFC 3864, September 2004.</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 class="lineno" valign="top"></td><td class="left">   [RFC4288]     Freed, N. and J. Klensin, "Media Type Specifications</td><td> </td><td class="right">   [RFC4288]     Freed, N. and J. Klensin, "Media Type Specifications</td><td class="lineno" valign="top"></td></tr>
641      <tr><td class="lineno" valign="top"></td><td class="left">                 and Registration Procedures", BCP 13, RFC 4288,</td><td> </td><td class="right">                 and Registration Procedures", BCP 13, RFC 4288,</td><td class="lineno" valign="top"></td></tr>
642      <tr><td class="lineno" valign="top"></td><td class="left">                 December 2005.</td><td> </td><td class="right">                 December 2005.</td><td class="lineno" valign="top"></td></tr>
643      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
644      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5226]     Narten, T. and H. Alvestrand, "Guidelines for Writing</td><td> </td><td class="right">   [RFC5226]     Narten, T. and H. Alvestrand, "Guidelines for Writing</td><td class="lineno" valign="top"></td></tr>
645      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
646      <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 35, line 27</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 35, line 16</em></th><td></td></tr>
647      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
648      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC1945] and [RFC2068] document protocol elements used by some</td><td> </td><td class="right">   [RFC1945] and [RFC2068] document protocol elements used by some</td><td class="lineno" valign="top"></td></tr>
649      <tr><td class="lineno" valign="top"></td><td class="left">   existing HTTP implementations, but not consistently and correctly</td><td> </td><td class="right">   existing HTTP implementations, but not consistently and correctly</td><td class="lineno" valign="top"></td></tr>
650      <tr><td class="lineno" valign="top"></td><td class="left">   across most HTTP/1.1 applications.  Implementors are advised to be</td><td> </td><td class="right">   across most HTTP/1.1 applications.  Implementors are advised to be</td><td class="lineno" valign="top"></td></tr>
651      <tr><td class="lineno" valign="top"></td><td class="left">   aware of these features, but cannot rely upon their presence in, or</td><td> </td><td class="right">   aware of these features, but cannot rely upon their presence in, or</td><td class="lineno" valign="top"></td></tr>
652      <tr><td class="lineno" valign="top"></td><td class="left">   interoperability with, other HTTP/1.1 applications.  Some of these</td><td> </td><td class="right">   interoperability with, other HTTP/1.1 applications.  Some of these</td><td class="lineno" valign="top"></td></tr>
653      <tr><td class="lineno" valign="top"></td><td class="left">   describe proposed experimental features, and some describe features</td><td> </td><td class="right">   describe proposed experimental features, and some describe features</td><td class="lineno" valign="top"></td></tr>
654      <tr><td class="lineno" valign="top"></td><td class="left">   that experimental deployment found lacking that are now addressed in</td><td> </td><td class="right">   that experimental deployment found lacking that are now addressed in</td><td class="lineno" valign="top"></td></tr>
655      <tr><td class="lineno" valign="top"></td><td class="left">   the base HTTP/1.1 specification.</td><td> </td><td class="right">   the base HTTP/1.1 specification.</td><td class="lineno" valign="top"></td></tr>
656      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
657      <tr><td><a name="diff0035" /></td></tr>
658      <tr><td class="lineno" valign="top"></td><td class="lblock">   A number of other <span class="delete">headers,</span> such as Content-Disposition and Title,</td><td> </td><td class="rblock">   A number of other <span class="insert">header fields,</span> such as Content-Disposition and</td><td class="lineno" valign="top"></td></tr>
659      <tr><td class="lineno" valign="top"></td><td class="lblock">   from SMTP and MIME are also often implemented (see [RFC2076]).</td><td> </td><td class="rblock">   Title, from SMTP and MIME are also often implemented (see [RFC2076]).</td><td class="lineno" valign="top"></td></tr>
660      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
661      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">B.1.  Content-Disposition</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
662      <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>
663      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The "Content-Disposition" response-header field has been proposed as</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
664      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   a means for the origin server to suggest a default filename if the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
665      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   user requests that the content is saved to a file.  This usage is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
666      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   derived from the definition of Content-Disposition in [RFC2183].</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
667      <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>
668      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     content-disposition = "Content-Disposition" ":" OWS</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
669      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                           content-disposition-v</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
670      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     content-disposition-v = disposition-type</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
671      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                             *( OWS ";" OWS disposition-parm )</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
672      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     disposition-type = "attachment" / disp-extension-token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
673      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     disposition-parm = filename-parm / disp-extension-parm</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
674      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     filename-parm = "filename" "=" quoted-string</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
675      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     disp-extension-token = token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
676      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     disp-extension-parm = token "=" word</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
677      <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>
678      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   An example is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
679      <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>
680      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     Content-Disposition: attachment; filename="fname.ext"</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
681      <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>
682      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The receiving user agent SHOULD NOT respect any directory path</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
683      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   information present in the filename-parm parameter, which is the only</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
684      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   parameter believed to apply to HTTP implementations at this time.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
685      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The filename SHOULD be treated as a terminal component only.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
686      <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>
687      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If this header is used in a response with the application/</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
688      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   octet-stream content-type, the implied suggestion is that the user</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
689      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   agent should not display the response, but directly enter a "save</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
690      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response as..." dialog.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
691      <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>
692      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   See Section 8.2 for Content-Disposition security issues.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
693      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
694      <tr><td class="lineno" valign="top"></td><td class="left">Appendix C.  Changes from RFC 2616</td><td> </td><td class="right">Appendix C.  Changes from RFC 2616</td><td class="lineno" valign="top"></td></tr>
695      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
696      <tr><td class="lineno" valign="top"></td><td class="left">   Clarify contexts that charset is used in.  (Section 2.1)</td><td> </td><td class="right">   Clarify contexts that charset is used in.  (Section 2.1)</td><td class="lineno" valign="top"></td></tr>
697      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
698      <tr><td class="lineno" valign="top"></td><td class="left">   Remove base URI setting semantics for Content-Location due to poor</td><td> </td><td class="right">   Remove base URI setting semantics for Content-Location due to poor</td><td class="lineno" valign="top"></td></tr>
699      <tr><td class="lineno" valign="top"></td><td class="left">   implementation support, which was caused by too many broken servers</td><td> </td><td class="right">   implementation support, which was caused by too many broken servers</td><td class="lineno" valign="top"></td></tr>
700      <tr><td><a name="diff0036" /></td></tr>
701      <tr><td class="lineno" valign="top"></td><td class="lblock">   emitting bogus Content-Location <span class="delete">headers,</span> and also the potentially</td><td> </td><td class="rblock">   emitting bogus Content-Location <span class="insert">header fields,</span> and also the</td><td class="lineno" valign="top"></td></tr>
702      <tr><td class="lineno" valign="top"></td><td class="lblock">   undesirable effect of potentially breaking relative links in <span class="delete">content-</span></td><td> </td><td class="rblock">   potentially undesirable effect of potentially breaking relative links</td><td class="lineno" valign="top"></td></tr>
703      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   negotiated</span> resources.  (Section 6.7)</td><td> </td><td class="rblock">   in <span class="insert">content-negotiated</span> resources.  (Section 6.7)</td><td class="lineno" valign="top"></td></tr>
704      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
705      <tr><td class="lineno" valign="top"></td><td class="left">   Remove reference to non-existant identity transfer-coding value</td><td> </td><td class="right">   Remove reference to non-existant identity transfer-coding value</td><td class="lineno" valign="top"></td></tr>
706      <tr><td class="lineno" valign="top"></td><td class="left">   tokens.  (Appendix A.5)</td><td> </td><td class="right">   tokens.  (Appendix A.5)</td><td class="lineno" valign="top"></td></tr>
707      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
708      <tr><td class="lineno" valign="top"></td><td class="left">Appendix D.  Collected ABNF</td><td> </td><td class="right">Appendix D.  Collected ABNF</td><td class="lineno" valign="top"></td></tr>
709      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
710      <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>
711      <tr><td class="lineno" valign="top"></td><td class="left">   Accept-Charset = "Accept-Charset:" OWS Accept-Charset-v</td><td> </td><td class="right">   Accept-Charset = "Accept-Charset:" OWS Accept-Charset-v</td><td class="lineno" valign="top"></td></tr>
712      <tr><td class="lineno" valign="top"></td><td class="left">   Accept-Charset-v = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="</td><td> </td><td class="right">   Accept-Charset-v = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="</td><td class="lineno" valign="top"></td></tr>
713      <tr><td class="lineno" valign="top"></td><td class="left">    qvalue ] *( OWS "," [ OWS ( charset / "*" ) [ OWS ";" OWS "q="</td><td> </td><td class="right">    qvalue ] *( OWS "," [ OWS ( charset / "*" ) [ OWS ";" OWS "q="</td><td class="lineno" valign="top"></td></tr>
714      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
715      <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 37, line 28</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 36, line 32</em></th><td></td></tr>
716      <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>
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">   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>
719      <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>
720      <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>
721      <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>
722      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
723      <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>
724      <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>
725      <tr><td class="lineno" valign="top"></td><td class="left">   content-coding = token</td><td> </td><td class="right">   content-coding = token</td><td class="lineno" valign="top"></td></tr>
726      <tr><td><a name="diff0037" /></td></tr>
727      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">content-disposition = "Content-Disposition:" OWS</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
728      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">    content-disposition-v</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
729      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   content-disposition-v = disposition-type *( OWS ";" OWS</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
730      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">    disposition-parm )</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
731      <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>
732      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   disp-extension-parm = token "=" word</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
733      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   disp-extension-token = token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
734      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   disposition-parm = filename-parm / disp-extension-parm</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
735      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   disposition-type = "attachment" / disp-extension-token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
736      <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>
737      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   filename-parm = "filename=" quoted-string</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
738      <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>
739      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   header-field = &lt;header-field, defined in [Part1], Section 3.2&gt;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
740      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></