source: draft-ietf-httpbis/diffs/draft-ietf-httpbis-p3-payload-17-from-16.diff.html

Last change on this file was 1467, checked in by julian.reschke@…, 8 years ago

Prepare publication of -17.

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html; charset=iso-8859-1
File size: 211.5 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-16.txt - draft-ietf-httpbis-p3-payload-17.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-16.txt&nbsp;</th><th> </th><th>&nbsp;draft-ietf-httpbis-p3-payload-17.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                                                     Adobe</td><td> </td><td class="right">Internet-Draft                                                     Adobe</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 25, 2012</span>                                      J. Mogul</td><td> </td><td class="rblock">Expires: <span class="insert">May 3, 2012      </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</td><td> </td><td class="right">                                                                   Adobe</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 24</span>, 2011</td><td> </td><td class="rblock">                                                        <span class="insert">October 31</span>, 2011</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">6</span></td><td> </td><td class="rblock">                    draft-ietf-httpbis-p3-payload-1<span class="insert">7</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, hypertext information</td><td> </td><td class="right">   protocol for distributed, collaborative, hypertext 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.</td><td> </td><td class="right">   "HTTP/1.1" and, taken together, obsoletes RFC 2616.</td><td class="lineno" valign="top"></td></tr>
74      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
75      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
76      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 1, line 49</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 1, line 49</em></th><td></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), which is archived at</td><td> </td><td class="right">   group mailing list (ietf-http-wg@w3.org), which is archived at</td><td class="lineno" valign="top"></td></tr>
80      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://lists.w3.org/Archives/Public/ietf-http-wg/&gt;.</td><td> </td><td class="right">   &lt;http://lists.w3.org/Archives/Public/ietf-http-wg/&gt;.</td><td class="lineno" valign="top"></td></tr>
81      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
82      <tr><td class="lineno" valign="top"></td><td class="left">   The current issues list is at</td><td> </td><td class="right">   The current issues list is at</td><td class="lineno" valign="top"></td></tr>
83      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://tools.ietf.org/wg/httpbis/trac/report/3&gt; and related</td><td> </td><td class="right">   &lt;http://tools.ietf.org/wg/httpbis/trac/report/3&gt; and related</td><td class="lineno" valign="top"></td></tr>
84      <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>
85      <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>
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><a name="diff0004" /></td></tr>
88      <tr><td class="lineno" valign="top"></td><td class="lblock">   The changes in this draft are summarized in Appendix E.1<span class="delete">7</span>.</td><td> </td><td class="rblock">   The changes in this draft are summarized in Appendix E.1<span class="insert">8</span>.</td><td class="lineno" valign="top"></td></tr>
89      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
90      <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>
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">   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>
93      <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>
94      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
95      <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>
96      <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>
97      <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>
98      <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>
99      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
100      <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>
101      <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>
102      <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>
103      <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>
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><a name="diff0005" /></td></tr>
106      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">February 25</span>, 2012.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">May 3</span>, 2012.</td><td class="lineno" valign="top"></td></tr>
107      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
108      <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>
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">   Copyright (c) 2011 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2011 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
111      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
112      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
113      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
114      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
115      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
116      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
117      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
118      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 3, line 4</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 3, line 4</em></th><td></td></tr>
119      <tr><td class="lineno" valign="top"></td><td class="left">   the copyright in such materials, this document may not be modified</td><td> </td><td class="right">   the copyright in such materials, this document may not be modified</td><td class="lineno" valign="top"></td></tr>
120      <tr><td class="lineno" valign="top"></td><td class="left">   outside the IETF Standards Process, and derivative works of it may</td><td> </td><td class="right">   outside the IETF Standards Process, and derivative works of it may</td><td class="lineno" valign="top"></td></tr>
121      <tr><td class="lineno" valign="top"></td><td class="left">   not be created outside the IETF Standards Process, except to format</td><td> </td><td class="right">   not be created outside the IETF Standards Process, except to format</td><td class="lineno" valign="top"></td></tr>
122      <tr><td class="lineno" valign="top"></td><td class="left">   it for publication as an RFC or to translate it into languages other</td><td> </td><td class="right">   it for publication as an RFC or to translate it into languages other</td><td class="lineno" valign="top"></td></tr>
123      <tr><td class="lineno" valign="top"></td><td class="left">   than English.</td><td> </td><td class="right">   than English.</td><td class="lineno" valign="top"></td></tr>
124      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
125      <tr><td class="lineno" valign="top"></td><td class="left">Table of Contents</td><td> </td><td class="right">Table of Contents</td><td class="lineno" valign="top"></td></tr>
126      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
127      <tr><td class="lineno" valign="top"></td><td class="left">   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
128      <tr><td class="lineno" valign="top"></td><td class="left">     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
129      <tr><td><a name="diff0006" /></td></tr>
130      <tr><td class="lineno" valign="top"></td><td class="lblock">     1.2.  <span class="delete">Requirements . . . . . . . . .</span> . . . . . . . . . . . . . .  5</td><td> </td><td class="rblock">     1.2.  <span class="insert">Conformance and Error Handling</span> . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
131      <tr><td class="lineno" valign="top"></td><td class="left">     1.3.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">     1.3.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
132      <tr><td class="lineno" valign="top"></td><td class="left">       1.3.1.  Core Rules . . . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">       1.3.1.  Core Rules . . . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
133      <tr><td class="lineno" valign="top"></td><td class="left">       1.3.2.  ABNF Rules defined in other Parts of the</td><td> </td><td class="right">       1.3.2.  ABNF Rules defined in other Parts of the</td><td class="lineno" valign="top"></td></tr>
134      <tr><td class="lineno" valign="top"></td><td class="left">               Specification  . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">               Specification  . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
135      <tr><td class="lineno" valign="top"></td><td class="left">   2.  Protocol Parameters  . . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">   2.  Protocol Parameters  . . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
136      <tr><td class="lineno" valign="top"></td><td class="left">     2.1.  Character Encodings (charset)  . . . . . . . . . . . . . .  6</td><td> </td><td class="right">     2.1.  Character Encodings (charset)  . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
137      <tr><td class="lineno" valign="top"></td><td class="left">     2.2.  Content Codings  . . . . . . . . . . . . . . . . . . . . .  7</td><td> </td><td class="right">     2.2.  Content Codings  . . . . . . . . . . . . . . . . . . . . .  7</td><td class="lineno" valign="top"></td></tr>
138      <tr><td class="lineno" valign="top"></td><td class="left">       2.2.1.  Content Coding Registry  . . . . . . . . . . . . . . .  8</td><td> </td><td class="right">       2.2.1.  Content Coding Registry  . . . . . . . . . . . . . . .  8</td><td class="lineno" valign="top"></td></tr>
139      <tr><td class="lineno" valign="top"></td><td class="left">     2.3.  Media Types  . . . . . . . . . . . . . . . . . . . . . . .  8</td><td> </td><td class="right">     2.3.  Media Types  . . . . . . . . . . . . . . . . . . . . . . .  8</td><td class="lineno" valign="top"></td></tr>
140      <tr><td class="lineno" valign="top"></td><td class="left">       2.3.1.  Canonicalization and Text Defaults . . . . . . . . . .  9</td><td> </td><td class="right">       2.3.1.  Canonicalization and Text Defaults . . . . . . . . . .  9</td><td class="lineno" valign="top"></td></tr>
141      <tr><td class="lineno" valign="top"></td><td class="left">       2.3.2.  Multipart Types  . . . . . . . . . . . . . . . . . . .  9</td><td> </td><td class="right">       2.3.2.  Multipart Types  . . . . . . . . . . . . . . . . . . .  9</td><td class="lineno" valign="top"></td></tr>
142      <tr><td class="lineno" valign="top"></td><td class="left">     2.4.  Language Tags  . . . . . . . . . . . . . . . . . . . . . . 10</td><td> </td><td class="right">     2.4.  Language Tags  . . . . . . . . . . . . . . . . . . . . . . 10</td><td class="lineno" valign="top"></td></tr>
143      <tr><td><a name="diff0007" /></td></tr>
144      <tr><td class="lineno" valign="top"></td><td class="lblock">   3.  Payload  . . . . . . . . . . . . . . . . . . . . . . . . . . . 1<span class="delete">0</span></td><td> </td><td class="rblock">   3.  Payload  . . . . . . . . . . . . . . . . . . . . . . . . . . . 1<span class="insert">1</span></td><td class="lineno" valign="top"></td></tr>
145      <tr><td class="lineno" valign="top"></td><td class="left">     3.1.  Payload Header Fields  . . . . . . . . . . . . . . . . . . 11</td><td> </td><td class="right">     3.1.  Payload Header Fields  . . . . . . . . . . . . . . . . . . 11</td><td class="lineno" valign="top"></td></tr>
146      <tr><td class="lineno" valign="top"></td><td class="left">     3.2.  Payload Body . . . . . . . . . . . . . . . . . . . . . . . 11</td><td> </td><td class="right">     3.2.  Payload Body . . . . . . . . . . . . . . . . . . . . . . . 11</td><td class="lineno" valign="top"></td></tr>
147      <tr><td class="lineno" valign="top"></td><td class="left">   4.  Representation . . . . . . . . . . . . . . . . . . . . . . . . 11</td><td> </td><td class="right">   4.  Representation . . . . . . . . . . . . . . . . . . . . . . . . 11</td><td class="lineno" valign="top"></td></tr>
148      <tr><td class="lineno" valign="top"></td><td class="left">     4.1.  Representation Header Fields . . . . . . . . . . . . . . . 12</td><td> </td><td class="right">     4.1.  Representation Header Fields . . . . . . . . . . . . . . . 12</td><td class="lineno" valign="top"></td></tr>
149      <tr><td class="lineno" valign="top"></td><td class="left">     4.2.  Representation Data  . . . . . . . . . . . . . . . . . . . 12</td><td> </td><td class="right">     4.2.  Representation Data  . . . . . . . . . . . . . . . . . . . 12</td><td class="lineno" valign="top"></td></tr>
150      <tr><td class="lineno" valign="top"></td><td class="left">   5.  Content Negotiation  . . . . . . . . . . . . . . . . . . . . . 13</td><td> </td><td class="right">   5.  Content Negotiation  . . . . . . . . . . . . . . . . . . . . . 13</td><td class="lineno" valign="top"></td></tr>
151      <tr><td class="lineno" valign="top"></td><td class="left">     5.1.  Server-driven Negotiation  . . . . . . . . . . . . . . . . 14</td><td> </td><td class="right">     5.1.  Server-driven Negotiation  . . . . . . . . . . . . . . . . 14</td><td class="lineno" valign="top"></td></tr>
152      <tr><td class="lineno" valign="top"></td><td class="left">     5.2.  Agent-driven Negotiation . . . . . . . . . . . . . . . . . 15</td><td> </td><td class="right">     5.2.  Agent-driven Negotiation . . . . . . . . . . . . . . . . . 15</td><td class="lineno" valign="top"></td></tr>
153      <tr><td class="lineno" valign="top"></td><td class="left">   6.  Header Field Definitions . . . . . . . . . . . . . . . . . . . 16</td><td> </td><td class="right">   6.  Header Field Definitions . . . . . . . . . . . . . . . . . . . 16</td><td class="lineno" valign="top"></td></tr>
154      <tr><td class="lineno" valign="top"></td><td class="left">     6.1.  Accept . . . . . . . . . . . . . . . . . . . . . . . . . . 16</td><td> </td><td class="right">     6.1.  Accept . . . . . . . . . . . . . . . . . . . . . . . . . . 16</td><td class="lineno" valign="top"></td></tr>
155      <tr><td class="lineno" valign="top"></td><td class="left">     6.2.  Accept-Charset . . . . . . . . . . . . . . . . . . . . . . 18</td><td> </td><td class="right">     6.2.  Accept-Charset . . . . . . . . . . . . . . . . . . . . . . 18</td><td class="lineno" valign="top"></td></tr>
156      <tr><td class="lineno" valign="top"></td><td class="left">     6.3.  Accept-Encoding  . . . . . . . . . . . . . . . . . . . . . 19</td><td> </td><td class="right">     6.3.  Accept-Encoding  . . . . . . . . . . . . . . . . . . . . . 19</td><td class="lineno" valign="top"></td></tr>
157      <tr><td class="lineno" valign="top"></td><td class="left">     6.4.  Accept-Language  . . . . . . . . . . . . . . . . . . . . . 20</td><td> </td><td class="right">     6.4.  Accept-Language  . . . . . . . . . . . . . . . . . . . . . 20</td><td class="lineno" valign="top"></td></tr>
158      <tr><td class="lineno" valign="top"></td><td class="left">     6.5.  Content-Encoding . . . . . . . . . . . . . . . . . . . . . 21</td><td> </td><td class="right">     6.5.  Content-Encoding . . . . . . . . . . . . . . . . . . . . . 21</td><td class="lineno" valign="top"></td></tr>
159      <tr><td class="lineno" valign="top"></td><td class="left">     6.6.  Content-Language . . . . . . . . . . . . . . . . . . . . . 22</td><td> </td><td class="right">     6.6.  Content-Language . . . . . . . . . . . . . . . . . . . . . 22</td><td class="lineno" valign="top"></td></tr>
160      <tr><td class="lineno" valign="top"></td><td class="left">     6.7.  Content-Location . . . . . . . . . . . . . . . . . . . . . 23</td><td> </td><td class="right">     6.7.  Content-Location . . . . . . . . . . . . . . . . . . . . . 23</td><td class="lineno" valign="top"></td></tr>
161      <tr><td><a name="diff0008" /></td></tr>
162      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.8.  Content-Type . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">24</span></td><td> </td><td class="rblock">     6.8.  Content-Type . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">25</span></td><td class="lineno" valign="top"></td></tr>
163      <tr><td class="lineno" valign="top"></td><td class="lblock">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="delete">24</span></td><td> </td><td class="rblock">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="insert">25</span></td><td class="lineno" valign="top"></td></tr>
164      <tr><td class="lineno" valign="top"></td><td class="left">     7.1.  Header Field Registration  . . . . . . . . . . . . . . . . 25</td><td> </td><td class="right">     7.1.  Header Field Registration  . . . . . . . . . . . . . . . . 25</td><td class="lineno" valign="top"></td></tr>
165      <tr><td class="lineno" valign="top"></td><td class="left">     7.2.  Content Coding Registry  . . . . . . . . . . . . . . . . . 25</td><td> </td><td class="right">     7.2.  Content Coding Registry  . . . . . . . . . . . . . . . . . 25</td><td class="lineno" valign="top"></td></tr>
166      <tr><td class="lineno" valign="top"></td><td class="left">   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 26</td><td> </td><td class="right">   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 26</td><td class="lineno" valign="top"></td></tr>
167      <tr><td class="lineno" valign="top"></td><td class="left">     8.1.  Privacy Issues Connected to Accept Header Fields . . . . . 26</td><td> </td><td class="right">     8.1.  Privacy Issues Connected to Accept Header Fields . . . . . 26</td><td class="lineno" valign="top"></td></tr>
168      <tr><td><a name="diff0009" /></td></tr>
169      <tr><td class="lineno" valign="top"></td><td class="lblock">   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 2<span class="delete">6</span></td><td> </td><td class="rblock">   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 2<span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
170      <tr><td class="lineno" valign="top"></td><td class="left">   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27</td><td> </td><td class="right">   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27</td><td class="lineno" valign="top"></td></tr>
171      <tr><td class="lineno" valign="top"></td><td class="left">     10.1. Normative References . . . . . . . . . . . . . . . . . . . 27</td><td> </td><td class="right">     10.1. Normative References . . . . . . . . . . . . . . . . . . . 27</td><td class="lineno" valign="top"></td></tr>
172      <tr><td><a name="diff0010" /></td></tr>
173      <tr><td class="lineno" valign="top"></td><td class="lblock">     10.2. Informative References . . . . . . . . . . . . . . . . . . 2<span class="delete">8</span></td><td> </td><td class="rblock">     10.2. Informative References . . . . . . . . . . . . . . . . . . 2<span class="insert">9</span></td><td class="lineno" valign="top"></td></tr>
174      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix A.  Differences between HTTP and MIME . . . . . . . . . . 30</td><td> </td><td class="right">   Appendix A.  Differences between HTTP and MIME . . . . . . . . . . 30</td><td class="lineno" valign="top"></td></tr>
175      <tr><td class="lineno" valign="top"></td><td class="left">     A.1.  MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 30</td><td> </td><td class="right">     A.1.  MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 30</td><td class="lineno" valign="top"></td></tr>
176      <tr><td><a name="diff0011" /></td></tr>
177      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 3<span class="delete">0</span></td><td> </td><td class="rblock">     A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 3<span class="insert">1</span></td><td class="lineno" valign="top"></td></tr>
178      <tr><td class="lineno" valign="top"></td><td class="left">     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 31</td><td> </td><td class="right">     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 31</td><td class="lineno" valign="top"></td></tr>
179      <tr><td class="lineno" valign="top"></td><td class="left">     A.4.  Introduction of Content-Encoding . . . . . . . . . . . . . 31</td><td> </td><td class="right">     A.4.  Introduction of Content-Encoding . . . . . . . . . . . . . 31</td><td class="lineno" valign="top"></td></tr>
180      <tr><td><a name="diff0012" /></td></tr>
181      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.5.  No Content-Transfer-Encoding . . . . . . . . . . . . . . . 3<span class="delete">1</span></td><td> </td><td class="rblock">     A.5.  No Content-Transfer-Encoding . . . . . . . . . . . . . . . 3<span class="insert">2</span></td><td class="lineno" valign="top"></td></tr>
182      <tr><td class="lineno" valign="top"></td><td class="left">     A.6.  Introduction of Transfer-Encoding  . . . . . . . . . . . . 32</td><td> </td><td class="right">     A.6.  Introduction of Transfer-Encoding  . . . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
183      <tr><td class="lineno" valign="top"></td><td class="left">     A.7.  MHTML and Line Length Limitations  . . . . . . . . . . . . 32</td><td> </td><td class="right">     A.7.  MHTML and Line Length Limitations  . . . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
184      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
185      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix B.  Additional Features . . . . . . . . . . . . . . . . . 32</td><td> </td><td class="right">   Appendix B.  Additional Features . . . . . . . . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
186      <tr><td><a name="diff0013" /></td></tr>
187      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix C.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 3<span class="delete">2</span></td><td> </td><td class="rblock">   Appendix C.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 3<span class="insert">3</span></td><td class="lineno" valign="top"></td></tr>
188      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 33</td><td> </td><td class="right">   Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 33</td><td class="lineno" valign="top"></td></tr>
189      <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>
190      <tr><td><a name="diff0014" /></td></tr>
191      <tr><td class="lineno" valign="top"></td><td class="lblock">                publication)  . . . . . . . . . . . . . . . . . . . . <span class="delete">34</span></td><td> </td><td class="rblock">                publication)  . . . . . . . . . . . . . . . . . . . . <span class="insert">35</span></td><td class="lineno" valign="top"></td></tr>
192      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.1.  Since RFC 2616 . . . . . . . . . . . . . . . . . . . . . . <span class="delete">34</span></td><td> </td><td class="rblock">     E.1.  Since RFC 2616 . . . . . . . . . . . . . . . . . . . . . . <span class="insert">35</span></td><td class="lineno" valign="top"></td></tr>
193      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.2.  Since draft-ietf-httpbis-p3-payload-00 . . . . . . . . . . <span class="delete">34</span></td><td> </td><td class="rblock">     E.2.  Since draft-ietf-httpbis-p3-payload-00 . . . . . . . . . . <span class="insert">35</span></td><td class="lineno" valign="top"></td></tr>
194      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.3.  Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . <span class="delete">35</span></td><td> </td><td class="rblock">     E.3.  Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . <span class="insert">36</span></td><td class="lineno" valign="top"></td></tr>
195      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.4.  Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . <span class="delete">35</span></td><td> </td><td class="rblock">     E.4.  Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . <span class="insert">36</span></td><td class="lineno" valign="top"></td></tr>
196      <tr><td class="lineno" valign="top"></td><td class="left">     E.5.  Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . 36</td><td> </td><td class="right">     E.5.  Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . 36</td><td class="lineno" valign="top"></td></tr>
197      <tr><td><a name="diff0015" /></td></tr>
198      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.6.  Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . <span class="delete">36</span></td><td> </td><td class="rblock">     E.6.  Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . <span class="insert">37</span></td><td class="lineno" valign="top"></td></tr>
199      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.7.  Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . <span class="delete">36</span></td><td> </td><td class="rblock">     E.7.  Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . <span class="insert">37</span></td><td class="lineno" valign="top"></td></tr>
200      <tr><td class="lineno" valign="top"></td><td class="left">     E.8.  Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . 37</td><td> </td><td class="right">     E.8.  Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . 37</td><td class="lineno" valign="top"></td></tr>
201      <tr><td><a name="diff0016" /></td></tr>
202      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.9.  Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . 3<span class="delete">7</span></td><td> </td><td class="rblock">     E.9.  Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . 3<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
203      <tr><td class="lineno" valign="top"></td><td class="left">     E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . 38</td><td> </td><td class="right">     E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . 38</td><td class="lineno" valign="top"></td></tr>
204      <tr><td class="lineno" valign="top"></td><td class="left">     E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . 38</td><td> </td><td class="right">     E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . 38</td><td class="lineno" valign="top"></td></tr>
205      <tr><td><a name="diff0017" /></td></tr>
206      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . <span class="delete">38</span></td><td> </td><td class="rblock">     E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . <span class="insert">39</span></td><td class="lineno" valign="top"></td></tr>
207      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.13. Since draft-ietf-httpbis-p3-payload-11 . . . . . . . . . . <span class="delete">39</span></td><td> </td><td class="rblock">     E.13. Since draft-ietf-httpbis-p3-payload-11 . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
208      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.14. Since draft-ietf-httpbis-p3-payload-12 . . . . . . . . . . <span class="delete">39</span></td><td> </td><td class="rblock">     E.14. Since draft-ietf-httpbis-p3-payload-12 . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
209      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.15. Since draft-ietf-httpbis-p3-payload-13 . . . . . . . . . . <span class="delete">39</span></td><td> </td><td class="rblock">     E.15. Since draft-ietf-httpbis-p3-payload-13 . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
210      <tr><td class="lineno" valign="top"></td><td class="left">     E.16. Since draft-ietf-httpbis-p3-payload-14 . . . . . . . . . . 40</td><td> </td><td class="right">     E.16. Since draft-ietf-httpbis-p3-payload-14 . . . . . . . . . . 40</td><td class="lineno" valign="top"></td></tr>
211      <tr><td class="lineno" valign="top"></td><td class="left">     E.17. Since draft-ietf-httpbis-p3-payload-15 . . . . . . . . . . 40</td><td> </td><td class="right">     E.17. Since draft-ietf-httpbis-p3-payload-15 . . . . . . . . . . 40</td><td class="lineno" valign="top"></td></tr>
212      <tr><td><a name="diff0018" /></td></tr>
213      <tr><td class="lineno" valign="top"></td><td class="lblock">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">40</span></td><td> </td><td class="rblock">     <span class="insert">E.18. Since draft-ietf-httpbis-p3-payload-16 . . . . . . . . . . 41</span></td><td class="lineno" valign="top"></td></tr>
214      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">41</span></td><td class="lineno" valign="top"></td></tr>
215      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
216      <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>
217      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
218      <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>
219      <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>
220      <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>
221      <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>
222      <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>
223      <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>
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"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
226      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 5, line 35</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 5, line 35</em></th><td></td></tr>
227      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
228      <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>
229      <tr><td class="lineno" valign="top"></td><td class="left">   played by participants in, and objects of, the HTTP communication.</td><td> </td><td class="right">   played by participants in, and objects of, the HTTP communication.</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">   content negotiation</td><td> </td><td class="right">   content negotiation</td><td class="lineno" valign="top"></td></tr>
232      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
233      <tr><td class="lineno" valign="top"></td><td class="left">      The mechanism for selecting the appropriate representation when</td><td> </td><td class="right">      The mechanism for selecting the appropriate representation when</td><td class="lineno" valign="top"></td></tr>
234      <tr><td class="lineno" valign="top"></td><td class="left">      servicing a request.  The representation in any response can be</td><td> </td><td class="right">      servicing a request.  The representation in any response can be</td><td class="lineno" valign="top"></td></tr>
235      <tr><td class="lineno" valign="top"></td><td class="left">      negotiated (including error responses).</td><td> </td><td class="right">      negotiated (including error responses).</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><a name="diff0019" /></td></tr>
238      <tr><td class="lineno" valign="top"></td><td class="lblock">1.2.  <span class="delete">Requirements</span></td><td> </td><td class="rblock">1.2.  <span class="insert">Conformance and Error Handling</span></td><td class="lineno" valign="top"></td></tr>
239      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
240      <tr><td class="lineno" valign="top"></td><td class="left">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td> </td><td class="right">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td class="lineno" valign="top"></td></tr>
241      <tr><td class="lineno" valign="top"></td><td class="left">   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td> </td><td class="right">   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td class="lineno" valign="top"></td></tr>
242      <tr><td class="lineno" valign="top"></td><td class="left">   document are to be interpreted as described in [RFC2119].</td><td> </td><td class="right">   document are to be interpreted as described in [RFC2119].</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><a name="diff0020" /></td></tr>
245      <tr><td class="lineno" valign="top"></td><td class="lblock">   An implementation is <span class="delete">not compliant</span> if it <span class="delete">fails to satisfy one or more</span></td><td> </td><td class="rblock">   <span class="insert">This document defines conformance criteria for several roles in HTTP</span></td><td class="lineno" valign="top"></td></tr>
246      <tr><td class="lineno" valign="top"></td><td class="lblock">   of the <span class="delete">"MUST" or "REQUIRED" level</span> requirements <span class="delete">for the protocols it</span></td><td> </td><td class="rblock"><span class="insert">   communication, including Senders, Recipients, Clients, Servers, User-</span></td><td class="lineno" valign="top"></td></tr>
247      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   implements.  An implementation</span> that <span class="delete">satisfies all the "MUST" or</span></td><td> </td><td class="rblock"><span class="insert">   Agents, Origin Servers, Intermediaries, Proxies and Gateways.  See</span></td><td class="lineno" valign="top"></td></tr>
248      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   "REQUIRED" level and all the "SHOULD" level</span> requirements <span class="delete">for its</span></td><td> </td><td class="rblock"><span class="insert">   Section 2 of [Part1] for definitions of these terms.</span></td><td class="lineno" valign="top"></td></tr>
249      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   protocols</span> is <span class="delete">said</span> to <span class="delete">be "unconditionally compliant"; one that</span></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
250      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   satisfies all</span> the <span class="delete">"MUST" level</span> requirements <span class="delete">but</span> not <span class="delete">all</span> the <span class="delete">"SHOULD"</span></td><td> </td><td class="rblock">   An implementation is <span class="insert">considered conformant</span> if it <span class="insert">complies with all</span> of</td><td class="lineno" valign="top"></td></tr>
251      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   level requirements</span> for <span class="delete">its protocols is said</span> to <span class="delete">be "conditionally</span></td><td> </td><td class="rblock">   the requirements <span class="insert">associated with its role(s).  Note</span> that <span class="insert">SHOULD-level</span></td><td class="lineno" valign="top"></td></tr>
252      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   compliant".</span></td><td> </td><td class="rblock">   requirements <span class="insert">are relevant here, unless one of the documented</span></td><td class="lineno" valign="top"></td></tr>
253      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   exceptions</span> is <span class="insert">applicable.</span></td><td class="lineno" valign="top"></td></tr>
254      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
255      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   This document also uses ABNF to define valid protocol elements</span></td><td class="lineno" valign="top"></td></tr>
256      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   (Section 1.3).  In addition</span> to the <span class="insert">prose</span> requirements <span class="insert">placed upon</span></td><td class="lineno" valign="top"></td></tr>
257      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   them, Senders MUST NOT generate protocol elements that are invalid.</span></td><td class="lineno" valign="top"></td></tr>
258      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
259      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Unless noted otherwise, Recipients MAY take steps to recover a usable</span></td><td class="lineno" valign="top"></td></tr>
260      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   protocol element from an invalid construct.  However, HTTP does</span> not</td><td class="lineno" valign="top"></td></tr>
261      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">define specific error handling mechanisms, except in cases where it</span></td><td class="lineno" valign="top"></td></tr>
262      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   has direct impact on security.  This is because different uses of</span> the</td><td class="lineno" valign="top"></td></tr>
263      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">protocol require different error handling strategies;</span> for <span class="insert">example, a</span></td><td class="lineno" valign="top"></td></tr>
264      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Web browser may wish to transparently recover from a response where</span></td><td class="lineno" valign="top"></td></tr>
265      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   the Location header field doesn't parse according to the ABNF,</span></td><td class="lineno" valign="top"></td></tr>
266      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   whereby in a systems control protocol using HTTP, this type of error</span></td><td class="lineno" valign="top"></td></tr>
267      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   recovery could lead</span> to <span class="insert">dangerous consequences.</span></td><td class="lineno" valign="top"></td></tr>
268      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
269      <tr><td class="lineno" valign="top"></td><td class="left">1.3.  Syntax Notation</td><td> </td><td class="right">1.3.  Syntax Notation</td><td class="lineno" valign="top"></td></tr>
270      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
271      <tr><td class="lineno" valign="top"></td><td class="left">   This specification uses the ABNF syntax defined in Section 1.2 of</td><td> </td><td class="right">   This specification uses the ABNF syntax defined in Section 1.2 of</td><td class="lineno" valign="top"></td></tr>
272      <tr><td class="lineno" valign="top"></td><td class="left">   [Part1] (which extends the syntax defined in [RFC5234] with a list</td><td> </td><td class="right">   [Part1] (which extends the syntax defined in [RFC5234] with a list</td><td class="lineno" valign="top"></td></tr>
273      <tr><td class="lineno" valign="top"></td><td class="left">   rule).  Appendix D shows the collected ABNF, with the list rule</td><td> </td><td class="right">   rule).  Appendix D shows the collected ABNF, with the list rule</td><td class="lineno" valign="top"></td></tr>
274      <tr><td class="lineno" valign="top"></td><td class="left">   expanded.</td><td> </td><td class="right">   expanded.</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 following core rules are included by reference, as defined in</td><td> </td><td class="right">   The following core rules are included by reference, as defined in</td><td class="lineno" valign="top"></td></tr>
277      <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>
278      <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>
279      <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>
280      <tr><td><a name="diff0021" /></td></tr>
281      <tr><td class="lineno" valign="top"></td><td class="lblock">   sequence of data), SP (space), VCHAR (any visible <span class="delete">USASCII character),</span></td><td> </td><td class="rblock">   sequence of data), SP (space), <span class="insert">and</span> VCHAR (any visible <span class="insert">US-ASCII</span></td><td class="lineno" valign="top"></td></tr>
282      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   and WSP (whitespace).</span></td><td> </td><td class="rblock"><span class="insert">   character).</span></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">1.3.1.  Core Rules</td><td> </td><td class="right">1.3.1.  Core Rules</td><td class="lineno" valign="top"></td></tr>
285      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
286      <tr><td class="lineno" valign="top"></td><td class="left">   The core rules below are defined in [Part1]:</td><td> </td><td class="right">   The core rules below are defined in [Part1]:</td><td class="lineno" valign="top"></td></tr>
287      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
288      <tr><td class="lineno" valign="top"></td><td class="left">     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>
289      <tr><td class="lineno" valign="top"></td><td class="left">     token          = &lt;token, defined in [Part1], Section 3.2.3&gt;</td><td> </td><td class="right">     token          = &lt;token, defined in [Part1], Section 3.2.3&gt;</td><td class="lineno" valign="top"></td></tr>
290      <tr><td class="lineno" valign="top"></td><td class="left">     word           = &lt;word, defined in [Part1], Section 3.2.3&gt;</td><td> </td><td class="right">     word           = &lt;word, defined in [Part1], Section 3.2.3&gt;</td><td class="lineno" valign="top"></td></tr>
291      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
292      <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>
293      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
294      <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>
295      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
296      <tr><td class="lineno" valign="top"></td><td class="left">     absolute-URI   = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;</td><td> </td><td class="right">     absolute-URI   = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;</td><td class="lineno" valign="top"></td></tr>
297      <tr><td class="lineno" valign="top"></td><td class="left">     partial-URI    = &lt;partial-URI, defined in [Part1], Section 2.7&gt;</td><td> </td><td class="right">     partial-URI    = &lt;partial-URI, defined in [Part1], Section 2.7&gt;</td><td class="lineno" valign="top"></td></tr>
298      <tr><td><a name="diff0022" /></td></tr>
299      <tr><td class="lineno" valign="top"></td><td class="lblock">     qvalue         = &lt;qvalue, defined in [Part1], Section <span class="delete">6.4</span>&gt;</td><td> </td><td class="rblock">     qvalue         = &lt;qvalue, defined in [Part1], Section <span class="insert">5.3</span>&gt;</td><td class="lineno" valign="top"></td></tr>
300      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
301      <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>
302      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
303      <tr><td class="lineno" valign="top"></td><td class="left">2.1.  Character Encodings (charset)</td><td> </td><td class="right">2.1.  Character Encodings (charset)</td><td class="lineno" valign="top"></td></tr>
304      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
305      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP uses charset names to indicate the character encoding of a</td><td> </td><td class="right">   HTTP uses charset names to indicate the character encoding of a</td><td class="lineno" valign="top"></td></tr>
306      <tr><td class="lineno" valign="top"></td><td class="left">   textual representation.</td><td> </td><td class="right">   textual representation.</td><td class="lineno" valign="top"></td></tr>
307      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
308      <tr><td class="lineno" valign="top"></td><td class="left">   A character encoding is identified by a case-insensitive token.  The</td><td> </td><td class="right">   A character encoding is identified by a case-insensitive token.  The</td><td class="lineno" valign="top"></td></tr>
309      <tr><td class="lineno" valign="top"></td><td class="left">   complete set of tokens is defined by the IANA Character Set registry</td><td> </td><td class="right">   complete set of tokens is defined by the IANA Character Set registry</td><td class="lineno" valign="top"></td></tr>
310      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
311      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 7, line 35</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 7, line 47</em></th><td></td></tr>
312      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
313      <tr><td class="lineno" valign="top"></td><td class="left">   All content-coding values are case-insensitive.  HTTP/1.1 uses</td><td> </td><td class="right">   All content-coding values are case-insensitive.  HTTP/1.1 uses</td><td class="lineno" valign="top"></td></tr>
314      <tr><td class="lineno" valign="top"></td><td class="left">   content-coding values in the Accept-Encoding (Section 6.3) and</td><td> </td><td class="right">   content-coding values in the Accept-Encoding (Section 6.3) and</td><td class="lineno" valign="top"></td></tr>
315      <tr><td class="lineno" valign="top"></td><td class="left">   Content-Encoding (Section 6.5) header fields.  Although the value</td><td> </td><td class="right">   Content-Encoding (Section 6.5) header fields.  Although the value</td><td class="lineno" valign="top"></td></tr>
316      <tr><td class="lineno" valign="top"></td><td class="left">   describes the content-coding, what is more important is that it</td><td> </td><td class="right">   describes the content-coding, what is more important is that it</td><td class="lineno" valign="top"></td></tr>
317      <tr><td class="lineno" valign="top"></td><td class="left">   indicates what decoding mechanism will be required to remove the</td><td> </td><td class="right">   indicates what decoding mechanism will be required to remove the</td><td class="lineno" valign="top"></td></tr>
318      <tr><td class="lineno" valign="top"></td><td class="left">   encoding.</td><td> </td><td class="right">   encoding.</td><td class="lineno" valign="top"></td></tr>
319      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
320      <tr><td class="lineno" valign="top"></td><td class="left">   compress</td><td> </td><td class="right">   compress</td><td class="lineno" valign="top"></td></tr>
321      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
322      <tr><td><a name="diff0023" /></td></tr>
323      <tr><td class="lineno" valign="top"></td><td class="lblock">      See Section <span class="delete">6.2</span>.2.1 of [Part1].</td><td> </td><td class="rblock">      See Section <span class="insert">5.1</span>.2.1 of [Part1].</td><td class="lineno" valign="top"></td></tr>
324      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
325      <tr><td class="lineno" valign="top"></td><td class="left">   deflate</td><td> </td><td class="right">   deflate</td><td class="lineno" valign="top"></td></tr>
326      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
327      <tr><td><a name="diff0024" /></td></tr>
328      <tr><td class="lineno" valign="top"></td><td class="lblock">      See Section <span class="delete">6.2</span>.2.2 of [Part1].</td><td> </td><td class="rblock">      See Section <span class="insert">5.1</span>.2.2 of [Part1].</td><td class="lineno" valign="top"></td></tr>
329      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
330      <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>
331      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
332      <tr><td><a name="diff0025" /></td></tr>
333      <tr><td class="lineno" valign="top"></td><td class="lblock">      See Section <span class="delete">6.2.2.3</span> of [Part1].</td><td> </td><td class="rblock">      See Section <span class="insert">5.1.2.3</span> of [Part1].</td><td class="lineno" valign="top"></td></tr>
334      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
335      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">identity</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
336      <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>
337      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      The default (identity) encoding; the use of no transformation</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
338      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      whatsoever.  This content-coding is used only in the Accept-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
339      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Encoding header field, and SHOULD NOT be used in the Content-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
340      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Encoding header field.</span></td><td> </td><td class="rblock"></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 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>
343      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
344      <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>
345      <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>
346      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
347      <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>
348      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
349      <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>
350      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
351      <tr><td class="lineno" valign="top"></td><td class="left">   o  Description</td><td> </td><td class="right">   o  Description</td><td class="lineno" valign="top"></td></tr>
352      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
353      <tr><td class="lineno" valign="top"></td><td class="left">   o  Pointer to specification text</td><td> </td><td class="right">   o  Pointer to specification text</td><td class="lineno" valign="top"></td></tr>
354      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
355      <tr><td class="lineno" valign="top"></td><td class="left">   Names of content codings MUST NOT overlap with names of transfer</td><td> </td><td class="right">   Names of content codings MUST NOT overlap with names of transfer</td><td class="lineno" valign="top"></td></tr>
356      <tr><td><a name="diff0026" /></td></tr>
357      <tr><td class="lineno" valign="top"></td><td class="lblock">   codings (Section <span class="delete">6.2</span> of [Part1]), unless the encoding transformation</td><td> </td><td class="rblock">   codings (Section <span class="insert">5.1</span> of [Part1]), unless the encoding transformation</td><td class="lineno" valign="top"></td></tr>
358      <tr><td class="lineno" valign="top"></td><td class="left">   is identical (as it is the case for the compression codings defined</td><td> </td><td class="right">   is identical (as it is the case for the compression codings defined</td><td class="lineno" valign="top"></td></tr>
359      <tr><td><a name="diff0027" /></td></tr>
360      <tr><td class="lineno" valign="top"></td><td class="lblock">   in Section <span class="delete">6.2</span>.2 of [Part1]).</td><td> </td><td class="rblock">   in Section <span class="insert">5.1</span>.2 of [Part1]).</td><td class="lineno" valign="top"></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">   Values to be added to this name space require a specification (see</td><td> </td><td class="right">   Values to be added to this name space require a specification (see</td><td class="lineno" valign="top"></td></tr>
363      <tr><td class="lineno" valign="top"></td><td class="left">   "Specification Required" in Section 4.1 of [RFC5226]), and MUST</td><td> </td><td class="right">   "Specification Required" in Section 4.1 of [RFC5226]), and MUST</td><td class="lineno" valign="top"></td></tr>
364      <tr><td class="lineno" valign="top"></td><td class="left">   conform to the purpose of content coding defined in this section.</td><td> </td><td class="right">   conform to the purpose of content coding defined in this section.</td><td class="lineno" valign="top"></td></tr>
365      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
366      <tr><td class="lineno" valign="top"></td><td class="left">   The registry itself is maintained at</td><td> </td><td class="right">   The registry itself is maintained at</td><td class="lineno" valign="top"></td></tr>
367      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-parameters&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-parameters&gt;.</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">2.3.  Media Types</td><td> </td><td class="right">2.3.  Media Types</td><td class="lineno" valign="top"></td></tr>
370      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
371      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
372      <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 11, line 21</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 11, line 29</em></th><td></td></tr>
373      <tr><td class="lineno" valign="top"></td><td class="left">3.1.  Payload Header Fields</td><td> </td><td class="right">3.1.  Payload Header Fields</td><td class="lineno" valign="top"></td></tr>
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">   HTTP header fields that specifically define the payload, rather than</td><td> </td><td class="right">   HTTP header fields that specifically define the payload, rather than</td><td class="lineno" valign="top"></td></tr>
376      <tr><td class="lineno" valign="top"></td><td class="left">   the associated representation, are referred to as "payload header</td><td> </td><td class="right">   the associated representation, are referred to as "payload header</td><td class="lineno" valign="top"></td></tr>
377      <tr><td class="lineno" valign="top"></td><td class="left">   fields".  The following payload header fields are defined by</td><td> </td><td class="right">   fields".  The following payload header fields are defined by</td><td class="lineno" valign="top"></td></tr>
378      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/1.1:</td><td> </td><td class="right">   HTTP/1.1:</td><td class="lineno" valign="top"></td></tr>
379      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
380      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+------------------------+</td><td> </td><td class="right">   +-------------------+------------------------+</td><td class="lineno" valign="top"></td></tr>
381      <tr><td class="lineno" valign="top"></td><td class="left">   | Header Field Name | Defined in...          |</td><td> </td><td class="right">   | Header Field Name | Defined in...          |</td><td class="lineno" valign="top"></td></tr>
382      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+------------------------+</td><td> </td><td class="right">   +-------------------+------------------------+</td><td class="lineno" valign="top"></td></tr>
383      <tr><td><a name="diff0028" /></td></tr>
384      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Content-Length    | Section <span class="delete">9</span>.2 of [Part1] |</td><td> </td><td class="rblock">   | Content-Length    | Section <span class="insert">8</span>.2 of [Part1] |</td><td class="lineno" valign="top"></td></tr>
385      <tr><td class="lineno" valign="top"></td><td class="left">   | Content-Range     | Section 5.2 of [Part5] |</td><td> </td><td class="right">   | Content-Range     | Section 5.2 of [Part5] |</td><td class="lineno" valign="top"></td></tr>
386      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+------------------------+</td><td> </td><td class="right">   +-------------------+------------------------+</td><td class="lineno" valign="top"></td></tr>
387      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
388      <tr><td class="lineno" valign="top"></td><td class="left">3.2.  Payload Body</td><td> </td><td class="right">3.2.  Payload Body</td><td class="lineno" valign="top"></td></tr>
389      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
390      <tr><td class="lineno" valign="top"></td><td class="left">   A payload body is only present in a message when a message-body is</td><td> </td><td class="right">   A payload body is only present in a message when a message-body is</td><td class="lineno" valign="top"></td></tr>
391      <tr><td class="lineno" valign="top"></td><td class="left">   present, as described in Section 3.3 of [Part1].  The payload body is</td><td> </td><td class="right">   present, as described in Section 3.3 of [Part1].  The payload body is</td><td class="lineno" valign="top"></td></tr>
392      <tr><td class="lineno" valign="top"></td><td class="left">   obtained from the message-body by decoding any Transfer-Encoding that</td><td> </td><td class="right">   obtained from the message-body by decoding any Transfer-Encoding that</td><td class="lineno" valign="top"></td></tr>
393      <tr><td class="lineno" valign="top"></td><td class="left">   might have been applied to ensure safe and proper transfer of the</td><td> </td><td class="right">   might have been applied to ensure safe and proper transfer of the</td><td class="lineno" valign="top"></td></tr>
394      <tr><td class="lineno" valign="top"></td><td class="left">   message.</td><td> </td><td class="right">   message.</td><td class="lineno" valign="top"></td></tr>
395      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
396      <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 15, line 16</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 15, line 24</em></th><td></td></tr>
397      <tr><td class="lineno" valign="top"></td><td class="left">       for multiple user's requests.</td><td> </td><td class="right">       for multiple user's requests.</td><td class="lineno" valign="top"></td></tr>
398      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
399      <tr><td class="lineno" valign="top"></td><td class="left">   Server-driven negotiation allows the user agent to specify its</td><td> </td><td class="right">   Server-driven negotiation allows the user agent to specify its</td><td class="lineno" valign="top"></td></tr>
400      <tr><td class="lineno" valign="top"></td><td class="left">   preferences, but it cannot expect responses to always honour them.</td><td> </td><td class="right">   preferences, but it cannot expect responses to always honour them.</td><td class="lineno" valign="top"></td></tr>
401      <tr><td class="lineno" valign="top"></td><td class="left">   For example, the origin server might not implement server-driven</td><td> </td><td class="right">   For example, the origin server might not implement server-driven</td><td class="lineno" valign="top"></td></tr>
402      <tr><td class="lineno" valign="top"></td><td class="left">   negotiation, or it might decide that sending a response that doesn't</td><td> </td><td class="right">   negotiation, or it might decide that sending a response that doesn't</td><td class="lineno" valign="top"></td></tr>
403      <tr><td class="lineno" valign="top"></td><td class="left">   conform to them is better than sending a 406 (Not Acceptable)</td><td> </td><td class="right">   conform to them is better than sending a 406 (Not Acceptable)</td><td class="lineno" valign="top"></td></tr>
404      <tr><td class="lineno" valign="top"></td><td class="left">   response.</td><td> </td><td class="right">   response.</td><td class="lineno" valign="top"></td></tr>
405      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
406      <tr><td class="lineno" valign="top"></td><td class="left">   Many of the mechanisms for expressing preferences use quality values</td><td> </td><td class="right">   Many of the mechanisms for expressing preferences use quality values</td><td class="lineno" valign="top"></td></tr>
407      <tr><td><a name="diff0029" /></td></tr>
408      <tr><td class="lineno" valign="top"></td><td class="lblock">   to declare relative preference.  See Section <span class="delete">6.4</span> of [Part1] for more</td><td> </td><td class="rblock">   to declare relative preference.  See Section <span class="insert">5.3</span> of [Part1] for more</td><td class="lineno" valign="top"></td></tr>
409      <tr><td class="lineno" valign="top"></td><td class="left">   information.</td><td> </td><td class="right">   information.</td><td class="lineno" valign="top"></td></tr>
410      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
411      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/1.1 includes the following header fields for enabling server-</td><td> </td><td class="right">   HTTP/1.1 includes the following header fields for enabling server-</td><td class="lineno" valign="top"></td></tr>
412      <tr><td class="lineno" valign="top"></td><td class="left">   driven negotiation through description of user agent capabilities and</td><td> </td><td class="right">   driven negotiation through description of user agent capabilities and</td><td class="lineno" valign="top"></td></tr>
413      <tr><td class="lineno" valign="top"></td><td class="left">   user preferences: Accept (Section 6.1), Accept-Charset (Section 6.2),</td><td> </td><td class="right">   user preferences: Accept (Section 6.1), Accept-Charset (Section 6.2),</td><td class="lineno" valign="top"></td></tr>
414      <tr><td class="lineno" valign="top"></td><td class="left">   Accept-Encoding (Section 6.3), Accept-Language (Section 6.4), and</td><td> </td><td class="right">   Accept-Encoding (Section 6.3), Accept-Language (Section 6.4), and</td><td class="lineno" valign="top"></td></tr>
415      <tr><td><a name="diff0030" /></td></tr>
416      <tr><td class="lineno" valign="top"></td><td class="lblock">   User-Agent (Section 9.<span class="delete">9</span> of [Part2]).  However, an origin server is</td><td> </td><td class="rblock">   User-Agent (Section 9.<span class="insert">10</span> of [Part2]).  However, an origin server is</td><td class="lineno" valign="top"></td></tr>
417      <tr><td class="lineno" valign="top"></td><td class="left">   not limited to these dimensions and MAY vary the response based on</td><td> </td><td class="right">   not limited to these dimensions and MAY vary the response based on</td><td class="lineno" valign="top"></td></tr>
418      <tr><td class="lineno" valign="top"></td><td class="left">   any aspect of the request, including aspects of the connection (e.g.,</td><td> </td><td class="right">   any aspect of the request, including aspects of the connection (e.g.,</td><td class="lineno" valign="top"></td></tr>
419      <tr><td class="lineno" valign="top"></td><td class="left">   IP address) or information within extension header fields not defined</td><td> </td><td class="right">   IP address) or information within extension header fields not defined</td><td class="lineno" valign="top"></td></tr>
420      <tr><td class="lineno" valign="top"></td><td class="left">   by this specification.</td><td> </td><td class="right">   by this specification.</td><td class="lineno" valign="top"></td></tr>
421      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
422      <tr><td class="lineno" valign="top"></td><td class="left">      Note: In practice, User-Agent based negotiation is fragile,</td><td> </td><td class="right">      Note: In practice, User-Agent based negotiation is fragile,</td><td class="lineno" valign="top"></td></tr>
423      <tr><td class="lineno" valign="top"></td><td class="left">      because new clients might not be recognized.</td><td> </td><td class="right">      because new clients might not be recognized.</td><td class="lineno" valign="top"></td></tr>
424      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
425      <tr><td class="lineno" valign="top"></td><td class="left">   The Vary header field (Section 3.5 of [Part6]) can be used to express</td><td> </td><td class="right">   The Vary header field (Section 3.5 of [Part6]) can be used to express</td><td class="lineno" valign="top"></td></tr>
426      <tr><td class="lineno" valign="top"></td><td class="left">   the parameters the server uses to select a representation that is</td><td> </td><td class="right">   the parameters the server uses to select a representation that is</td><td class="lineno" valign="top"></td></tr>
427      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
428      <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 16, line 50</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 17, line 10</em></th><td></td></tr>
429      <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>
430      <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>
431      <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>
432      <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>
433      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
434      <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>
435      <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>
436      <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>
437      <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>
438      <tr><td class="lineno" valign="top"></td><td class="left">   or user agent to indicate the relative degree of preference for that</td><td> </td><td class="right">   or user agent to indicate the relative degree of preference for that</td><td class="lineno" valign="top"></td></tr>
439      <tr><td><a name="diff0031" /></td></tr>
440      <tr><td class="lineno" valign="top"></td><td class="lblock">   media-range, using the qvalue scale from 0 to 1 (Section <span class="delete">6.4</span> of</td><td> </td><td class="rblock">   media-range, using the qvalue scale from 0 to 1 (Section <span class="insert">5.3</span> of</td><td class="lineno" valign="top"></td></tr>
441      <tr><td class="lineno" valign="top"></td><td class="left">   [Part1]).  The default value is q=1.</td><td> </td><td class="right">   [Part1]).  The default value is q=1.</td><td class="lineno" valign="top"></td></tr>
442      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
443      <tr><td class="lineno" valign="top"></td><td class="left">      Note: Use of the "q" parameter name to separate media type</td><td> </td><td class="right">      Note: Use of the "q" parameter name to separate media type</td><td class="lineno" valign="top"></td></tr>
444      <tr><td class="lineno" valign="top"></td><td class="left">      parameters from Accept extension parameters is due to historical</td><td> </td><td class="right">      parameters from Accept extension parameters is due to historical</td><td class="lineno" valign="top"></td></tr>
445      <tr><td class="lineno" valign="top"></td><td class="left">      practice.  Although this prevents any media type parameter named</td><td> </td><td class="right">      practice.  Although this prevents any media type parameter named</td><td class="lineno" valign="top"></td></tr>
446      <tr><td class="lineno" valign="top"></td><td class="left">      "q" from being used with a media range, such an event is believed</td><td> </td><td class="right">      "q" from being used with a media range, such an event is believed</td><td class="lineno" valign="top"></td></tr>
447      <tr><td class="lineno" valign="top"></td><td class="left">      to be unlikely given the lack of any "q" parameters in the IANA</td><td> </td><td class="right">      to be unlikely given the lack of any "q" parameters in the IANA</td><td class="lineno" valign="top"></td></tr>
448      <tr><td class="lineno" valign="top"></td><td class="left">      media type registry and the rare usage of any media type</td><td> </td><td class="right">      media type registry and the rare usage of any media type</td><td class="lineno" valign="top"></td></tr>
449      <tr><td class="lineno" valign="top"></td><td class="left">      parameters in Accept.  Future media types are discouraged from</td><td> </td><td class="right">      parameters in Accept.  Future media types are discouraged from</td><td class="lineno" valign="top"></td></tr>
450      <tr><td class="lineno" valign="top"></td><td class="left">      registering any parameter named "q".</td><td> </td><td class="right">      registering any parameter named "q".</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 class="lineno" valign="top"></td><td class="left">   The example</td><td> </td><td class="right">   The example</td><td class="lineno" valign="top"></td></tr>
453      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
454      <tr><td class="lineno" valign="top"></td><td class="left">     Accept: audio/*; q=0.2, audio/basic</td><td> </td><td class="right">     Accept: audio/*; q=0.2, audio/basic</td><td class="lineno" valign="top"></td></tr>
455      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
456      <tr><td class="lineno" valign="top"></td><td class="left">   SHOULD be interpreted as "I prefer audio/basic, but send me any audio</td><td> </td><td class="right">   SHOULD be interpreted as "I prefer audio/basic, but send me any audio</td><td class="lineno" valign="top"></td></tr>
457      <tr><td class="lineno" valign="top"></td><td class="left">   type if it is the best available after an 80% mark-down in quality".</td><td> </td><td class="right">   type if it is the best available after an 80% mark-down in quality".</td><td class="lineno" valign="top"></td></tr>
458      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
459      <tr><td><a name="diff0032" /></td></tr>
460      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">If no</span> Accept header field <span class="delete">is present, then it is assumed</span> that the</td><td> </td><td class="rblock">   <span class="insert">A request without any</span> Accept header field <span class="insert">implies</span> that the <span class="insert">user agent</span></td><td class="lineno" valign="top"></td></tr>
461      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">client accepts all</span> media <span class="delete">types.</span>  If an Accept header field is present</td><td> </td><td class="rblock"><span class="insert">   will accept any</span> media <span class="insert">type in response.</span>  If an Accept header field is</td><td class="lineno" valign="top"></td></tr>
462      <tr><td class="lineno" valign="top"></td><td class="lblock">   in a <span class="delete">request, but</span> the <span class="delete">server cannot send a</span> response <span class="delete">which</span> is</td><td> </td><td class="rblock">   present in a <span class="insert">request and none of the available representations for</span></td><td class="lineno" valign="top"></td></tr>
463      <tr><td class="lineno" valign="top"></td><td class="lblock">   acceptable, <span class="delete">then</span> the server <span class="delete">can</span> either <span class="delete">send a response in another</span></td><td> </td><td class="rblock">   the response <span class="insert">have a media type that</span> is <span class="insert">listed as</span> acceptable, the</td><td class="lineno" valign="top"></td></tr>
464      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   format, or</span> a 406 (Not Acceptable) <span class="delete">response.</span></td><td> </td><td class="rblock">   <span class="insert">origin</span> server <span class="insert">MAY</span> either <span class="insert">honor the Accept header field by sending</span> a</td><td class="lineno" valign="top"></td></tr>
465      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   406 (Not Acceptable) <span class="insert">response or disregard the Accept header field by</span></td><td class="lineno" valign="top"></td></tr>
466      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   treating the response as if it is not subject to content negotiation.</span></td><td class="lineno" valign="top"></td></tr>
467      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
468      <tr><td class="lineno" valign="top"></td><td class="left">   A more elaborate example is</td><td> </td><td class="right">   A more elaborate example is</td><td class="lineno" valign="top"></td></tr>
469      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
470      <tr><td class="lineno" valign="top"></td><td class="left">     Accept: text/plain; q=0.5, text/html,</td><td> </td><td class="right">     Accept: text/plain; q=0.5, text/html,</td><td class="lineno" valign="top"></td></tr>
471      <tr><td class="lineno" valign="top"></td><td class="left">             text/x-dvi; q=0.8, text/x-c</td><td> </td><td class="right">             text/x-dvi; q=0.8, text/x-c</td><td class="lineno" valign="top"></td></tr>
472      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
473      <tr><td class="lineno" valign="top"></td><td class="left">   Verbally, this would be interpreted as "text/html and text/x-c are</td><td> </td><td class="right">   Verbally, this would be interpreted as "text/html and text/x-c are</td><td class="lineno" valign="top"></td></tr>
474      <tr><td class="lineno" valign="top"></td><td class="left">   the preferred media types, but if they do not exist, then send the</td><td> </td><td class="right">   the preferred media types, but if they do not exist, then send the</td><td class="lineno" valign="top"></td></tr>
475      <tr><td class="lineno" valign="top"></td><td class="left">   text/x-dvi representation, and if that does not exist, send the text/</td><td> </td><td class="right">   text/x-dvi representation, and if that does not exist, send the text/</td><td class="lineno" valign="top"></td></tr>
476      <tr><td class="lineno" valign="top"></td><td class="left">   plain representation".</td><td> </td><td class="right">   plain representation".</td><td class="lineno" valign="top"></td></tr>
477      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
478      <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 19, line 6</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 19, line 16</em></th><td></td></tr>
479      <tr><td class="lineno" valign="top"></td><td class="left">   value is q=1.  An example is</td><td> </td><td class="right">   value is q=1.  An example is</td><td class="lineno" valign="top"></td></tr>
480      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
481      <tr><td class="lineno" valign="top"></td><td class="left">     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>
482      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
483      <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>
484      <tr><td class="lineno" valign="top"></td><td class="left">   matches every character encoding which is not mentioned elsewhere in</td><td> </td><td class="right">   matches every character encoding which is not mentioned elsewhere in</td><td class="lineno" valign="top"></td></tr>
485      <tr><td class="lineno" valign="top"></td><td class="left">   the Accept-Charset field.  If no "*" is present in an Accept-Charset</td><td> </td><td class="right">   the Accept-Charset field.  If no "*" is present in an Accept-Charset</td><td class="lineno" valign="top"></td></tr>
486      <tr><td class="lineno" valign="top"></td><td class="left">   field, then all character encodings not explicitly mentioned get a</td><td> </td><td class="right">   field, then all character encodings not explicitly mentioned get a</td><td class="lineno" valign="top"></td></tr>
487      <tr><td class="lineno" valign="top"></td><td class="left">   quality value of 0.</td><td> </td><td class="right">   quality value of 0.</td><td class="lineno" valign="top"></td></tr>
488      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
489      <tr><td><a name="diff0033" /></td></tr>
490      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">If no</span> Accept-Charset header field <span class="delete">is present, the default is</span> that any</td><td> </td><td class="rblock">   <span class="insert">A request without any</span> Accept-Charset header field <span class="insert">implies</span> that <span class="insert">the</span></td><td class="lineno" valign="top"></td></tr>
491      <tr><td class="lineno" valign="top"></td><td class="lblock">   character encoding <span class="delete">is acceptable.</span>  If an Accept-Charset header field</td><td> </td><td class="rblock"><span class="insert">   user agent will accept</span> any character encoding <span class="insert">in response.</span>  If an</td><td class="lineno" valign="top"></td></tr>
492      <tr><td class="lineno" valign="top"></td><td class="lblock">   is present in a <span class="delete">request, but</span> the <span class="delete">server cannot send a</span> response <span class="delete">which</span></td><td> </td><td class="rblock">   Accept-Charset header field is present in a <span class="insert">request and none of the</span></td><td class="lineno" valign="top"></td></tr>
493      <tr><td class="lineno" valign="top"></td><td class="lblock">   is acceptable, <span class="delete">then</span> the server <span class="delete">can</span> either <span class="delete">use another character</span></td><td> </td><td class="rblock"><span class="insert">   available representations for</span> the response <span class="insert">have a character encoding</span></td><td class="lineno" valign="top"></td></tr>
494      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   encoding, or send</span> a 406 (Not Acceptable) <span class="delete">response.</span></td><td> </td><td class="rblock"><span class="insert">   that</span> is <span class="insert">listed as</span> acceptable, the <span class="insert">origin</span> server <span class="insert">MAY</span> either <span class="insert">honor the</span></td><td class="lineno" valign="top"></td></tr>
495      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Accept-Charset header field by sending</span> a 406 (Not Acceptable)</td><td class="lineno" valign="top"></td></tr>
496      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">response or disregard the Accept-Charset header field by treating the</span></td><td class="lineno" valign="top"></td></tr>
497      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   response as if it is not subject to content negotiation.</span></td><td class="lineno" valign="top"></td></tr>
498      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
499      <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>
500      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
501      <tr><td class="lineno" valign="top"></td><td class="left">   The "Accept-Encoding" header field can be used by user agents to</td><td> </td><td class="right">   The "Accept-Encoding" header field can be used by user agents to</td><td class="lineno" valign="top"></td></tr>
502      <tr><td class="lineno" valign="top"></td><td class="left">   indicate what response content-codings (Section 2.2) are acceptable</td><td> </td><td class="right">   indicate what response content-codings (Section 2.2) are acceptable</td><td class="lineno" valign="top"></td></tr>
503      <tr><td><a name="diff0034" /></td></tr>
504      <tr><td class="lineno" valign="top"></td><td class="lblock">   in the response.</td><td> </td><td class="rblock">   in the response.  <span class="insert">An "identity" token is used as a synonym for "no</span></td><td class="lineno" valign="top"></td></tr>
505      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   encoding" in order to communicate when no encoding is preferred.</span></td><td class="lineno" valign="top"></td></tr>
506      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
507      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Encoding  = #( codings [ OWS ";" OWS "q=" qvalue ] )</td><td> </td><td class="right">     Accept-Encoding  = #( codings [ OWS ";" OWS "q=" qvalue ] )</td><td class="lineno" valign="top"></td></tr>
508      <tr><td><a name="diff0035" /></td></tr>
509      <tr><td class="lineno" valign="top"></td><td class="lblock">     codings          = <span class="delete">( content-coding / "*" )</span></td><td> </td><td class="rblock">     codings          = <span class="insert">content-coding / "identity" / "*"</span></td><td class="lineno" valign="top"></td></tr>
510      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
511      <tr><td class="lineno" valign="top"></td><td class="left">   Each codings value MAY be given an associated quality value which</td><td> </td><td class="right">   Each codings value MAY be given an associated quality value which</td><td class="lineno" valign="top"></td></tr>
512      <tr><td class="lineno" valign="top"></td><td class="left">   represents the preference for that encoding.  The default value is</td><td> </td><td class="right">   represents the preference for that encoding.  The default value is</td><td class="lineno" valign="top"></td></tr>
513      <tr><td class="lineno" valign="top"></td><td class="left">   q=1.</td><td> </td><td class="right">   q=1.</td><td class="lineno" valign="top"></td></tr>
514      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
515      <tr><td><a name="diff0036" /></td></tr>
516      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Examples of its use are:</span></td><td> </td><td class="rblock">   <span class="insert">For example,</span></td><td class="lineno" valign="top"></td></tr>
517      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
518      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Encoding: compress, gzip</td><td> </td><td class="right">     Accept-Encoding: compress, gzip</td><td class="lineno" valign="top"></td></tr>
519      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Encoding:</td><td> </td><td class="right">     Accept-Encoding:</td><td class="lineno" valign="top"></td></tr>
520      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Encoding: *</td><td> </td><td class="right">     Accept-Encoding: *</td><td class="lineno" valign="top"></td></tr>
521      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Encoding: compress;q=0.5, gzip;q=1.0</td><td> </td><td class="right">     Accept-Encoding: compress;q=0.5, gzip;q=1.0</td><td class="lineno" valign="top"></td></tr>
522      <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0</td><td> </td><td class="right">     Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0</td><td class="lineno" valign="top"></td></tr>
523      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
524      <tr><td><a name="diff0037" /></td></tr>
525      <tr><td class="lineno" valign="top"></td><td class="lblock">   A server tests whether a content-coding is acceptable, according to</td><td> </td><td class="rblock">   A server tests whether a content-coding <span class="insert">for a given representation</span> is</td><td class="lineno" valign="top"></td></tr>
526      <tr><td class="lineno" valign="top"></td><td class="lblock">   an Accept-Encoding field, using these rules:</td><td> </td><td class="rblock">   acceptable, according to an Accept-Encoding field, using these rules:</td><td class="lineno" valign="top"></td></tr>
527      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
528      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">1.  If the content-coding is one of the content-codings listed in the</span></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">       Accept-Encoding field, then it is acceptable, unless it is</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">       accompanied by a qvalue of 0.  (As defined in Section 6.4 of</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">       [Part1], a qvalue of 0 means "not acceptable".)</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="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
533      <tr><td><a name="diff0038" /></td></tr>
534      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">2</span>.  The special "*" symbol in an Accept-Encoding field matches any</td><td> </td><td class="rblock">   <span class="insert">1</span>.  The special "*" symbol in an Accept-Encoding field matches any</td><td class="lineno" valign="top"></td></tr>
535      <tr><td class="lineno" valign="top"></td><td class="left">       available content-coding not explicitly listed in the header</td><td> </td><td class="right">       available content-coding not explicitly listed in the header</td><td class="lineno" valign="top"></td></tr>
536      <tr><td class="lineno" valign="top"></td><td class="left">       field.</td><td> </td><td class="right">       field.</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><a name="diff0039" /></td></tr>
539      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">3.</span>  If <span class="delete">multiple content-codings are acceptable, then</span> the acceptable</td><td> </td><td class="rblock">   <span class="insert">2.</span>  If the <span class="insert">representation has no content-coding, then it is</span></td><td class="lineno" valign="top"></td></tr>
540      <tr><td class="lineno" valign="top"></td><td class="lblock">       <span class="delete">content-coding with</span> the <span class="delete">highest non-zero qvalue is preferred.</span></td><td> </td><td class="rblock">       acceptable <span class="insert">by default unless specifically excluded by</span> the <span class="insert">Accept-</span></td><td class="lineno" valign="top"></td></tr>
541      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       Encoding field stating either "identity;q=0" or "*;q=0" without a</span></td><td class="lineno" valign="top"></td></tr>
542      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       more specific entry for "identity".</span></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><a name="diff0040" /></td></tr>
545      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">4.  The "identity"</span> content-coding is <span class="delete">always acceptable, unless</span></td><td> </td><td class="rblock">   <span class="insert">3.  If the representation's</span> content-coding is <span class="insert">one of</span> the <span class="insert">content-</span></td><td class="lineno" valign="top"></td></tr>
546      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       specifically refused because</span> the <span class="delete">Accept-Encoding field includes</span></td><td> </td><td class="rblock"><span class="insert">       codings listed in</span> the Accept-Encoding <span class="insert">field,</span> then <span class="insert">it is</span></td><td class="lineno" valign="top"></td></tr>
547      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       "identity;q=0", or because the field includes "*;q=0" and does</span></td><td> </td><td class="rblock"><span class="insert">       acceptable unless it</span> is <span class="insert">accompanied by a qvalue of 0.  (As</span></td><td class="lineno" valign="top"></td></tr>
548      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       not explicitly include the "identity" content-coding.  If</span> the</td><td> </td><td class="rblock"><span class="insert">       defined in Section 5.3 of [Part1], a qvalue of 0 means "not</span></td><td class="lineno" valign="top"></td></tr>
549      <tr><td class="lineno" valign="top"></td><td class="lblock">       Accept-Encoding <span class="delete">field-value is empty,</span> then <span class="delete">only the "identity"</span></td><td> </td><td class="rblock"><span class="insert">       acceptable".)</span></td><td class="lineno" valign="top"></td></tr>
550      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       encoding</span> is <span class="delete">acceptable.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
551      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
552      <tr><td><a name="diff0041" /></td></tr>
553      <tr><td class="lineno" valign="top"></td><td class="lblock">   If <span class="delete">an Accept-Encoding field is present in a request, but the server</span></td><td> </td><td class="rblock">   <span class="insert">4.</span>  If <span class="insert">multiple content-codings are</span> acceptable, then the <span class="insert">acceptable</span></td><td class="lineno" valign="top"></td></tr>
554      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   cannot send a response which is</span> acceptable, then the <span class="delete">server SHOULD</span></td><td> </td><td class="rblock"><span class="insert">       content-coding with</span> the <span class="insert">highest non-zero qvalue is preferred.</span></td><td class="lineno" valign="top"></td></tr>
555      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   send a response without any encoding (i.e.,</span> the <span class="delete">"identity" encoding).</span></td><td> </td><td class="rblock"></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><a name="diff0042" /></td></tr>
558      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">If no</span> Accept-Encoding field <span class="delete">is present in</span> a <span class="delete">request, the server MAY</span></td><td> </td><td class="rblock">   <span class="insert">An</span> Accept-Encoding <span class="insert">header</span> field <span class="insert">with</span> a <span class="insert">combined field-value that is</span></td><td class="lineno" valign="top"></td></tr>
559      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   assume</span> that the <span class="delete">client will accept</span> any <span class="delete">content coding.  In this case,</span></td><td> </td><td class="rblock"><span class="insert">   empty implies</span> that the <span class="insert">user agent does not want</span> any <span class="insert">content-coding in</span></td><td class="lineno" valign="top"></td></tr>
560      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   if "identity"</span> is <span class="delete">one</span> of the available <span class="delete">content-codings, then the</span></td><td> </td><td class="rblock"><span class="insert">   response.  If an Accept-Encoding header field</span> is <span class="insert">present in a request</span></td><td class="lineno" valign="top"></td></tr>
561      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   server SHOULD use</span> the <span class="delete">"identity" content-coding, unless it has</span></td><td> </td><td class="rblock"><span class="insert">   and none</span> of the available <span class="insert">representations for</span> the <span class="insert">response have</span> a</td><td class="lineno" valign="top"></td></tr>
562      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   additional information that</span> a <span class="delete">different</span> content-coding is <span class="delete">meaningful</span></td><td> </td><td class="rblock">   content-coding <span class="insert">that</span> is <span class="insert">listed as acceptable,</span> the <span class="insert">origin server SHOULD</span></td><td class="lineno" valign="top"></td></tr>
563      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to</span> the <span class="delete">client.</span></td><td> </td><td class="rblock"><span class="insert">   send a response without any content-coding.</span></td><td class="lineno" valign="top"></td></tr>
564      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
565      <tr><td><a name="diff0043" /></td></tr>
566      <tr><td class="lineno" valign="top"></td><td class="lblock">      <span class="delete">Note: If the</span> request <span class="delete">does not include</span> an Accept-Encoding <span class="delete">field,</span></td><td> </td><td class="rblock">   <span class="insert">A</span> request <span class="insert">without</span> an Accept-Encoding <span class="insert">header field implies that</span> the</td><td class="lineno" valign="top"></td></tr>
567      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      and if</span> the <span class="delete">"identity"</span> content-coding is <span class="delete">unavailable, then content-</span></td><td> </td><td class="rblock">   <span class="insert">user agent will accept any content-coding in response, but a</span></td><td class="lineno" valign="top"></td></tr>
568      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      codings commonly understood by HTTP/1.0 clients (i.e., "gzip" and</span></td><td> </td><td class="rblock"><span class="insert">   representation without</span> content-coding is <span class="insert">preferred for compatibility</span></td><td class="lineno" valign="top"></td></tr>
569      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      "compress") are preferred; some older clients improperly display</span></td><td> </td><td class="rblock">   with the <span class="insert">widest variety of user agents.</span></td><td class="lineno" valign="top"></td></tr>
570      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      messages sent</span> with <span class="delete">other content-codings.  The server might also</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
571      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      make this decision based on information about</span> the <span class="delete">particular user-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
572      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      agent or client.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
573      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
574      <tr><td class="lineno" valign="top"></td><td class="left">      Note: Most HTTP/1.0 applications do not recognize or obey qvalues</td><td> </td><td class="right">      Note: Most HTTP/1.0 applications do not recognize or obey qvalues</td><td class="lineno" valign="top"></td></tr>
575      <tr><td class="lineno" valign="top"></td><td class="left">      associated with content-codings.  This means that qvalues will not</td><td> </td><td class="right">      associated with content-codings.  This means that qvalues will not</td><td class="lineno" valign="top"></td></tr>
576      <tr><td class="lineno" valign="top"></td><td class="left">      work and are not permitted with x-gzip or x-compress.</td><td> </td><td class="right">      work and are not permitted with x-gzip or x-compress.</td><td class="lineno" valign="top"></td></tr>
577      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
578      <tr><td class="lineno" valign="top"></td><td class="left">6.4.  Accept-Language</td><td> </td><td class="right">6.4.  Accept-Language</td><td class="lineno" valign="top"></td></tr>
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">   The "Accept-Language" header field can be used by user agents to</td><td> </td><td class="right">   The "Accept-Language" header field can be used by user agents to</td><td class="lineno" valign="top"></td></tr>
581      <tr><td class="lineno" valign="top"></td><td class="left">   indicate the set of natural languages that are preferred in the</td><td> </td><td class="right">   indicate the set of natural languages that are preferred in the</td><td class="lineno" valign="top"></td></tr>
582      <tr><td class="lineno" valign="top"></td><td class="left">   response.  Language tags are defined in Section 2.4.</td><td> </td><td class="right">   response.  Language tags are defined in Section 2.4.</td><td class="lineno" valign="top"></td></tr>
583      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
584      <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 21, line 34</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 21, line 40</em></th><td></td></tr>
585      <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>
586      <tr><td class="lineno" valign="top"></td><td class="left">      and ought to be provided appropriate guidance.  As an example,</td><td> </td><td class="right">      and ought to be provided appropriate guidance.  As an example,</td><td class="lineno" valign="top"></td></tr>
587      <tr><td class="lineno" valign="top"></td><td class="left">      users might assume that on selecting "en-gb", they will be served</td><td> </td><td class="right">      users might assume that on selecting "en-gb", they will be served</td><td class="lineno" valign="top"></td></tr>
588      <tr><td class="lineno" valign="top"></td><td class="left">      any kind of English document if British English is not available.</td><td> </td><td class="right">      any kind of English document if British English is not available.</td><td class="lineno" valign="top"></td></tr>
589      <tr><td class="lineno" valign="top"></td><td class="left">      A user agent might suggest in such a case to add "en" to get the</td><td> </td><td class="right">      A user agent might suggest in such a case to add "en" to get the</td><td class="lineno" valign="top"></td></tr>
590      <tr><td class="lineno" valign="top"></td><td class="left">      best matching behavior.</td><td> </td><td class="right">      best matching behavior.</td><td class="lineno" valign="top"></td></tr>
591      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
592      <tr><td class="lineno" valign="top"></td><td class="left">6.5.  Content-Encoding</td><td> </td><td class="right">6.5.  Content-Encoding</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">   The "Content-Encoding" header field indicates what content-codings</td><td> </td><td class="right">   The "Content-Encoding" header field indicates what content-codings</td><td class="lineno" valign="top"></td></tr>
595      <tr><td><a name="diff0044" /></td></tr>
596      <tr><td class="lineno" valign="top"></td><td class="lblock">   have been applied to the <span class="delete">representation,</span> and thus what decoding</td><td> </td><td class="rblock">   have been applied to the <span class="insert">representation beyond those inherent in the</span></td><td class="lineno" valign="top"></td></tr>
597      <tr><td class="lineno" valign="top"></td><td class="lblock">   mechanisms must be applied in order to obtain the media-type</td><td> </td><td class="rblock"><span class="insert">   media type,</span> and thus what decoding mechanisms must be applied in</td><td class="lineno" valign="top"></td></tr>
598      <tr><td class="lineno" valign="top"></td><td class="lblock">   referenced by the Content-Type header field.  Content-Encoding is</td><td> </td><td class="rblock">   order to obtain the media-type referenced by the Content-Type header</td><td class="lineno" valign="top"></td></tr>
599      <tr><td class="lineno" valign="top"></td><td class="lblock">   primarily used to allow a representation to be compressed without</td><td> </td><td class="rblock">   field.  Content-Encoding is primarily used to allow a representation</td><td class="lineno" valign="top"></td></tr>
600      <tr><td class="lineno" valign="top"></td><td class="lblock">   losing the identity of its underlying media type.</td><td> </td><td class="rblock">   to be compressed without losing the identity of its underlying media</td><td class="lineno" valign="top"></td></tr>
601      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   type.</td><td class="lineno" valign="top"></td></tr>
602      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
603      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Encoding = 1#content-coding</td><td> </td><td class="right">     Content-Encoding = 1#content-coding</td><td class="lineno" valign="top"></td></tr>
604      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
605      <tr><td class="lineno" valign="top"></td><td class="left">   Content codings are defined in Section 2.2.  An example of its use is</td><td> </td><td class="right">   Content codings are defined in Section 2.2.  An example of its use is</td><td class="lineno" valign="top"></td></tr>
606      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
607      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Encoding: gzip</td><td> </td><td class="right">     Content-Encoding: gzip</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 class="lineno" valign="top"></td><td class="left">   The content-coding is a characteristic of the representation.</td><td> </td><td class="right">   The content-coding is a characteristic of the representation.</td><td class="lineno" valign="top"></td></tr>
610      <tr><td class="lineno" valign="top"></td><td class="left">   Typically, the representation body is stored with this encoding and</td><td> </td><td class="right">   Typically, the representation body is stored with this encoding and</td><td class="lineno" valign="top"></td></tr>
611      <tr><td class="lineno" valign="top"></td><td class="left">   is only decoded before rendering or analogous usage.  However, a</td><td> </td><td class="right">   is only decoded before rendering or analogous usage.  However, a</td><td class="lineno" valign="top"></td></tr>
612      <tr><td class="lineno" valign="top"></td><td class="left">   transforming proxy MAY modify the content-coding if the new coding is</td><td> </td><td class="right">   transforming proxy MAY modify the content-coding if the new coding is</td><td class="lineno" valign="top"></td></tr>
613      <tr><td class="lineno" valign="top"></td><td class="left">   known to be acceptable to the recipient, unless the "no-transform"</td><td> </td><td class="right">   known to be acceptable to the recipient, unless the "no-transform"</td><td class="lineno" valign="top"></td></tr>
614      <tr><td class="lineno" valign="top"></td><td class="left">   cache-control directive is present in the message.</td><td> </td><td class="right">   cache-control directive is present in the message.</td><td class="lineno" valign="top"></td></tr>
615      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
616      <tr><td><a name="diff0045" /></td></tr>
617      <tr><td class="lineno" valign="top"></td><td class="lblock">   If the <span class="delete">content-coding of</span> a <span class="delete">representation</span> is <span class="delete">not "identity",</span> then <span class="delete">the</span></td><td> </td><td class="rblock">   If the <span class="insert">media type includes an inherent encoding, such as</span> a <span class="insert">data</span></td><td class="lineno" valign="top"></td></tr>
618      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   representation metadata MUST include</span> a Content-Encoding <span class="delete">header field</span></td><td> </td><td class="rblock"><span class="insert">   format that</span> is <span class="insert">always compressed,</span> then <span class="insert">that encoding would not be</span></td><td class="lineno" valign="top"></td></tr>
619      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   (Section 6.5)</span> that <span class="delete">lists</span> the <span class="delete">non-identity content-coding(s) used.</span></td><td> </td><td class="rblock"><span class="insert">   restated as</span> a Content-Encoding <span class="insert">even if it happens to be the same</span></td><td class="lineno" valign="top"></td></tr>
620      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   algorithm as one of the content-codings.  Such a content-coding would</span></td><td class="lineno" valign="top"></td></tr>
621      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   only be listed if, for some bizarre reason, it is applied a second</span></td><td class="lineno" valign="top"></td></tr>
622      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   time to form the representation.  Likewise, an origin server might</span></td><td class="lineno" valign="top"></td></tr>
623      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   choose to publish the same payload data as multiple representations</span></td><td class="lineno" valign="top"></td></tr>
624      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   that <span class="insert">differ only in whether</span> the <span class="insert">coding is defined as part of Content-</span></td><td class="lineno" valign="top"></td></tr>
625      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Type or Content-Encoding, since some user agents will behave</span></td><td class="lineno" valign="top"></td></tr>
626      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   differently in their handling of each response (e.g., open a "Save as</span></td><td class="lineno" valign="top"></td></tr>
627      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   ..." dialog instead of automatic decompression and rendering of</span></td><td class="lineno" valign="top"></td></tr>
628      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   content).</span></td><td class="lineno" valign="top"></td></tr>
629      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
630      <tr><td><a name="diff0046" /></td></tr>
631      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">If the content-coding of a</span> representation <span class="delete">in</span> a <span class="delete">request message is not</span></td><td> </td><td class="rblock">   <span class="insert">A</span> representation <span class="insert">that has</span> a <span class="insert">content-coding applied</span> to <span class="insert">it MUST include</span></td><td class="lineno" valign="top"></td></tr>
632      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   acceptable</span> to <span class="delete">the origin server, the server SHOULD respond with</span> a</td><td> </td><td class="rblock">   a <span class="insert">Content-Encoding header field (Section 6.5) that lists the content-</span></td><td class="lineno" valign="top"></td></tr>
633      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">status code of 415 (Unsupported Media Type).</span></td><td> </td><td class="rblock"><span class="insert">   coding(s) applied.</span></td><td class="lineno" valign="top"></td></tr>
634      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
635      <tr><td class="lineno" valign="top"></td><td class="left">   If multiple encodings have been applied to a representation, the</td><td> </td><td class="right">   If multiple encodings have been applied to a representation, the</td><td class="lineno" valign="top"></td></tr>
636      <tr><td class="lineno" valign="top"></td><td class="left">   content codings MUST be listed in the order in which they were</td><td> </td><td class="right">   content codings MUST be listed in the order in which they were</td><td class="lineno" valign="top"></td></tr>
637      <tr><td class="lineno" valign="top"></td><td class="left">   applied.  Additional information about the encoding parameters MAY be</td><td> </td><td class="right">   applied.  Additional information about the encoding parameters MAY be</td><td class="lineno" valign="top"></td></tr>
638      <tr><td class="lineno" valign="top"></td><td class="left">   provided by other header fields not defined by this specification.</td><td> </td><td class="right">   provided by other header fields not defined by this specification.</td><td class="lineno" valign="top"></td></tr>
639      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
640      <tr><td><a name="diff0047" /></td></tr>
641      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">If the content-coding of a representation in a request message is not</span></td><td class="lineno" valign="top"></td></tr>
642      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   acceptable to the origin server, the server SHOULD respond with a</span></td><td class="lineno" valign="top"></td></tr>
643      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   status code of 415 (Unsupported Media Type).</span></td><td class="lineno" valign="top"></td></tr>
644      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
645      <tr><td class="lineno" valign="top"></td><td class="left">6.6.  Content-Language</td><td> </td><td class="right">6.6.  Content-Language</td><td class="lineno" valign="top"></td></tr>
646      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
647      <tr><td class="lineno" valign="top"></td><td class="left">   The "Content-Language" header field describes the natural language(s)</td><td> </td><td class="right">   The "Content-Language" header field describes the natural language(s)</td><td class="lineno" valign="top"></td></tr>
648      <tr><td class="lineno" valign="top"></td><td class="left">   of the intended audience for the representation.  Note that this</td><td> </td><td class="right">   of the intended audience for the representation.  Note that this</td><td class="lineno" valign="top"></td></tr>
649      <tr><td class="lineno" valign="top"></td><td class="left">   might not be equivalent to all the languages used within the</td><td> </td><td class="right">   might not be equivalent to all the languages used within the</td><td class="lineno" valign="top"></td></tr>
650      <tr><td class="lineno" valign="top"></td><td class="left">   representation.</td><td> </td><td class="right">   representation.</td><td class="lineno" valign="top"></td></tr>
651      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
652      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Language = 1#language-tag</td><td> </td><td class="right">     Content-Language = 1#language-tag</td><td class="lineno" valign="top"></td></tr>
653      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
654      <tr><td class="lineno" valign="top"></td><td class="left">   Language tags are defined in Section 2.4.  The primary purpose of</td><td> </td><td class="right">   Language tags are defined in Section 2.4.  The primary purpose of</td><td class="lineno" valign="top"></td></tr>
655      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
656      <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 25, line 40</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 26, line 11</em></th><td></td></tr>
657      <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>
658      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
659      <tr><td class="lineno" valign="top"></td><td class="left">   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>
660      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-parameters&gt; shall be updated</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-parameters&gt; shall be updated</td><td class="lineno" valign="top"></td></tr>
661      <tr><td class="lineno" valign="top"></td><td class="left">   with the registration below:</td><td> </td><td class="right">   with the registration below:</td><td class="lineno" valign="top"></td></tr>
662      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
663      <tr><td class="lineno" valign="top"></td><td class="left">   +----------+-----------------------------------------+--------------+</td><td> </td><td class="right">   +----------+-----------------------------------------+--------------+</td><td class="lineno" valign="top"></td></tr>
664      <tr><td class="lineno" valign="top"></td><td class="left">   | Name     | Description                             | Reference    |</td><td> </td><td class="right">   | Name     | Description                             | Reference    |</td><td class="lineno" valign="top"></td></tr>
665      <tr><td class="lineno" valign="top"></td><td class="left">   +----------+-----------------------------------------+--------------+</td><td> </td><td class="right">   +----------+-----------------------------------------+--------------+</td><td class="lineno" valign="top"></td></tr>
666      <tr><td class="lineno" valign="top"></td><td class="left">   | compress | UNIX "compress" program method          | Section      |</td><td> </td><td class="right">   | compress | UNIX "compress" program method          | Section      |</td><td class="lineno" valign="top"></td></tr>
667      <tr><td><a name="diff0048" /></td></tr>
668      <tr><td class="lineno" valign="top"></td><td class="lblock">   |          |                                         | <span class="delete">6.2</span>.2.1 of   |</td><td> </td><td class="rblock">   |          |                                         | <span class="insert">5.1</span>.2.1 of   |</td><td class="lineno" valign="top"></td></tr>
669      <tr><td class="lineno" valign="top"></td><td class="left">   |          |                                         | [Part1]      |</td><td> </td><td class="right">   |          |                                         | [Part1]      |</td><td class="lineno" valign="top"></td></tr>
670      <tr><td class="lineno" valign="top"></td><td class="left">   | deflate  | "deflate" compression mechanism         | Section      |</td><td> </td><td class="right">   | deflate  | "deflate" compression mechanism         | Section      |</td><td class="lineno" valign="top"></td></tr>
671      <tr><td><a name="diff0049" /></td></tr>
672      <tr><td class="lineno" valign="top"></td><td class="lblock">   |          | ([RFC1951]) used inside the "zlib" data | <span class="delete">6.2</span>.2.2 of   |</td><td> </td><td class="rblock">   |          | ([RFC1951]) used inside the "zlib" data | <span class="insert">5.1</span>.2.2 of   |</td><td class="lineno" valign="top"></td></tr>
673      <tr><td class="lineno" valign="top"></td><td class="left">   |          | format ([RFC1950])                      | [Part1]      |</td><td> </td><td class="right">   |          | format ([RFC1950])                      | [Part1]      |</td><td class="lineno" valign="top"></td></tr>
674      <tr><td class="lineno" valign="top"></td><td class="left">   | gzip     | Same as GNU zip [RFC1952]               | Section      |</td><td> </td><td class="right">   | gzip     | Same as GNU zip [RFC1952]               | Section      |</td><td class="lineno" valign="top"></td></tr>
675      <tr><td><a name="diff0050" /></td></tr>
676      <tr><td class="lineno" valign="top"></td><td class="lblock">   |          |                                         | <span class="delete">6.2</span>.2.3 of   |</td><td> </td><td class="rblock">   |          |                                         | <span class="insert">5.1</span>.2.3 of   |</td><td class="lineno" valign="top"></td></tr>
677      <tr><td class="lineno" valign="top"></td><td class="left">   |          |                                         | [Part1]      |</td><td> </td><td class="right">   |          |                                         | [Part1]      |</td><td class="lineno" valign="top"></td></tr>
678      <tr><td><a name="diff0051" /></td></tr>
679      <tr><td class="lineno" valign="top"></td><td class="lblock">   | identity | <span class="delete">No transformation</span>                       | Section <span class="delete">2.2</span>  |</td><td> </td><td class="rblock">   | identity | <span class="insert">reserved (synonym for "no encoding" in</span>  | Section <span class="insert">6.3  |</span></td><td class="lineno" valign="top"></td></tr>
680      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   |          | Accept-Encoding header field)           |</span>              |</td><td class="lineno" valign="top"></td></tr>
681      <tr><td class="lineno" valign="top"></td><td class="left">   +----------+-----------------------------------------+--------------+</td><td> </td><td class="right">   +----------+-----------------------------------------+--------------+</td><td class="lineno" valign="top"></td></tr>
682      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
683      <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>
684      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
685      <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>
686      <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>
687      <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>
688      <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>
689      <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>
690      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
691      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
692      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 26, line 50</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 27, line 20</em></th><td></td></tr>
693      <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>
694      <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>
695      <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>
696      <tr><td class="lineno" valign="top"></td><td class="left">   measure, proxies could filter the accept header fields in relayed</td><td> </td><td class="right">   measure, proxies could filter the accept header fields in relayed</td><td class="lineno" valign="top"></td></tr>
697      <tr><td class="lineno" valign="top"></td><td class="left">   requests.  General purpose user agents which provide a high degree of</td><td> </td><td class="right">   requests.  General purpose user agents which provide a high degree of</td><td class="lineno" valign="top"></td></tr>
698      <tr><td class="lineno" valign="top"></td><td class="left">   header configurability SHOULD warn users about the loss of privacy</td><td> </td><td class="right">   header configurability SHOULD warn users about the loss of privacy</td><td class="lineno" valign="top"></td></tr>
699      <tr><td class="lineno" valign="top"></td><td class="left">   which can be involved.</td><td> </td><td class="right">   which can be involved.</td><td class="lineno" valign="top"></td></tr>
700      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
701      <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>
702      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
703      <tr><td><a name="diff0052" /></td></tr>
704      <tr><td class="lineno" valign="top"></td><td class="lblock">   See Section 1<span class="delete">2</span> of [Part1].</td><td> </td><td class="rblock">   See Section 1<span class="insert">1</span> of [Part1].</td><td class="lineno" valign="top"></td></tr>
705      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
706      <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>
707      <tr><td><a name="diff0053" /></td></tr>
708      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">                                                                         </span></td><td class="lineno" valign="top"></td></tr>
709      <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>
710      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
711      <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>
712      <tr><td class="lineno" valign="top"></td><td class="left">              Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,</td><td> </td><td class="right">              Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,</td><td class="lineno" valign="top"></td></tr>
713      <tr><td class="lineno" valign="top"></td><td class="left">              and J. Reschke, Ed., "HTTP/1.1, part 1: URIs, Connections,</td><td> </td><td class="right">              and J. Reschke, Ed., "HTTP/1.1, part 1: URIs, Connections,</td><td class="lineno" valign="top"></td></tr>
714      <tr><td><a name="diff0054" /></td></tr>
715      <tr><td class="lineno" valign="top"></td><td class="lblock">              and Message Parsing", <span class="delete">draft-ietf-httpbis-p1-messaging-16</span></td><td> </td><td class="rblock">              and Message Parsing", <span class="insert">draft-ietf-httpbis-p1-messaging-17</span></td><td class="lineno" valign="top"></td></tr>
716      <tr><td class="lineno" valign="top"></td><td class="lblock">              (work in progress), <span class="delete">August</span> 2011.</td><td> </td><td class="rblock">              (work in progress), <span class="insert">October</span> 2011.</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">   [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>
719      <tr><td class="lineno" valign="top"></td><td class="left">              Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,</td><td> </td><td class="right">              Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,</td><td class="lineno" valign="top"></td></tr>
720      <tr><td class="lineno" valign="top"></td><td class="left">              and J. Reschke, Ed., "HTTP/1.1, part 2: Message</td><td> </td><td class="right">              and J. Reschke, Ed., "HTTP/1.1, part 2: Message</td><td class="lineno" valign="top"></td></tr>
721      <tr><td><a name="diff0055" /></td></tr>
722      <tr><td class="lineno" valign="top"></td><td class="lblock">              Semantics", <span class="delete">draft-ietf-httpbis-p2-semantics-16</span> (work in</td><td> </td><td class="rblock">              Semantics", <span class="insert">draft-ietf-httpbis-p2-semantics-17</span> (work in</td><td class="lineno" valign="top"></td></tr>
723      <tr><td class="lineno" valign="top"></td><td class="lblock">              progress), <span class="delete">August</span> 2011.</td><td> </td><td class="rblock">              progress), <span class="insert">October</span> 2011.</td><td class="lineno" valign="top"></td></tr>
724      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
725      <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.,</