source: draft-ietf-httpbis-http2/00/draft-ietf-httpbis-http2.html

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

update to latest version of rfc2629.xslt, regen all HTML

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