source: draft-ietf-httpbis/latest/auth48/rfc7230.diff.html @ 2666

Last change on this file since 2666 was 2666, checked in by julian.reschke@…, 6 years ago

quoting, punctuation (#553)

File size: 65.8 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: p1-messaging.unpg.txt - rfc7230-to-be.unpg.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;p1-messaging.unpg.txt&nbsp;</th><th> </th><th>&nbsp;rfc7230-to-be.unpg.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><a name="diff0001" /></td></tr>
41      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">HTTPbis Working Group</span>                                   R. Fielding, Ed.</td><td> </td><td class="rblock"><span class="insert">Internet Engineering Task Force (IETF)</span>                  R. Fielding, Ed.</td><td class="lineno" valign="top"></td></tr>
42      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Internet-Draft</span>                                                     Adobe</td><td> </td><td class="rblock"><span class="insert">Request for Comments: 7230</span>                                         Adobe</td><td class="lineno" valign="top"></td></tr>
43      <tr><td class="lineno" valign="top"></td><td class="left">Obsoletes: 2145, 2616                                    J. Reschke, Ed.</td><td> </td><td class="right">Obsoletes: 2145, 2616                                    J. Reschke, Ed.</td><td class="lineno" valign="top"></td></tr>
44      <tr><td><a name="diff0002" /></td></tr>
45      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">(if approved)                                                 greenbytes</span></td><td> </td><td class="rblock">Updates: 2817, 2818                                           <span class="insert">greenbytes</span></td><td class="lineno" valign="top"></td></tr>
46      <tr><td class="lineno" valign="top"></td><td class="lblock">Updates: 2817, 2818 <span class="delete">(if approved)                           May 12, 2014</span></td><td> </td><td class="rblock"><span class="insert">Category:</span> Standards Track                                       <span class="insert">May</span> 2014</td><td class="lineno" valign="top"></td></tr>
47      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Intended status:</span> Standards Track</td><td> </td><td class="rblock"><span class="insert">ISSN: 2070-1721</span></td><td class="lineno" valign="top"></td></tr>
48      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 13,</span> 2014</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
49      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
50      <tr><td class="lineno" valign="top"></td><td class="left">   Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</td><td> </td><td class="right">   Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</td><td class="lineno" valign="top"></td></tr>
51      <tr><td><a name="diff0003" /></td></tr>
52      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 draft-ietf-httpbis-p1-messaging-latest</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
53      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
54      <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>
55      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
56      <tr><td class="lineno" valign="top"></td><td class="left">   The Hypertext Transfer Protocol (HTTP) is a stateless application-</td><td> </td><td class="right">   The Hypertext Transfer Protocol (HTTP) is a stateless application-</td><td class="lineno" valign="top"></td></tr>
57      <tr><td class="lineno" valign="top"></td><td class="left">   level protocol for distributed, collaborative, hypertext information</td><td> </td><td class="right">   level protocol for distributed, collaborative, hypertext information</td><td class="lineno" valign="top"></td></tr>
58      <tr><td class="lineno" valign="top"></td><td class="left">   systems.  This document provides an overview of HTTP architecture and</td><td> </td><td class="right">   systems.  This document provides an overview of HTTP architecture and</td><td class="lineno" valign="top"></td></tr>
59      <tr><td class="lineno" valign="top"></td><td class="left">   its associated terminology, defines the "http" and "https" Uniform</td><td> </td><td class="right">   its associated terminology, defines the "http" and "https" Uniform</td><td class="lineno" valign="top"></td></tr>
60      <tr><td class="lineno" valign="top"></td><td class="left">   Resource Identifier (URI) schemes, defines the HTTP/1.1 message</td><td> </td><td class="right">   Resource Identifier (URI) schemes, defines the HTTP/1.1 message</td><td class="lineno" valign="top"></td></tr>
61      <tr><td class="lineno" valign="top"></td><td class="left">   syntax and parsing requirements, and describes related security</td><td> </td><td class="right">   syntax and parsing requirements, and describes related security</td><td class="lineno" valign="top"></td></tr>
62      <tr><td class="lineno" valign="top"></td><td class="left">   concerns for implementations.</td><td> </td><td class="right">   concerns for implementations.</td><td class="lineno" valign="top"></td></tr>
63      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
64      <tr><td><a name="diff0004" /></td></tr>
65      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Editorial Note (To be removed by RFC Editor)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
66      <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>
67      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Discussion of this draft takes place on the HTTPBIS working group</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
68      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   mailing list (ietf-http-wg@w3.org), which is archived at</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
69      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   &lt;http://lists.w3.org/Archives/Public/ietf-http-wg/&gt;.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
70      <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>
71      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The current issues list is at</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
72      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   &lt;http://tools.ietf.org/wg/httpbis/trac/report/3&gt; and related</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
73      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   documents (including fancy diffs) can be found at</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
74      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   &lt;http://tools.ietf.org/wg/httpbis/&gt;.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
75      <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>
76      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   _This is a temporary document for the purpose of tracking the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
77      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   editorial changes made during the AUTH48 (RFC publication) phase._</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
78      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
79      <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>
80      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
81      <tr><td><a name="diff0005" /></td></tr>
82      <tr><td class="lineno" valign="top"></td><td class="lblock">   This <span class="delete">Internet-Draft</span> is <span class="delete">submitted in full conformance with the</span></td><td> </td><td class="rblock">   This is <span class="insert">an</span> Internet <span class="insert">Standards Track document.</span></td><td class="lineno" valign="top"></td></tr>
83      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   provisions of BCP 78 and BCP 79.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
84      <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>
85      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Internet-Drafts are working documents of the</span> Internet <span class="delete">Engineering</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
86      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Task Force (IETF).  Note that other groups may also distribute</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
87      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   working documents as Internet-Drafts.  The list of current Internet-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
88      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Drafts is at http://datatracker.ietf.org/drafts/current/.</span></td><td> </td><td class="rblock"></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><a name="diff0006" /></td></tr>
91      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Internet-Drafts are draft documents valid for</span> a <span class="delete">maximum</span> of <span class="delete">six months</span></td><td> </td><td class="rblock">   <span class="insert">This document is</span> a <span class="insert">product of the Internet Engineering Task Force</span></td><td class="lineno" valign="top"></td></tr>
92      <tr><td class="lineno" valign="top"></td><td class="lblock">   and <span class="delete">may be updated, replaced, or obsoleted</span> by <span class="delete">other documents at any</span></td><td> </td><td class="rblock"><span class="insert">   (IETF).  It represents the consensus</span> of <span class="insert">the IETF community.  It has</span></td><td class="lineno" valign="top"></td></tr>
93      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   time.  It</span> is <span class="delete">inappropriate to use Internet-Drafts as reference</span></td><td> </td><td class="rblock"><span class="insert">   received public review</span> and <span class="insert">has been approved for publication</span> by <span class="insert">the</span></td><td class="lineno" valign="top"></td></tr>
94      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   material or to cite them other than as "work</span> in <span class="delete">progress."</span></td><td> </td><td class="rblock"><span class="insert">   Internet Engineering Steering Group (IESG).  Further information on</span></td><td class="lineno" valign="top"></td></tr>
95      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Internet Standards</span> is <span class="insert">available</span> in <span class="insert">Section 2 of RFC 5741.</span></td><td class="lineno" valign="top"></td></tr>
96      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
97      <tr><td><a name="diff0007" /></td></tr>
98      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">This Internet-Draft will expire</span> on <span class="delete">November 13, 2014.</span></td><td> </td><td class="rblock">   <span class="insert">Information about the current status of this document, any errata,</span></td><td class="lineno" valign="top"></td></tr>
99      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   and how to provide feedback</span> on <span class="insert">it may be obtained at</span></td><td class="lineno" valign="top"></td></tr>
100      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   http://www.rfc-editor.org/info/rfc7230.</span></td><td class="lineno" valign="top"></td></tr>
101      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
102      <tr><td 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>
103      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
104      <tr><td class="lineno" valign="top"></td><td class="left">   Copyright (c) 2014 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2014 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
105      <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>
106      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
107      <tr><td class="lineno" valign="top"></td><td class="left">   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>
108      <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>
109      <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>
110      <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>
111      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
112      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 4, line 38</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 4, line 17</em></th><td></td></tr>
113      <tr><td class="lineno" valign="top"></td><td class="left">     9.5.  Request Smuggling  . . . . . . . . . . . . . . . . . . . . 69</td><td> </td><td class="right">     9.5.  Request Smuggling  . . . . . . . . . . . . . . . . . . . . 69</td><td class="lineno" valign="top"></td></tr>
114      <tr><td class="lineno" valign="top"></td><td class="left">     9.6.  Message Integrity  . . . . . . . . . . . . . . . . . . . . 69</td><td> </td><td class="right">     9.6.  Message Integrity  . . . . . . . . . . . . . . . . . . . . 69</td><td class="lineno" valign="top"></td></tr>
115      <tr><td class="lineno" valign="top"></td><td class="left">     9.7.  Message Confidentiality  . . . . . . . . . . . . . . . . . 69</td><td> </td><td class="right">     9.7.  Message Confidentiality  . . . . . . . . . . . . . . . . . 69</td><td class="lineno" valign="top"></td></tr>
116      <tr><td class="lineno" valign="top"></td><td class="left">     9.8.  Privacy of Server Log Information  . . . . . . . . . . . . 70</td><td> </td><td class="right">     9.8.  Privacy of Server Log Information  . . . . . . . . . . . . 70</td><td class="lineno" valign="top"></td></tr>
117      <tr><td class="lineno" valign="top"></td><td class="left">   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 70</td><td> </td><td class="right">   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 70</td><td class="lineno" valign="top"></td></tr>
118      <tr><td class="lineno" valign="top"></td><td class="left">   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72</td><td> </td><td class="right">   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72</td><td class="lineno" valign="top"></td></tr>
119      <tr><td class="lineno" valign="top"></td><td class="left">     11.1. Normative References . . . . . . . . . . . . . . . . . . . 72</td><td> </td><td class="right">     11.1. Normative References . . . . . . . . . . . . . . . . . . . 72</td><td class="lineno" valign="top"></td></tr>
120      <tr><td class="lineno" valign="top"></td><td class="left">     11.2. Informative References . . . . . . . . . . . . . . . . . . 73</td><td> </td><td class="right">     11.2. Informative References . . . . . . . . . . . . . . . . . . 73</td><td class="lineno" valign="top"></td></tr>
121      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix A.  HTTP Version History  . . . . . . . . . . . . . . . . 75</td><td> </td><td class="right">   Appendix A.  HTTP Version History  . . . . . . . . . . . . . . . . 75</td><td class="lineno" valign="top"></td></tr>
122      <tr><td class="lineno" valign="top"></td><td class="left">     A.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . 76</td><td> </td><td class="right">     A.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . 76</td><td class="lineno" valign="top"></td></tr>
123      <tr><td><a name="diff0008" /></td></tr>
124      <tr><td class="lineno" valign="top"></td><td class="lblock">       A.1.1.  <span class="delete">Multi-homed</span> Web Servers  . . . . . . . . . . . . . . . 76</td><td> </td><td class="rblock">       A.1.1.  <span class="insert">Multihomed</span> Web Servers . . . . . . . . . . . . . . . <span class="insert">.</span> 76</td><td class="lineno" valign="top"></td></tr>
125      <tr><td class="lineno" valign="top"></td><td class="lblock">       A.1.2.  Keep-Alive Connections . . . . . . . . . . . . . . . . <span class="delete">77</span></td><td> </td><td class="rblock">       A.1.2.  Keep-Alive Connections . . . . . . . . . . . . . . . . <span class="insert">76</span></td><td class="lineno" valign="top"></td></tr>
126      <tr><td class="lineno" valign="top"></td><td class="left">       A.1.3.  Introduction of Transfer-Encoding  . . . . . . . . . . 77</td><td> </td><td class="right">       A.1.3.  Introduction of Transfer-Encoding  . . . . . . . . . . 77</td><td class="lineno" valign="top"></td></tr>
127      <tr><td class="lineno" valign="top"></td><td class="left">     A.2.  Changes from RFC 2616  . . . . . . . . . . . . . . . . . . 77</td><td> </td><td class="right">     A.2.  Changes from RFC 2616  . . . . . . . . . . . . . . . . . . 77</td><td class="lineno" valign="top"></td></tr>
128      <tr><td><a name="diff0009" /></td></tr>
129      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix B.  Collected ABNF  . . . . . . . . . . . . . . . . . . . <span class="delete">80</span></td><td> </td><td class="rblock">   Appendix B.  Collected ABNF  . . . . . . . . . . . . . . . . . . . <span class="insert">79</span></td><td class="lineno" valign="top"></td></tr>
130      <tr><td class="lineno" valign="top"></td><td class="left">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82</td><td> </td><td class="right">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82</td><td class="lineno" valign="top"></td></tr>
131      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
132      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
133      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
134      <tr><td class="lineno" valign="top"></td><td class="left">   The Hypertext Transfer Protocol (HTTP) is a stateless application-</td><td> </td><td class="right">   The Hypertext Transfer Protocol (HTTP) is a stateless application-</td><td class="lineno" valign="top"></td></tr>
135      <tr><td class="lineno" valign="top"></td><td class="left">   level request/response protocol that uses extensible semantics and</td><td> </td><td class="right">   level request/response protocol that uses extensible semantics and</td><td class="lineno" valign="top"></td></tr>
136      <tr><td class="lineno" valign="top"></td><td class="left">   self-descriptive message payloads for flexible interaction with</td><td> </td><td class="right">   self-descriptive message payloads for flexible interaction with</td><td class="lineno" valign="top"></td></tr>
137      <tr><td class="lineno" valign="top"></td><td class="left">   network-based hypertext information systems.  This document is the</td><td> </td><td class="right">   network-based hypertext information systems.  This document is the</td><td class="lineno" valign="top"></td></tr>
138      <tr><td class="lineno" valign="top"></td><td class="left">   first in a series of documents that collectively form the HTTP/1.1</td><td> </td><td class="right">   first in a series of documents that collectively form the HTTP/1.1</td><td class="lineno" valign="top"></td></tr>
139      <tr><td class="lineno" valign="top"></td><td class="left">   specification:</td><td> </td><td class="right">   specification:</td><td class="lineno" valign="top"></td></tr>
140      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
141      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 26, line 11</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 26, line 11</em></th><td></td></tr>
142      <tr><td class="lineno" valign="top"></td><td class="left">   received, or replace each received obs-fold with one or more SP</td><td> </td><td class="right">   received, or replace each received obs-fold with one or more SP</td><td class="lineno" valign="top"></td></tr>
143      <tr><td class="lineno" valign="top"></td><td class="left">   octets prior to interpreting the field value or forwarding the</td><td> </td><td class="right">   octets prior to interpreting the field value or forwarding the</td><td class="lineno" valign="top"></td></tr>
144      <tr><td class="lineno" valign="top"></td><td class="left">   message downstream.</td><td> </td><td class="right">   message downstream.</td><td class="lineno" valign="top"></td></tr>
145      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
146      <tr><td class="lineno" valign="top"></td><td class="left">   A user agent that receives an obs-fold in a response message that is</td><td> </td><td class="right">   A user agent that receives an obs-fold in a response message that is</td><td class="lineno" valign="top"></td></tr>
147      <tr><td class="lineno" valign="top"></td><td class="left">   not within a message/http container MUST replace each received obs-</td><td> </td><td class="right">   not within a message/http container MUST replace each received obs-</td><td class="lineno" valign="top"></td></tr>
148      <tr><td class="lineno" valign="top"></td><td class="left">   fold with one or more SP octets prior to interpreting the field</td><td> </td><td class="right">   fold with one or more SP octets prior to interpreting the field</td><td class="lineno" valign="top"></td></tr>
149      <tr><td class="lineno" valign="top"></td><td class="left">   value.</td><td> </td><td class="right">   value.</td><td class="lineno" valign="top"></td></tr>
150      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
151      <tr><td class="lineno" valign="top"></td><td class="left">   Historically, HTTP has allowed field content with text in the</td><td> </td><td class="right">   Historically, HTTP has allowed field content with text in the</td><td class="lineno" valign="top"></td></tr>
152      <tr><td><a name="diff0010" /></td></tr>
153      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">ISO-8859-1 charset</span> [ISO-8859-1], supporting other charsets only</td><td> </td><td class="rblock">   <span class="insert">ISO-8859-charset</span> [ISO-8859-1], supporting other charsets only through</td><td class="lineno" valign="top"></td></tr>
154      <tr><td class="lineno" valign="top"></td><td class="lblock">   through use of [RFC2047] encoding.  In practice, most HTTP header</td><td> </td><td class="rblock">   use of [RFC2047] encoding.  In practice, most HTTP header field</td><td class="lineno" valign="top"></td></tr>
155      <tr><td class="lineno" valign="top"></td><td class="lblock">   field values use only a subset of the US-ASCII charset [USASCII].</td><td> </td><td class="rblock">   values use only a subset of the US-ASCII charset [USASCII].  Newly</td><td class="lineno" valign="top"></td></tr>
156      <tr><td class="lineno" valign="top"></td><td class="lblock">   Newly defined header fields SHOULD limit their field values to</td><td> </td><td class="rblock">   defined header fields SHOULD limit their field values to US-ASCII</td><td class="lineno" valign="top"></td></tr>
157      <tr><td class="lineno" valign="top"></td><td class="lblock">   US-ASCII octets.  A recipient SHOULD treat other octets in field</td><td> </td><td class="rblock">   octets.  A recipient SHOULD treat other octets in field content</td><td class="lineno" valign="top"></td></tr>
158      <tr><td class="lineno" valign="top"></td><td class="lblock">   content (obs-text) as opaque data.</td><td> </td><td class="rblock">   (obs-text) as opaque data.</td><td class="lineno" valign="top"></td></tr>
159      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
160      <tr><td class="lineno" valign="top"></td><td class="left">3.2.5.  Field Limits</td><td> </td><td class="right">3.2.5.  Field Limits</td><td class="lineno" valign="top"></td></tr>
161      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
162      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP does not place a predefined limit on the length of each header</td><td> </td><td class="right">   HTTP does not place a predefined limit on the length of each header</td><td class="lineno" valign="top"></td></tr>
163      <tr><td class="lineno" valign="top"></td><td class="left">   field or on the length of the header section as a whole, as described</td><td> </td><td class="right">   field or on the length of the header section as a whole, as described</td><td class="lineno" valign="top"></td></tr>
164      <tr><td class="lineno" valign="top"></td><td class="left">   in Section 2.5.  Various ad hoc limitations on individual header</td><td> </td><td class="right">   in Section 2.5.  Various ad hoc limitations on individual header</td><td class="lineno" valign="top"></td></tr>
165      <tr><td class="lineno" valign="top"></td><td class="left">   field length are found in practice, often depending on the specific</td><td> </td><td class="right">   field length are found in practice, often depending on the specific</td><td class="lineno" valign="top"></td></tr>
166      <tr><td class="lineno" valign="top"></td><td class="left">   field semantics.</td><td> </td><td class="right">   field semantics.</td><td class="lineno" valign="top"></td></tr>
167      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
168      <tr><td class="lineno" valign="top"></td><td class="left">   A server that receives a request header field, or set of fields,</td><td> </td><td class="right">   A server that receives a request header field, or set of fields,</td><td class="lineno" valign="top"></td></tr>
169      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
170      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 27, line 42</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 27, line 42</em></th><td></td></tr>
171      <tr><td class="lineno" valign="top"></td><td class="left">   The message body (if any) of an HTTP message is used to carry the</td><td> </td><td class="right">   The message body (if any) of an HTTP message is used to carry the</td><td class="lineno" valign="top"></td></tr>
172      <tr><td class="lineno" valign="top"></td><td class="left">   payload body of that request or response.  The message body is</td><td> </td><td class="right">   payload body of that request or response.  The message body is</td><td class="lineno" valign="top"></td></tr>
173      <tr><td class="lineno" valign="top"></td><td class="left">   identical to the payload body unless a transfer coding has been</td><td> </td><td class="right">   identical to the payload body unless a transfer coding has been</td><td class="lineno" valign="top"></td></tr>
174      <tr><td class="lineno" valign="top"></td><td class="left">   applied, as described in Section 3.3.1.</td><td> </td><td class="right">   applied, as described in Section 3.3.1.</td><td class="lineno" valign="top"></td></tr>
175      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
176      <tr><td class="lineno" valign="top"></td><td class="left">     message-body = *OCTET</td><td> </td><td class="right">     message-body = *OCTET</td><td class="lineno" valign="top"></td></tr>
177      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
178      <tr><td class="lineno" valign="top"></td><td class="left">   The rules for when a message body is allowed in a message differ for</td><td> </td><td class="right">   The rules for when a message body is allowed in a message differ for</td><td class="lineno" valign="top"></td></tr>
179      <tr><td class="lineno" valign="top"></td><td class="left">   requests and responses.</td><td> </td><td class="right">   requests and responses.</td><td class="lineno" valign="top"></td></tr>
180      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
181      <tr><td><a name="diff0011" /></td></tr>
182      <tr><td class="lineno" valign="top"></td><td class="lblock">   The presence of a message body in a request is signaled by a <span class="delete">Content-</span></td><td> </td><td class="rblock">   The presence of a message body in a request is signaled by a</td><td class="lineno" valign="top"></td></tr>
183      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Length</span> or Transfer-Encoding header field.  Request message framing is</td><td> </td><td class="rblock">   <span class="insert">"Content-Length"</span> or Transfer-Encoding header field.  Request message</td><td class="lineno" valign="top"></td></tr>
184      <tr><td class="lineno" valign="top"></td><td class="lblock">   independent of method semantics, even if the method does not define</td><td> </td><td class="rblock">   framing is independent of method semantics, even if the method does</td><td class="lineno" valign="top"></td></tr>
185      <tr><td class="lineno" valign="top"></td><td class="lblock">   any use for a message body.</td><td> </td><td class="rblock">   not define any use for a message body.</td><td class="lineno" valign="top"></td></tr>
186      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
187      <tr><td class="lineno" valign="top"></td><td class="left">   The presence of a message body in a response depends on both the</td><td> </td><td class="right">   The presence of a message body in a response depends on both the</td><td class="lineno" valign="top"></td></tr>
188      <tr><td class="lineno" valign="top"></td><td class="left">   request method to which it is responding and the response status code</td><td> </td><td class="right">   request method to which it is responding and the response status code</td><td class="lineno" valign="top"></td></tr>
189      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 3.1.2).  Responses to the HEAD request method (Section 4.3.2</td><td> </td><td class="right">   (Section 3.1.2).  Responses to the HEAD request method (Section 4.3.2</td><td class="lineno" valign="top"></td></tr>
190      <tr><td class="lineno" valign="top"></td><td class="left">   of [RFC7231]) never include a message body because the associated</td><td> </td><td class="right">   of [RFC7231]) never include a message body because the associated</td><td class="lineno" valign="top"></td></tr>
191      <tr><td class="lineno" valign="top"></td><td class="left">   response header fields (e.g., Transfer-Encoding, Content-Length,</td><td> </td><td class="right">   response header fields (e.g., Transfer-Encoding, Content-Length,</td><td class="lineno" valign="top"></td></tr>
192      <tr><td class="lineno" valign="top"></td><td class="left">   etc.), if present, indicate only what their values would have been if</td><td> </td><td class="right">   etc.), if present, indicate only what their values would have been if</td><td class="lineno" valign="top"></td></tr>
193      <tr><td class="lineno" valign="top"></td><td class="left">   the request method had been GET (Section 4.3.1 of [RFC7231]). 2xx</td><td> </td><td class="right">   the request method had been GET (Section 4.3.1 of [RFC7231]). 2xx</td><td class="lineno" valign="top"></td></tr>
194      <tr><td class="lineno" valign="top"></td><td class="left">   (Successful) responses to a CONNECT request method (Section 4.3.6 of</td><td> </td><td class="right">   (Successful) responses to a CONNECT request method (Section 4.3.6 of</td><td class="lineno" valign="top"></td></tr>
195      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7231]) switch to tunnel mode instead of having a message body.</td><td> </td><td class="right">   [RFC7231]) switch to tunnel mode instead of having a message body.</td><td class="lineno" valign="top"></td></tr>
196      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
197      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 49, line 18</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 49, line 18</em></th><td></td></tr>
198      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
199      <tr><td class="lineno" valign="top"></td><td class="left">   A proxy MUST NOT modify the "absolute-path" and "query" parts of the</td><td> </td><td class="right">   A proxy MUST NOT modify the "absolute-path" and "query" parts of the</td><td class="lineno" valign="top"></td></tr>
200      <tr><td class="lineno" valign="top"></td><td class="left">   received request-target when forwarding it to the next inbound</td><td> </td><td class="right">   received request-target when forwarding it to the next inbound</td><td class="lineno" valign="top"></td></tr>
201      <tr><td class="lineno" valign="top"></td><td class="left">   server, except as noted above to replace an empty path with "/" or</td><td> </td><td class="right">   server, except as noted above to replace an empty path with "/" or</td><td class="lineno" valign="top"></td></tr>
202      <tr><td class="lineno" valign="top"></td><td class="left">   "*".</td><td> </td><td class="right">   "*".</td><td class="lineno" valign="top"></td></tr>
203      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
204      <tr><td class="lineno" valign="top"></td><td class="left">   A proxy MAY modify the message body through application or removal of</td><td> </td><td class="right">   A proxy MAY modify the message body through application or removal of</td><td class="lineno" valign="top"></td></tr>
205      <tr><td class="lineno" valign="top"></td><td class="left">   a transfer coding (Section 4).</td><td> </td><td class="right">   a transfer coding (Section 4).</td><td class="lineno" valign="top"></td></tr>
206      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
207      <tr><td class="lineno" valign="top"></td><td class="left">   A proxy MUST NOT transform the payload (Section 3.3 of [RFC7231]) of</td><td> </td><td class="right">   A proxy MUST NOT transform the payload (Section 3.3 of [RFC7231]) of</td><td class="lineno" valign="top"></td></tr>
208      <tr><td><a name="diff0012" /></td></tr>
209      <tr><td class="lineno" valign="top"></td><td class="lblock">   a message that contains a no-transform <span class="delete">cache-c</span>ontrol directive</td><td> </td><td class="rblock">   a message that contains a no-transform <span class="insert">Cache-C</span>ontrol directive</td><td class="lineno" valign="top"></td></tr>
210      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 5.2 of [RFC7234]).</td><td> </td><td class="right">   (Section 5.2 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr>
211      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
212      <tr><td class="lineno" valign="top"></td><td class="left">   A proxy MAY transform the payload of a message that does not contain</td><td> </td><td class="right">   A proxy MAY transform the payload of a message that does not contain</td><td class="lineno" valign="top"></td></tr>
213      <tr><td><a name="diff0013" /></td></tr>
214      <tr><td class="lineno" valign="top"></td><td class="lblock">   a no-transform <span class="delete">cache-c</span>ontrol directive.  A proxy that transforms a</td><td> </td><td class="rblock">   a no-transform <span class="insert">Cache-C</span>ontrol directive.  A proxy that transforms a</td><td class="lineno" valign="top"></td></tr>
215      <tr><td class="lineno" valign="top"></td><td class="left">   payload MUST add a Warning header field with the warn-code of 214</td><td> </td><td class="right">   payload MUST add a Warning header field with the warn-code of 214</td><td class="lineno" valign="top"></td></tr>
216      <tr><td class="lineno" valign="top"></td><td class="left">   ("Transformation Applied") if one is not already in the message (see</td><td> </td><td class="right">   ("Transformation Applied") if one is not already in the message (see</td><td class="lineno" valign="top"></td></tr>
217      <tr><td class="lineno" valign="top"></td><td class="left">   Section 5.5 of [RFC7234]).  A proxy that transforms the payload of a</td><td> </td><td class="right">   Section 5.5 of [RFC7234]).  A proxy that transforms the payload of a</td><td class="lineno" valign="top"></td></tr>
218      <tr><td class="lineno" valign="top"></td><td class="left">   200 (OK) response can further inform downstream recipients that a</td><td> </td><td class="right">   200 (OK) response can further inform downstream recipients that a</td><td class="lineno" valign="top"></td></tr>
219      <tr><td class="lineno" valign="top"></td><td class="left">   transformation has been applied by changing the response status code</td><td> </td><td class="right">   transformation has been applied by changing the response status code</td><td class="lineno" valign="top"></td></tr>
220      <tr><td class="lineno" valign="top"></td><td class="left">   to 203 (Non-Authoritative Information) (Section 6.3.4 of [RFC7231]).</td><td> </td><td class="right">   to 203 (Non-Authoritative Information) (Section 6.3.4 of [RFC7231]).</td><td class="lineno" valign="top"></td></tr>
221      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
222      <tr><td class="lineno" valign="top"></td><td class="left">   A proxy SHOULD NOT modify header fields that provide information</td><td> </td><td class="right">   A proxy SHOULD NOT modify header fields that provide information</td><td class="lineno" valign="top"></td></tr>
223      <tr><td class="lineno" valign="top"></td><td class="left">   about the endpoints of the communication chain, the resource state,</td><td> </td><td class="right">   about the endpoints of the communication chain, the resource state,</td><td class="lineno" valign="top"></td></tr>
224      <tr><td class="lineno" valign="top"></td><td class="left">   or the selected representation (other than the payload) unless the</td><td> </td><td class="right">   or the selected representation (other than the payload) unless the</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-l6" /><small>skipping to change at</small><em> page 67, line 10</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 67, line 10</em></th><td></td></tr>
227      <tr><td class="lineno" valign="top"></td><td class="left">   The "https" scheme (Section 2.7.2) is intended to prevent (or at</td><td> </td><td class="right">   The "https" scheme (Section 2.7.2) is intended to prevent (or at</td><td class="lineno" valign="top"></td></tr>
228      <tr><td class="lineno" valign="top"></td><td class="left">   least reveal) many of these potential attacks on establishing</td><td> </td><td class="right">   least reveal) many of these potential attacks on establishing</td><td class="lineno" valign="top"></td></tr>
229      <tr><td class="lineno" valign="top"></td><td class="left">   authority, provided that the negotiated TLS connection is secured and</td><td> </td><td class="right">   authority, provided that the negotiated TLS connection is secured and</td><td class="lineno" valign="top"></td></tr>
230      <tr><td class="lineno" valign="top"></td><td class="left">   the client properly verifies that the communicating server's identity</td><td> </td><td class="right">   the client properly verifies that the communicating server's identity</td><td class="lineno" valign="top"></td></tr>
231      <tr><td class="lineno" valign="top"></td><td class="left">   matches the target URI's authority component (see [RFC2818]).</td><td> </td><td class="right">   matches the target URI's authority component (see [RFC2818]).</td><td class="lineno" valign="top"></td></tr>
232      <tr><td class="lineno" valign="top"></td><td class="left">   Correctly implementing such verification can be difficult (see</td><td> </td><td class="right">   Correctly implementing such verification can be difficult (see</td><td class="lineno" valign="top"></td></tr>
233      <tr><td class="lineno" valign="top"></td><td class="left">   [Georgiev]).</td><td> </td><td class="right">   [Georgiev]).</td><td class="lineno" valign="top"></td></tr>
234      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
235      <tr><td class="lineno" valign="top"></td><td class="left">9.2.  Risks of Intermediaries</td><td> </td><td class="right">9.2.  Risks of Intermediaries</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="diff0014" /></td></tr>
238      <tr><td class="lineno" valign="top"></td><td class="lblock">   By their very nature, HTTP intermediaries are men<span class="delete">-in-the-</span>middle and,</td><td> </td><td class="rblock">   By their very nature, HTTP intermediaries are men<span class="insert"> in the </span>middle and,</td><td class="lineno" valign="top"></td></tr>
239      <tr><td class="lineno" valign="top"></td><td class="left">   thus, represent an opportunity for man-in-the-middle attacks.</td><td> </td><td class="right">   thus, represent an opportunity for man-in-the-middle attacks.</td><td class="lineno" valign="top"></td></tr>
240      <tr><td class="lineno" valign="top"></td><td class="left">   Compromise of the systems on which the intermediaries run can result</td><td> </td><td class="right">   Compromise of the systems on which the intermediaries run can result</td><td class="lineno" valign="top"></td></tr>
241      <tr><td class="lineno" valign="top"></td><td class="left">   in serious security and privacy problems.  Intermediaries might have</td><td> </td><td class="right">   in serious security and privacy problems.  Intermediaries might have</td><td class="lineno" valign="top"></td></tr>
242      <tr><td class="lineno" valign="top"></td><td class="left">   access to security-related information, personal information about</td><td> </td><td class="right">   access to security-related information, personal information about</td><td class="lineno" valign="top"></td></tr>
243      <tr><td class="lineno" valign="top"></td><td class="left">   individual users and organizations, and proprietary information</td><td> </td><td class="right">   individual users and organizations, and proprietary information</td><td class="lineno" valign="top"></td></tr>
244      <tr><td class="lineno" valign="top"></td><td class="left">   belonging to users and content providers.  A compromised</td><td> </td><td class="right">   belonging to users and content providers.  A compromised</td><td class="lineno" valign="top"></td></tr>
245      <tr><td class="lineno" valign="top"></td><td class="left">   intermediary, or an intermediary implemented or configured without</td><td> </td><td class="right">   intermediary, or an intermediary implemented or configured without</td><td class="lineno" valign="top"></td></tr>
246      <tr><td class="lineno" valign="top"></td><td class="left">   regard to security and privacy considerations, might be used in the</td><td> </td><td class="right">   regard to security and privacy considerations, might be used in the</td><td class="lineno" valign="top"></td></tr>
247      <tr><td class="lineno" valign="top"></td><td class="left">   commission of a wide range of potential attacks.</td><td> </td><td class="right">   commission of a wide range of potential attacks.</td><td class="lineno" valign="top"></td></tr>
248      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
249      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
250      <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 73, line 7</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 73, line 7</em></th><td></td></tr>
251      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3986]     Berners-Lee, T., Fielding, R., and L. Masinter,</td><td> </td><td class="right">   [RFC3986]     Berners-Lee, T., Fielding, R., and L. Masinter,</td><td class="lineno" valign="top"></td></tr>
252      <tr><td class="lineno" valign="top"></td><td class="left">                 "Uniform Resource Identifier (URI): Generic Syntax",</td><td> </td><td class="right">                 "Uniform Resource Identifier (URI): Generic Syntax",</td><td class="lineno" valign="top"></td></tr>
253      <tr><td class="lineno" valign="top"></td><td class="left">                 STD 66, RFC 3986, January 2005.</td><td> </td><td class="right">                 STD 66, RFC 3986, January 2005.</td><td class="lineno" valign="top"></td></tr>
254      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
255      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5234]     Crocker, D., Ed. and P. Overell, "Augmented BNF for</td><td> </td><td class="right">   [RFC5234]     Crocker, D., Ed. and P. Overell, "Augmented BNF for</td><td class="lineno" valign="top"></td></tr>
256      <tr><td class="lineno" valign="top"></td><td class="left">                 Syntax Specifications: ABNF", STD 68, RFC 5234,</td><td> </td><td class="right">                 Syntax Specifications: ABNF", STD 68, RFC 5234,</td><td class="lineno" valign="top"></td></tr>
257      <tr><td class="lineno" valign="top"></td><td class="left">                 January 2008.</td><td> </td><td class="right">                 January 2008.</td><td class="lineno" valign="top"></td></tr>
258      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
259      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7231]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="right">   [RFC7231]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td class="lineno" valign="top"></td></tr>
260      <tr><td class="lineno" valign="top"></td><td class="left">                 Transfer Protocol (HTTP/1.1): Semantics and Content",</td><td> </td><td class="right">                 Transfer Protocol (HTTP/1.1): Semantics and Content",</td><td class="lineno" valign="top"></td></tr>
261      <tr><td><a name="diff0015" /></td></tr>
262      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p2-semantics-latest (work in</span></td><td> </td><td class="rblock">                 <span class="insert">RFC 7231,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
263      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 progress),</span> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
264      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
265      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7232]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="right">   [RFC7232]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td class="lineno" valign="top"></td></tr>
266      <tr><td class="lineno" valign="top"></td><td class="left">                 Transfer Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="right">                 Transfer Protocol (HTTP/1.1): Conditional Requests",</td><td class="lineno" valign="top"></td></tr>
267      <tr><td><a name="diff0016" /></td></tr>
268      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p4-conditional-latest (work in</span></td><td> </td><td class="rblock">                 <span class="insert">RFC 7232,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
269      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 progress),</span> May 2014.</td><td> </td><td class="rblock"></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">   [RFC7233]     Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td> </td><td class="right">   [RFC7233]     Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr>
272      <tr><td class="lineno" valign="top"></td><td class="left">                 "Hypertext Transfer Protocol (HTTP/1.1): Range</td><td> </td><td class="right">                 "Hypertext Transfer Protocol (HTTP/1.1): Range</td><td class="lineno" valign="top"></td></tr>
273      <tr><td><a name="diff0017" /></td></tr>
274      <tr><td class="lineno" valign="top"></td><td class="lblock">                 Requests", <span class="delete">draft-ietf-httpbis-p5-range-latest (work in</span></td><td> </td><td class="rblock">                 Requests", <span class="insert">RFC 7233,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
275      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 progress),</span> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
276      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
277      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7234]     Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td> </td><td class="right">   [RFC7234]     Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td class="lineno" valign="top"></td></tr>
278      <tr><td class="lineno" valign="top"></td><td class="left">                 Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td> </td><td class="right">                 Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td class="lineno" valign="top"></td></tr>
279      <tr><td><a name="diff0018" /></td></tr>
280      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p6-cache-latest (work in progress),</span></td><td> </td><td class="rblock">                 <span class="insert">RFC 7234,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
281      <tr><td class="lineno" valign="top"></td><td class="lblock">                 May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
282      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
283      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7235]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="right">   [RFC7235]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td class="lineno" valign="top"></td></tr>
284      <tr><td class="lineno" valign="top"></td><td class="left">                 Transfer Protocol (HTTP/1.1): Authentication",</td><td> </td><td class="right">                 Transfer Protocol (HTTP/1.1): Authentication",</td><td class="lineno" valign="top"></td></tr>
285      <tr><td><a name="diff0019" /></td></tr>
286      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p7-auth-latest (work in progress),</span></td><td> </td><td class="rblock">                 <span class="insert">RFC 7235,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
287      <tr><td class="lineno" valign="top"></td><td class="lblock">                 May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
288      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
289      <tr><td class="lineno" valign="top"></td><td class="left">   [USASCII]     American National Standards Institute, "Coded Character</td><td> </td><td class="right">   [USASCII]     American National Standards Institute, "Coded Character</td><td class="lineno" valign="top"></td></tr>
290      <tr><td class="lineno" valign="top"></td><td class="left">                 Set -- 7-bit American Standard Code for Information</td><td> </td><td class="right">                 Set -- 7-bit American Standard Code for Information</td><td class="lineno" valign="top"></td></tr>
291      <tr><td class="lineno" valign="top"></td><td class="left">                 Interchange", ANSI X3.4, 1986.</td><td> </td><td class="right">                 Interchange", ANSI X3.4, 1986.</td><td class="lineno" valign="top"></td></tr>
292      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
293      <tr><td class="lineno" valign="top"></td><td class="left">   [Welch]       Welch, T., "A Technique for High-Performance Data</td><td> </td><td class="right">   [Welch]       Welch, T., "A Technique for High-Performance Data</td><td class="lineno" valign="top"></td></tr>
294      <tr><td class="lineno" valign="top"></td><td class="left">                 Compression", IEEE Computer 17(6), June 1984.</td><td> </td><td class="right">                 Compression", IEEE Computer 17(6), June 1984.</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">11.2.  Informative References</td><td> </td><td class="right">11.2.  Informative References</td><td class="lineno" valign="top"></td></tr>
297      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
298      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
299      <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 76, line 36</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 76, line 29</em></th><td></td></tr>
300      <tr><td class="lineno" valign="top"></td><td class="left">   implements name-based virtual hosts ought to disable support for</td><td> </td><td class="right">   implements name-based virtual hosts ought to disable support for</td><td class="lineno" valign="top"></td></tr>
301      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/0.9.  Most requests that appear to be HTTP/0.9 are, in fact,</td><td> </td><td class="right">   HTTP/0.9.  Most requests that appear to be HTTP/0.9 are, in fact,</td><td class="lineno" valign="top"></td></tr>
302      <tr><td class="lineno" valign="top"></td><td class="left">   badly constructed HTTP/1.x requests caused by a client failing to</td><td> </td><td class="right">   badly constructed HTTP/1.x requests caused by a client failing to</td><td class="lineno" valign="top"></td></tr>
303      <tr><td class="lineno" valign="top"></td><td class="left">   properly encode the request-target.</td><td> </td><td class="right">   properly encode the request-target.</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">A.1.  Changes from HTTP/1.0</td><td> </td><td class="right">A.1.  Changes from HTTP/1.0</td><td class="lineno" valign="top"></td></tr>
306      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
307      <tr><td class="lineno" valign="top"></td><td class="left">   This section summarizes major differences between versions HTTP/1.0</td><td> </td><td class="right">   This section summarizes major differences between versions HTTP/1.0</td><td class="lineno" valign="top"></td></tr>
308      <tr><td class="lineno" valign="top"></td><td class="left">   and HTTP/1.1.</td><td> </td><td class="right">   and HTTP/1.1.</td><td class="lineno" valign="top"></td></tr>
309      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
310      <tr><td><a name="diff0020" /></td></tr>
311      <tr><td class="lineno" valign="top"></td><td class="lblock">A.1.1.  Multi<span class="delete">-</span>homed Web Servers</td><td> </td><td class="rblock">A.1.1.  Multihomed Web Servers</td><td class="lineno" valign="top"></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">   The requirements that clients and servers support the Host header</td><td> </td><td class="right">   The requirements that clients and servers support the Host header</td><td class="lineno" valign="top"></td></tr>
314      <tr><td class="lineno" valign="top"></td><td class="left">   field (Section 5.4), report an error if it is missing from an</td><td> </td><td class="right">   field (Section 5.4), report an error if it is missing from an</td><td class="lineno" valign="top"></td></tr>
315      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/1.1 request, and accept absolute URIs (Section 5.3) are among</td><td> </td><td class="right">   HTTP/1.1 request, and accept absolute URIs (Section 5.3) are among</td><td class="lineno" valign="top"></td></tr>
316      <tr><td class="lineno" valign="top"></td><td class="left">   the most important changes defined by HTTP/1.1.</td><td> </td><td class="right">   the most important changes defined by HTTP/1.1.</td><td class="lineno" valign="top"></td></tr>
317      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
318      <tr><td class="lineno" valign="top"></td><td class="left">   Older HTTP/1.0 clients assumed a one-to-one relationship of IP</td><td> </td><td class="right">   Older HTTP/1.0 clients assumed a one-to-one relationship of IP</td><td class="lineno" valign="top"></td></tr>
319      <tr><td class="lineno" valign="top"></td><td class="left">   addresses and servers; there was no other established mechanism for</td><td> </td><td class="right">   addresses and servers; there was no other established mechanism for</td><td class="lineno" valign="top"></td></tr>
320      <tr><td class="lineno" valign="top"></td><td class="left">   distinguishing the intended server of a request than the IP address</td><td> </td><td class="right">   distinguishing the intended server of a request than the IP address</td><td class="lineno" valign="top"></td></tr>
321      <tr><td class="lineno" valign="top"></td><td class="left">   to which that request was directed.  The Host header field was</td><td> </td><td class="right">   to which that request was directed.  The Host header field was</td><td class="lineno" valign="top"></td></tr>
322
323     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
324     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 20 change blocks.&nbsp;</a></th></tr>
325     <tr class="stats"><td></td><th><i>60 lines changed or deleted</i></th><th><i> </i></th><th><i>36 lines changed or added</i></th><td></td></tr>
326     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.38. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
327   </table>
328   </body>
329   </html>
Note: See TracBrowser for help on using the repository browser.