source: draft-ietf-httpbis-http2/latest/draft-ietf-httpbis-http2.html @ 2124

Last change on this file since 2124 was 2124, checked in by martin.thomson@…, 7 years ago

Changing title.

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 146.5 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>Hypertext Transfer Protocol version 2.0</title><script>
7var buttonsAdded = false;
8
9function init() {
10  var fb = document.createElement("div");
11  fb.className = "feedback noprint";
12  fb.setAttribute("onclick", "feedback();");
13  fb.appendChild(document.createTextNode("feedback"));
14
15  var bodyl = document.getElementsByTagName("body");
16  bodyl.item(0).appendChild(fb);
17}
18
19function feedback() {
20  toggleButtonsToElementsByName("h1");
21  toggleButtonsToElementsByName("h2");
22  toggleButtonsToElementsByName("h3");
23  toggleButtonsToElementsByName("h4");
24 
25  buttonsAdded = !buttonsAdded;
26}
27
28function toggleButtonsToElementsByName(name) {
29  var list = document.getElementsByTagName(name);
30  for (var i = 0; i < list.length; i++) {
31    toggleButton(list.item(i));
32  }
33}
34
35function toggleButton(node) {
36  if (! buttonsAdded) {
37 
38    // docname
39    var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:";
40
41    var id = node.getAttribute("id");
42    // better id available?
43    var titlelinks = node.getElementsByTagName("a");
44    for (var i = 0; i < titlelinks.length; i++) {
45      var tl = titlelinks.item(i);
46      if (tl.getAttribute("id")) {
47        id = tl.getAttribute("id");
48      }
49    }
50
51    // ref
52    var ref = window.location.toString();
53    var hash = ref.indexOf("#");
54    if (hash != -1) {
55      ref = ref.substring(0, hash);
56    }
57    if (id != "") {
58      ref += "#" + id;
59    }
60   
61    // docname
62    var docname = "draft-ietf-httpbis-http2-latest";
63
64    // section
65    var section = node.textContent;
66    section = section.replace("\u00a0", " ");
67   
68    // build URI from template
69    var uri = template.replace("{docname}", encodeURIComponent(docname));
70    uri = uri.replace("{section}", encodeURIComponent(section));
71    uri = uri.replace("{ref}", encodeURIComponent(ref));
72 
73    var button = document.createElement("a");
74    button.className = "fbbutton noprint";
75    button.setAttribute("href", uri);
76    button.appendChild(document.createTextNode("send feedback"));
77    node.appendChild(button);
78  }
79  else {
80    var buttons = node.getElementsByTagName("a");
81    for (var i = 0; i < buttons.length; i++) {
82      var b = buttons.item(i);
83      if (b.className == "fbbutton noprint") {
84        node.removeChild(b);
85      }
86    }
87  }
88}</script><style type="text/css" title="Xml2Rfc (sans serif)">
89a {
90  text-decoration: none;
91}
92a.smpl {
93  color: black;
94}
95a:hover {
96  text-decoration: underline;
97}
98a:active {
99  text-decoration: underline;
100}
101address {
102  margin-top: 1em;
103  margin-left: 2em;
104  font-style: normal;
105}
106body {
107  color: black;
108  font-family: verdana, helvetica, arial, sans-serif;
109  font-size: 10pt;
110  margin-right: 2em;
111}
112cite {
113  font-style: normal;
114}
115dl {
116  margin-left: 2em;
117}
118ul.empty {
119  list-style-type: none;
120}
121ul.empty li {
122  margin-top: .5em;
123}
124dl p {
125  margin-left: 0em;
126}
127dt {
128  margin-top: .5em;
129}
130h1 {
131  font-size: 14pt;
132  line-height: 21pt;
133  page-break-after: avoid;
134}
135h1.np {
136  page-break-before: always;
137}
138h1 a {
139  color: #333333;
140}
141h2 {
142  font-size: 12pt;
143  line-height: 15pt;
144  page-break-after: avoid;
145}
146h3, h4, h5, h6 {
147  font-size: 10pt;
148  page-break-after: avoid;
149}
150h2 a, h3 a, h4 a, h5 a, h6 a {
151  color: black;
152}
153img {
154  margin-left: 3em;
155}
156li {
157  margin-left: 2em;
158}
159ol {
160  margin-left: 2em;
161}
162ol.la {
163  list-style-type: lower-alpha;
164}
165ol.ua {
166  list-style-type: upper-alpha;
167}
168ol p {
169  margin-left: 0em;
170}
171p {
172  margin-left: 2em;
173}
174pre {
175  margin-left: 3em;
176  background-color: lightyellow;
177  padding: .25em;
178  page-break-inside: avoid;
179}
180pre.ccmarker {
181  background-color: white;
182  color: gray;
183}
184pre.ccmarker > span {
185  font-size: small;
186}
187pre.cct {
188  margin-bottom: -1em;
189}
190pre.ccb {
191  margin-top: -1em;
192}
193pre.text2 {
194  border-style: dotted;
195  border-width: 1px;
196  background-color: #f0f0f0;
197  width: 69em;
198}
199pre.inline {
200  background-color: white;
201  padding: 0em;
202}
203pre.text {
204  border-style: dotted;
205  border-width: 1px;
206  background-color: #f8f8f8;
207  width: 69em;
208}
209pre.drawing {
210  border-style: solid;
211  border-width: 1px;
212  background-color: #f8f8f8;
213  padding: 2em;
214}
215table {
216  margin-left: 2em;
217}
218table.header {
219  border-spacing: 1px;
220  width: 95%;
221  font-size: 10pt;
222  color: white;
223}
224td.top {
225  vertical-align: top;
226}
227td.topnowrap {
228  vertical-align: top;
229  white-space: nowrap; 
230}
231table.header td {
232  background-color: gray;
233  width: 50%;
234}
235td.reference {
236  vertical-align: top;
237  white-space: nowrap;
238  padding-right: 1em;
239}
240thead {
241  display:table-header-group;
242}
243ul.toc, ul.toc ul {
244  list-style: none;
245  margin-left: 1.5em;
246  padding-left: 0em;
247}
248ul.toc li {
249  line-height: 150%;
250  font-weight: bold;
251  font-size: 10pt;
252  margin-left: 0em;
253}
254ul.toc li li {
255  line-height: normal;
256  font-weight: normal;
257  font-size: 9pt;
258  margin-left: 0em;
259}
260li.excluded {
261  font-size: 0pt;
262}
263ul p {
264  margin-left: 0em;
265}
266ul.ind, ul.ind ul {
267  list-style: none;
268  margin-left: 1.5em;
269  padding-left: 0em;
270  page-break-before: avoid;
271}
272ul.ind li {
273  font-weight: bold;
274  line-height: 200%;
275  margin-left: 0em;
276}
277ul.ind li li {
278  font-weight: normal;
279  line-height: 150%;
280  margin-left: 0em;
281}
282.avoidbreak {
283  page-break-inside: avoid;
284}
285
286.comment {
287  background-color: yellow;
288}
289.center {
290  text-align: center;
291}
292.error {
293  color: red;
294  font-style: italic;
295  font-weight: bold;
296}
297.figure {
298  font-weight: bold;
299  text-align: center;
300  font-size: 9pt;
301}
302.filename {
303  color: #333333;
304  font-weight: bold;
305  font-size: 12pt;
306  line-height: 21pt;
307  text-align: center;
308}
309.fn {
310  font-weight: bold;
311}
312.hidden {
313  display: none;
314}
315.left {
316  text-align: left;
317}
318.right {
319  text-align: right;
320}
321.title {
322  color: #990000;
323  font-size: 18pt;
324  line-height: 18pt;
325  font-weight: bold;
326  text-align: center;
327  margin-top: 36pt;
328}
329.vcardline {
330  display: block;
331}
332.warning {
333  font-size: 14pt;
334  background-color: yellow;
335}
336.feedback {
337  position: fixed;
338  bottom: 1%;
339  right: 1%;
340  padding: 3px 5px;
341  color: white;
342  border-radius: 5px;
343  background: #a00000;
344  border: 1px solid silver;
345}
346.fbbutton {
347  margin-left: 1em;
348  color: #303030;
349  font-size: small;
350  font-weight: normal;
351  background: #d0d000;
352  padding: 1px 4px;
353  border: 1px solid silver;
354  border-radius: 5px;
355}
356
357@media print {
358  .noprint {
359    display: none;
360  }
361 
362  a {
363    color: black;
364    text-decoration: none;
365  }
366
367  table.header {
368    width: 90%;
369  }
370
371  td.header {
372    width: 50%;
373    color: black;
374    background-color: white;
375    vertical-align: top;
376    font-size: 12pt;
377  }
378
379  ul.toc a:nth-child(2)::after {
380    content: leader('.') target-counter(attr(href), page);
381  }
382 
383  ul.ind li li a {
384    content: target-counter(attr(href), page);
385  }
386 
387  .print2col {
388    column-count: 2;
389    -moz-column-count: 2;
390    column-fill: auto;
391  }
392}
393
394@page {
395  @top-left {
396       content: "Internet-Draft"; 
397  } 
398  @top-right {
399       content: "January 2013"; 
400  } 
401  @top-center {
402       content: "HTTP/2.0"; 
403  } 
404  @bottom-left {
405       content: "Belshe, et al."; 
406  } 
407  @bottom-center {
408       content: "Expires July 20, 2013"; 
409  } 
410  @bottom-right {
411       content: "[Page " counter(page) "]"; 
412  } 
413}
414
415@page:first { 
416    @top-left {
417      content: normal;
418    }
419    @top-right {
420      content: normal;
421    }
422    @top-center {
423      content: normal;
424    }
425}
426</style><link rel="Contents" href="#rfc.toc">
427      <link rel="Author" href="#rfc.authors">
428      <link rel="Copyright" href="#rfc.copyrightnotice">
429      <link rel="Index" href="#rfc.index">
430      <link rel="Chapter" title="1 Overview" href="#rfc.section.1">
431      <link rel="Chapter" title="2 HTTP/2.0 Framing Layer" href="#rfc.section.2">
432      <link rel="Chapter" title="3 HTTP Layering over HTTP/2.0" href="#rfc.section.3">
433      <link rel="Chapter" title="4 Design Rationale and Notes" href="#rfc.section.4">
434      <link rel="Chapter" title="5 Security Considerations" href="#rfc.section.5">
435      <link rel="Chapter" title="6 Privacy Considerations" href="#rfc.section.6">
436      <link rel="Chapter" title="7 Requirements Notation" href="#rfc.section.7">
437      <link rel="Chapter" title="8 Acknowledgements" href="#rfc.section.8">
438      <link rel="Chapter" href="#rfc.section.9" title="9 Normative References">
439      <link rel="Appendix" title="A Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.A">
440      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.588, 2012-08-25 12:28:24, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
441      <meta name="keywords" content="HTTP">
442      <link rel="schema.dct" href="http://purl.org/dc/terms/">
443      <meta name="dct.creator" content="Belshe, M.">
444      <meta name="dct.creator" content="Peon, R.">
445      <meta name="dct.creator" content="Thomson, M.">
446      <meta name="dct.creator" content="Melnikov, A.">
447      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-http2-latest">
448      <meta name="dct.issued" scheme="ISO8601" content="2013-01-16">
449      <meta name="dct.abstract" content="This document describes HTTP/2.0, a protocol designed for low-latency transport of content over the World Wide Web. HTTP/2.0 introduces two layers of protocol. The lower layer is a general purpose framing layer which can be used atop a reliable transport (likely TCP) for multiplexed, prioritized, and compressed data communication of many concurrent streams. The upper layer of the protocol provides HTTP-like RFC2616 semantics for compatibility with existing HTTP application servers.">
450      <meta name="description" content="This document describes HTTP/2.0, a protocol designed for low-latency transport of content over the World Wide Web. HTTP/2.0 introduces two layers of protocol. The lower layer is a general purpose framing layer which can be used atop a reliable transport (likely TCP) for multiplexed, prioritized, and compressed data communication of many concurrent streams. The upper layer of the protocol provides HTTP-like RFC2616 semantics for compatibility with existing HTTP application servers.">
451   </head>
452   <body onload="init();">
453      <table class="header">
454         <tbody>
455            <tr>
456               <td class="left">HTTPbis Working Group</td>
457               <td class="right">M. Belshe</td>
458            </tr>
459            <tr>
460               <td class="left">Internet-Draft</td>
461               <td class="right">Twist</td>
462            </tr>
463            <tr>
464               <td class="left">Intended status: Informational</td>
465               <td class="right">R. Peon</td>
466            </tr>
467            <tr>
468               <td class="left">Expires: July 20, 2013</td>
469               <td class="right">Google, Inc</td>
470            </tr>
471            <tr>
472               <td class="left"></td>
473               <td class="right">M. Thomson, Editor</td>
474            </tr>
475            <tr>
476               <td class="left"></td>
477               <td class="right">Microsoft</td>
478            </tr>
479            <tr>
480               <td class="left"></td>
481               <td class="right">A. Melnikov, Editor</td>
482            </tr>
483            <tr>
484               <td class="left"></td>
485               <td class="right">Isode Ltd</td>
486            </tr>
487            <tr>
488               <td class="left"></td>
489               <td class="right">January 16, 2013</td>
490            </tr>
491         </tbody>
492      </table>
493      <p class="title">Hypertext Transfer Protocol version 2.0<br><span class="filename">draft-ietf-httpbis-http2-latest</span></p>
494      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
495      <p>This document describes HTTP/2.0, a protocol designed for low-latency transport of content over the World Wide Web. HTTP/2.0
496         introduces two layers of protocol. The lower layer is a general purpose framing layer which can be used atop a reliable transport
497         (likely TCP) for multiplexed, prioritized, and compressed data communication of many concurrent streams. The upper layer of
498         the protocol provides HTTP-like <a href="#RFC2616">RFC2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">[RFC2616]</cite> semantics for compatibility with existing HTTP application servers.
499      </p> 
500      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
501      <p>This draft is a work-in-progress, and does not yet reflect Working Group consensus.</p> 
502      <p>This draft contains features from the SPDY Protocol as a starting point, as per the Working Group's charter. Future drafts
503         will add, remove and change text, based upon the Working Group's decisions.
504      </p> 
505      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
506      </p> 
507      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/21">http://tools.ietf.org/wg/httpbis/trac/report/21</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
508      </p> 
509      <p>The changes in this draft are summarized in <a href="#changes.since.draft-ietf-httpbis-http2-00" title="Since draft-ietf-httpbis-http2-00">Appendix&nbsp;A.1</a>.
510      </p> 
511      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
512      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
513      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
514         working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
515      </p>
516      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
517         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
518         in progress”.
519      </p>
520      <p>This Internet-Draft will expire on July 20, 2013.</p>
521      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
522      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
523      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
524         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
525         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
526         BSD License.
527      </p>
528      <hr class="noprint">
529      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
530      <ul class="toc">
531         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#intro">Overview</a><ul>
532               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.1">Document Organization</a></li>
533               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.2">Definitions</a></li>
534            </ul>
535         </li>
536         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#FramingLayer">HTTP/2.0 Framing Layer</a><ul>
537               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.1">Session (Connections)</a></li>
538               <li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.2">Framing</a><ul>
539                     <li><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#ControlFrames">Control frames</a></li>
540                     <li><a href="#rfc.section.2.2.2">2.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#DataFrames">Data frames</a></li>
541                  </ul>
542               </li>
543               <li><a href="#rfc.section.2.3">2.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.3">Streams</a><ul>
544                     <li><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#StreamFrames">Stream frames</a></li>
545                     <li><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#StreamCreation">Stream creation</a><ul>
546                           <li><a href="#rfc.section.2.3.2.1">2.3.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.3.2.1">Unidirectional streams</a></li>
547                           <li><a href="#rfc.section.2.3.2.2">2.3.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.3.2.2">Bidirectional streams</a></li>
548                        </ul>
549                     </li>
550                     <li><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#StreamPriority">Stream priority</a></li>
551                     <li><a href="#rfc.section.2.3.4">2.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.3.4">Stream headers</a></li>
552                     <li><a href="#rfc.section.2.3.5">2.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.3.5">Stream data exchange</a></li>
553                     <li><a href="#rfc.section.2.3.6">2.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#StreamHalfClose">Stream half-close</a></li>
554                     <li><a href="#rfc.section.2.3.7">2.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#StreamClose">Stream close</a></li>
555                  </ul>
556               </li>
557               <li><a href="#rfc.section.2.4">2.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.4">Error Handling</a><ul>
558                     <li><a href="#rfc.section.2.4.1">2.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#SessionErrorHandler">Session Error Handling</a></li>
559                     <li><a href="#rfc.section.2.4.2">2.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#StreamErrorHandler">Stream Error Handling</a></li>
560                  </ul>
561               </li>
562               <li><a href="#rfc.section.2.5">2.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.5">Data flow</a></li>
563               <li><a href="#rfc.section.2.6">2.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.6">Control frame types</a><ul>
564                     <li><a href="#rfc.section.2.6.1">2.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#SYN_STREAM">SYN_STREAM</a></li>
565                     <li><a href="#rfc.section.2.6.2">2.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#SYN_REPLY">SYN_REPLY</a></li>
566                     <li><a href="#rfc.section.2.6.3">2.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#RST_STREAM">RST_STREAM</a></li>
567                     <li><a href="#rfc.section.2.6.4">2.6.4</a>&nbsp;&nbsp;&nbsp;<a href="#SETTINGS">SETTINGS</a></li>
568                     <li><a href="#rfc.section.2.6.5">2.6.5</a>&nbsp;&nbsp;&nbsp;<a href="#PING">PING</a></li>
569                     <li><a href="#rfc.section.2.6.6">2.6.6</a>&nbsp;&nbsp;&nbsp;<a href="#GOAWAY">GOAWAY</a></li>
570                     <li><a href="#rfc.section.2.6.7">2.6.7</a>&nbsp;&nbsp;&nbsp;<a href="#HEADERS">HEADERS</a></li>
571                     <li><a href="#rfc.section.2.6.8">2.6.8</a>&nbsp;&nbsp;&nbsp;<a href="#WINDOW_UPDATE">WINDOW_UPDATE</a></li>
572                     <li><a href="#rfc.section.2.6.9">2.6.9</a>&nbsp;&nbsp;&nbsp;<a href="#CREDENTIAL">CREDENTIAL</a></li>
573                     <li><a href="#rfc.section.2.6.10">2.6.10</a>&nbsp;&nbsp;&nbsp;<a href="#HeaderBlock">Name/Value Header Block</a><ul>
574                           <li><a href="#rfc.section.2.6.10.1">2.6.10.1</a>&nbsp;&nbsp;&nbsp;<a href="#Compression">Compression</a></li>
575                        </ul>
576                     </li>
577                  </ul>
578               </li>
579            </ul>
580         </li>
581         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#HTTPLayer">HTTP Layering over HTTP/2.0</a><ul>
582               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.1">Connection Management</a><ul>
583                     <li><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.1.1">Use of GOAWAY</a></li>
584                  </ul>
585               </li>
586               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.2">HTTP Request/Response</a><ul>
587                     <li><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.2.1">Request</a></li>
588                     <li><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.2.2">Response</a></li>
589                     <li><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#Authentication">Authentication</a><ul>
590                           <li><a href="#rfc.section.3.2.3.1">3.2.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.2.3.1">Stateless Authentication</a></li>
591                           <li><a href="#rfc.section.3.2.3.2">3.2.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.2.3.2">Stateful Authentication</a></li>
592                        </ul>
593                     </li>
594                  </ul>
595               </li>
596               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.3">Server Push Transactions</a><ul>
597                     <li><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.3.1">Server implementation</a></li>
598                     <li><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.3.2">Client implementation</a></li>
599                  </ul>
600               </li>
601            </ul>
602         </li>
603         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4">Design Rationale and Notes</a><ul>
604               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.1">Separation of Framing Layer and Application Layer</a></li>
605               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.2">Error handling - Framing Layer</a></li>
606               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.3">One Connection Per Domain</a></li>
607               <li><a href="#rfc.section.4.4">4.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.4">Fixed vs Variable Length Fields</a></li>
608               <li><a href="#rfc.section.4.5">4.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.5">Compression Context(s)</a></li>
609               <li><a href="#rfc.section.4.6">4.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.6">Unidirectional streams</a></li>
610               <li><a href="#rfc.section.4.7">4.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.7">Data Compression</a></li>
611               <li><a href="#rfc.section.4.8">4.8</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.8">Server Push</a></li>
612            </ul>
613         </li>
614         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5">Security Considerations</a><ul>
615               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.1">Use of Same-origin constraints</a></li>
616               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.2">HTTP Headers and HTTP/2.0 Headers</a></li>
617               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.3">Cross-Protocol Attacks</a></li>
618               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.4">Server Push Implicit Headers</a></li>
619            </ul>
620         </li>
621         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6">Privacy Considerations</a><ul>
622               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.1">Long Lived Connections</a></li>
623               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.2">SETTINGS frame</a></li>
624            </ul>
625         </li>
626         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.7">Requirements Notation</a></li>
627         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8">Acknowledgements</a></li>
628         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">Normative References</a></li>
629         <li><a href="#rfc.authors">Authors' Addresses</a></li>
630         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
631               <li><a href="#rfc.section.A.1">A.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.draft-ietf-httpbis-http2-00">Since draft-ietf-httpbis-http2-00</a></li>
632               <li><a href="#rfc.section.A.2">A.2</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.draft-mbelshe-httpbis-spdy-00">Since draft-mbelshe-httpbis-spdy-00</a></li>
633            </ul>
634         </li>
635         <li><a href="#rfc.index">Index</a></li>
636      </ul>
637      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="intro" href="#intro">Overview</a></h1>
638      <p id="rfc.section.1.p.1">One of the bottlenecks of HTTP implementations is that HTTP relies on multiple connections for concurrency. This causes several
639         problems, including additional round trips for connection setup, slow-start delays, and connection rationing by the client,
640         where it tries to avoid opening too many connections to any single server. HTTP pipelining helps some, but only achieves partial
641         multiplexing. In addition, pipelining has proven non-deployable in existing browsers due to intermediary interference.
642      </p>
643      <p id="rfc.section.1.p.2">HTTP/2.0 adds a framing layer for multiplexing multiple, concurrent streams across a single TCP connection (or any reliable
644         transport stream). The framing layer is optimized for HTTP-like request-response streams, such that applications which run
645         over HTTP today can work over HTTP/2.0 with little or no change on behalf of the web application writer.
646      </p>
647      <p id="rfc.section.1.p.3">The HTTP/2.0 session offers four improvements over HTTP: </p>
648      <ul class="empty">
649         <li>Multiplexed requests: There is no limit to the number of requests that can be issued concurrently over a single HTTP/2.0 connection.</li>
650         <li>Prioritized requests: Clients can request certain resources to be delivered first. This avoids the problem of congesting the
651            network channel with non-critical resources when a high-priority request is pending.
652         </li>
653         <li>Compressed headers: Clients today send a significant amount of redundant data in the form of HTTP headers. Because a single
654            web page may require 50 or 100 subrequests, this data is significant.
655         </li>
656         <li>Server pushed streams: Server Push enables content to be pushed from servers to clients without a request.</li>
657      </ul>
658      <p id="rfc.section.1.p.4">HTTP/2.0 attempts to preserve the existing semantics of HTTP. All features such as cookies, ETags, Vary headers, Content-Encoding
659         negotiations, etc work as they do with HTTP; HTTP/2.0 only replaces the way the data is written to the network.
660      </p>
661      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;Document Organization
662      </h2>
663      <p id="rfc.section.1.1.p.1">The HTTP/2.0 Specification is split into two parts: a framing layer (<a href="#FramingLayer" title="HTTP/2.0 Framing Layer">Section&nbsp;2</a>), which multiplexes a TCP connection into independent, length-prefixed frames, and an HTTP layer (<a href="#HTTPLayer" title="HTTP Layering over HTTP/2.0">Section&nbsp;3</a>), which specifies the mechanism for overlaying HTTP request/response pairs on top of the framing layer. While some of the
664         framing layer concepts are isolated from the HTTP layer, building a generic framing layer has not been a goal. The framing
665         layer is tailored to the needs of the HTTP protocol and server push.
666      </p>
667      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;Definitions
668      </h2>
669      <p id="rfc.section.1.2.p.1"> </p>
670      <ul class="empty">
671         <li>client: The endpoint initiating the HTTP/2.0 session.</li>
672         <li>connection: A transport-level connection between two endpoints.</li>
673         <li>endpoint: Either the client or server of a connection.</li>
674         <li>frame: A header-prefixed sequence of bytes sent over a HTTP/2.0 session.</li>
675         <li>server: The endpoint which did not initiate the HTTP/2.0 session.</li>
676         <li>session: A synonym for a connection.</li>
677         <li>session error: An error on the HTTP/2.0 session.</li>
678         <li>stream: A bi-directional flow of bytes across a virtual channel within a HTTP/2.0 session.</li>
679         <li>stream error: An error on an individual HTTP/2.0 stream.</li>
680      </ul>
681      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="FramingLayer" href="#FramingLayer">HTTP/2.0 Framing Layer</a></h1>
682      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;Session (Connections)
683      </h2>
684      <p id="rfc.section.2.1.p.1">The HTTP/2.0 framing layer (or "session") runs atop a reliable transport layer such as <a href="#RFC0793">TCP</a> <cite title="Transmission Control Protocol" id="rfc.xref.RFC0793.1">[RFC0793]</cite>. The client is the TCP connection initiator. HTTP/2.0 connections are persistent connections.
685      </p>
686      <p id="rfc.section.2.1.p.2">For best performance, it is expected that clients will not close open connections until the user navigates away from all web
687         pages referencing a connection, or until the server closes the connection. Servers are encouraged to leave connections open
688         for as long as possible, but can terminate idle connections if necessary. When either endpoint closes the transport-level
689         connection, it MUST first send a GOAWAY (<a href="#GOAWAY" title="GOAWAY">Section&nbsp;2.6.6</a>) frame so that the endpoints can reliably determine if requests finished before the close.
690      </p>
691      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;Framing
692      </h2>
693      <p id="rfc.section.2.2.p.1">Once the connection is established, clients and servers exchange framed messages. There are two types of frames: control frames (<a href="#ControlFrames" title="Control frames">Section&nbsp;2.2.1</a>) and data frames (<a href="#DataFrames" title="Data frames">Section&nbsp;2.2.2</a>). Frames always have a common header which is 8 bytes in length.
694      </p>
695      <p id="rfc.section.2.2.p.2">The first bit is a control bit indicating whether a frame is a control frame or data frame. Control frames carry a version
696         number, a frame type, flags, and a length. Data frames contain the stream ID, flags, and the length for the payload carried
697         after the common header. The simple header is designed to make reading and writing of frames easy.
698      </p>
699      <p id="rfc.section.2.2.p.3">All integer values, including length, version, and type, are in network byte order. HTTP/2.0 does not enforce alignment of
700         types in dynamically sized frames.
701      </p>
702      <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a id="ControlFrames" href="#ControlFrames">Control frames</a></h3>
703      <div id="rfc.figure.u.1"></div> <pre>+----------------------------------+
704|C| Version(15bits) | Type(16bits) |
705+----------------------------------+
706| Flags (8)  |  Length (24 bits)   |
707+----------------------------------+
708|               Data               |
709+----------------------------------+
710  </pre> <p id="rfc.section.2.2.1.p.2">Control bit: The 'C' bit is a single bit indicating if this is a control message. For control frames this value is always
711         1.
712      </p>
713      <p id="rfc.section.2.2.1.p.3">Version: The version number of the HTTP/2.0 protocol. This document describes HTTP/2.0 version 3.</p>
714      <p id="rfc.section.2.2.1.p.4">Type: The type of control frame. See Control Frames for the complete list of control frames.</p>
715      <p id="rfc.section.2.2.1.p.5">Flags: Flags related to this frame. Flags for control frames and data frames are different.</p>
716      <p id="rfc.section.2.2.1.p.6">Length: An unsigned 24-bit value representing the number of bytes after the length field.</p>
717      <p id="rfc.section.2.2.1.p.7">Data: data associated with this control frame. The format and length of this data is controlled by the control frame type.</p>
718      <p id="rfc.section.2.2.1.p.8">Control frame processing requirements: </p>
719      <ul class="empty">
720         <li>Note that full length control frames (16MB) can be large for implementations running on resource-limited hardware. In such
721            cases, implementations MAY limit the maximum length frame supported. However, all implementations MUST be able to receive
722            control frames of at least 8192 octets in length.
723         </li>
724      </ul>
725      <h3 id="rfc.section.2.2.2"><a href="#rfc.section.2.2.2">2.2.2</a>&nbsp;<a id="DataFrames" href="#DataFrames">Data frames</a></h3>
726      <div id="rfc.figure.u.2"></div> <pre>+----------------------------------+
727|C|       Stream-ID (31bits)       |
728+----------------------------------+
729| Flags (8)  |  Length (24 bits)   |
730+----------------------------------+
731|               Data               |
732+----------------------------------+
733  </pre> <p id="rfc.section.2.2.2.p.2">Control bit: For data frames this value is always 0.</p>
734      <p id="rfc.section.2.2.2.p.3">Stream-ID: A 31-bit value identifying the stream.</p>
735      <p id="rfc.section.2.2.2.p.4">Flags: Flags related to this frame. Valid flags are: </p>
736      <ul class="empty">
737         <li>0x01 = FLAG_FIN - signifies that this frame represents the last frame to be transmitted on this stream. See Stream Close (<a href="#StreamClose" title="Stream close">Section&nbsp;2.3.7</a>) below.
738         </li>
739         <li>0x02 = FLAG_COMPRESS - indicates that the data in this frame has been compressed.</li>
740      </ul>
741      <p id="rfc.section.2.2.2.p.5">Length: An unsigned 24-bit value representing the number of bytes after the length field. The total size of a data frame is
742         8 bytes + length. It is valid to have a zero-length data frame.
743      </p>
744      <p id="rfc.section.2.2.2.p.6">Data: The variable-length data payload; the length was defined in the length field.</p>
745      <p id="rfc.section.2.2.2.p.7">Data frame processing requirements: </p>
746      <ul class="empty">
747         <li>If an endpoint receives a data frame for a stream-id which is not open and the endpoint has not sent a GOAWAY (<a href="#GOAWAY" title="GOAWAY">Section&nbsp;2.6.6</a>) frame, it MUST send issue a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with the error code INVALID_STREAM for the stream-id.
748         </li>
749         <li>If the endpoint which created the stream receives a data frame before receiving a SYN_REPLY on that stream, it is a protocol
750            error, and the recipient MUST issue a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with the status code PROTOCOL_ERROR for the stream-id.
751         </li>
752         <li>Implementors note: If an endpoint receives multiple data frames for invalid stream-ids, it MAY close the session.</li>
753         <li>All HTTP/2.0 endpoints MUST accept compressed data frames. Compression of data frames is always done using zlib compression.
754            Each stream initializes and uses its own compression context dedicated to use within that stream. Endpoints are encouraged
755            to use application level compression rather than HTTP/2.0 stream level compression.
756         </li>
757         <li>Each HTTP/2.0 stream sending compressed frames creates its own zlib context for that stream, and these compression contexts
758            MUST be distinct from the compression contexts used with SYN_STREAM/SYN_REPLY/HEADER compression. (Thus, if both endpoints
759            of a stream are compressing data on the stream, there will be two zlib contexts, one for sending and one for receiving).
760         </li>
761      </ul>
762      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;Streams
763      </h2>
764      <p id="rfc.section.2.3.p.1">Streams are independent sequences of bi-directional data divided into frames with several properties: </p>
765      <ul class="empty">
766         <li>Streams may be created by either the client or server.</li>
767         <li>Streams optionally carry a set of name/value header pairs.</li>
768         <li>Streams can concurrently send data interleaved with other streams.</li>
769         <li>Streams may be cancelled.</li>
770      </ul>
771      <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="StreamFrames" href="#StreamFrames">Stream frames</a></h3>
772      <p id="rfc.section.2.3.1.p.1">HTTP/2.0 defines 3 control frames to manage the lifecycle of a stream: </p>
773      <ul class="empty">
774         <li>SYN_STREAM - Open a new stream</li>
775         <li>SYN_REPLY - Remote acknowledgement of a new, open stream</li>
776         <li>RST_STREAM - Close a stream</li>
777      </ul>
778      <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="StreamCreation" href="#StreamCreation">Stream creation</a></h3>
779      <p id="rfc.section.2.3.2.p.1">A stream is created by sending a control frame with the type set to SYN_STREAM (<a href="#SYN_STREAM" title="SYN_STREAM">Section&nbsp;2.6.1</a>). If the server is initiating the stream, the Stream-ID must be even. If the client is initiating the stream, the Stream-ID
780         must be odd. 0 is not a valid Stream-ID. Stream-IDs from each side of the connection must increase monotonically as new streams
781         are created. E.g. Stream 2 may be created after stream 3, but stream 7 must not be created after stream 9. Stream IDs do not
782         wrap: when a client or server cannot create a new stream id without exceeding a 31 bit value, it MUST NOT create a new stream.
783      </p>
784      <p id="rfc.section.2.3.2.p.2">The stream-id MUST increase with each new stream. If an endpoint receives a SYN_STREAM with a stream id which is less than
785         any previously received SYN_STREAM, it MUST issue a session error (<a href="#SessionErrorHandler" title="Session Error Handling">Section&nbsp;2.4.1</a>) with the status PROTOCOL_ERROR.
786      </p>
787      <p id="rfc.section.2.3.2.p.3">It is a protocol error to send two SYN_STREAMs with the same stream-id. If a recipient receives a second SYN_STREAM for the
788         same stream, it MUST issue a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with the status code PROTOCOL_ERROR.
789      </p>
790      <p id="rfc.section.2.3.2.p.4">Upon receipt of a SYN_STREAM, the recipient can reject the stream by sending a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with the error code REFUSED_STREAM. Note, however, that the creating endpoint may have already sent additional frames for
791         that stream which cannot be immediately stopped.
792      </p>
793      <p id="rfc.section.2.3.2.p.5">Once the stream is created, the creator may immediately send HEADERS or DATA frames for that stream, without needing to wait
794         for the recipient to acknowledge.
795      </p>
796      <h4 id="rfc.section.2.3.2.1"><a href="#rfc.section.2.3.2.1">2.3.2.1</a>&nbsp;Unidirectional streams
797      </h4>
798      <p id="rfc.section.2.3.2.1.p.1">When an endpoint creates a stream with the FLAG_UNIDIRECTIONAL flag set, it creates a unidirectional stream which the creating
799         endpoint can use to send frames, but the receiving endpoint cannot. The receiving endpoint is implicitly already in the half-closed (<a href="#StreamHalfClose" title="Stream half-close">Section&nbsp;2.3.6</a>) state.
800      </p>
801      <h4 id="rfc.section.2.3.2.2"><a href="#rfc.section.2.3.2.2">2.3.2.2</a>&nbsp;Bidirectional streams
802      </h4>
803      <p id="rfc.section.2.3.2.2.p.1">SYN_STREAM frames which do not use the FLAG_UNIDIRECTIONAL flag are bidirectional streams. Both endpoints can send data on
804         a bi-directional stream.
805      </p>
806      <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="StreamPriority" href="#StreamPriority">Stream priority</a></h3>
807      <p id="rfc.section.2.3.3.p.1">The creator of a stream assigns a priority for that stream. Priority is represented as an integer from 0 to 7. 0 represents
808         the highest priority and 7 represents the lowest priority.
809      </p>
810      <p id="rfc.section.2.3.3.p.2">The sender and recipient SHOULD use best-effort to process streams in the order of highest priority to lowest priority.</p>
811      <h3 id="rfc.section.2.3.4"><a href="#rfc.section.2.3.4">2.3.4</a>&nbsp;Stream headers
812      </h3>
813      <p id="rfc.section.2.3.4.p.1">Streams carry optional sets of name/value pair headers which carry metadata about the stream. After the stream has been created,
814         and as long as the sender is not closed (<a href="#StreamClose" title="Stream close">Section&nbsp;2.3.7</a>) or half-closed (<a href="#StreamHalfClose" title="Stream half-close">Section&nbsp;2.3.6</a>), each side may send HEADERS frame(s) containing the header data. Header data can be sent in multiple HEADERS frames, and
815         HEADERS frames may be interleaved with data frames.
816      </p>
817      <h3 id="rfc.section.2.3.5"><a href="#rfc.section.2.3.5">2.3.5</a>&nbsp;Stream data exchange
818      </h3>
819      <p id="rfc.section.2.3.5.p.1">Once a stream is created, it can be used to send arbitrary amounts of data. Generally this means that a series of data frames
820         will be sent on the stream until a frame containing the FLAG_FIN flag is set. The FLAG_FIN can be set on a SYN_STREAM (<a href="#SYN_STREAM" title="SYN_STREAM">Section&nbsp;2.6.1</a>), SYN_REPLY (<a href="#SYN_REPLY" title="SYN_REPLY">Section&nbsp;2.6.2</a>), HEADERS (<a href="#HEADERS" title="HEADERS">Section&nbsp;2.6.7</a>) or a DATA (<a href="#DataFrames" title="Data frames">Section&nbsp;2.2.2</a>) frame. Once the FLAG_FIN has been sent, the stream is considered to be half-closed.
821      </p>
822      <h3 id="rfc.section.2.3.6"><a href="#rfc.section.2.3.6">2.3.6</a>&nbsp;<a id="StreamHalfClose" href="#StreamHalfClose">Stream half-close</a></h3>
823      <p id="rfc.section.2.3.6.p.1">When one side of the stream sends a frame with the FLAG_FIN flag set, the stream is half-closed from that endpoint. The sender
824         of the FLAG_FIN MUST NOT send further frames on that stream. When both sides have half-closed, the stream is closed.
825      </p>
826      <p id="rfc.section.2.3.6.p.2">If an endpoint receives a data frame after the stream is half-closed from the sender (e.g. the endpoint has already received
827         a prior frame for the stream with the FIN flag set), it MUST send a RST_STREAM to the sender with the status STREAM_ALREADY_CLOSED.
828      </p>
829      <h3 id="rfc.section.2.3.7"><a href="#rfc.section.2.3.7">2.3.7</a>&nbsp;<a id="StreamClose" href="#StreamClose">Stream close</a></h3>
830      <p id="rfc.section.2.3.7.p.1">There are 3 ways that streams can be terminated: </p>
831      <ul class="empty">
832         <li>Normal termination: Normal stream termination occurs when both sender and recipient have half-closed the stream by sending
833            a FLAG_FIN.
834         </li>
835         <li>Abrupt termination: Either the client or server can send a RST_STREAM control frame at any time. A RST_STREAM contains an
836            error code to indicate the reason for failure. When a RST_STREAM is sent from the stream originator, it indicates a failure
837            to complete the stream and that no further data will be sent on the stream. When a RST_STREAM is sent from the stream recipient,
838            the sender, upon receipt, should stop sending any data on the stream. The stream recipient should be aware that there is a
839            race between data already in transit from the sender and the time the RST_STREAM is received. See Stream Error Handling (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>)
840         </li>
841         <li>TCP connection teardown: If the TCP connection is torn down while un-closed streams exist, then the endpoint must assume that
842            the stream was abnormally interrupted and may be incomplete.
843         </li>
844      </ul>
845      <p id="rfc.section.2.3.7.p.2">If an endpoint receives a data frame after the stream is closed, it must send a RST_STREAM to the sender with the status PROTOCOL_ERROR.</p>
846      <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;Error Handling
847      </h2>
848      <p id="rfc.section.2.4.p.1">The HTTP/2.0 framing layer has only two types of errors, and they are always handled consistently. Any reference in this specification
849         to "issue a session error" refers to <a href="#SessionErrorHandler" title="Session Error Handling">Section&nbsp;2.4.1</a>. Any reference to "issue a stream error" refers to <a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>.
850      </p>
851      <h3 id="rfc.section.2.4.1"><a href="#rfc.section.2.4.1">2.4.1</a>&nbsp;<a id="SessionErrorHandler" href="#SessionErrorHandler">Session Error Handling</a></h3>
852      <p id="rfc.section.2.4.1.p.1">A session error is any error which prevents further processing of the framing layer or which corrupts the session compression
853         state. When a session error occurs, the endpoint encountering the error MUST first send a GOAWAY (<a href="#GOAWAY" title="GOAWAY">Section&nbsp;2.6.6</a>) frame with the stream id of most recently received stream from the remote endpoint, and the error code for why the session
854         is terminating. After sending the GOAWAY frame, the endpoint MUST close the TCP connection.
855      </p>
856      <p id="rfc.section.2.4.1.p.2">Note that the session compression state is dependent upon both endpoints always processing all compressed data. If an endpoint
857         partially processes a frame containing compressed data without updating compression state properly, future control frames
858         which use compression will be always be errored. Implementations SHOULD always try to process compressed data so that errors
859         which could be handled as stream errors do not become session errors.
860      </p>
861      <p id="rfc.section.2.4.1.p.3">Note that because this GOAWAY is sent during a session error case, it is possible that the GOAWAY will not be reliably received
862         by the receiving endpoint. It is a best-effort attempt to communicate with the remote about why the session is going down.
863      </p>
864      <h3 id="rfc.section.2.4.2"><a href="#rfc.section.2.4.2">2.4.2</a>&nbsp;<a id="StreamErrorHandler" href="#StreamErrorHandler">Stream Error Handling</a></h3>
865      <p id="rfc.section.2.4.2.p.1">A stream error is an error related to a specific stream-id which does not affect processing of other streams at the framing
866         layer. Upon a stream error, the endpoint MUST send a RST_STREAM (<a href="#RST_STREAM" title="RST_STREAM">Section&nbsp;2.6.3</a>) frame which contains the stream id of the stream where the error occurred and the error status which caused the error. After
867         sending the RST_STREAM, the stream is closed to the sending endpoint. After sending the RST_STREAM, if the sender receives
868         any frames other than a RST_STREAM for that stream id, it will result in sending additional RST_STREAM frames. An endpoint
869         MUST NOT send a RST_STREAM in response to an RST_STREAM, as doing so would lead to RST_STREAM loops. Sending a RST_STREAM
870         does not cause the HTTP/2.0 session to be closed.
871      </p>
872      <p id="rfc.section.2.4.2.p.2">If an endpoint has multiple RST_STREAM frames to send in succession for the same stream-id and the same error code, it MAY
873         coalesce them into a single RST_STREAM frame. (This can happen if a stream is closed, but the remote sends multiple data frames.
874         There is no reason to send a RST_STREAM for each frame in succession).
875      </p>
876      <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;Data flow
877      </h2>
878      <p id="rfc.section.2.5.p.1">Because TCP provides a single stream of data on which HTTP/2.0 multiplexes multiple logical streams, clients and servers must
879         intelligently interleave data messages for concurrent sessions.
880      </p>
881      <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;Control frame types
882      </h2>
883      <h3 id="rfc.section.2.6.1"><a href="#rfc.section.2.6.1">2.6.1</a>&nbsp;<a id="SYN_STREAM" href="#SYN_STREAM">SYN_STREAM</a></h3>
884      <p id="rfc.section.2.6.1.p.1">The SYN_STREAM control frame allows the sender to asynchronously create a stream between the endpoints. See Stream Creation (<a href="#StreamCreation" title="Stream creation">Section&nbsp;2.3.2</a>)
885      </p>
886      <div id="rfc.figure.u.3"></div> <pre>+------------------------------------+
887|1|    version    |         1        |
888+------------------------------------+
889|  Flags (8)  |  Length (24 bits)    |
890+------------------------------------+
891|X|           Stream-ID (31bits)     |
892+------------------------------------+
893|X| Associated-To-Stream-ID (31bits) |
894+------------------------------------+
895| Pri|Unused | Slot |                |
896+-------------------+                |
897| Number of Name/Value pairs (int32) |   &lt;+
898+------------------------------------+    |
899|     Length of name (int32)         |    | This section is the
900+------------------------------------+    | "Name/Value Header
901|           Name (string)            |    | Block", and is
902+------------------------------------+    | compressed.
903|     Length of value  (int32)       |    |
904+------------------------------------+    |
905|          Value   (string)          |    |
906+------------------------------------+    |
907|           (repeats)                |   &lt;+
908            </pre> <p id="rfc.section.2.6.1.p.3">Flags: Flags related to this frame. Valid flags are: </p>
909      <ul class="empty">
910         <li>0x01 = FLAG_FIN - marks this frame as the last frame to be transmitted on this stream and puts the sender in the half-closed (<a href="#StreamHalfClose" title="Stream half-close">Section&nbsp;2.3.6</a>) state.
911         </li>
912         <li>0x02 = FLAG_UNIDIRECTIONAL - a stream created with this flag puts the recipient in the half-closed (<a href="#StreamHalfClose" title="Stream half-close">Section&nbsp;2.3.6</a>) state.
913         </li>
914      </ul>
915      <p id="rfc.section.2.6.1.p.4">Length: The length is the number of bytes which follow the length field in the frame. For SYN_STREAM frames, this is 10 bytes
916         plus the length of the compressed Name/Value block.
917      </p>
918      <p id="rfc.section.2.6.1.p.5">Stream-ID: The 31-bit identifier for this stream. This stream-id will be used in frames which are part of this stream.</p>
919      <p id="rfc.section.2.6.1.p.6">Associated-To-Stream-ID: The 31-bit identifier for a stream which this stream is associated to. If this stream is independent
920         of all other streams, it should be 0.
921      </p>
922      <p id="rfc.section.2.6.1.p.7">Priority: A 3-bit priority (<a href="#StreamPriority" title="Stream priority">Section&nbsp;2.3.3</a>) field.
923      </p>
924      <p id="rfc.section.2.6.1.p.8">Unused: 5 bits of unused space, reserved for future use.</p>
925      <p id="rfc.section.2.6.1.p.9">Slot: An 8 bit unsigned integer specifying the index in the server's CREDENTIAL vector of the client certificate to be used
926         for this request. see CREDENTIAL frame (<a href="#CREDENTIAL" title="CREDENTIAL">Section&nbsp;2.6.9</a>). The value 0 means no client certificate should be associated with this stream.
927      </p>
928      <p id="rfc.section.2.6.1.p.10">Name/Value Header Block: A set of name/value pairs carried as part of the SYN_STREAM. see Name/Value Header Block (<a href="#HeaderBlock" title="Name/Value Header Block">Section&nbsp;2.6.10</a>).
929      </p>
930      <p id="rfc.section.2.6.1.p.11">If an endpoint receives a SYN_STREAM which is larger than the implementation supports, it MAY send a RST_STREAM with error
931         code FRAME_TOO_LARGE. All implementations MUST support the minimum size limits defined in the Control Frames section (<a href="#ControlFrames" title="Control frames">Section&nbsp;2.2.1</a>).
932      </p>
933      <h3 id="rfc.section.2.6.2"><a href="#rfc.section.2.6.2">2.6.2</a>&nbsp;<a id="SYN_REPLY" href="#SYN_REPLY">SYN_REPLY</a></h3>
934      <p id="rfc.section.2.6.2.p.1">SYN_REPLY indicates the acceptance of a stream creation by the recipient of a SYN_STREAM frame.</p>
935      <div id="rfc.figure.u.4"></div> <pre>+------------------------------------+
936|1|    version    |         2        |
937+------------------------------------+
938|  Flags (8)  |  Length (24 bits)    |
939+------------------------------------+
940|X|           Stream-ID (31bits)     |
941+------------------------------------+
942| Number of Name/Value pairs (int32) |   &lt;+
943+------------------------------------+    |
944|     Length of name (int32)         |    | This section is the
945+------------------------------------+    | "Name/Value Header
946|           Name (string)            |    | Block", and is
947+------------------------------------+    | compressed.
948|     Length of value  (int32)       |    |
949+------------------------------------+    |
950|          Value   (string)          |    |
951+------------------------------------+    |
952|           (repeats)                |   &lt;+
953            </pre> <p id="rfc.section.2.6.2.p.3">Flags: Flags related to this frame. Valid flags are: </p>
954      <ul class="empty">
955         <li>0x01 = FLAG_FIN - marks this frame as the last frame to be transmitted on this stream and puts the sender in the half-closed (<a href="#StreamHalfClose" title="Stream half-close">Section&nbsp;2.3.6</a>) state.
956         </li>
957      </ul>
958      <p id="rfc.section.2.6.2.p.4">Length: The length is the number of bytes which follow the length field in the frame. For SYN_REPLY frames, this is 4 bytes
959         plus the length of the compressed Name/Value block.
960      </p>
961      <p id="rfc.section.2.6.2.p.5">Stream-ID: The 31-bit identifier for this stream.</p>
962      <p id="rfc.section.2.6.2.p.6">If an endpoint receives multiple SYN_REPLY frames for the same active stream ID, it MUST issue a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with the error code STREAM_IN_USE.
963      </p>
964      <p id="rfc.section.2.6.2.p.7">Name/Value Header Block: A set of name/value pairs carried as part of the SYN_STREAM. see Name/Value Header Block (<a href="#HeaderBlock" title="Name/Value Header Block">Section&nbsp;2.6.10</a>).
965      </p>
966      <p id="rfc.section.2.6.2.p.8">If an endpoint receives a SYN_REPLY which is larger than the implementation supports, it MAY send a RST_STREAM with error
967         code FRAME_TOO_LARGE. All implementations MUST support the minimum size limits defined in the Control Frames section (<a href="#ControlFrames" title="Control frames">Section&nbsp;2.2.1</a>).
968      </p>
969      <h3 id="rfc.section.2.6.3"><a href="#rfc.section.2.6.3">2.6.3</a>&nbsp;<a id="RST_STREAM" href="#RST_STREAM">RST_STREAM</a></h3>
970      <p id="rfc.section.2.6.3.p.1">The RST_STREAM frame allows for abnormal termination of a stream. When sent by the creator of a stream, it indicates the creator
971         wishes to cancel the stream. When sent by the recipient of a stream, it indicates an error or that the recipient did not want
972         to accept the stream, so the stream should be closed.
973      </p>
974      <div id="rfc.figure.u.5"></div> <pre>+----------------------------------+
975|1|   version    |         3       |
976+----------------------------------+
977| Flags (8)  |         8           |
978+----------------------------------+
979|X|          Stream-ID (31bits)    |
980+----------------------------------+
981|          Status code             |
982+----------------------------------+
983            </pre> <p id="rfc.section.2.6.3.p.3">Flags: Flags related to this frame. RST_STREAM does not define any flags. This value must be 0.</p>
984      <p id="rfc.section.2.6.3.p.4">Length: An unsigned 24-bit value representing the number of bytes after the length field. For RST_STREAM control frames, this
985         value is always 8.
986      </p>
987      <p id="rfc.section.2.6.3.p.5">Stream-ID: The 31-bit identifier for this stream.</p>
988      <p id="rfc.section.2.6.3.p.6">Status code: (32 bits) An indicator for why the stream is being terminated.The following status codes are defined: </p>
989      <ul class="empty">
990         <li>1 - PROTOCOL_ERROR. This is a generic error, and should only be used if a more specific error is not available.</li>
991         <li>2 - INVALID_STREAM. This is returned when a frame is received for a stream which is not active.</li>
992         <li>3 - REFUSED_STREAM. Indicates that the stream was refused before any processing has been done on the stream.</li>
993         <li>4 - UNSUPPORTED_VERSION. Indicates that the recipient of a stream does not support the HTTP/2.0 version requested.</li>
994         <li>5 - CANCEL. Used by the creator of a stream to indicate that the stream is no longer needed.</li>
995         <li>6 - INTERNAL_ERROR. This is a generic error which can be used when the implementation has internally failed, not due to anything
996            in the protocol.
997         </li>
998         <li>7 - FLOW_CONTROL_ERROR. The endpoint detected that its peer violated the flow control protocol.</li>
999         <li>8 - STREAM_IN_USE. The endpoint received a SYN_REPLY for a stream already open.</li>
1000         <li>9 - STREAM_ALREADY_CLOSED. The endpoint received a data or SYN_REPLY frame for a stream which is half closed.</li>
1001         <li>10 - INVALID_CREDENTIALS. The server received a request for a resource whose origin does not have valid credentials in the
1002            client certificate vector.
1003         </li>
1004         <li>11 - FRAME_TOO_LARGE. The endpoint received a frame which this implementation could not support. If FRAME_TOO_LARGE is sent
1005            for a SYN_STREAM, HEADERS, or SYN_REPLY frame without fully processing the compressed portion of those frames, then the compression
1006            state will be out-of-sync with the other endpoint. In this case, senders of FRAME_TOO_LARGE MUST close the session.
1007         </li>
1008         <li>Note: 0 is not a valid status code for a RST_STREAM.</li>
1009      </ul>
1010      <p id="rfc.section.2.6.3.p.7">After receiving a RST_STREAM on a stream, the recipient must not send additional frames for that stream, and the stream moves
1011         into the closed state.
1012      </p>
1013      <h3 id="rfc.section.2.6.4"><a href="#rfc.section.2.6.4">2.6.4</a>&nbsp;<a id="SETTINGS" href="#SETTINGS">SETTINGS</a></h3>
1014      <p id="rfc.section.2.6.4.p.1">A SETTINGS frame contains a set of id/value pairs for communicating configuration data about how the two endpoints may communicate.
1015         SETTINGS frames can be sent at any time by either endpoint, are optionally sent, and are fully asynchronous. When the server
1016         is the sender, the sender can request that configuration data be persisted by the client across HTTP/2.0 sessions and returned
1017         to the server in future communications.
1018      </p>
1019      <p id="rfc.section.2.6.4.p.2">Persistence of SETTINGS ID/Value pairs is done on a per origin/IP pair (the "origin" is the set of scheme, host, and port
1020         from the URI. See <a href="#RFC6454" id="rfc.xref.RFC6454.1"><cite title="The Web Origin Concept">[RFC6454]</cite></a>). That is, when a client connects to a server, and the server persists settings within the client, the client SHOULD return
1021         the persisted settings on future connections to the same origin AND IP address and TCP port. Clients MUST NOT request servers
1022         to use the persistence features of the SETTINGS frames, and servers MUST ignore persistence related flags sent by a client.
1023      </p>
1024      <div id="rfc.figure.u.6"></div> <pre>+----------------------------------+
1025|1|   version    |         4       |
1026+----------------------------------+
1027| Flags (8)  |  Length (24 bits)   |
1028+----------------------------------+
1029|         Number of entries        |
1030+----------------------------------+
1031|          ID/Value Pairs          |
1032|             ...                  |
1033            </pre> <p id="rfc.section.2.6.4.p.4">Control bit: The control bit is always 1 for this message.</p>
1034      <p id="rfc.section.2.6.4.p.5">Version: The HTTP/2.0 version number.</p>
1035      <p id="rfc.section.2.6.4.p.6">Type: The message type for a SETTINGS message is 4.</p>
1036      <p id="rfc.section.2.6.4.p.7">Flags: FLAG_SETTINGS_CLEAR_SETTINGS (0x1): When set, the client should clear any previously persisted SETTINGS ID/Value pairs.
1037         If this frame contains ID/Value pairs with the FLAG_SETTINGS_PERSIST_VALUE set, then the client will first clear its existing,
1038         persisted settings, and then persist the values with the flag set which are contained within this frame. Because persistence
1039         is only implemented on the client, this flag can only be used when the sender is the server.
1040      </p>
1041      <p id="rfc.section.2.6.4.p.8">Length: An unsigned 24-bit value representing the number of bytes after the length field. The total size of a SETTINGS frame
1042         is 8 bytes + length.
1043      </p>
1044      <p id="rfc.section.2.6.4.p.9">Number of entries: A 32-bit value representing the number of ID/value pairs in this message.</p>
1045      <p id="rfc.section.2.6.4.p.10">ID: A 32-bit ID number, comprised of 8 bits of flags and 24 bits of unique ID. </p>
1046      <ul class="empty">
1047         <li>ID.flags:
1048            <ul class="empty">
1049               <li>FLAG_SETTINGS_PERSIST_VALUE (0x1): When set, the sender of this SETTINGS frame is requesting that the recipient persist the
1050                  ID/Value and return it in future SETTINGS frames sent from the sender to this recipient. Because persistence is only implemented
1051                  on the client, this flag is only sent by the server.
1052               </li>
1053               <li>FLAG_SETTINGS_PERSISTED (0x2): When set, the sender is notifying the recipient that this ID/Value pair was previously sent
1054                  to the sender by the recipient with the FLAG_SETTINGS_PERSIST_VALUE, and the sender is returning it. Because persistence is
1055                  only implemented on the client, this flag is only sent by the client.
1056               </li>
1057            </ul> 
1058         </li>
1059         <li>Defined IDs:
1060            <ul class="empty">
1061               <li>1 - SETTINGS_UPLOAD_BANDWIDTH allows the sender to send its expected upload bandwidth on this channel. This number is an estimate.
1062                  The value should be the integral number of kilobytes per second that the sender predicts as an expected maximum upload channel
1063                  capacity.
1064               </li>
1065               <li>2 - SETTINGS_DOWNLOAD_BANDWIDTH allows the sender to send its expected download bandwidth on this channel. This number is
1066                  an estimate. The value should be the integral number of kilobytes per second that the sender predicts as an expected maximum
1067                  download channel capacity.
1068               </li>
1069               <li>3 - SETTINGS_ROUND_TRIP_TIME allows the sender to send its expected round-trip-time on this channel. The round trip time is
1070                  defined as the minimum amount of time to send a control frame from this client to the remote and receive a response. The value
1071                  is represented in milliseconds.
1072               </li>
1073               <li>4 - SETTINGS_MAX_CONCURRENT_STREAMS allows the sender to inform the remote endpoint the maximum number of concurrent streams
1074                  which it will allow. By default there is no limit. For implementors it is recommended that this value be no smaller than 100.
1075               </li>
1076               <li>5 - SETTINGS_CURRENT_CWND allows the sender to inform the remote endpoint of the current TCP CWND value.</li>
1077               <li>6 - SETTINGS_DOWNLOAD_RETRANS_RATE allows the sender to inform the remote endpoint the retransmission rate (bytes retransmitted
1078                  / total bytes transmitted).
1079               </li>
1080               <li>7 - SETTINGS_INITIAL_WINDOW_SIZE allows the sender to inform the remote endpoint the initial window size (in bytes) for new
1081                  streams.
1082               </li>
1083               <li>8 - SETTINGS_CLIENT_CERTIFICATE_VECTOR_SIZE allows the server to inform the client of the new size of the client certificate
1084                  vector.
1085               </li>
1086            </ul> 
1087         </li>
1088      </ul>
1089      <p id="rfc.section.2.6.4.p.11">Value: A 32-bit value.</p>
1090      <p id="rfc.section.2.6.4.p.12">The message is intentionally extensible for future information which may improve client-server communications. The sender
1091         does not need to send every type of ID/value. It must only send those for which it has accurate values to convey. When multiple
1092         ID/value pairs are sent, they should be sent in order of lowest id to highest id. A single SETTINGS frame MUST not contain
1093         multiple values for the same ID. If the recipient of a SETTINGS frame discovers multiple values for the same ID, it MUST ignore
1094         all values except the first one.
1095      </p>
1096      <p id="rfc.section.2.6.4.p.13">A server may send multiple SETTINGS frames containing different ID/Value pairs. When the same ID/Value is sent twice, the
1097         most recent value overrides any previously sent values. If the server sends IDs 1, 2, and 3 with the FLAG_SETTINGS_PERSIST_VALUE
1098         in a first SETTINGS frame, and then sends IDs 4 and 5 with the FLAG_SETTINGS_PERSIST_VALUE, when the client returns the persisted
1099         state on its next SETTINGS frame, it SHOULD send all 5 settings (1, 2, 3, 4, and 5 in this example) to the server.
1100      </p>
1101      <h3 id="rfc.section.2.6.5"><a href="#rfc.section.2.6.5">2.6.5</a>&nbsp;<a id="PING" href="#PING">PING</a></h3>
1102      <p id="rfc.section.2.6.5.p.1">The PING control frame is a mechanism for measuring a minimal round-trip time from the sender. It can be sent from the client
1103         or the server. Recipients of a PING frame should send an identical frame to the sender as soon as possible (if there is other
1104         pending data waiting to be sent, PING should take highest priority). Each ping sent by a sender should use a unique ID.
1105      </p>
1106      <div id="rfc.figure.u.7"></div> <pre>+----------------------------------+
1107|1|   version    |         6       |
1108+----------------------------------+
1109| 0 (flags) |     4 (length)       |
1110+----------------------------------|
1111|            32-bit ID             |
1112+----------------------------------+
1113            </pre> <p id="rfc.section.2.6.5.p.3">Control bit: The control bit is always 1 for this message.</p>
1114      <p id="rfc.section.2.6.5.p.4">Version: The HTTP/2.0 version number.</p>
1115      <p id="rfc.section.2.6.5.p.5">Type: The message type for a PING message is 6.</p>
1116      <p id="rfc.section.2.6.5.p.6">Length: This frame is always 4 bytes long.</p>
1117      <p id="rfc.section.2.6.5.p.7">ID: A unique ID for this ping, represented as an unsigned 32 bit value. When the client initiates a ping, it must use an odd
1118         numbered ID. When the server initiates a ping, it must use an even numbered ping. Use of odd/even IDs is required in order
1119         to avoid accidental looping on PINGs (where each side initiates an identical PING at the same time).
1120      </p>
1121      <p id="rfc.section.2.6.5.p.8">Note: If a sender uses all possible PING ids (e.g. has sent all 2^31 possible IDs), it can wrap and start re-using IDs.</p>
1122      <p id="rfc.section.2.6.5.p.9">If a server receives an even numbered PING which it did not initiate, it must ignore the PING. If a client receives an odd
1123         numbered PING which it did not initiate, it must ignore the PING.
1124      </p>
1125      <h3 id="rfc.section.2.6.6"><a href="#rfc.section.2.6.6">2.6.6</a>&nbsp;<a id="GOAWAY" href="#GOAWAY">GOAWAY</a></h3>
1126      <p id="rfc.section.2.6.6.p.1">The GOAWAY control frame is a mechanism to tell the remote side of the connection to stop creating streams on this session.
1127         It can be sent from the client or the server. Once sent, the sender will not respond to any new SYN_STREAMs on this session.
1128         Recipients of a GOAWAY frame must not send additional streams on this session, although a new session can be established for
1129         new streams. The purpose of this message is to allow an endpoint to gracefully stop accepting new streams (perhaps for a reboot
1130         or maintenance), while still finishing processing of previously established streams.
1131      </p>
1132      <p id="rfc.section.2.6.6.p.2">There is an inherent race condition between an endpoint sending SYN_STREAMs and the remote sending a GOAWAY message. To deal
1133         with this case, the GOAWAY contains a last-stream-id indicating the stream-id of the last stream which was created on the
1134         sending endpoint in this session. If the receiver of the GOAWAY sent new SYN_STREAMs for sessions after this last-stream-id,
1135         they were not processed by the server and the receiver may treat the stream as though it had never been created at all (hence
1136         the receiver may want to re-create the stream later on a new session).
1137      </p>
1138      <p id="rfc.section.2.6.6.p.3">Endpoints should always send a GOAWAY message before closing a connection so that the remote can know whether a stream has
1139         been partially processed or not. (For example, if an HTTP client sends a POST at the same time that a server closes a connection,
1140         the client cannot know if the server started to process that POST request if the server does not send a GOAWAY frame to indicate
1141         where it stopped working).
1142      </p>
1143      <p id="rfc.section.2.6.6.p.4">After sending a GOAWAY message, the sender must ignore all SYN_STREAM frames for new streams.</p>
1144      <div id="rfc.figure.u.8"></div> <pre>+----------------------------------+
1145|1|   version    |         7       |
1146+----------------------------------+
1147| 0 (flags) |     8 (length)       |
1148+----------------------------------|
1149|X|  Last-good-stream-ID (31 bits) |
1150+----------------------------------+
1151|          Status code             |
1152+----------------------------------+
1153            </pre> <p id="rfc.section.2.6.6.p.6">Control bit: The control bit is always 1 for this message.</p>
1154      <p id="rfc.section.2.6.6.p.7">Version: The HTTP/2.0 version number.</p>
1155      <p id="rfc.section.2.6.6.p.8">Type: The message type for a GOAWAY message is 7.</p>
1156      <p id="rfc.section.2.6.6.p.9">Length: This frame is always 8 bytes long.</p>
1157      <p id="rfc.section.2.6.6.p.10">Last-good-stream-Id: The last stream id which was replied to (with either a SYN_REPLY or RST_STREAM) by the sender of the
1158         GOAWAY message. If no streams were replied to, this value MUST be 0.
1159      </p>
1160      <p id="rfc.section.2.6.6.p.11">Status: The reason for closing the session. </p>
1161      <ul class="empty">
1162         <li>0 - OK. This is a normal session teardown.</li>
1163         <li>1 - PROTOCOL_ERROR. This is a generic error, and should only be used if a more specific error is not available.</li>
1164         <li>2 - INTERNAL_ERROR. This is a generic error which can be used when the implementation has internally failed, not due to anything
1165            in the protocol.
1166         </li>
1167      </ul>
1168      <h3 id="rfc.section.2.6.7"><a href="#rfc.section.2.6.7">2.6.7</a>&nbsp;<a id="HEADERS" href="#HEADERS">HEADERS</a></h3>
1169      <p id="rfc.section.2.6.7.p.1">The HEADERS frame augments a stream with additional headers. It may be optionally sent on an existing stream at any time.
1170         Specific application of the headers in this frame is application-dependent. The name/value header block within this frame
1171         is compressed.
1172      </p>
1173      <div id="rfc.figure.u.9"></div> <pre>+------------------------------------+
1174|1|   version     |          8       |
1175+------------------------------------+
1176| Flags (8)  |   Length (24 bits)    |
1177+------------------------------------+
1178|X|          Stream-ID (31bits)      |
1179+------------------------------------+
1180| Number of Name/Value pairs (int32) |   &lt;+
1181+------------------------------------+    |
1182|     Length of name (int32)         |    | This section is the
1183+------------------------------------+    | "Name/Value Header
1184|           Name (string)            |    | Block", and is
1185+------------------------------------+    | compressed.
1186|     Length of value  (int32)       |    |
1187+------------------------------------+    |
1188|          Value   (string)          |    |
1189+------------------------------------+    |
1190|           (repeats)                |   &lt;+
1191            </pre> <p id="rfc.section.2.6.7.p.3">Flags: Flags related to this frame. Valid flags are: </p>
1192      <ul class="empty">
1193         <li>0x01 = FLAG_FIN - marks this frame as the last frame to be transmitted on this stream and puts the sender in the half-closed (<a href="#StreamHalfClose" title="Stream half-close">Section&nbsp;2.3.6</a>) state.
1194         </li>
1195      </ul>
1196      <p id="rfc.section.2.6.7.p.4">Length: An unsigned 24 bit value representing the number of bytes after the length field. The minimum length of the length
1197         field is 4 (when the number of name value pairs is 0).
1198      </p>
1199      <p id="rfc.section.2.6.7.p.5">Stream-ID: The stream this HEADERS block is associated with.</p>
1200      <p id="rfc.section.2.6.7.p.6">Name/Value Header Block: A set of name/value pairs carried as part of the SYN_STREAM. see Name/Value Header Block (<a href="#HeaderBlock" title="Name/Value Header Block">Section&nbsp;2.6.10</a>).
1201      </p>
1202      <h3 id="rfc.section.2.6.8"><a href="#rfc.section.2.6.8">2.6.8</a>&nbsp;<a id="WINDOW_UPDATE" href="#WINDOW_UPDATE">WINDOW_UPDATE</a></h3>
1203      <p id="rfc.section.2.6.8.p.1">The WINDOW_UPDATE control frame is used to implement per stream flow control in HTTP/2.0. Flow control in HTTP/2.0 is per
1204         hop, that is, only between the two endpoints of a HTTP/2.0 connection. If there are one or more intermediaries between the
1205         client and the origin server, flow control signals are not explicitly forwarded by the intermediaries. (However, throttling
1206         of data transfer by any recipient may have the effect of indirectly propagating flow control information upstream back to
1207         the original sender.) Flow control only applies to the data portion of data frames. Recipients must buffer all control frames.
1208         If a recipient fails to buffer an entire control frame, it MUST issue a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with the status code FLOW_CONTROL_ERROR for the stream.
1209      </p>
1210      <p id="rfc.section.2.6.8.p.2">Flow control in HTTP/2.0 is implemented by a data transfer window kept by the sender of each stream. The data transfer window
1211         is a simple uint32 that indicates how many bytes of data the sender can transmit. After a stream is created, but before any
1212         data frames have been transmitted, the sender begins with the initial window size. This window size is a measure of the buffering
1213         capability of the recipient. The sender must not send a data frame with data length greater than the transfer window size.
1214         After sending each data frame, the sender decrements its transfer window size by the amount of data transmitted. When the
1215         window size becomes less than or equal to 0, the sender must pause transmitting data frames. At the other end of the stream,
1216         the recipient sends a WINDOW_UPDATE control back to notify the sender that it has consumed some data and freed up buffer space
1217         to receive more data.
1218      </p>
1219      <div id="rfc.figure.u.10"></div> <pre>+----------------------------------+
1220|1|   version    |         9       |
1221+----------------------------------+
1222| 0 (flags) |     8 (length)       |
1223+----------------------------------+
1224|X|     Stream-ID (31-bits)        |
1225+----------------------------------+
1226|X|  Delta-Window-Size (31-bits)   |
1227+----------------------------------+
1228            </pre> <p id="rfc.section.2.6.8.p.4">Control bit: The control bit is always 1 for this message.</p>
1229      <p id="rfc.section.2.6.8.p.5">Version: The HTTP/2.0 version number.</p>
1230      <p id="rfc.section.2.6.8.p.6">Type: The message type for a WINDOW_UPDATE message is 9.</p>
1231      <p id="rfc.section.2.6.8.p.7">Length: The length field is always 8 for this frame (there are 8 bytes after the length field).</p>
1232      <p id="rfc.section.2.6.8.p.8">Stream-ID: The stream ID that this WINDOW_UPDATE control frame is for.</p>
1233      <p id="rfc.section.2.6.8.p.9">Delta-Window-Size: The additional number of bytes that the sender can transmit in addition to existing remaining window size.
1234         The legal range for this field is 1 to 2^31 - 1 (0x7fffffff) bytes.
1235      </p>
1236      <p id="rfc.section.2.6.8.p.10">The window size as kept by the sender must never exceed 2^31 (although it can become negative in one special case). If a sender
1237         receives a WINDOW_UPDATE that causes the its window size to exceed this limit, it must send RST_STREAM with status code FLOW_CONTROL_ERROR
1238         to terminate the stream.
1239      </p>
1240      <p id="rfc.section.2.6.8.p.11">When a HTTP/2.0 connection is first established, the default initial window size for all streams is 64KB. An endpoint can
1241         use the SETTINGS control frame to adjust the initial window size for the connection. That is, its peer can start out using
1242         the 64KB default initial window size when sending data frames before receiving the SETTINGS. Because SETTINGS is asynchronous,
1243         there may be a race condition if the recipient wants to decrease the initial window size, but its peer immediately sends 64KB
1244         on the creation of a new connection, before waiting for the SETTINGS to arrive. This is one case where the window size kept
1245         by the sender will become negative. Once the sender detects this condition, it must stop sending data frames and wait for
1246         the recipient to catch up. The recipient has two choices:
1247      </p>
1248      <ul class="empty">
1249         <li>immediately send RST_STREAM with FLOW_CONTROL_ERROR status code.</li>
1250         <li>allow the head of line blocking (as there is only one stream for the session and the amount of data in flight is bounded by
1251            the default initial window size), and send WINDOW_UPDATE as it consumes data.
1252         </li>
1253      </ul>
1254      <p id="rfc.section.2.6.8.p.12">In the case of option 2, both sides must compute the window size based on the initial window size in the SETTINGS. For example,
1255         if the recipient sets the initial window size to be 16KB, and the sender sends 64KB immediately on connection establishment,
1256         the sender will discover its window size is -48KB on receipt of the SETTINGS. As the recipient consumes the first 16KB, it
1257         must send a WINDOW_UPDATE of 16KB back to the sender. This interaction continues until the sender's window size becomes positive
1258         again, and it can resume transmitting data frames.
1259      </p>
1260      <p id="rfc.section.2.6.8.p.13">After the recipient reads in a data frame with FLAG_FIN that marks the end of the data stream, it should not send WINDOW_UPDATE
1261         frames as it consumes the last data frame. A sender should ignore all the WINDOW_UPDATE frames associated with the stream
1262         after it send the last frame for the stream.
1263      </p>
1264      <p id="rfc.section.2.6.8.p.14">The data frames from the sender and the WINDOW_UPDATE frames from the recipient are completely asynchronous with respect to
1265         each other. This property allows a recipient to aggressively update the window size kept by the sender to prevent the stream
1266         from stalling.
1267      </p>
1268      <h3 id="rfc.section.2.6.9"><a href="#rfc.section.2.6.9">2.6.9</a>&nbsp;<a id="CREDENTIAL" href="#CREDENTIAL">CREDENTIAL</a></h3>
1269      <p id="rfc.section.2.6.9.p.1">The CREDENTIAL control frame is used by the client to send additional client certificates to the server. A HTTP/2.0 client
1270         may decide to send requests for resources from different origins on the same HTTP/2.0 session if it decides that that server
1271         handles both origins. For example if the IP address associated with both hostnames matches and the SSL server certificate
1272         presented in the initial handshake is valid for both hostnames. However, because the SSL connection can contain at most one
1273         client certificate, the client needs a mechanism to send additional client certificates to the server.
1274      </p>
1275      <p id="rfc.section.2.6.9.p.2">The server is required to maintain a vector of client certificates associated with a HTTP/2.0 session. When the client needs
1276         to send a client certificate to the server, it will send a CREDENTIAL frame that specifies the index of the slot in which
1277         to store the certificate as well as proof that the client posesses the corresponding private key. The initial size of this
1278         vector must be 8. If the client provides a client certificate during the first TLS handshake, the contents of this certificate
1279         must be copied into the first slot (index 1) in the CREDENTIAL vector, though it may be overwritten by subsequent CREDENTIAL
1280         frames. The server must exclusively use the CREDENTIAL vector when evaluating the client certificates associated with an origin.
1281         The server may change the size of this vector by sending a SETTINGS frame with the setting SETTINGS_CLIENT_CERTIFICATE_VECTOR_SIZE
1282         value specified. In the event that the new size is smaller than the current size, truncation occurs preserving lower-index
1283         slots as possible.
1284      </p>
1285      <p id="rfc.section.2.6.9.p.3">TLS renegotiation with client authentication is incompatible with HTTP/2.0 given the multiplexed nature of HTTP/2.0. Specifically,
1286         imagine that the client has 2 requests outstanding to the server for two different pages (in different tabs). When the renegotiation
1287         + client certificate request comes in, the browser is unable to determine which resource triggered the client certificate
1288         request, in order to prompt the user accordingly.
1289      </p>
1290      <div id="rfc.figure.u.11"></div> <pre>+----------------------------------+
1291|1|000000000000001|0000000000001011|
1292+----------------------------------+
1293| flags (8)  |  Length (24 bits)   |
1294+----------------------------------+
1295|  Slot (16 bits) |                |
1296+-----------------+                |
1297|      Proof Length (32 bits)      |
1298+----------------------------------+
1299|               Proof              |
1300+----------------------------------+ &lt;+
1301|   Certificate Length (32 bits)   |  |
1302+----------------------------------+  | Repeated until end of frame
1303|            Certificate           |  |
1304+----------------------------------+ &lt;+
1305            </pre> <p id="rfc.section.2.6.9.p.5">Slot: The index in the server's client certificate vector where this certificate should be stored. If there is already a certificate
1306         stored at this index, it will be overwritten. The index is one based, not zero based; zero is an invalid slot index.
1307      </p>
1308      <p id="rfc.section.2.6.9.p.6">Proof: Cryptographic proof that the client has possession of the private key associated with the certificate. The format is
1309         a TLS digitally-signed element (<a href="#RFC5246" id="rfc.xref.RFC5246.1"><cite title="The Transport Layer Security (TLS) Protocol Version 1.2">[RFC5246]</cite></a>, <a href="http://tools.ietf.org/html/rfc5246#section-4.7">Section 4.7</a>). The signature algorithm must be the same as that used in the CertificateVerify message. However, since the MD5+SHA1 signature
1310         type used in TLS 1.0 connections can not be correctly encoded in a digitally-signed element, SHA1 must be used when MD5+SHA1
1311         was used in the SSL connection. The signature is calculated over a 32 byte TLS extractor value (http://tools.ietf.org/html/rfc5705)
1312         with a label of "EXPORTER HTTP/2.0 certificate proof" using the empty string as context. ForRSA certificates the signature
1313         would be a PKCS#1 v1.5 signature. For ECDSA, it would be an ECDSA-Sig-Value (http://tools.ietf.org/html/rfc5480#appendix-A).
1314         For a 1024-bit RSA key, the CREDENTIAL message would be ~500 bytes.
1315      </p>
1316      <p id="rfc.section.2.6.9.p.7">Certificate: The certificate chain, starting with the leaf certificate. Each certificate must be encoded as a 32 bit length,
1317         followed by a DER encoded certificate. The certificate must be of the same type (RSA, ECDSA, etc) as the client certificate
1318         associated with the SSL connection.
1319      </p>
1320      <p id="rfc.section.2.6.9.p.8">If the server receives a request for a resource with unacceptable credential (either missing or invalid), it must reply with
1321         a RST_STREAM frame with the status code INVALID_CREDENTIALS. Upon receipt of a RST_STREAM frame with INVALID_CREDENTIALS,
1322         the client should initiate a new stream directly to the requested origin and resend the request. Note, HTTP/2.0 does not allow
1323         the server to request different client authentication for different resources in the same origin.
1324      </p>
1325      <p id="rfc.section.2.6.9.p.9">If the server receives an invalid CREDENTIAL frame, it MUST respond with a GOAWAY frame and shutdown the session.</p>
1326      <h3 id="rfc.section.2.6.10"><a href="#rfc.section.2.6.10">2.6.10</a>&nbsp;<a id="HeaderBlock" href="#HeaderBlock">Name/Value Header Block</a></h3>
1327      <p id="rfc.section.2.6.10.p.1">The Name/Value Header Block is found in the SYN_STREAM, SYN_REPLY and HEADERS control frames, and shares a common format:</p>
1328      <div id="rfc.figure.u.12"></div> <pre>+------------------------------------+
1329| Number of Name/Value pairs (int32) |
1330+------------------------------------+
1331|     Length of name (int32)         |
1332+------------------------------------+
1333|           Name (string)            |
1334+------------------------------------+
1335|     Length of value  (int32)       |
1336+------------------------------------+
1337|          Value   (string)          |
1338+------------------------------------+
1339|           (repeats)                |
1340            </pre> <p id="rfc.section.2.6.10.p.3">Number of Name/Value pairs: The number of repeating name/value pairs following this field.</p>
1341      <p id="rfc.section.2.6.10.p.4">List of Name/Value pairs: </p>
1342      <ul class="empty">
1343         <li>Length of Name: a 32-bit value containing the number of octets in the name field. Note that in practice, this length must
1344            not exceed 2^24, as that is the maximum size of a HTTP/2.0 frame.
1345         </li>
1346         <li>Name: 0 or more octets, 8-bit sequences of data, excluding 0.</li>
1347         <li>Length of Value: a 32-bit value containing the number of octets in the value field. Note that in practice, this length must
1348            not exceed 2^24, as that is the maximum size of a HTTP/2.0 frame.
1349         </li>
1350         <li>Value: 0 or more octets, 8-bit sequences of data, excluding 0.</li>
1351      </ul>
1352      <p id="rfc.section.2.6.10.p.5">Each header name must have at least one value. Header names are encoded using the <a href="#ASCII">US-ASCII character set</a> <cite title="US-ASCII. Coded Character Set - 7-Bit American Standard Code for Information Interchange. Standard ANSI X3.4-1986, ANSI, 1986." id="rfc.xref.ASCII.1">[ASCII]</cite> and must be all lower case. The length of each name must be greater than zero. A recipient of a zero-length name MUST issue
1353         a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with the status code PROTOCOL_ERROR for the stream-id.
1354      </p>
1355      <p id="rfc.section.2.6.10.p.6">Duplicate header names are not allowed. To send two identically named headers, send a header with two values, where the values
1356         are separated by a single NUL (0) byte. A header value can either be empty (e.g. the length is zero) or it can contain multiple,
1357         NUL-separated values, each with length greater than zero. The value never starts nor ends with a NUL character. Recipients
1358         of illegal value fields MUST issue a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with the status code PROTOCOL_ERROR for the stream-id.
1359      </p>
1360      <h4 id="rfc.section.2.6.10.1"><a href="#rfc.section.2.6.10.1">2.6.10.1</a>&nbsp;<a id="Compression" href="#Compression">Compression</a></h4>
1361      <p id="rfc.section.2.6.10.1.p.1">The Name/Value Header Block is a section of the SYN_STREAM, SYN_REPLY, and HEADERS frames used to carry header meta-data.
1362         This block is always compressed using zlib compression. Within this specification, any reference to 'zlib' is referring to
1363         the <a href="#RFC1950">ZLIB Compressed Data Format Specification Version 3.3 as part of RFC1950.</a> <cite title="ZLIB Compressed Data Format Specification version 3.3" id="rfc.xref.RFC1950.1">[RFC1950]</cite></p>
1364      <p id="rfc.section.2.6.10.1.p.2">For each HEADERS compression instance, the initial state is initialized using the following <a href="#UDELCOMPRESSION">dictionary</a> <cite title="A Methodology to Derive SPDY's Initial Dictionary for Zlib Compression" id="rfc.xref.UDELCOMPRESSION.1">[UDELCOMPRESSION]</cite>:
1365      </p>
1366      <div id="rfc.figure.u.13"></div> <pre class="ccmarker cct"><span>&lt;CODE BEGINS&gt;</span></pre><pre class="text">const unsigned char http2_dictionary_txt[] = {
1367  0x00, 0x00, 0x00, 0x07, 0x6f, 0x70, 0x74, 0x69,  \\ - - - - o p t i
1368  0x6f, 0x6e, 0x73, 0x00, 0x00, 0x00, 0x04, 0x68,  \\ o n s - - - - h
1369  0x65, 0x61, 0x64, 0x00, 0x00, 0x00, 0x04, 0x70,  \\ e a d - - - - p
1370  0x6f, 0x73, 0x74, 0x00, 0x00, 0x00, 0x03, 0x70,  \\ o s t - - - - p
1371  0x75, 0x74, 0x00, 0x00, 0x00, 0x06, 0x64, 0x65,  \\ u t - - - - d e
1372  0x6c, 0x65, 0x74, 0x65, 0x00, 0x00, 0x00, 0x05,  \\ l e t e - - - -
1373  0x74, 0x72, 0x61, 0x63, 0x65, 0x00, 0x00, 0x00,  \\ t r a c e - - -
1374  0x06, 0x61, 0x63, 0x63, 0x65, 0x70, 0x74, 0x00,  \\ - a c c e p t -
1375  0x00, 0x00, 0x0e, 0x61, 0x63, 0x63, 0x65, 0x70,  \\ - - - a c c e p
1376  0x74, 0x2d, 0x63, 0x68, 0x61, 0x72, 0x73, 0x65,  \\ t - c h a r s e
1377  0x74, 0x00, 0x00, 0x00, 0x0f, 0x61, 0x63, 0x63,  \\ t - - - - a c c
1378  0x65, 0x70, 0x74, 0x2d, 0x65, 0x6e, 0x63, 0x6f,  \\ e p t - e n c o
1379  0x64, 0x69, 0x6e, 0x67, 0x00, 0x00, 0x00, 0x0f,  \\ d i n g - - - -
1380  0x61, 0x63, 0x63, 0x65, 0x70, 0x74, 0x2d, 0x6c,  \\ a c c e p t - l
1381  0x61, 0x6e, 0x67, 0x75, 0x61, 0x67, 0x65, 0x00,  \\ a n g u a g e -
1382  0x00, 0x00, 0x0d, 0x61, 0x63, 0x63, 0x65, 0x70,  \\ - - - a c c e p
1383  0x74, 0x2d, 0x72, 0x61, 0x6e, 0x67, 0x65, 0x73,  \\ t - r a n g e s
1384  0x00, 0x00, 0x00, 0x03, 0x61, 0x67, 0x65, 0x00,  \\ - - - - a g e -
1385  0x00, 0x00, 0x05, 0x61, 0x6c, 0x6c, 0x6f, 0x77,  \\ - - - a l l o w
1386  0x00, 0x00, 0x00, 0x0d, 0x61, 0x75, 0x74, 0x68,  \\ - - - - a u t h
1387  0x6f, 0x72, 0x69, 0x7a, 0x61, 0x74, 0x69, 0x6f,  \\ o r i z a t i o
1388  0x6e, 0x00, 0x00, 0x00, 0x0d, 0x63, 0x61, 0x63,  \\ n - - - - c a c
1389  0x68, 0x65, 0x2d, 0x63, 0x6f, 0x6e, 0x74, 0x72,  \\ h e - c o n t r
1390  0x6f, 0x6c, 0x00, 0x00, 0x00, 0x0a, 0x63, 0x6f,  \\ o l - - - - c o
1391  0x6e, 0x6e, 0x65, 0x63, 0x74, 0x69, 0x6f, 0x6e,  \\ n n e c t i o n
1392  0x00, 0x00, 0x00, 0x0c, 0x63, 0x6f, 0x6e, 0x74,  \\ - - - - c o n t
1393  0x65, 0x6e, 0x74, 0x2d, 0x62, 0x61, 0x73, 0x65,  \\ e n t - b a s e
1394  0x00, 0x00, 0x00, 0x10, 0x63, 0x6f, 0x6e, 0x74,  \\ - - - - c o n t
1395  0x65, 0x6e, 0x74, 0x2d, 0x65, 0x6e, 0x63, 0x6f,  \\ e n t - e n c o
1396  0x64, 0x69, 0x6e, 0x67, 0x00, 0x00, 0x00, 0x10,  \\ d i n g - - - -
1397  0x63, 0x6f, 0x6e, 0x74, 0x65, 0x6e, 0x74, 0x2d,  \\ c o n t e n t -
1398  0x6c, 0x61, 0x6e, 0x67, 0x75, 0x61, 0x67, 0x65,  \\ l a n g u a g e
1399  0x00, 0x00, 0x00, 0x0e, 0x63, 0x6f, 0x6e, 0x74,  \\ - - - - c o n t
1400  0x65, 0x6e, 0x74, 0x2d, 0x6c, 0x65, 0x6e, 0x67,  \\ e n t - l e n g
1401  0x74, 0x68, 0x00, 0x00, 0x00, 0x10, 0x63, 0x6f,  \\ t h - - - - c o
1402  0x6e, 0x74, 0x65, 0x6e, 0x74, 0x2d, 0x6c, 0x6f,  \\ n t e n t - l o
1403  0x63, 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x00,  \\ c a t i o n - -
1404  0x00, 0x0b, 0x63, 0x6f, 0x6e, 0x74, 0x65, 0x6e,  \\ - - c o n t e n
1405  0x74, 0x2d, 0x6d, 0x64, 0x35, 0x00, 0x00, 0x00,  \\ t - m d 5 - - -
1406  0x0d, 0x63, 0x6f, 0x6e, 0x74, 0x65, 0x6e, 0x74,  \\ - c o n t e n t
1407  0x2d, 0x72, 0x61, 0x6e, 0x67, 0x65, 0x00, 0x00,  \\ - r a n g e - -
1408  0x00, 0x0c, 0x63, 0x6f, 0x6e, 0x74, 0x65, 0x6e,  \\ - - c o n t e n
1409  0x74, 0x2d, 0x74, 0x79, 0x70, 0x65, 0x00, 0x00,  \\ t - t y p e - -
1410  0x00, 0x04, 0x64, 0x61, 0x74, 0x65, 0x00, 0x00,  \\ - - d a t e - -
1411  0x00, 0x04, 0x65, 0x74, 0x61, 0x67, 0x00, 0x00,  \\ - - e t a g - -
1412  0x00, 0x06, 0x65, 0x78, 0x70, 0x65, 0x63, 0x74,  \\ - - e x p e c t
1413  0x00, 0x00, 0x00, 0x07, 0x65, 0x78, 0x70, 0x69,  \\ - - - - e x p i
1414  0x72, 0x65, 0x73, 0x00, 0x00, 0x00, 0x04, 0x66,  \\ r e s - - - - f
1415  0x72, 0x6f, 0x6d, 0x00, 0x00, 0x00, 0x04, 0x68,  \\ r o m - - - - h
1416  0x6f, 0x73, 0x74, 0x00, 0x00, 0x00, 0x08, 0x69,  \\ o s t - - - - i
1417  0x66, 0x2d, 0x6d, 0x61, 0x74, 0x63, 0x68, 0x00,  \\ f - m a t c h -
1418  0x00, 0x00, 0x11, 0x69, 0x66, 0x2d, 0x6d, 0x6f,  \\ - - - i f - m o
1419  0x64, 0x69, 0x66, 0x69, 0x65, 0x64, 0x2d, 0x73,  \\ d i f i e d - s
1420  0x69, 0x6e, 0x63, 0x65, 0x00, 0x00, 0x00, 0x0d,  \\ i n c e - - - -
1421  0x69, 0x66, 0x2d, 0x6e, 0x6f, 0x6e, 0x65, 0x2d,  \\ i f - n o n e -
1422  0x6d, 0x61, 0x74, 0x63, 0x68, 0x00, 0x00, 0x00,  \\ m a t c h - - -
1423  0x08, 0x69, 0x66, 0x2d, 0x72, 0x61, 0x6e, 0x67,  \\ - i f - r a n g
1424  0x65, 0x00, 0x00, 0x00, 0x13, 0x69, 0x66, 0x2d,  \\ e - - - - i f -
1425  0x75, 0x6e, 0x6d, 0x6f, 0x64, 0x69, 0x66, 0x69,  \\ u n m o d i f i
1426  0x65, 0x64, 0x2d, 0x73, 0x69, 0x6e, 0x63, 0x65,  \\ e d - s i n c e
1427  0x00, 0x00, 0x00, 0x0d, 0x6c, 0x61, 0x73, 0x74,  \\ - - - - l a s t
1428  0x2d, 0x6d, 0x6f, 0x64, 0x69, 0x66, 0x69, 0x65,  \\ - m o d i f i e
1429  0x64, 0x00, 0x00, 0x00, 0x08, 0x6c, 0x6f, 0x63,  \\ d - - - - l o c
1430  0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x00, 0x00,  \\ a t i o n - - -
1431  0x0c, 0x6d, 0x61, 0x78, 0x2d, 0x66, 0x6f, 0x72,  \\ - m a x - f o r
1432  0x77, 0x61, 0x72, 0x64, 0x73, 0x00, 0x00, 0x00,  \\ w a r d s - - -
1433  0x06, 0x70, 0x72, 0x61, 0x67, 0x6d, 0x61, 0x00,  \\ - p r a g m a -
1434  0x00, 0x00, 0x12, 0x70, 0x72, 0x6f, 0x78, 0x79,  \\ - - - p r o x y
1435  0x2d, 0x61, 0x75, 0x74, 0x68, 0x65, 0x6e, 0x74,  \\ - a u t h e n t
1436  0x69, 0x63, 0x61, 0x74, 0x65, 0x00, 0x00, 0x00,  \\ i c a t e - - -
1437  0x13, 0x70, 0x72, 0x6f, 0x78, 0x79, 0x2d, 0x61,  \\ - p r o x y - a
1438  0x75, 0x74, 0x68, 0x6f, 0x72, 0x69, 0x7a, 0x61,  \\ u t h o r i z a
1439  0x74, 0x69, 0x6f, 0x6e, 0x00, 0x00, 0x00, 0x05,  \\ t i o n - - - -
1440  0x72, 0x61, 0x6e, 0x67, 0x65, 0x00, 0x00, 0x00,  \\ r a n g e - - -
1441  0x07, 0x72, 0x65, 0x66, 0x65, 0x72, 0x65, 0x72,  \\ - r e f e r e r
1442  0x00, 0x00, 0x00, 0x0b, 0x72, 0x65, 0x74, 0x72,  \\ - - - - r e t r
1443  0x79, 0x2d, 0x61, 0x66, 0x74, 0x65, 0x72, 0x00,  \\ y - a f t e r -
1444  0x00, 0x00, 0x06, 0x73, 0x65, 0x72, 0x76, 0x65,  \\ - - - s e r v e
1445  0x72, 0x00, 0x00, 0x00, 0x02, 0x74, 0x65, 0x00,  \\ r - - - - t e -
1446  0x00, 0x00, 0x07, 0x74, 0x72, 0x61, 0x69, 0x6c,  \\ - - - t r a i l
1447  0x65, 0x72, 0x00, 0x00, 0x00, 0x11, 0x74, 0x72,  \\ e r - - - - t r
1448  0x61, 0x6e, 0x73, 0x66, 0x65, 0x72, 0x2d, 0x65,  \\ a n s f e r - e
1449  0x6e, 0x63, 0x6f, 0x64, 0x69, 0x6e, 0x67, 0x00,  \\ n c o d i n g -
1450  0x00, 0x00, 0x07, 0x75, 0x70, 0x67, 0x72, 0x61,  \\ - - - u p g r a
1451  0x64, 0x65, 0x00, 0x00, 0x00, 0x0a, 0x75, 0x73,  \\ d e - - - - u s
1452  0x65, 0x72, 0x2d, 0x61, 0x67, 0x65, 0x6e, 0x74,  \\ e r - a g e n t
1453  0x00, 0x00, 0x00, 0x04, 0x76, 0x61, 0x72, 0x79,  \\ - - - - v a r y
1454  0x00, 0x00, 0x00, 0x03, 0x76, 0x69, 0x61, 0x00,  \\ - - - - v i a -
1455  0x00, 0x00, 0x07, 0x77, 0x61, 0x72, 0x6e, 0x69,  \\ - - - w a r n i
1456  0x6e, 0x67, 0x00, 0x00, 0x00, 0x10, 0x77, 0x77,  \\ n g - - - - w w
1457  0x77, 0x2d, 0x61, 0x75, 0x74, 0x68, 0x65, 0x6e,  \\ w - a u t h e n
1458  0x74, 0x69, 0x63, 0x61, 0x74, 0x65, 0x00, 0x00,  \\ t i c a t e - -
1459  0x00, 0x06, 0x6d, 0x65, 0x74, 0x68, 0x6f, 0x64,  \\ - - m e t h o d
1460  0x00, 0x00, 0x00, 0x03, 0x67, 0x65, 0x74, 0x00,  \\ - - - - g e t -
1461  0x00, 0x00, 0x06, 0x73, 0x74, 0x61, 0x74, 0x75,  \\ - - - s t a t u
1462  0x73, 0x00, 0x00, 0x00, 0x06, 0x32, 0x30, 0x30,  \\ s - - - - 2 0 0
1463  0x20, 0x4f, 0x4b, 0x00, 0x00, 0x00, 0x07, 0x76,  \\ - O K - - - - v
1464  0x65, 0x72, 0x73, 0x69, 0x6f, 0x6e, 0x00, 0x00,  \\ e r s i o n - -
1465  0x00, 0x08, 0x48, 0x54, 0x54, 0x50, 0x2f, 0x31,  \\ - - H T T P - 1
1466  0x2e, 0x31, 0x00, 0x00, 0x00, 0x03, 0x75, 0x72,  \\ - 1 - - - - u r
1467  0x6c, 0x00, 0x00, 0x00, 0x06, 0x70, 0x75, 0x62,  \\ l - - - - p u b
1468  0x6c, 0x69, 0x63, 0x00, 0x00, 0x00, 0x0a, 0x73,  \\ l i c - - - - s
1469  0x65, 0x74, 0x2d, 0x63, 0x6f, 0x6f, 0x6b, 0x69,  \\ e t - c o o k i
1470  0x65, 0x00, 0x00, 0x00, 0x0a, 0x6b, 0x65, 0x65,  \\ e - - - - k e e
1471  0x70, 0x2d, 0x61, 0x6c, 0x69, 0x76, 0x65, 0x00,  \\ p - a l i v e -
1472  0x00, 0x00, 0x06, 0x6f, 0x72, 0x69, 0x67, 0x69,  \\ - - - o r i g i
1473  0x6e, 0x31, 0x30, 0x30, 0x31, 0x30, 0x31, 0x32,  \\ n 1 0 0 1 0 1 2
1474  0x30, 0x31, 0x32, 0x30, 0x32, 0x32, 0x30, 0x35,  \\ 0 1 2 0 2 2 0 5
1475  0x32, 0x30, 0x36, 0x33, 0x30, 0x30, 0x33, 0x30,  \\ 2 0 6 3 0 0 3 0
1476  0x32, 0x33, 0x30, 0x33, 0x33, 0x30, 0x34, 0x33,  \\ 2 3 0 3 3 0 4 3
1477  0x30, 0x35, 0x33, 0x30, 0x36, 0x33, 0x30, 0x37,  \\ 0 5 3 0 6 3 0 7
1478  0x34, 0x30, 0x32, 0x34, 0x30, 0x35, 0x34, 0x30,  \\ 4 0 2 4 0 5 4 0
1479  0x36, 0x34, 0x30, 0x37, 0x34, 0x30, 0x38, 0x34,  \\ 6 4 0 7 4 0 8 4
1480  0x30, 0x39, 0x34, 0x31, 0x30, 0x34, 0x31, 0x31,  \\ 0 9 4 1 0 4 1 1
1481  0x34, 0x31, 0x32, 0x34, 0x31, 0x33, 0x34, 0x31,  \\ 4 1 2 4 1 3 4 1
1482  0x34, 0x34, 0x31, 0x35, 0x34, 0x31, 0x36, 0x34,  \\ 4 4 1 5 4 1 6 4
1483  0x31, 0x37, 0x35, 0x30, 0x32, 0x35, 0x30, 0x34,  \\ 1 7 5 0 2 5 0 4
1484  0x35, 0x30, 0x35, 0x32, 0x30, 0x33, 0x20, 0x4e,  \\ 5 0 5 2 0 3 - N
1485  0x6f, 0x6e, 0x2d, 0x41, 0x75, 0x74, 0x68, 0x6f,  \\ o n - A u t h o
1486  0x72, 0x69, 0x74, 0x61, 0x74, 0x69, 0x76, 0x65,  \\ r i t a t i v e
1487  0x20, 0x49, 0x6e, 0x66, 0x6f, 0x72, 0x6d, 0x61,  \\ - I n f o r m a
1488  0x74, 0x69, 0x6f, 0x6e, 0x32, 0x30, 0x34, 0x20,  \\ t i o n 2 0 4 -
1489  0x4e, 0x6f, 0x20, 0x43, 0x6f, 0x6e, 0x74, 0x65,  \\ N o - C o n t e
1490  0x6e, 0x74, 0x33, 0x30, 0x31, 0x20, 0x4d, 0x6f,  \\ n t 3 0 1 - M o
1491  0x76, 0x65, 0x64, 0x20, 0x50, 0x65, 0x72, 0x6d,  \\ v e d - P e r m
1492  0x61, 0x6e, 0x65, 0x6e, 0x74, 0x6c, 0x79, 0x34,  \\ a n e n t l y 4
1493  0x30, 0x30, 0x20, 0x42, 0x61, 0x64, 0x20, 0x52,  \\ 0 0 - B a d - R
1494  0x65, 0x71, 0x75, 0x65, 0x73, 0x74, 0x34, 0x30,  \\ e q u e s t 4 0
1495  0x31, 0x20, 0x55, 0x6e, 0x61, 0x75, 0x74, 0x68,  \\ 1 - U n a u t h
1496  0x6f, 0x72, 0x69, 0x7a, 0x65, 0x64, 0x34, 0x30,  \\ o r i z e d 4 0
1497  0x33, 0x20, 0x46, 0x6f, 0x72, 0x62, 0x69, 0x64,  \\ 3 - F o r b i d
1498  0x64, 0x65, 0x6e, 0x34, 0x30, 0x34, 0x20, 0x4e,  \\ d e n 4 0 4 - N
1499  0x6f, 0x74, 0x20, 0x46, 0x6f, 0x75, 0x6e, 0x64,  \\ o t - F o u n d
1500  0x35, 0x30, 0x30, 0x20, 0x49, 0x6e, 0x74, 0x65,  \\ 5 0 0 - I n t e
1501  0x72, 0x6e, 0x61, 0x6c, 0x20, 0x53, 0x65, 0x72,  \\ r n a l - S e r
1502  0x76, 0x65, 0x72, 0x20, 0x45, 0x72, 0x72, 0x6f,  \\ v e r - E r r o
1503  0x72, 0x35, 0x30, 0x31, 0x20, 0x4e, 0x6f, 0x74,  \\ r 5 0 1 - N o t
1504  0x20, 0x49, 0x6d, 0x70, 0x6c, 0x65, 0x6d, 0x65,  \\ - I m p l e m e
1505  0x6e, 0x74, 0x65, 0x64, 0x35, 0x30, 0x33, 0x20,  \\ n t e d 5 0 3 -
1506  0x53, 0x65, 0x72, 0x76, 0x69, 0x63, 0x65, 0x20,  \\ S e r v i c e -
1507  0x55, 0x6e, 0x61, 0x76, 0x61, 0x69, 0x6c, 0x61,  \\ U n a v a i l a
1508  0x62, 0x6c, 0x65, 0x4a, 0x61, 0x6e, 0x20, 0x46,  \\ b l e J a n - F
1509  0x65, 0x62, 0x20, 0x4d, 0x61, 0x72, 0x20, 0x41,  \\ e b - M a r - A
1510  0x70, 0x72, 0x20, 0x4d, 0x61, 0x79, 0x20, 0x4a,  \\ p r - M a y - J
1511  0x75, 0x6e, 0x20, 0x4a, 0x75, 0x6c, 0x20, 0x41,  \\ u n - J u l - A
1512  0x75, 0x67, 0x20, 0x53, 0x65, 0x70, 0x74, 0x20,  \\ u g - S e p t -
1513  0x4f, 0x63, 0x74, 0x20, 0x4e, 0x6f, 0x76, 0x20,  \\ O c t - N o v -
1514  0x44, 0x65, 0x63, 0x20, 0x30, 0x30, 0x3a, 0x30,  \\ D e c - 0 0 - 0
1515  0x30, 0x3a, 0x30, 0x30, 0x20, 0x4d, 0x6f, 0x6e,  \\ 0 - 0 0 - M o n
1516  0x2c, 0x20, 0x54, 0x75, 0x65, 0x2c, 0x20, 0x57,  \\ - - T u e - - W
1517  0x65, 0x64, 0x2c, 0x20, 0x54, 0x68, 0x75, 0x2c,  \\ e d - - T h u -
1518  0x20, 0x46, 0x72, 0x69, 0x2c, 0x20, 0x53, 0x61,  \\ - F r i - - S a
1519  0x74, 0x2c, 0x20, 0x53, 0x75, 0x6e, 0x2c, 0x20,  \\ t - - S u n - -
1520  0x47, 0x4d, 0x54, 0x63, 0x68, 0x75, 0x6e, 0x6b,  \\ G M T c h u n k
1521  0x65, 0x64, 0x2c, 0x74, 0x65, 0x78, 0x74, 0x2f,  \\ e d - t e x t -
1522  0x68, 0x74, 0x6d, 0x6c, 0x2c, 0x69, 0x6d, 0x61,  \\ h t m l - i m a
1523  0x67, 0x65, 0x2f, 0x70, 0x6e, 0x67, 0x2c, 0x69,  \\ g e - p n g - i
1524  0x6d, 0x61, 0x67, 0x65, 0x2f, 0x6a, 0x70, 0x67,  \\ m a g e - j p g
1525  0x2c, 0x69, 0x6d, 0x61, 0x67, 0x65, 0x2f, 0x67,  \\ - i m a g e - g
1526  0x69, 0x66, 0x2c, 0x61, 0x70, 0x70, 0x6c, 0x69,  \\ i f - a p p l i
1527  0x63, 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x2f, 0x78,  \\ c a t i o n - x
1528  0x6d, 0x6c, 0x2c, 0x61, 0x70, 0x70, 0x6c, 0x69,  \\ m l - a p p l i
1529  0x63, 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x2f, 0x78,  \\ c a t i o n - x
1530  0x68, 0x74, 0x6d, 0x6c, 0x2b, 0x78, 0x6d, 0x6c,  \\ h t m l - x m l
1531  0x2c, 0x74, 0x65, 0x78, 0x74, 0x2f, 0x70, 0x6c,  \\ - t e x t - p l
1532  0x61, 0x69, 0x6e, 0x2c, 0x74, 0x65, 0x78, 0x74,  \\ a i n - t e x t
1533  0x2f, 0x6a, 0x61, 0x76, 0x61, 0x73, 0x63, 0x72,  \\ - j a v a s c r
1534  0x69, 0x70, 0x74, 0x2c, 0x70, 0x75, 0x62, 0x6c,  \\ i p t - p u b l
1535  0x69, 0x63, 0x70, 0x72, 0x69, 0x76, 0x61, 0x74,  \\ i c p r i v a t
1536  0x65, 0x6d, 0x61, 0x78, 0x2d, 0x61, 0x67, 0x65,  \\ e m a x - a g e
1537  0x3d, 0x67, 0x7a, 0x69, 0x70, 0x2c, 0x64, 0x65,  \\ - g z i p - d e
1538  0x66, 0x6c, 0x61, 0x74, 0x65, 0x2c, 0x73, 0x64,  \\ f l a t e - s d
1539  0x63, 0x68, 0x63, 0x68, 0x61, 0x72, 0x73, 0x65,  \\ c h c h a r s e
1540  0x74, 0x3d, 0x75, 0x74, 0x66, 0x2d, 0x38, 0x63,  \\ t - u t f - 8 c
1541  0x68, 0x61, 0x72, 0x73, 0x65, 0x74, 0x3d, 0x69,  \\ h a r s e t - i
1542  0x73, 0x6f, 0x2d, 0x38, 0x38, 0x35, 0x39, 0x2d,  \\ s o - 8 8 5 9 -
1543  0x31, 0x2c, 0x75, 0x74, 0x66, 0x2d, 0x2c, 0x2a,  \\ 1 - u t f - - -
1544  0x2c, 0x65, 0x6e, 0x71, 0x3d, 0x30, 0x2e         \\ - e n q - 0 -
1545};
1546</pre><pre class="ccmarker ccb"><span>&lt;CODE ENDS&gt;</span></pre> <p id="rfc.section.2.6.10.1.p.4">The entire contents of the name/value header block is compressed using zlib. There is a single zlib stream for all name value
1547         pairs in one direction on a connection. HTTP/2.0 uses a SYNC_FLUSH between each compressed frame.
1548      </p>
1549      <p id="rfc.section.2.6.10.1.p.5">Implementation notes: the compression engine can be tuned to favor speed or size. Optimizing for size increases memory use
1550         and CPU consumption. Because header blocks are generally small, implementors may want to reduce the window-size of the compression
1551         engine from the default 15bits (a 32KB window) to more like 11bits (a 2KB window). The exact setting is chosen by the compressor,
1552         the decompressor will work with any setting.
1553      </p>
1554      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="HTTPLayer" href="#HTTPLayer">HTTP Layering over HTTP/2.0</a></h1>
1555      <p id="rfc.section.3.p.1">HTTP/2.0 is intended to be as compatible as possible with current web-based applications. This means that, from the perspective
1556         of the server business logic or application API, the features of HTTP are unchanged. To achieve this, all of the application
1557         request and response header semantics are preserved, although the syntax of conveying those semantics has changed. Thus, the
1558         rules from the <a href="#RFC2616">HTTP/1.1 specification in RFC2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">[RFC2616]</cite> apply with the changes in the sections below.
1559      </p>
1560      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;Connection Management
1561      </h2>
1562      <p id="rfc.section.3.1.p.1">Clients SHOULD NOT open more than one HTTP/2.0 session to a given <a href="#RFC6454">origin</a> <cite title="The Web Origin Concept" id="rfc.xref.RFC6454.2">[RFC6454]</cite> concurrently.
1563      </p>
1564      <p id="rfc.section.3.1.p.2">Note that it is possible for one HTTP/2.0 session to be finishing (e.g. a GOAWAY message has been sent, but not all streams
1565         have finished), while another HTTP/2.0 session is starting.
1566      </p>
1567      <h3 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;Use of GOAWAY
1568      </h3>
1569      <p id="rfc.section.3.1.1.p.1">HTTP/2.0 provides a GOAWAY message which can be used when closing a connection from either the client or server. Without a
1570         server GOAWAY message, HTTP has a race condition where the client sends a request (a new SYN_STREAM) just as the server is
1571         closing the connection, and the client cannot know if the server received the stream or not. By using the last-stream-id in
1572         the GOAWAY, servers can indicate to the client if a request was processed or not.
1573      </p>
1574      <p id="rfc.section.3.1.1.p.2">Note that some servers will choose to send the GOAWAY and immediately terminate the connection without waiting for active
1575         streams to finish. The client will be able to determine this because HTTP/2.0 streams are determinstically closed. This abrupt
1576         termination will force the client to heuristically decide whether to retry the pending requests. Clients always need to be
1577         capable of dealing with this case because they must deal with accidental connection termination cases, which are the same
1578         as the server never having sent a GOAWAY.
1579      </p>
1580      <p id="rfc.section.3.1.1.p.3">More sophisticated servers will use GOAWAY to implement a graceful teardown. They will send the GOAWAY and provide some time
1581         for the active streams to finish before terminating the connection.
1582      </p>
1583      <p id="rfc.section.3.1.1.p.4">If a HTTP/2.0 client closes the connection, it should also send a GOAWAY message. This allows the server to know if any server-push
1584         streams were received by the client.
1585      </p>
1586      <p id="rfc.section.3.1.1.p.5">If the endpoint closing the connection has not received any SYN_STREAMs from the remote, the GOAWAY will contain a last-stream-id
1587         of 0.
1588      </p>
1589      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;HTTP Request/Response
1590      </h2>
1591      <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;Request
1592      </h3>
1593      <p id="rfc.section.3.2.1.p.1">The client initiates a request by sending a SYN_STREAM frame. For requests which do not contain a body, the SYN_STREAM frame
1594         MUST set the FLAG_FIN, indicating that the client intends to send no further data on this stream. For requests which do contain
1595         a body, the SYN_STREAM will not contain the FLAG_FIN, and the body will follow the SYN_STREAM in a series of DATA frames.
1596         The last DATA frame will set the FLAG_FIN to indicate the end of the body.
1597      </p>
1598      <p id="rfc.section.3.2.1.p.2">The SYN_STREAM Name/Value section will contain all of the HTTP headers which are associated with an HTTP request. The header
1599         block in HTTP/2.0 is mostly unchanged from today's HTTP header block, with the following differences:
1600      </p>
1601      <ul class="empty">
1602         <li>The first line of the request is unfolded into name/value pairs like other HTTP headers and MUST be present:
1603            <ul class="empty">
1604               <li>":method" - the HTTP method for this request (e.g. "GET", "POST", "HEAD", etc)</li>
1605               <li>":path" - the url-path for this url with "/" prefixed. (See <a href="#RFC1738">RFC1738</a> <cite title="Uniform Resource Locators (URL)" id="rfc.xref.RFC1738.1">[RFC1738]</cite>). For example, for "http://www.google.com/search?q=dogs" the path would be "/search?q=dogs".
1606               </li>
1607               <li>":version" - the HTTP version of this request (e.g. "HTTP/1.1")</li>
1608            </ul> 
1609         </li>
1610         <li>In addition, the following two name/value pairs must also be present in every request:
1611            <ul class="empty">
1612               <li>":host" - the hostport (See <a href="#RFC1738">RFC1738</a> <cite title="Uniform Resource Locators (URL)" id="rfc.xref.RFC1738.2">[RFC1738]</cite>) portion of the URL for this request (e.g. "www.google.com:1234"). This header is the same as the HTTP 'Host' header.
1613               </li>
1614               <li>":scheme" - the scheme portion of the URL for this request (e.g. "https"))</li>
1615            </ul>
1616         </li>
1617         <li>Header names are all lowercase.</li>
1618         <li>The Connection, Host, Keep-Alive, Proxy-Connection, and Transfer-Encoding headers are not valid and MUST not be sent.</li>
1619         <li>User-agents MUST support gzip compression. Regardless of the Accept-Encoding sent by the user-agent, the server may always
1620            send content encoded with gzip or deflate encoding.
1621         </li>
1622         <li>If a server receives a request where the sum of the data frame payload lengths does not equal the size of the Content-Length
1623            header, the server MUST return a 400 (Bad Request) error.
1624         </li>
1625         <li>POST-specific changes:
1626            <ul class="empty">
1627               <li>Although POSTs are inherently chunked, POST requests SHOULD also be accompanied by a Content-Length header. There are two
1628                  reasons for this: First, it assists with upload progress meters for an improved user experience. But second, we know from
1629                  early versions of HTTP/2.0 that failure to send a content length header is incompatible with many existing HTTP server implementations.
1630                  Existing user-agents do not omit the Content-Length header, and server implementations have come to depend upon this.
1631               </li>
1632            </ul> 
1633         </li>
1634      </ul>
1635      <p id="rfc.section.3.2.1.p.3">The user-agent is free to prioritize requests as it sees fit. If the user-agent cannot make progress without receiving a resource,
1636         it should attempt to raise the priority of that resource. Resources such as images, SHOULD generally use the lowest priority.
1637      </p>
1638      <p id="rfc.section.3.2.1.p.4">If a client sends a SYN_STREAM without all of the method, host, path, scheme, and version headers, the server MUST reply with
1639         a HTTP 400 Bad Request reply.
1640      </p>
1641      <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;Response
1642      </h3>
1643      <p id="rfc.section.3.2.2.p.1">The server responds to a client request with a SYN_REPLY frame. Symmetric to the client's upload stream, server will send
1644         data after the SYN_REPLY frame via a series of DATA frames, and the last data frame will contain the FLAG_FIN to indicate
1645         successful end-of-stream. If a response (like a 202 or 204 response) contains no body, the SYN_REPLY frame may contain the
1646         FLAG_FIN flag to indicate no further data will be sent on the stream.
1647      </p>
1648      <p id="rfc.section.3.2.2.p.2"> </p>
1649      <ul class="empty">
1650         <li>The response status line is unfolded into name/value pairs like other HTTP headers and must be present:
1651            <ul class="empty">
1652               <li>":status" - The HTTP response status code (e.g. "200" or "200 OK")</li>
1653               <li>":version" - The HTTP response version (e.g. "HTTP/1.1")</li>
1654            </ul> 
1655         </li>
1656         <li>All header names must be lowercase.</li>
1657         <li>The Connection, Keep-Alive, Proxy-Connection, and Transfer-Encoding headers are not valid and MUST not be sent.</li>
1658         <li>Responses MAY be accompanied by a Content-Length header for advisory purposes. (e.g. for UI progress meters)</li>
1659         <li>If a client receives a response where the sum of the data frame payload lengths does not equal the size of the Content-Length
1660            header, the client MUST ignore the content length header.
1661         </li>
1662      </ul>
1663      <p id="rfc.section.3.2.2.p.3">If a client receives a SYN_REPLY without a status or without a version header, the client must reply with a RST_STREAM frame
1664         indicating a PROTOCOL ERROR.
1665      </p>
1666      <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="Authentication" href="#Authentication">Authentication</a></h3>
1667      <p id="rfc.section.3.2.3.p.1">When a client sends a request to an origin server that requires authentication, the server can reply with a "401 Unauthorized"
1668         response, and include a WWW-Authenticate challenge header that defines the authentication scheme to be used. The client then
1669         retries the request with an Authorization header appropriate to the specified authentication scheme.
1670      </p>
1671      <p id="rfc.section.3.2.3.p.2">There are four options for proxy authentication, Basic, Digest, NTLM and Negotiate (SPNEGO). The first two options were defined
1672         in <a href="#RFC2617">RFC2617</a> <cite title="HTTP Authentication: Basic and Digest Access Authentication" id="rfc.xref.RFC2617.1">[RFC2617]</cite>, and are stateless. The second two options were developed by Microsoft and specified in <a href="#RFC4559">RFC4559</a> <cite title="SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows" id="rfc.xref.RFC4559.1">[RFC4559]</cite>, and are stateful; otherwise known as multi-round authentication, or connection authentication.
1673      </p>
1674      <h4 id="rfc.section.3.2.3.1"><a href="#rfc.section.3.2.3.1">3.2.3.1</a>&nbsp;Stateless Authentication
1675      </h4>
1676      <p id="rfc.section.3.2.3.1.p.1">Stateless Authentication over HTTP/2.0 is identical to how it is performed over HTTP. If multiple HTTP/2.0 streams are concurrently
1677         sent to a single server, each will authenticate independently, similar to how two HTTP connections would independently authenticate
1678         to a proxy server.
1679      </p>
1680      <h4 id="rfc.section.3.2.3.2"><a href="#rfc.section.3.2.3.2">3.2.3.2</a>&nbsp;Stateful Authentication
1681      </h4>
1682      <p id="rfc.section.3.2.3.2.p.1">Unfortunately, the stateful authentication mechanisms were implemented and defined in a such a way that directly violates
1683         RFC2617 - they do not include a "realm" as part of the request. This is problematic in HTTP/2.0 because it makes it impossible
1684         for a client to disambiguate two concurrent server authentication challenges.
1685      </p>
1686      <p id="rfc.section.3.2.3.2.p.2">To deal with this case, HTTP/2.0 servers using Stateful Authentication MUST implement one of two changes: </p>
1687      <ul class="empty">
1688         <li>Servers can add a "realm=&lt;desired realm&gt;" header so that the two authentication requests can be disambiguated and run concurrently.
1689            Unfortunately, given how these mechanisms work, this is probably not practical.
1690         </li>
1691         <li>Upon sending the first stateful challenge response, the server MUST buffer and defer all further frames which are not part
1692            of completing the challenge until the challenge has completed. Completing the authentication challenge may take multiple round
1693            trips. Once the client receives a "401 Authenticate" response for a stateful authentication type, it MUST stop sending new
1694            requests to the server until the authentication has completed by receiving a non-401 response on at least one stream.
1695         </li>
1696      </ul>
1697      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;Server Push Transactions
1698      </h2>
1699      <p id="rfc.section.3.3.p.1">HTTP/2.0 enables a server to send multiple replies to a client for a single request. The rationale for this feature is that
1700         sometimes a server knows that it will need to send multiple resources in response to a single request. Without server push
1701         features, the client must first download the primary resource, then discover the secondary resource(s), and request them.
1702         Pushing of resources avoids the round-trip delay, but also creates a potential race where a server can be pushing content
1703         which a user-agent is in the process of requesting. The following mechanics attempt to prevent the race condition while enabling
1704         the performance benefit.
1705      </p>
1706      <p id="rfc.section.3.3.p.2">Browsers receiving a pushed response MUST validate that the server is authorized to push the URL using the <a href="#RFC6454">browser same-origin</a> <cite title="The Web Origin Concept" id="rfc.xref.RFC6454.3">[RFC6454]</cite> policy. For example, a HTTP/2.0 connection to www.foo.com is generally not permitted to push a response for www.evil.com.
1707      </p>
1708      <p id="rfc.section.3.3.p.3">If the browser accepts a pushed response (e.g. it does not send a RST_STREAM), the browser MUST attempt to cache the pushed
1709         response in same way that it would cache any other response. This means validating the response headers and inserting into
1710         the disk cache.
1711      </p>
1712      <p id="rfc.section.3.3.p.4">Because pushed responses have no request, they have no request headers associated with them. At the framing layer, HTTP/2.0
1713         pushed streams contain an "associated-stream-id" which indicates the requested stream for which the pushed stream is related.
1714         The pushed stream inherits all of the headers from the associated-stream-id with the exception of ":host", ":scheme", and
1715         ":path", which are provided as part of the pushed response stream headers. The browser MUST store these inherited and implied
1716         request headers with the cached resource.
1717      </p>
1718      <p id="rfc.section.3.3.p.5">Implementation note: With server push, it is theoretically possible for servers to push unreasonable amounts of content or
1719         resources to the user-agent. Browsers MUST implement throttles to protect against unreasonable push attacks.
1720      </p>
1721      <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;Server implementation
1722      </h3>
1723      <p id="rfc.section.3.3.1.p.1">When the server intends to push a resource to the user-agent, it opens a new stream by sending a unidirectional SYN_STREAM.
1724         The SYN_STREAM MUST include an Associated-To-Stream-ID, and MUST set the FLAG_UNIDIRECTIONAL flag. The SYN_STREAM MUST include
1725         headers for ":scheme", ":host", ":path", which represent the URL for the resource being pushed. Subsequent headers may follow
1726         in HEADERS frames. The purpose of the association is so that the user-agent can differentiate which request induced the pushed
1727         stream; without it, if the user-agent had two tabs open to the same page, each pushing unique content under a fixed URL, the
1728         user-agent would not be able to differentiate the requests.
1729      </p>
1730      <p id="rfc.section.3.3.1.p.2">The Associated-To-Stream-ID must be the ID of an existing, open stream. The reason for this restriction is to have a clear
1731         endpoint for pushed content. If the user-agent requested a resource on stream 11, the server replies on stream 11. It can
1732         push any number of additional streams to the client before sending a FLAG_FIN on stream 11. However, once the originating
1733         stream is closed no further push streams may be associated with it. The pushed streams do not need to be closed (FIN set)
1734         before the originating stream is closed, they only need to be created before the originating stream closes.
1735      </p>
1736      <p id="rfc.section.3.3.1.p.3">It is illegal for a server to push a resource with the Associated-To-Stream-ID of 0.</p>
1737      <p id="rfc.section.3.3.1.p.4">To minimize race conditions with the client, the SYN_STREAM for the pushed resources MUST be sent prior to sending any content
1738         which could allow the client to discover the pushed resource and request it.
1739      </p>
1740      <p id="rfc.section.3.3.1.p.5">The server MUST only push resources which would have been returned from a GET request.</p>
1741      <p id="rfc.section.3.3.1.p.6">Note: If the server does not have all of the Name/Value Response headers available at the time it issues the HEADERS frame
1742         for the pushed resource, it may later use an additional HEADERS frame to augment the name/value pairs to be associated with
1743         the pushed stream. The subsequent HEADERS frame(s) must not contain a header for ':host', ':scheme', or ':path' (e.g. the
1744         server can't change the identity of the resource to be pushed). The HEADERS frame must not contain duplicate headers with
1745         a previously sent HEADERS frame. The server must send a HEADERS frame including the scheme/host/port headers before sending
1746         any data frames on the stream.
1747      </p>
1748      <h3 id="rfc.section.3.3.2"><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;Client implementation
1749      </h3>
1750      <p id="rfc.section.3.3.2.p.1">When fetching a resource the client has 3 possibilities: </p>
1751      <ul class="empty">
1752         <li>the resource is not being pushed</li>
1753         <li>the resource is being pushed, but the data has not yet arrived</li>
1754         <li>the resource is being pushed, and the data has started to arrive</li>
1755      </ul>
1756      <p id="rfc.section.3.3.2.p.2">When a SYN_STREAM and HEADERS frame which contains an Associated-To-Stream-ID is received, the client must not issue GET requests
1757         for the resource in the pushed stream, and instead wait for the pushed stream to arrive.
1758      </p>
1759      <p id="rfc.section.3.3.2.p.3">If a client receives a server push stream with stream-id 0, it MUST issue a session error (<a href="#SessionErrorHandler" title="Session Error Handling">Section&nbsp;2.4.1</a>) with the status code PROTOCOL_ERROR.
1760      </p>
1761      <p id="rfc.section.3.3.2.p.4">When a client receives a SYN_STREAM from the server without a the ':host', ':scheme', and ':path' headers in the Name/Value
1762         section, it MUST reply with a RST_STREAM with error code HTTP_PROTOCOL_ERROR.
1763      </p>
1764      <p id="rfc.section.3.3.2.p.5">To cancel individual server push streams, the client can issue a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with error code CANCEL. Upon receipt, the server MUST stop sending on this stream immediately (this is an Abrupt termination).
1765      </p>
1766      <p id="rfc.section.3.3.2.p.6">To cancel all server push streams related to a request, the client may issue a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with error code CANCEL on the associated-stream-id. By cancelling that stream, the server MUST immediately stop sending frames
1767         for any streams with in-association-to for the original stream.
1768      </p>
1769      <p id="rfc.section.3.3.2.p.7">If the server sends a HEADER frame containing duplicate headers with a previous HEADERS frame for the same stream, the client
1770         must issue a stream error (<a href="#StreamErrorHandler" title="Stream Error Handling">Section&nbsp;2.4.2</a>) with error code PROTOCOL ERROR.
1771      </p>
1772      <p id="rfc.section.3.3.2.p.8">If the server sends a HEADERS frame after sending a data frame for the same stream, the client MAY ignore the HEADERS frame.
1773         Ignoring the HEADERS frame after a data frame prevents handling of HTTP's trailing headers (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.40).
1774      </p>
1775      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;Design Rationale and Notes
1776      </h1>
1777      <p id="rfc.section.4.p.1">Authors' notes: The notes in this section have no bearing on the HTTP/2.0 protocol as specified within this document, and
1778         none of these notes should be considered authoritative about how the protocol works. However, these notes may prove useful
1779         in future debates about how to resolve protocol ambiguities or how to evolve the protocol going forward. They may be removed
1780         before the final draft.
1781      </p>
1782      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;Separation of Framing Layer and Application Layer
1783      </h2>
1784      <p id="rfc.section.4.1.p.1">Readers may note that this specification sometimes blends the framing layer (<a href="#FramingLayer" title="HTTP/2.0 Framing Layer">Section&nbsp;2</a>) with requirements of a specific application - HTTP (<a href="#HTTPLayer" title="HTTP Layering over HTTP/2.0">Section&nbsp;3</a>). This is reflected in the request/response nature of the streams, the definition of the HEADERS and compression contexts
1785         which are very similar to HTTP, and other areas as well.
1786      </p>
1787      <p id="rfc.section.4.1.p.2">This blending is intentional - the primary goal of this protocol is to create a low-latency protocol for use with HTTP. Isolating
1788         the two layers is convenient for description of the protocol and how it relates to existing HTTP implementations. However,
1789         the ability to reuse the HTTP/2.0 framing layer is a non goal.
1790      </p>
1791      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;Error handling - Framing Layer
1792      </h2>
1793      <p id="rfc.section.4.2.p.1">Error handling at the HTTP/2.0 layer splits errors into two groups: Those that affect an individual HTTP/2.0 stream, and those
1794         that do not.
1795      </p>
1796      <p id="rfc.section.4.2.p.2">When an error is confined to a single stream, but general framing is in tact, HTTP/2.0 attempts to use the RST_STREAM as a
1797         mechanism to invalidate the stream but move forward without aborting the connection altogether.
1798      </p>
1799      <p id="rfc.section.4.2.p.3">For errors occuring outside of a single stream context, HTTP/2.0 assumes the entire session is hosed. In this case, the endpoint
1800         detecting the error should initiate a connection close.
1801      </p>
1802      <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;One Connection Per Domain
1803      </h2>
1804      <p id="rfc.section.4.3.p.1">HTTP/2.0 attempts to use fewer connections than other protocols have traditionally used. The rationale for this behavior is
1805         because it is very difficult to provide a consistent level of service (e.g. TCP slow-start), prioritization, or optimal compression
1806         when the client is connecting to the server through multiple channels.
1807      </p>
1808      <p id="rfc.section.4.3.p.2">Through lab measurements, we have seen consistent latency benefits by using fewer connections from the client. The overall
1809         number of packets sent by HTTP/2.0 can be as much as 40% less than HTTP. Handling large numbers of concurrent connections
1810         on the server also does become a scalability problem, and HTTP/2.0 reduces this load.
1811      </p>
1812      <p id="rfc.section.4.3.p.3">The use of multiple connections is not without benefit, however. Because HTTP/2.0 multiplexes multiple, independent streams
1813         onto a single stream, it creates a potential for head-of-line blocking problems at the transport level. In tests so far, the
1814         negative effects of head-of-line blocking (especially in the presence of packet loss) is outweighed by the benefits of compression
1815         and prioritization.
1816      </p>
1817      <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;Fixed vs Variable Length Fields
1818      </h2>
1819      <p id="rfc.section.4.4.p.1">HTTP/2.0 favors use of fixed length 32bit fields in cases where smaller, variable length encodings could have been used. To
1820         some, this seems like a tragic waste of bandwidth. HTTP/2.0 choses the simple encoding for speed and simplicity.
1821      </p>
1822      <p id="rfc.section.4.4.p.2">The goal of HTTP/2.0 is to reduce latency on the network. The overhead of HTTP/2.0 frames is generally quite low. Each data
1823         frame is only an 8 byte overhead for a 1452 byte payload (~0.6%). At the time of this writing, bandwidth is already plentiful,
1824         and there is a strong trend indicating that bandwidth will continue to increase. With an average worldwide bandwidth of 1Mbps,
1825         and assuming that a variable length encoding could reduce the overhead by 50%, the latency saved by using a variable length
1826         encoding would be less than 100 nanoseconds. More interesting are the effects when the larger encodings force a packet boundary,
1827         in which case a round-trip could be induced. However, by addressing other aspects of HTTP/2.0 and TCP interactions, we believe
1828         this is completely mitigated.
1829      </p>
1830      <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;Compression Context(s)
1831      </h2>
1832      <p id="rfc.section.4.5.p.1">When isolating the compression contexts used for communicating with multiple origins, we had a few choices to make. We could
1833         have maintained a map (or list) of compression contexts usable for each origin. The basic case is easy - each HEADERS frame
1834         would need to identify the context to use for that frame. However, compression contexts are not cheap, so the lifecycle of
1835         each context would need to be bounded. For proxy servers, where we could churn through many contexts, this would be a concern.
1836         We considered using a static set of contexts, say 16 of them, which would bound the memory use. We also considered dynamic
1837         contexts, which could be created on the fly, and would need to be subsequently destroyed. All of these are complicated, and
1838         ultimately we decided that such a mechanism creates too many problems to solve.
1839      </p>
1840      <p id="rfc.section.4.5.p.2">Alternatively, we've chosen the simple approach, which is to simply provide a flag for resetting the compression context.
1841         For the common case (no proxy), this fine because most requests are to the same origin and we never need to reset the context.
1842         For cases where we are using two different origins over a single HTTP/2.0 session, we simply reset the compression state between
1843         each transition.
1844      </p>
1845      <h2 id="rfc.section.4.6"><a href="#rfc.section.4.6">4.6</a>&nbsp;Unidirectional streams
1846      </h2>
1847      <p id="rfc.section.4.6.p.1">Many readers notice that unidirectional streams are both a bit confusing in concept and also somewhat redundant. If the recipient
1848         of a stream doesn't wish to send data on a stream, it could simply send a SYN_REPLY with the FLAG_FIN bit set. The FLAG_UNIDIRECTIONAL
1849         is, therefore, not necessary.
1850      </p>
1851      <p id="rfc.section.4.6.p.2">It is true that we don't need the UNIDIRECTIONAL markings. It is added because it avoids the recipient of pushed streams from
1852         needing to send a set of empty frames (e.g. the SYN_STREAM w/ FLAG_FIN) which otherwise serve no purpose.
1853      </p>
1854      <h2 id="rfc.section.4.7"><a href="#rfc.section.4.7">4.7</a>&nbsp;Data Compression
1855      </h2>
1856      <p id="rfc.section.4.7.p.1">Generic compression of data portion of the streams (as opposed to compression of the headers) without knowing the content
1857         of the stream is redundant. There is no value in compressing a stream which is already compressed. Because of this, HTTP/2.0
1858         does allow data compression to be optional. We included it because study of existing websites shows that many sites are not
1859         using compression as they should, and users suffer because of it. We wanted a mechanism where, at the HTTP/2.0 layer, site
1860         administrators could simply force compression - it is better to compress twice than to not compress.
1861      </p>
1862      <p id="rfc.section.4.7.p.2">Overall, however, with this feature being optional and sometimes redundant, it is unclear if it is useful at all. We will
1863         likely remove it from the specification.
1864      </p>
1865      <h2 id="rfc.section.4.8"><a href="#rfc.section.4.8">4.8</a>&nbsp;Server Push
1866      </h2>
1867      <p id="rfc.section.4.8.p.1">A subtle but important point is that server push streams must be declared before the associated stream is closed. The reason
1868         for this is so that proxies have a lifetime for which they can discard information about previous streams. If a pushed stream
1869         could associate itself with an already-closed stream, then endpoints would not have a specific lifecycle for when they could
1870         disavow knowledge of the streams which went before.
1871      </p>
1872      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;Security Considerations
1873      </h1>
1874      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;Use of Same-origin constraints
1875      </h2>
1876      <p id="rfc.section.5.1.p.1">This specification uses the <a href="#RFC6454">same-origin policy</a> <cite title="The Web Origin Concept" id="rfc.xref.RFC6454.4">[RFC6454]</cite> in all cases where verification of content is required.
1877      </p>
1878      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;HTTP Headers and HTTP/2.0 Headers
1879      </h2>
1880      <p id="rfc.section.5.2.p.1">At the application level, HTTP uses name/value pairs in its headers. Because HTTP/2.0 merges the existing HTTP headers with
1881         HTTP/2.0 headers, there is a possibility that some HTTP applications already use a particular header name. To avoid any conflicts,
1882         all headers introduced for layering HTTP over HTTP/2.0 are prefixed with ":". ":" is not a valid sequence in HTTP header naming,
1883         preventing any possible conflict.
1884      </p>
1885      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;Cross-Protocol Attacks
1886      </h2>
1887      <p id="rfc.section.5.3.p.1">By utilizing TLS, we believe that HTTP/2.0 introduces no new cross-protocol attacks. TLS encrypts the contents of all transmission
1888         (except the handshake itself), making it difficult for attackers to control the data which could be used in a cross-protocol
1889         attack.
1890      </p>
1891      <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;Server Push Implicit Headers
1892      </h2>
1893      <p id="rfc.section.5.4.p.1">Pushed resources do not have an associated request. In order for existing HTTP cache control validations (such as the Vary
1894         header) to work, however, all cached resources must have a set of request headers. For this reason, browsers MUST be careful
1895         to inherit request headers from the associated stream for the push. This includes the 'Cookie' header.
1896      </p>
1897      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;Privacy Considerations
1898      </h1>
1899      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;Long Lived Connections
1900      </h2>
1901      <p id="rfc.section.6.1.p.1">HTTP/2.0 aims to keep connections open longer between clients and servers in order to reduce the latency when a user makes
1902         a request. The maintenance of these connections over time could be used to expose private information. For example, a user
1903         using a browser hours after the previous user stopped using that browser may be able to learn about what the previous user
1904         was doing. This is a problem with HTTP in its current form as well, however the short lived connections make it less of a
1905         risk.
1906      </p>
1907      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;SETTINGS frame
1908      </h2>
1909      <p id="rfc.section.6.2.p.1">The HTTP/2.0 SETTINGS frame allows servers to store out-of-band transmitted information about the communication between client
1910         and server on the client. Although this is intended only to be used to reduce latency, renegade servers could use it as a
1911         mechanism to store identifying information about the client in future requests.
1912      </p>
1913      <p id="rfc.section.6.2.p.2">Clients implementing privacy modes, such as Google Chrome's "incognito mode", may wish to disable client-persisted SETTINGS
1914         storage.
1915      </p>
1916      <p id="rfc.section.6.2.p.3">Clients MUST clear persisted SETTINGS information when clearing the cookies.</p>
1917      <p id="rfc.section.6.2.p.4">TODO: Put range maximums on each type of setting to limit inappropriate uses.</p>
1918      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;Requirements Notation
1919      </h1>
1920      <p id="rfc.section.7.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
1921         in this document are to be interpreted as described in <a href="#RFC2119">RFC 2119</a> <cite title="Key words for use in RFCs to Indicate Requirement Levels" id="rfc.xref.RFC2119.1">[RFC2119]</cite>.
1922      </p>
1923      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;Acknowledgements
1924      </h1>
1925      <p id="rfc.section.8.p.1">Prior to being used as the basis for HTTP/2.0, the following individuals contributed to the design and evolution of SPDY:
1926         Adam Langley, Wan-Teh Chang, Jim Morrison, Mark Nottingham, Alyssa Wilk, Costin Manolache, William Chan, Vitaliy Lvin, Joe
1927         Chan, Adam Barth, Ryan Hamilton, Gavin Peters, Kent Alstad, Kevin Lindsay, Paul Amer, Fan Yang, Jonathan Leighton.
1928      </p>
1929      <h1 id="rfc.references"><a href="#rfc.section.9" id="rfc.section.9">9.</a> Normative References
1930      </h1>
1931      <table>                           
1932         <tr>
1933            <td class="reference"><b id="ASCII">[ASCII]</b></td>
1934            <td class="top">“US-ASCII. Coded Character Set - 7-Bit American Standard Code for Information Interchange. Standard ANSI X3.4-1986, ANSI, 1986.”.</td>
1935         </tr>
1936         <tr>
1937            <td class="reference"><b id="RFC0793">[RFC0793]</b></td>
1938            <td class="top">Postel, J., “<a href="http://tools.ietf.org/html/rfc793">Transmission Control Protocol</a>”, STD&nbsp;7, RFC&nbsp;793, September&nbsp;1981.
1939            </td>
1940         </tr>
1941         <tr>
1942            <td class="reference"><b id="RFC1738">[RFC1738]</b></td>
1943            <td class="top">Berners-Lee, T., Masinter, L., and M. McCahill, “<a href="http://tools.ietf.org/html/rfc1738">Uniform Resource Locators (URL)</a>”, RFC&nbsp;1738, December&nbsp;1994.
1944            </td>
1945         </tr>
1946         <tr>
1947            <td class="reference"><b id="RFC1950">[RFC1950]</b></td>
1948            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.
1949            </td>
1950         </tr>
1951         <tr>
1952            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1953            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
1954            </td>
1955         </tr>
1956         <tr>
1957            <td class="reference"><b id="RFC2285">[RFC2285]</b></td>
1958            <td class="top">Mandeville, R., “<a href="http://tools.ietf.org/html/rfc2285">Benchmarking Terminology for LAN Switching Devices</a>”, RFC&nbsp;2285, February&nbsp;1998.
1959            </td>
1960         </tr>
1961         <tr>
1962            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1963            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
1964            </td>
1965         </tr>
1966         <tr>
1967            <td class="reference"><b id="RFC2617">[RFC2617]</b></td>
1968            <td class="top"><a href="mailto:john@math.nwu.edu" title="Northwestern University, Department of Mathematics">Franks, J.</a>, <a href="mailto:pbaker@verisign.com" title="Verisign Inc.">Hallam-Baker, P.</a>, <a href="mailto:jeff@AbiSource.com" title="AbiSource, Inc.">Hostetler, J.</a>, <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">Lawrence, S.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, Luotonen, A., and <a href="mailto:stewart@OpenMarket.com" title="Open Market, Inc.">L. Stewart</a>, “<a href="http://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>”, RFC&nbsp;2617, June&nbsp;1999.
1969            </td>
1970         </tr>
1971         <tr>
1972            <td class="reference"><b id="RFC4366">[RFC4366]</b></td>
1973            <td class="top">Blake-Wilson, S., Nystrom, M., Hopwood, D., Mikkelsen, J., and T. Wright, “<a href="http://tools.ietf.org/html/rfc4366">Transport Layer Security (TLS) Extensions</a>”, RFC&nbsp;4366, April&nbsp;2006.
1974            </td>
1975         </tr>
1976         <tr>
1977            <td class="reference"><b id="RFC4559">[RFC4559]</b></td>
1978            <td class="top">Jaganathan, K., Zhu, L., and J. Brezak, “<a href="http://tools.ietf.org/html/rfc4559">SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows</a>”, RFC&nbsp;4559, June&nbsp;2006.
1979            </td>
1980         </tr>
1981         <tr>
1982            <td class="reference"><b id="RFC5246">[RFC5246]</b></td>
1983            <td class="top">Dierks, T. and E. Rescorla, “<a href="http://tools.ietf.org/html/rfc5246">The Transport Layer Security (TLS) Protocol Version 1.2</a>”, RFC&nbsp;5246, August&nbsp;2008.
1984            </td>
1985         </tr>
1986         <tr>
1987            <td class="reference"><b id="RFC6454">[RFC6454]</b></td>
1988            <td class="top">Barth, A., “<a href="http://tools.ietf.org/html/rfc6454">The Web Origin Concept</a>”, RFC&nbsp;6454, December&nbsp;2011.
1989            </td>
1990         </tr>
1991         <tr>
1992            <td class="reference"><b id="TLSNPN">[TLSNPN]</b></td>
1993            <td class="top">Langley, A., “<a href="http://tools.ietf.org/html/draft-agl-tls-nextprotoneg-01">TLS Next Protocol Negotiation</a>”, Internet-Draft&nbsp;draft-agl-tls-nextprotoneg-01 (work in progress), August&nbsp;2010.
1994            </td>
1995         </tr>
1996         <tr>
1997            <td class="reference"><b id="UDELCOMPRESSION">[UDELCOMPRESSION]</b></td>
1998            <td class="top">Yang, F., Amer, P., and J. Leighton, “<a href="http://www.eecis.udel.edu/~amer/PEL/poc/pdf/SPDY-Fan.pdf">A Methodology to Derive SPDY's Initial Dictionary for Zlib Compression</a>”, &lt;<a href="http://www.eecis.udel.edu/~amer/PEL/poc/pdf/SPDY-Fan.pdf">http://www.eecis.udel.edu/~amer/PEL/poc/pdf/SPDY-Fan.pdf</a>&gt;.
1999            </td>
2000         </tr>
2001      </table>
2002      <div class="avoidbreak">
2003         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
2004         <address class="vcard"><span class="vcardline"><span class="fn">Mike Belshe</span><span class="n hidden"><span class="family-name">Belshe</span><span class="given-name">Mike</span></span></span><span class="org vcardline">Twist</span><span class="vcardline">Email: <a href="mailto:mbelshe@chromium.org"><span class="email">mbelshe@chromium.org</span></a></span></address>
2005         <address class="vcard"><span class="vcardline"><span class="fn">Roberto Peon</span><span class="n hidden"><span class="family-name">Peon</span><span class="given-name">Roberto</span></span></span><span class="org vcardline">Google, Inc</span><span class="vcardline">Email: <a href="mailto:fenix@google.com"><span class="email">fenix@google.com</span></a></span></address>
2006         <address class="vcard"><span class="vcardline"><span class="fn">Martin Thomson</span>
2007               (editor)
2008               <span class="n hidden"><span class="family-name">Thomson</span><span class="given-name">Martin</span></span></span><span class="org vcardline">Microsoft</span><span class="adr"><span class="street-address vcardline">3210 Porter Drive</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="postal-code">94043</span></span><span class="country-name vcardline">US</span></span><span class="vcardline">Email: <a href="mailto:martin.thomson@skype.net"><span class="email">martin.thomson@skype.net</span></a></span></address>
2009         <address class="vcard"><span class="vcardline"><span class="fn">Alexey Melnikov</span>
2010               (editor)
2011               <span class="n hidden"><span class="family-name">Melnikov</span><span class="given-name">Alexey</span></span></span><span class="org vcardline">Isode Ltd</span><span class="adr"><span class="street-address vcardline">5 Castle Business Village</span><span class="street-address vcardline">36 Station Road</span><span class="vcardline"><span class="locality">Hampton</span>, <span class="region">Middlesex</span>&nbsp;<span class="postal-code">TW12 2BX</span></span><span class="country-name vcardline">UK</span></span><span class="vcardline">Email: <a href="mailto:Alexey.Melnikov@isode.com"><span class="email">Alexey.Melnikov@isode.com</span></a></span></address>
2012      </div>
2013      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
2014      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.since.draft-ietf-httpbis-http2-00" href="#changes.since.draft-ietf-httpbis-http2-00">Since draft-ietf-httpbis-http2-00</a></h2>
2015      <p id="rfc.section.A.1.p.1">Changed title throughout.</p>
2016      <p id="rfc.section.A.1.p.2">Removed section on Incompatibilities with SPDY draft#2.</p>
2017      <p id="rfc.section.A.1.p.3">Changed INTERNAL_ERROR on GOAWAY to have a value of 2 &lt;<a href="https://groups.google.com/forum/?fromgroups#!topic/spdy-dev/cfUef2gL3iU">https://groups.google.com/forum/?fromgroups#!topic/spdy-dev/cfUef2gL3iU</a>&gt;.
2018      </p>
2019      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.since.draft-mbelshe-httpbis-spdy-00" href="#changes.since.draft-mbelshe-httpbis-spdy-00">Since draft-mbelshe-httpbis-spdy-00</a></h2>
2020      <p id="rfc.section.A.2.p.1">Adopted as base for draft-ietf-httpbis-http2.</p>
2021      <p id="rfc.section.A.2.p.2">Updated authors/editors list.</p>
2022      <p id="rfc.section.A.2.p.3">Added status note.</p>
2023      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
2024      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> 
2025      </p>
2026      <div class="print2col">
2027         <ul class="ind">
2028            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
2029                  <li><em>ASCII</em>&nbsp;&nbsp;<a href="#rfc.xref.ASCII.1">2.6.10</a>, <a href="#ASCII"><b>9</b></a></li>
2030               </ul>
2031            </li>
2032            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
2033                  <li><em>RFC0793</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC0793.1">2.1</a>, <a href="#RFC0793"><b>9</b></a></li>
2034                  <li><em>RFC1738</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1738.1">3.2.1</a>, <a href="#rfc.xref.RFC1738.2">3.2.1</a>, <a href="#RFC1738"><b>9</b></a></li>
2035                  <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">2.6.10.1</a>, <a href="#RFC1950"><b>9</b></a></li>
2036                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">7</a>, <a href="#RFC2119"><b>9</b></a></li>
2037                  <li><em>RFC2285</em>&nbsp;&nbsp;<a href="#RFC2285"><b>9</b></a></li>
2038                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">§</a>, <a href="#rfc.xref.RFC2616.2">3</a>, <a href="#RFC2616"><b>9</b></a></li>
2039                  <li><em>RFC2617</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2617.1">3.2.3</a>, <a href="#RFC2617"><b>9</b></a></li>
2040                  <li><em>RFC4366</em>&nbsp;&nbsp;<a href="#RFC4366"><b>9</b></a></li>
2041                  <li><em>RFC4559</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4559.1">3.2.3</a>, <a href="#RFC4559"><b>9</b></a></li>
2042                  <li><em>RFC5246</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5246.1">2.6.9</a>, <a href="#RFC5246"><b>9</b></a><ul>
2043                        <li><em>Section 4.7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5246.1">2.6.9</a></li>
2044                     </ul>
2045                  </li>
2046                  <li><em>RFC6454</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC6454.1">2.6.4</a>, <a href="#rfc.xref.RFC6454.2">3.1</a>, <a href="#rfc.xref.RFC6454.3">3.3</a>, <a href="#rfc.xref.RFC6454.4">5.1</a>, <a href="#RFC6454"><b>9</b></a></li>
2047               </ul>
2048            </li>
2049            <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul>
2050                  <li><em>TLSNPN</em>&nbsp;&nbsp;<a href="#TLSNPN"><b>9</b></a></li>
2051               </ul>
2052            </li>
2053            <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul>
2054                  <li><em>UDELCOMPRESSION</em>&nbsp;&nbsp;<a href="#rfc.xref.UDELCOMPRESSION.1">2.6.10.1</a>, <a href="#UDELCOMPRESSION"><b>9</b></a></li>
2055               </ul>
2056            </li>
2057         </ul>
2058      </div>
2059   </body>
2060</html>
Note: See TracBrowser for help on using the repository browser.