[xhr-1] Initial commit for Level 1.
authorJungkee Song <jungkee.song@samsung.com>
Wed, 23 Oct 2013 21:47:37 +0900
changeset 141 71cfc398c10e
parent 140 4f9d511e8556
child 142 78d1c707ae88
[xhr-1] Initial commit for Level 1.
xhr-1/Makefile
xhr-1/Overview.html
xhr-1/Overview.src.html
xhr-1/README.markdown
xhr-1/data/RFCs.json
xhr-1/data/references.json
xhr-1/data/specs.json
xhr-1/data/xrefs/css/cssom-values.json
xhr-1/data/xrefs/css/cssom-view.json
xhr-1/data/xrefs/css/cssom.json
xhr-1/data/xrefs/dom/crypto.json
xhr-1/data/xrefs/dom/dom.json
xhr-1/data/xrefs/dom/domps.json
xhr-1/data/xrefs/dom/editing.json
xhr-1/data/xrefs/dom/fileapi.json
xhr-1/data/xrefs/dom/fullscreen.json
xhr-1/data/xrefs/dom/html-cleaner.py
xhr-1/data/xrefs/dom/html-generated.json
xhr-1/data/xrefs/dom/html.json
xhr-1/data/xrefs/dom/html.py
xhr-1/data/xrefs/dom/notifications.json
xhr-1/data/xrefs/dom/progress-events.json
xhr-1/data/xrefs/dom/typedarray.json
xhr-1/data/xrefs/dom/webidl.json
xhr-1/data/xrefs/dom/xhr.json
xhr-1/data/xrefs/dom/xml.json
xhr-1/data/xrefs/dom/xmlns.json
xhr-1/data/xrefs/dom/xmlss.json
xhr-1/data/xrefs/network/cors.json
xhr-1/data/xrefs/network/encoding.json
xhr-1/data/xrefs/network/from-origin.json
xhr-1/data/xrefs/network/http.json
xhr-1/data/xrefs/network/origin.json
xhr-1/data/xrefs/network/uri.json
xhr-1/data/xrefs/network/url.json
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/xhr-1/Makefile	Wed Oct 23 21:47:37 2013 +0900
@@ -0,0 +1,17 @@
+ANOLIS = anolis
+
+all: Overview.html data/xrefs/dom/xhr.json
+
+Overview.html: Overview.src.html data Makefile
+	$(ANOLIS) --output-encoding=ascii --omit-optional-tags --quote-attr-values \
+	--w3c-compat --enable=xspecxref --enable=refs --w3c-shortname="XMLHttpRequest" \
+	--filter=".publish" $< [email protected]
+
+data/xrefs/dom/xhr.json: Overview.src.html Makefile
+	$(ANOLIS) [email protected] $< /tmp/spec
+
+publish: Overview.src.html data Makefile
+	$(ANOLIS) --output-encoding=ascii --omit-optional-tags --quote-attr-values \
+	--w3c-compat --enable=xspecxref --enable=refs --w3c-shortname="XMLHttpRequest" \
+	--filter=".dontpublish" --pubdate="$(PUBDATE)" --w3c-status=WD \
+	$< TR/Overview.html
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/xhr-1/Overview.html	Wed Oct 23 21:47:37 2013 +0900
@@ -0,0 +1,2801 @@
+<!DOCTYPE html><html lang="en-US"><head>
+  <meta charset="utf-8">
+  <title>XMLHttpRequest Level 1</title>
+  <style>
+   pre.idl { border:solid thin; background:#eee; color:#000; padding:0.5em }
+   pre.idl :link, pre.idl :visited { color:inherit; background:transparent }
+   pre code { color:inherit; background:transparent }
+   .example { margin-left:1em; padding-left:1em; border-left:double; color:#222; background:#fcfcfc }
+   .note { margin-left:2em; font-weight:bold; font-style:italic; color:#008000 }
+   p.note::before { content:"Note: " }
+   .XXX { padding:.5em; border:solid #f00 }
+   p.XXX::before { content:"Issue: " }
+   dl.switch { padding-left:2em }
+   dl.switch > dt { text-indent:-1.5em }
+   dl.switch > dt:before { content:'\21AA'; padding:0 0.5em 0 0; display:inline-block; width:1em; text-align:right; line-height:0.5em }
+   dl.domintro { color: green; margin: 2em 0 2em 2em; padding: 0.5em 1em; border: none; background: #DDFFDD; }
+   dl.domintro dt, dl.domintro dt * { color: black; text-decoration: none; }
+   dl.domintro dd { margin: 0.5em 0 1em 2em; padding: 0; }
+   dl.domintro dd p { margin: 0.5em 0; }
+   dl.domintro:before { display: table; margin: -1em -0.5em -0.5em auto; width: auto; content: 'This box is non-normative. Implementation requirements are given below this box.'; color: red; border: solid 2px; background: white; padding: 0 0.25em; }
+   em.ct { text-transform:lowercase; font-variant:small-caps; font-style:normal }
+   dfn { font-weight:bold; font-style:normal }
+   code { color:orangered }
+   code :link, code :visited { color:inherit }
+   hr:not(.top) { display:block; background:none; border:none; padding:0; margin:2em 0; height:auto }
+   table { border-collapse:collapse; border-style:hidden hidden none hidden }
+   table thead { border-bottom:solid }
+   table tbody th:first-child { border-left:solid }
+   table td, table th { border-left:solid; border-right:solid; border-bottom:solid thin; vertical-align:top; padding:0.2em }
+  </style>
+  <link href="https://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet">
+ </head>
+ <body>
+  <div class="head">
+
+<!--begin-logo-->
+<p><a href="http://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"></a></p>
+<!--end-logo-->
+
+
+   <h1 class="head" id="xmlhttprequest-ls">XMLHttpRequest Level 1</h1>
+
+   <h2 class="no-num no-toc" id="w3c-doctype">Editor's Draft 23 October 2013</h2>
+
+   <dl>
+    <dt>This Version:</dt>
+    <dd class="dontpublish"><a href="http://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html">http://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html</a></dd>
+    <dt class="dontpublish">Participate:</dt>
+    <dd class="dontpublish">Send feedback to
+    <a href="mailto:[email protected]?subject=%5BXHR%5D%20">[email protected]</a>
+    (<a href="http://lists.w3.org/Archives/Public/public-webapps/">archives</a>) or
+    <a href="https://www.w3.org/Bugs/Public/enter_bug.cgi?product=WebAppsWG&amp;component=XHR">file a bug</a>
+    (<a href="https://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWG&amp;component=XHR&amp;resolution=---">open bugs</a>)
+    <dd class="dontpublish"><a href="http://wiki.whatwg.org/wiki/IRC">IRC: #whatwg on Freenode</a>
+
+    <dt class="dontpublish">Version History:
+    <dd class="dontpublish"><a href="http://dvcs.w3.org/hg/xhr/shortlog">http://dvcs.w3.org/hg/xhr/xhr-1/shortlog</a>
+
+    <dt>Previous Versions:</dt>
+    <dd><a href="http://www.w3.org/TR/2012/WD-XMLHttpRequest-20121206/">http://www.w3.org/TR/2012/WD-XMLHttpRequest-20121206/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2012/WD-XMLHttpRequest-20120117/">http://www.w3.org/TR/2012/WD-XMLHttpRequest-20120117/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2011/WD-XMLHttpRequest2-20110816/">http://www.w3.org/TR/2011/WD-XMLHttpRequest2-20110816/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2010/WD-XMLHttpRequest2-20100907/">http://www.w3.org/TR/2010/WD-XMLHttpRequest2-20100907/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2009/WD-XMLHttpRequest2-20090820/">http://www.w3.org/TR/2009/WD-XMLHttpRequest2-20090820/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080930/">http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080930/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080225/">http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080225/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2007/WD-XMLHttpRequest-20071026/">http://www.w3.org/TR/2007/WD-XMLHttpRequest-20071026/</a>
+    <dd><a href="http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070618/">http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070618/</a>
+    <dd><a href="http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070227/">http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070227/</a>
+    <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060927/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060927/</a>
+    <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060619/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060619/</a>
+    <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/</a>
+
+    <dt>Editor:</dt>
+    <dd><a href="http://jaubourg.net/">Julian Aubourg</a>
+     (<a href="http://www.creative-area.net/">Creative Area</a>)
+     &lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</dd>
+    <dd><a href="mailto:[email protected]">&#xc1a1;&#xc815;&#xae30;(Jungkee Song)</a>
+     (<a href="http://www.samsung.com/sec/">Samsung Electronics Co., Ltd.</a>)
+     &lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</dd>
+    <dd><a href="http://www.hallvord.com/">Hallvord R. M. Steen</a>
+     (<a href="http://www.mozilla.org/">Mozilla</a>)
+     &lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</dd>
+
+    <dt>Previous Editor:</dt>
+    <dd><a href="http://annevankesteren.nl/">Anne van Kesteren</a>
+     (<a href="http://www.mozilla.org/">Mozilla</a>)
+     &lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</dd>
+   </dl>
+  </div>
+
+<div class="w3conly">
+<!--begin-copyright-->
+<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2013 <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
+<!--end-copyright--></div>
+
+  
+
+  <hr class="top">
+
+
+<div class="dontpublish"><!-- ED version -->
+  <h2 class="no-num no-toc" id="specabstract">Abstract</h2>
+
+  <p>The XMLHttpRequest specification defines an API that provides scripted
+  client functionality for transferring data between a client and a server.
+
+  <h2 class="no-num no-toc" id="sotd">Status of this Document</h2>
+
+  <p><em>This section describes the status of this document at the time of its
+  publication. Other documents may supersede this document. A list of current
+  W3C publications and the latest revision of this technical report can be
+  found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>
+  at http://www.w3.org/TR/.</em></p>
+
+  <p>If you wish to make comments regarding this document in a manner
+  that is tracked by the W3C, please submit them via using <a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=WebAppsWG">our public bug database</a>, or please send comments to
+  <a href="mailto:[email protected]?subject=%5BXHR%5D%20">[email protected]</a>
+  (<a href="http://lists.w3.org/Archives/Public/public-webapps/">archived</a>)
+  with <samp>[XHR]</samp> at the start of the subject line.</p>
+
+  <p>The bulk of the text of this specification is also
+   available in the WHATWG <a href="http://xhr.spec.whatwg.org/">XMLHttpRequest Living Standard</a>, under a license that permits reuse of the specification text.</p>
+
+  <p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications Working
+  Group</a> is the W3C working group responsible for this specification's progress along the W3C Recommendation track. This specification is the 23 October 2013 Editor's Draft.</p>
+  
+  <p>Publication as an Editor's Draft does not imply endorsement by the W3C
+  Membership. This is a draft document and may be updated, replaced or
+  obsoleted by other documents at any time. It is inappropriate to cite this
+  document as other than work in progress.</p>
+
+  <p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C Web Applications working group actively pursues convergence of XMLHttpRequest specification with the WHATWG.</p>
+
+  <p>This document was produced by a group operating under the
+  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004
+  W3C Patent Policy</a>. W3C maintains a
+  <a href="http://www.w3.org/2004/01/pp-impl/42538/status" rel="disclosure">public
+  list of any patent disclosures</a> made in connection with the deliverables of
+  the group; that page also includes instructions for disclosing a patent. An
+  individual who has actual knowledge of a patent which the individual believes
+  contains
+  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
+  Claim(s)</a> must disclose the information in accordance with
+  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+  6 of the W3C Patent Policy</a>.</p>
+
+</div>
+
+<h2 class="no-num no-toc" id="toc">Table of Contents</h2>
+
+  
+<!--begin-toc-->
+<ol class="toc">
+ <li><a class="no-test" href="#introduction"><span class="secno">1 </span>Introduction</a>
+  <ol class="toc">
+   <li><a class="no-test" href="#specification-history"><span class="secno">1.1 </span>Specification history</a></ol></li>
+ <li><a class="no-test" href="#conformance"><span class="secno">2 </span>Conformance</a>
+  <ol class="toc">
+   <li><a class="no-test" href="#dependencies"><span class="secno">2.1 </span>Dependencies</a></li>
+   <li><a class="no-test" href="#extensibility"><span class="secno">2.2 </span>Extensibility</a></ol></li>
+ <li><a class="no-test" href="#terminology"><span class="secno">3 </span>Terminology</a></li>
+ <li><a href="#interface-xmlhttprequest"><span class="secno">4 </span>Interface <code title="">XMLHttpRequest</code></a>
+  <ol class="toc">
+   <li><a href="#task-sources"><span class="secno">4.1 </span>Task sources</a></li>
+   <li><a href="#constructors"><span class="secno">4.2 </span>Constructors</a></li>
+   <li><a href="#garbage-collection"><span class="secno">4.3 </span>Garbage collection</a></li>
+   <li><a href="#event-handlers"><span class="secno">4.4 </span>Event handlers</a></li>
+   <li><a href="#states"><span class="secno">4.5 </span>States</a></li>
+   <li><a href="#request"><span class="secno">4.6 </span>Request</a>
+    <ol class="toc">
+     <li><a href="#the-open()-method"><span class="secno">4.6.1 </span>The <code title="">open()</code> method</a></li>
+     <li><a href="#the-setrequestheader()-method"><span class="secno">4.6.2 </span>The <code title="">setRequestHeader()</code> method</a></li>
+     <li><a href="#the-timeout-attribute"><span class="secno">4.6.3 </span>The <code title="">timeout</code> attribute</a></li>
+     <li><a href="#the-withcredentials-attribute"><span class="secno">4.6.4 </span>The <code title="">withCredentials</code> attribute</a></li>
+     <li><a href="#the-upload-attribute"><span class="secno">4.6.5 </span>The <code title="">upload</code> attribute</a></li>
+     <li><a href="#the-send()-method"><span class="secno">4.6.6 </span>The <code title="">send()</code> method</a></li>
+     <li><a href="#infrastructure-for-the-send()-method"><span class="secno">4.6.7 </span>Infrastructure for the <code title="">send()</code> method</a></li>
+     <li><a href="#the-abort()-method"><span class="secno">4.6.8 </span>The <code title="">abort()</code> method</a></ol></li>
+   <li><a href="#response"><span class="secno">4.7 </span>Response</a>
+    <ol class="toc">
+     <li><a href="#the-status-attribute"><span class="secno">4.7.1 </span>The <code title="">status</code> attribute</a></li>
+     <li><a href="#the-statustext-attribute"><span class="secno">4.7.2 </span>The <code title="">statusText</code> attribute</a></li>
+     <li><a href="#the-getresponseheader()-method"><span class="secno">4.7.3 </span>The <code title="">getResponseHeader()</code> method</a></li>
+     <li><a href="#the-getallresponseheaders()-method"><span class="secno">4.7.4 </span>The <code title="">getAllResponseHeaders()</code> method</a></li>
+     <li><a href="#response-entity-body-0"><span class="secno">4.7.5 </span>Response entity body</a></li>
+     <li><a href="#the-overridemimetype()-method"><span class="secno">4.7.6 </span>The <code title="">overrideMimeType()</code> method</a></li>
+     <li><a href="#the-responsetype-attribute"><span class="secno">4.7.7 </span>The <code title="">responseType</code> attribute</a></li>
+     <li><a href="#the-response-attribute"><span class="secno">4.7.8 </span>The <code title="">response</code> attribute</a></li>
+     <li><a href="#the-responsetext-attribute"><span class="secno">4.7.9 </span>The <code title="">responseText</code> attribute</a></li>
+     <li><a href="#the-responsexml-attribute"><span class="secno">4.7.10 </span>The <code title="">responseXML</code> attribute</a></ol></li>
+   <li><a href="#events"><span class="secno">4.8 </span>Events summary</a></ol></li>
+ <li><a href="#interface-formdata"><span class="secno">5 </span>Interface <code title="">FormData</code></a></li>
+ <li><a class="no-num" href="#references">References</a></li>
+ <li><a class="no-num" href="#acknowledgments">Acknowledgments</a></ol>
+<!--end-toc-->
+
+
+
+  <h2 class="no-test" id="introduction"><span class="secno">1 </span>Introduction</h2>
+
+  <p><em>This section is non-normative.</em></p>
+
+  <p>The <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object is the ECMAScript HTTP API.
+  <a class="informative" href="#refsECMASCRIPT">[ECMASCRIPT]</a>
+  <!-- XXX elaborate on options -->
+
+  <p>The name of the object is <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> for compatibility
+  with the Web, though each component of this name is potentially
+  misleading. First, the object supports any text based format, including
+  XML. Second, it can be used to make requests over both HTTP and HTTPS
+  (some implementations support protocols in addition to HTTP and HTTPS, but
+  that functionality is not covered by this specification). Finally, it
+  supports "requests" in a broad sense of the term as it pertains to HTTP;
+  namely all activity involved with HTTP requests or responses for the
+  defined HTTP methods.</p>
+  <!-- XXX need to improve point 2 -->
+
+  <div class="example">
+   <p>Some simple code to do something with data from an XML document
+   fetched over the network:</p>
+
+   <pre><code>function processData(data) {
+  // taking care of data
+}
+
+function handler() {
+  if(this.readyState == this.DONE) {
+    if(this.status == 200 &amp;&amp;
+       this.responseXML != null &amp;&amp;
+       this.responseXML.getElementById('test').textContent) {
+      // success!
+      processData(this.responseXML.getElementById('test').textContent);
+      return;
+    }
+    // something went wrong
+    processData(null);
+  }
+}
+
+var client = new XMLHttpRequest();
+client.onreadystatechange = handler;
+client.open("GET", "unicorn.xml");
+client.send();</code></pre>
+
+   <p>If you just want to log a message to the server:</p>
+
+   <pre><code>function log(message) {
+  var client = new XMLHttpRequest();
+  client.open("POST", "/log");
+  client.setRequestHeader("Content-Type", "text/plain;charset=UTF-8");
+  client.send(message);
+}</code></pre>
+
+   <p>Or if you want to check the status of a document on the server:</p>
+
+   <pre><code>function fetchStatus(address) {
+  var client = new XMLHttpRequest();
+  client.onreadystatechange = function() {
+    // in case of network errors this might not give reliable results
+    if(this.readyState == this.DONE)
+      returnStatus(this.status);
+  }
+  client.open("HEAD", address);
+  client.send();
+}</code></pre>
+  </div>
+
+
+<h3 class="no-test" id="specification-history"><span class="secno">1.1 </span>Specification history</h3>
+
+<p>The <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object was initially defined as part of
+the WHATWG's HTML effort. (Long after Microsoft shipped an implementation.)
+It moved to the W3C in 2006. Extensions (e.g. progress events and
+cross-origin requests) to <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> were developed in a
+separate draft (XMLHttpRequest Level 2) until end of 2011, at which point
+the two drafts were merged and <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> became a single
+entity again from a standards perspective.
+
+<p>Historical discussion can be found in the following mailing list
+archives:
+
+<ul>
+ <li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/">[email protected]</a>
+ <li><a href="http://lists.w3.org/Archives/Public/public-webapi/">[email protected]</a>
+ <li><a href="http://lists.w3.org/Archives/Public/public-appformats/">[email protected]</a>
+ <li><a href="http://lists.w3.org/Archives/Public/public-webapps/">[email protected]</a>
+</ul>
+
+
+
+<h2 class="no-test" id="conformance"><span class="secno">2 </span>Conformance</h2>
+
+<p>All diagrams, examples, and notes in this specification are
+non-normative, as are all sections explicitly marked non-normative.
+Everything else in this specification is normative.
+
+<p>The key words "MUST", "MUST NOT", "REQUIRED", <!--"SHALL", "SHALL
+NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
+"OPTIONAL" in the normative parts of this specification are to be
+interpreted as described in RFC2119. For readability, these words do
+not appear in all uppercase letters in this specification.
+<a href="#refsRFC2119">[RFC2119]</a>
+
+
+  <h3 class="no-test" id="dependencies"><span class="secno">2.1 </span>Dependencies</h3>
+
+  <p>This specification relies on several underlying specifications.</p>
+
+  <dl>
+   <dt>Cross-Origin Resource Sharing</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support the algorithms of the Cross-Origin Resource Sharing
+   specification. <a href="#refsCORS">[CORS]</a></dd>
+
+   <dt>DOM4</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support at least the subset of the functionality defined in DOM4 that
+   this specification relies upon, such as various exceptions and
+   <code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#eventtarget">EventTarget</a></code>. <a href="#refsDOM">[DOM]</a></dd>
+
+   <dt>DOM Parsing and Serialization
+   <dd><p>A <span>conforming user agent</span> must support at least the
+   <a class="external" href="http://html5.org/specs/dom-parsing.html#concept-serialize" title="concept-serialize">serialize</a>
+   concept from DOM Parsing and Serialization.
+   <a href="#refsDOMPS">[DOMPS]</a>
+
+   <dt>Encoding Standard
+   <dd><p>A <span>conforming user agent</span> must 
+   support at least the subset of the functionality defined in Encoding Standard that
+   this specification relies upon, such as the <code class="external" title="utf-8"><a href="http://encoding.spec.whatwg.org/#utf-8">utf-8</a></code> <code class="external" title="encoding"><a href="http://encoding.spec.whatwg.org/#encoding">encoding</a></code>.
+   <a href="#refsENCODING">[ENCODING]</a>
+
+   <dt>File API</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support at least the subset of the functionality defined in File API that
+   this specification relies upon, such as the <code class="external"><a href="http://dev.w3.org/2006/webapi/FileAPI/#blob">Blob</a></code> and
+   <code class="external"><a href="http://dev.w3.org/2006/webapi/FileAPI/#file">File</a></code> interfaces. <a href="#refsFILEAPI">[FILEAPI]</a></p>
+
+   <dt>HTML</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support at least the subset of the functionality defined in HTML that
+   this specification relies upon, such as the basics of the
+   <code class="external"><a href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#window">Window</a></code> object and serializing a <code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#document">Document</a></code>
+   object. <a href="#refsHTML">[HTML]</a>
+
+   <dt>HTTP</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support some version of the HTTP protocol. Requirements regarding HTTP
+   are made throughout the specification. <a href="#refsHTTP">[HTTP]</a>
+
+   <dt>Progress Events</dt>
+   <dd><p>A <span>conforming user agent</span> must support the
+   Progress Events specification.
+   <a href="#refsPROGRESSEVENTS">[PROGRESSEVENTS]</a>
+
+   <dt>Typed Array</dt>
+   <dd><p>A <span>conforming user agent</span> must support the
+   <code class="external"><a href="http://www.khronos.org/registry/typedarray/specs/latest/#ARRAYBUFFER">ArrayBuffer</a></code> and
+   <code class="external"><a href="http://www.khronos.org/registry/typedarray/specs/latest/#ARRAYBUFFERVIEW">ArrayBufferView</a></code> objects.
+   <a href="#refsTYPEDARRAY">[TYPEDARRAY]</a>
+
+   <dt>URL</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support the URL parsing algorithm of the URL
+   specification. <a href="#refsURL">[URL]</a></dd>
+
+   <dt>Web IDL</dt>
+   <dd><p>A <span>conforming user agent</span> must also
+   be a conforming implementation of the IDL fragments in this
+   specification, as described in the Web IDL specification.
+   <a href="#refsWEBIDL">[WEBIDL]</a>
+
+   <dt>XML</dt>
+   <dd><p>A <span>conforming user agent</span> must be a
+   conforming XML processor that reports violations of namespace
+   well-formedness. <a href="#refsXML">[XML]</a>
+   <a href="#refsXMLNS">[XMLNS]</a>
+  </dl>
+
+
+  <h3 class="no-test" id="extensibility"><span class="secno">2.2 </span>Extensibility</h3>
+
+  <p>User agents, Working Groups, and other interested parties are
+  <em>strongly encouraged</em> to discuss new features on a relevant public
+  forum, preferably
+  <a href="mailto:[email protected]">[email protected]</a>. If this
+  is for some reason not possible prefix the extension in some way. E.g. if
+  company Foo wants to add a proprietary method <code>bar()</code> it could
+  be named <code>fooBar()</code> to prevent clashes with a potential
+  non-proprietary method <code>bar()</code>.</p>
+
+
+
+  <h2 class="no-test" id="terminology"><span class="secno">3 </span>Terminology</h2>
+
+
+  <p>The term <dfn id="user-credentials">user credentials</dfn> for the purposes of this
+  specification means cookies, HTTP authentication, and client-side SSL
+  certificates. Specifically it does not refer to proxy authentication or
+  the <code title="http-origin">Origin</code> header.
+  <a href="#refsCOOKIES">[COOKIES]</a> <!-- XXX ref? --></p>
+
+
+  <h2 id="interface-xmlhttprequest"><span class="secno">4 </span>Interface <code title="">XMLHttpRequest</code></h2>
+
+  <pre class="idl">[NoInterfaceObject]
+interface <dfn id="xmlhttprequesteventtarget">XMLHttpRequestEventTarget</dfn> : <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#eventtarget">EventTarget</a> {
+  // <a href="#event-handlers">event handlers</a>
+  attribute <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#eventhandler">EventHandler</a> <a href="#handler-xhr-onloadstart" title="handler-xhr-onloadstart">onloadstart</a>;
+  attribute <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#eventhandler">EventHandler</a> <a href="#handler-xhr-onprogress" title="handler-xhr-onprogress">onprogress</a>;
+  attribute <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#eventhandler">EventHandler</a> <a href="#handler-xhr-onabort" title="handler-xhr-onabort">onabort</a>;
+  attribute <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#eventhandler">EventHandler</a> <a href="#handler-xhr-onerror" title="handler-xhr-onerror">onerror</a>;
+  attribute <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#eventhandler">EventHandler</a> <a href="#handler-xhr-onload" title="handler-xhr-onload">onload</a>;
+  attribute <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#eventhandler">EventHandler</a> <a href="#handler-xhr-ontimeout" title="handler-xhr-ontimeout">ontimeout</a>;
+  attribute <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#eventhandler">EventHandler</a> <a href="#handler-xhr-onloadend" title="handler-xhr-onloadend">onloadend</a>;
+};
+
+interface <dfn id="xmlhttprequestupload">XMLHttpRequestUpload</dfn> : <a href="#xmlhttprequesteventtarget">XMLHttpRequestEventTarget</a> {
+
+};
+
+enum <dfn id="xmlhttprequestresponsetype">XMLHttpRequestResponseType</dfn> {
+  "",
+  "arraybuffer",
+  "blob",
+  "document",
+  "text"
+};
+
+dictionary <dfn id="xmlhttprequestoptions">XMLHttpRequestOptions</dfn> {
+  boolean anonymous = false;
+};
+
+[<a href="#dom-xmlhttprequest" title="dom-XMLHttpRequest">Constructor</a>(optional <a href="#xmlhttprequestoptions">XMLHttpRequestOptions</a> <var title="">options</var>)]
+interface <dfn id="xmlhttprequest">XMLHttpRequest</dfn> : <a href="#xmlhttprequesteventtarget">XMLHttpRequestEventTarget</a> {
+  // <a href="#event-handlers">event handler</a>
+  attribute <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#eventhandler">EventHandler</a> <a href="#handler-xhr-onreadystatechange" title="handler-xhr-onreadystatechange">onreadystatechange</a>;
+
+  // <a href="#states">states</a>
+  const unsigned short <a href="#dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT">UNSENT</a> = 0;
+  const unsigned short <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a> = 1;
+  const unsigned short <a href="#dom-xmlhttprequest-headers_received" title="dom-XMLHttpRequest-HEADERS_RECEIVED">HEADERS_RECEIVED</a> = 2;
+  const unsigned short <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a> = 3;
+  const unsigned short <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a> = 4;
+  readonly attribute unsigned short <a href="#dom-xmlhttprequest-readystate" title="dom-XMLHttpRequest-readyState">readyState</a>;
+
+  // <a href="#request">request</a>
+  void <a href="#dom-xmlhttprequest-open" title="dom-XMLHttpRequest-open">open</a>(ByteString <var>method</var>, [EnsureUTF16] DOMString <var title="">url</var>, optional boolean <var>async</var> = true, optional [EnsureUTF16] DOMString? <var>username</var> = null, optional [EnsureUTF16] DOMString? <var>password</var> = null);
+  void <a href="#dom-xmlhttprequest-setrequestheader" title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader</a>(ByteString <var>header</var>, ByteString <var>value</var>);
+           attribute unsigned long <a href="#dom-xmlhttprequest-timeout" title="dom-XMLHttpRequest-timeout">timeout</a>;
+           attribute boolean <a href="#dom-xmlhttprequest-withcredentials" title="dom-XMLHttpRequest-withCredentials">withCredentials</a>;
+  readonly attribute <a href="#xmlhttprequestupload">XMLHttpRequestUpload</a> <a href="#dom-xmlhttprequest-upload" title="dom-XMLHttpRequest-upload">upload</a>;
+  void <a href="#dom-xmlhttprequest-send" title="dom-XMLHttpRequest-send">send</a>(optional (<a class="external" href="http://www.khronos.org/registry/typedarray/specs/latest/#ARRAYBUFFERVIEW">ArrayBufferView</a> or <a class="external" href="http://dev.w3.org/2006/webapi/FileAPI/#blob">Blob</a> or <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#document">Document</a> or [EnsureUTF16] DOMString or <a href="#formdata">FormData</a>)? <var>data</var> = null);
+  void <a href="#dom-xmlhttprequest-abort" title="dom-XMLHttpRequest-abort">abort</a>();
+
+  // <a href="#response">response</a>
+  readonly attribute unsigned short <a href="#dom-xmlhttprequest-status" title="dom-XMLHttpRequest-status">status</a>;
+  readonly attribute ByteString <a href="#dom-xmlhttprequest-statustext" title="dom-XMLHttpRequest-statusText">statusText</a>;
+  ByteString? <a href="#dom-xmlhttprequest-getresponseheader" title="dom-XMLHttpRequest-getResponseHeader">getResponseHeader</a>(ByteString <var>header</var>);
+  ByteString <a href="#dom-xmlhttprequest-getallresponseheaders" title="dom-XMLHttpRequest-getAllResponseHeaders">getAllResponseHeaders</a>();
+  void <a href="#dom-xmlhttprequest-overridemimetype" title="dom-XMLHttpRequest-overrideMimeType">overrideMimeType</a>(DOMString <var>mime</var>);
+           attribute <a href="#xmlhttprequestresponsetype">XMLHttpRequestResponseType</a> <a href="#dom-xmlhttprequest-responsetype" title="dom-XMLHttpRequest-responseType">responseType</a>;
+  readonly attribute any <a href="#dom-xmlhttprequest-response" title="dom-XMLHttpRequest-response">response</a>;
+  readonly attribute DOMString <a href="#dom-xmlhttprequest-responsetext" title="dom-XMLHttpRequest-responseText">responseText</a>;
+  readonly attribute <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#document">Document</a>? <a href="#dom-xmlhttprequest-responsexml" title="dom-XMLHttpRequest-responseXML">responseXML</a>;
+};</pre>
+
+<p>Each <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object has a unique, associated
+<code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.
+
+<p>If the <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+<a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#worker-environment">worker environment</a>, implementations must act as if
+<code title="">Document</code> and <code title="">Document?</code> in the above IDL were not
+exposed. I.e. <code title="dom-XMLHttpRequest-send"><a href="#dom-xmlhttprequest-send">send()</a></code> is not overloaded with it
+and <code title="dom-XMLHttpRequest-responseXML"><a href="#dom-xmlhttprequest-responsexml">responseXML</a></code> always returns null (as
+required by its definition, too).
+
+
+<h3 id="task-sources"><span class="secno">4.1 </span>Task sources</h3>
+
+<p>Each <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object has its own
+<a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#task-source">task source</a>. Namely, the
+<dfn id="xmlhttprequest-task-source"><code>XMLHttpRequest</code> task source</dfn>.
+
+
+  <h3 id="constructors"><span class="secno">4.2 </span>Constructors</h3>
+
+  <p>The <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object has an associated
+  <dfn id="anonymous-flag">anonymous flag</dfn>. If the <a href="#anonymous-flag">anonymous flag</a> is set,
+  <a href="#user-credentials">user credentials</a> and the
+  <a href="#source-origin">source origin</a> are not exposed when
+  <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#fetch" title="fetch">fetching</a> resources.
+
+  <p>When the <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a>
+  is a <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a>, the
+  <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object has an associated
+  <dfn id="concept-xmlhttprequest-document" title="concept-XMLHttpRequest-document">document</dfn>.
+
+  <dl class="domintro">
+    <dt><code><var title="">client</var> = new <a href="#dom-xmlhttprequest" title="dom-XMLHttpRequest">XMLHttpRequest</a>()</code>
+    <dd>Returns a new <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object.
+
+    <dt><code><var title="">client</var> = new <a href="#dom-xmlhttprequest" title="dom-XMLHttpRequest">XMLHttpRequest</a>({anonymous:true})</code>
+    <dd>Returns a new <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object that has its
+    <a href="#anonymous-flag">anonymous flag</a> set.
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest" title="dom-XMLHttpRequest"><code>XMLHttpRequest(<var title="">options</var>)</code></dfn>
+  constructor must run these steps:
+
+  <ol>
+    <li><p>Let <var title="">xhr</var> be a new <code><a href="#xmlhttprequest">XMLHttpRequest</a></code>
+    object.
+
+    <li><p>If <var title="">options</var>'s <code title="">anonymous</code> member is
+    true, set <var title="">xhr</var>'s <a href="#anonymous-flag">anonymous flag</a>.
+
+    <li><p>If the
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a>, set <var title="">xhr</var>'s
+    <a href="#concept-xmlhttprequest-document" title="concept-XMLHttpRequest-document">document</a> to the
+    <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-document" title="concept-document">document</a>
+    associated with the global object of <var title="">xhr</var>'s interface
+    object.
+
+    <li><p>Return <var title="">xhr</var>.
+  </ol>
+
+
+<h3 id="garbage-collection"><span class="secno">4.3 </span>Garbage collection</h3>
+
+<!-- Based on EventSource and WebSocket. Not sure what I am doing. -->
+
+<p>An <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object must not be garbage collected if
+its state is <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a> and the
+<a href="#send-flag"><code>send()</code> flag</a> is set, its state is
+<a href="#dom-xmlhttprequest-headers_received" title="dom-XMLHttpRequest-HEADERS_RECEIVED">HEADERS_RECEIVED</a>, or
+its state is <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a>, and
+one of the following is true:
+
+<ul>
+ <li><p>It has one or more
+ <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-event-listener" title="concept-event-listener">event listeners</a>
+ registered whose <b>type</b> is
+ <code title="event-xhr-readystatechange"><a href="#event-xhr-readystatechange">readystatechange</a></code>,
+ <code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code>,
+ <code title="event-xhr-abort"><a href="#event-xhr-abort">abort</a></code>,
+ <code title="event-xhr-error"><a href="#event-xhr-error">error</a></code>,
+ <code title="event-xhr-load"><a href="#event-xhr-load">load</a></code>,
+ <code title="event-xhr-timeout"><a href="#event-xhr-timeout">timeout</a></code>, or
+ <code title="event-xhr-loadend"><a href="#event-xhr-loadend">loadend</a></code>.
+ <li><p>The <a href="#upload-complete-flag">upload complete flag</a> is unset and the associated
+ <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object has one or more
+ <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-event-listener" title="concept-event-listener">event listeners</a>
+ registered whose <b>type</b> is
+ <code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code>,
+ <code title="event-xhr-abort"><a href="#event-xhr-abort">abort</a></code>,
+ <code title="event-xhr-error"><a href="#event-xhr-error">error</a></code>,
+ <code title="event-xhr-load"><a href="#event-xhr-load">load</a></code>,
+ <code title="event-xhr-timeout"><a href="#event-xhr-timeout">timeout</a></code>, or
+ <code title="event-xhr-loadend"><a href="#event-xhr-loadend">loadend</a></code>.
+</ul>
+
+<p>If an <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object is garbage collected while its
+connection is still open, the user agent must <a href="#terminate-the-request">terminate the request</a>.</p>
+
+
+
+  <h3 id="event-handlers"><span class="secno">4.4 </span>Event handlers</h3>
+
+
+  <p>The following are the
+  <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#event-handlers">event handlers</a> (and their corresponding
+  <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#event-handler-event-type" title="event handler event type">event handler event types</a>)
+  that must be supported on objects implementing an interface that inherits
+  from <code><a href="#xmlhttprequesteventtarget">XMLHttpRequestEventTarget</a></code> as attributes:</p>
+
+  <table>
+   <thead>
+    <tr>
+     <th><a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#event-handlers" title="event handlers">event handler</a>
+     <th><a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#event-handler-event-type">event handler event type</a>
+   <tbody>
+    <tr>
+     <td><dfn id="handler-xhr-onloadstart" title="handler-xhr-onloadstart"><code>onloadstart</code></dfn>
+     <td><code title="event-xhr-loadstart"><a href="#event-xhr-loadstart">loadstart</a></code>
+    <tr>
+     <td><dfn id="handler-xhr-onprogress" title="handler-xhr-onprogress"><code>onprogress</code></dfn>
+     <td><code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code>
+    <tr>
+     <td><dfn id="handler-xhr-onabort" title="handler-xhr-onabort"><code>onabort</code></dfn>
+     <td><code title="event-xhr-abort"><a href="#event-xhr-abort">abort</a></code>
+    <tr>
+     <td><dfn id="handler-xhr-onerror" title="handler-xhr-onerror"><code>onerror</code></dfn>
+     <td><code title="event-xhr-error"><a href="#event-xhr-error">error</a></code>
+    <tr>
+     <td><dfn id="handler-xhr-onload" title="handler-xhr-onload"><code>onload</code></dfn>
+     <td><code title="event-xhr-load"><a href="#event-xhr-load">load</a></code>
+    <tr>
+     <td><dfn id="handler-xhr-ontimeout" title="handler-xhr-ontimeout"><code>ontimeout</code></dfn>
+     <td><code title="event-xhr-timeout"><a href="#event-xhr-timeout">timeout</a></code>
+    <tr>
+     <td><dfn id="handler-xhr-onloadend" title="handler-xhr-onloadend"><code>onloadend</code></dfn>
+     <td><code title="event-xhr-loadend"><a href="#event-xhr-loadend">loadend</a></code>
+  </table>
+
+
+  <p>The following is the
+  <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#event-handlers" title="event handlers">event handler</a>
+  (and its corresponding
+  <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#event-handler-event-type">event handler event type</a>) that must be
+  supported as attribute solely by the
+  <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object:</p>
+
+  <table>
+   <thead>
+    <tr>
+     <th><a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#event-handlers" title="event handlers">event handler</a>
+     <th><a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#event-handler-event-type">event handler event type</a>
+   <tbody>
+    <tr>
+     <td><dfn id="handler-xhr-onreadystatechange" title="handler-xhr-onreadystatechange"><code>onreadystatechange</code></dfn>
+     <td><code title="event-xhr-readystatechange"><a href="#event-xhr-readystatechange">readystatechange</a></code></td>
+  </table>
+
+
+  <h3 id="states"><span class="secno">4.5 </span>States</h3>
+
+  <dl class="domintro">
+    <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-readystate" title="dom-XMLHttpRequest-readyState">readyState</a></code>
+    <dd><p>Returns the current state.
+  </dl>
+
+  <p>The <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object can be in several states. The
+  <dfn id="dom-xmlhttprequest-readystate" title="dom-XMLHttpRequest-readyState"><code>readyState</code></dfn>
+  attribute must return the current state, which must be one of the
+  following values:</p>
+
+  <dl>
+   <dt><dfn id="dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT"><code>UNSENT</code></dfn>
+   (numeric value 0)</dt>
+   <dd><p>The object has been constructed.</dd>
+
+   <dt><dfn id="dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED"><code>OPENED</code></dfn>
+   (numeric value 1)</dt>
+   <dd><p>The <code title="dom-XMLHttpRequest-open"><a href="#dom-xmlhttprequest-open">open()</a></code> method has been successfully invoked.
+   During this state request headers can be set using
+   <code title="dom-XMLHttpRequest-setRequestHeader"><a href="#dom-xmlhttprequest-setrequestheader">setRequestHeader()</a></code>
+   and the request can be made using the
+   <code title="dom-XMLHttpRequest-send"><a href="#dom-xmlhttprequest-send">send()</a></code> method.</dd>
+
+   <dt><dfn id="dom-xmlhttprequest-headers_received" title="dom-XMLHttpRequest-HEADERS_RECEIVED"><code>HEADERS_RECEIVED</code></dfn>
+   (numeric value 2)</dt>
+   <dd><p>All redirects (if any) have been followed and all HTTP headers of
+   the final response have been received. Several response members of the
+   object are now available.</dd>
+
+   <dt><dfn id="dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING"><code>LOADING</code></dfn>
+   (numeric value 3)</dt>
+   <dd><p>The <a href="#response-entity-body">response entity body</a> is being received.</dd>
+
+   <dt><dfn id="dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE"><code>DONE</code></dfn>
+   (numeric value 4)</dt>
+   <dd><p>The data transfer has been completed or something went wrong
+   during the transfer (e.g. infinite redirects).</dd>
+  </dl>
+
+  <p>The <dfn id="send-flag"><code>send()</code> flag</dfn> indicates
+  that the <code title="dom-XMLHttpRequest-send"><a href="#dom-xmlhttprequest-send">send()</a></code> method has
+  been invoked. It is initially unset and is used during the
+  <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a> state.
+
+  <p>The <dfn id="error-flag">error flag</dfn> indicates some type of
+  network error or fetch termination. It is initially unset.
+
+<h3 id="request"><span class="secno">4.6 </span>Request</h3>
+
+<p>Each <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object has the following
+request-associated concepts:
+
+<dfn id="request-method">request method</dfn>,
+<dfn id="request-url">request URL</dfn>,
+<dfn id="author-request-headers">author request headers</dfn>,
+<dfn id="request-entity-body">request entity body</dfn>,
+<dfn id="source-origin">source origin</dfn>,
+<dfn id="referrer-source">referrer source</dfn>,
+<dfn id="synchronous-flag">synchronous flag</dfn>,
+<dfn id="upload-complete-flag">upload complete flag</dfn>, and
+<dfn id="upload-events-flag">upload events flag</dfn>.
+
+<p>The <a href="#author-request-headers">author request headers</a> is a list of HTTP header names
+and corresponding header values. Comparisons against the HTTP header names
+must be done in a case-insensitive manner. Initially it must be empty.
+
+<p>The <a href="#request-entity-body">request entity body</a> must initially be null.
+
+<p>The <a href="#synchronous-flag">synchronous flag</a>,
+<a href="#upload-complete-flag">upload complete flag</a>, and
+<a href="#upload-events-flag">upload events flag</a> must be initially unset.
+
+<hr>
+
+<p>To <dfn id="terminate-the-request">terminate the request</dfn> run these steps:
+
+<ol>
+ <li><p>Set the <a href="#error-flag">error flag</a>.
+
+ <li><p>Cancel any instance of the <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#fetch">fetch</a> algorithm
+ opened by this object.
+
+ <li><p>If there are any <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#concept-task" title="concept-task">tasks</a> from
+ the object's <a href="#xmlhttprequest-task-source"><code>XMLHttpRequest</code> task source</a> in one of the
+ <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#task-queue" title="task queue">task queues</a>, then remove them.
+</ol>
+
+
+  <h4 id="the-open()-method"><span class="secno">4.6.1 </span>The <code title="">open()</code> method</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-open" title="dom-XMLHttpRequest-open">open</a>(<var title="">method</var>, <var title="">url</var> [, <var title="">async</var> = true [, <var title="">username</var> = null [, <var title="">password</var> = null]]])</code>
+
+   <dd>
+    <p>Sets the <a href="#request-method">request method</a>, <a href="#request-url">request URL</a>, and
+    <a href="#synchronous-flag">synchronous flag</a>.</p>
+
+    <p>Throws a JavaScript <code class="external"><a href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-predefined-exception">TypeError</a></code> if
+    either <var title="">method</var> is not a valid HTTP method or
+    <var title="">url</var> cannot be parsed.
+
+    <p>Throws a "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#securityerror">SecurityError</a></code>" exception
+    if <var title="">method</var> is a case-insensitive match for
+    <code>CONNECT</code>, <code>TRACE</code> or <code>TRACK</code>.</p>
+
+    <p>Throws an "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidaccesserror">InvalidAccessError</a></code>"
+    exception if <var title="">async</var> is false, the
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a>, and either the
+    <a href="#anonymous-flag">anonymous flag</a> is set, the
+    <code title="dom-XMLHttpRequest-timeout"><a href="#dom-xmlhttprequest-timeout">timeout</a></code> attribute is not
+    zero, the
+    <code title="dom-XMLHttpRequest-withCredentials"><a href="#dom-xmlhttprequest-withcredentials">withCredentials</a></code>
+    attribute is true, or the
+    <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code>
+    attribute is not the empty string.
+  </dl>
+
+<p>The 
+<dfn id="dom-xmlhttprequest-open" title="dom-XMLHttpRequest-open"><code>open(<var title="">method</var>, <var title="">url</var>, <var title="">async</var>, <var title="">username</var>, <var title="">password</var>)</code></dfn>
+method must run these steps:
+
+<ol>
+ <li><p>Let <var title="">base</var> be null.
+
+ <li>
+  <p>If the <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+  <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a>, run these steps:
+
+  <ol>
+   <li><p>If <a href="#concept-xmlhttprequest-document" title="concept-XMLHttpRequest-document">document</a> is not 
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#fully-active">fully active</a>, 
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an 
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.
+
+   <li><p>Set <var title="">base</var> to the 
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/urls.html#document-base-url">document base URL</a> of
+   <a href="#concept-xmlhttprequest-document" title="concept-XMLHttpRequest-document">document</a>.
+
+   <li><p>Set <a href="#source-origin">source origin</a> to a globally unique identifier if the 
+   <a href="#anonymous-flag">anonymous flag</a> is set, and the <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#origin">origin</a> 
+   of <a href="#concept-xmlhttprequest-document" title="concept-XMLHttpRequest-document">document</a> otherwise.
+
+   <li><p>Set <a href="#referrer-source">referrer source</a> to 
+   <a href="#concept-xmlhttprequest-document" title="concept-XMLHttpRequest-document">document</a>.
+  </ol>
+
+ <li>
+  <p>If the <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+  <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#worker-environment">worker environment</a>, run these steps:
+
+  <ol>
+   <li><p>Set <var title="">base</var> to the 
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#script's-base-url">script's base URL</a>.
+
+   <li><p>Set <a href="#source-origin">source origin</a> to the 
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#concept-script" title="concept-script">script</a>'s
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#origin">origin</a>.
+
+   <li><p>Set <a href="#referrer-source">referrer source</a> to the 
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#script's-referrer-source">script's referrer source</a>.
+  </ol>
+
+ <li><p>If <var>method</var> does not match the <a class="external" href="http://tools.ietf.org/html/rfc2616/#section-5.1.1">Method</a> 
+ token production, <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> a JavaScript <code class="external"><a href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-predefined-exception">TypeError</a></code>.
+
+ <li>
+  <p>If <var>method</var> is a case-insensitive match for <code>CONNECT</code>, 
+  <code>DELETE</code>, <code>GET</code>, <code>HEAD</code>, <code>OPTIONS</code>, 
+  <code>POST</code>, <code>PUT</code>, <code>TRACE</code>, or <code>TRACK</code>, subtract 
+  0x20 from each byte in the range 0x61 (ASCII a) to 0x7A (ASCII z).
+ 
+  <p class="note">If it does not match any of the above, it is passed 
+  through <em>literally</em>, including in the final request.
+  <!-- WebKit (and supposedly Gecko) also uppercase: COPY, INDEX, LOCK, 
+  M-POST, MKCOL, MOVE, PROPFIND, PROPPATCH, and UNLOCK. -->
+
+ <li>
+  <p>If <var>method</var> is a case-sensitive match for <code>CONNECT</code>, 
+  <code>TRACE</code>, or <code>TRACK</code>, 
+  <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> a 
+  "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#securityerror">SecurityError</a></code>" exception.
+
+  <p class="note">Allowing these methods would pose a security risk. 
+  <a href="#refsHTTPVERBSEC">[HTTPVERBSEC]</a>
+
+ <li><p>Let <var title="">parsed URL</var> be the result of 
+ <a class="external" href="http://url.spec.whatwg.org/#concept-url-parser" title="concept-url-parser">parsing</a> <var title="">url</var> 
+ with <var title="">base</var>.
+
+ <li><p>If <var title="">parsed URL</var> is failure, 
+ <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> a JavaScript <code class="external"><a href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-predefined-exception">TypeError</a></code>.
+
+ <li>
+  <p>If <var title="">parsed URL</var>'s <a class="external" href="http://url.spec.whatwg.org/#relative-flag">relative flag</a> is 
+  set, run these substeps:
+
+  <ol>
+   <li><p>If the <var title="">username</var> argument is not null, set 
+   <var title="">parsed URL</var>'s 
+   <a class="external" href="http://url.spec.whatwg.org/#concept-url-username" title="concept-url-username">username</a> to 
+   <var>username</var>.
+
+   <li><p>If the <var title="">password</var> argument is not null, set 
+   <var title="">parsed URL</var>'s 
+   <a class="external" href="http://url.spec.whatwg.org/#concept-url-password" title="concept-url-password">password</a> to
+   <var>password</var>.
+  </ol>
+
+ <li><p>If <var>async</var> is false, the
+ <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+ <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a>, and either the
+ <a href="#anonymous-flag">anonymous flag</a> is set, the
+ <code title="dom-XMLHttpRequest-timeout"><a href="#dom-xmlhttprequest-timeout">timeout</a></code> attribute value is not zero, the
+ <code title="dom-XMLHttpRequest-withCredentials"><a href="#dom-xmlhttprequest-withcredentials">withCredentials</a></code> attribute value is 
+ true, or the <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> attribute 
+ value is not the empty string, 
+ <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+ "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidaccesserror">InvalidAccessError</a></code>" exception.
+
+ <li>
+  <p><a href="#terminate-the-request">Terminate the request</a>.
+
+  <p class="note">After all, a request can be ongoing at this point. 
+
+ <li>
+  <p>Set variables associated with the object as follows:</p>
+
+  <ul>
+   <li><p>Set <a href="#request-method">request method</a> to <var>method</var>.
+   <li><p>Set <a href="#request-url">request URL</a> to <var title="">parsed URL</var>.
+   <li><p>If <var>async</var> is false, set the <a href="#synchronous-flag">synchronous flag</a>.
+   <li><p>Set <a href="#author-request-headers">author request headers</a> to the empty list.
+   <li><p>Unset the <a href="#send-flag"><code>send()</code> flag</a>.
+   <li><p>Set <a href="#response-entity-body">response entity body</a> to null.
+   <li><p>Set <a href="#arraybuffer-response-entity-body">arraybuffer response entity body</a> to null.
+   <li><p>Set <a href="#blob-response-entity-body">blob response entity body</a> to null.
+   <li><p>Set <a href="#document-response-entity-body">document response entity body</a> to null.
+   <li><p>Set <a href="#text-response-entity-body">text response entity body</a> to null.
+  </ul>
+
+ <li>
+  <p>If the state is not <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a>, run these
+  substeps:
+
+  <ol>
+   <li><p>Change the state to <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a>.
+
+   <li><p><a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-event-fire" title="concept-event-fire">Fire an event</a> named <code title="event-xhr-readystatechange"><a href="#event-xhr-readystatechange">readystatechange</a></code>.
+  </ol>
+</ol>
+
+  <h4 id="the-setrequestheader()-method"><span class="secno">4.6.2 </span>The <code title="">setRequestHeader()</code> method</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-setrequestheader" title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader</a>(<var title="">header</var>, <var title="">value</var>)</code>
+
+   <dd>
+    <p>Appends an header to the list of
+    <a href="#author-request-headers">author request headers</a>, or if <var>header</var> is already
+    in the list of <a href="#author-request-headers">author request headers</a>, combines its value
+    with <var>value</var>.</p>
+
+    <p>Throws an "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>"
+    exception if the state is not
+    <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a> or if the
+    <a href="#send-flag"><code>send()</code> flag</a> is set.</p>
+
+    <p>Throws a JavaScript <code class="external"><a href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-predefined-exception">TypeError</a></code> if
+    <var title="">header</var> is not a valid HTTP header field name or if
+    <var title="">value</var> is not a valid HTTP header field value.</p>
+   </dd>
+  </dl>
+
+  <p class="note">As indicated in the algorithm below certain headers cannot
+  be set and are left up to the user agent. In addition there are certain
+  other headers the user agent will take control of if they are not set by
+  the author as indicated at the end of the
+  <code title="dom-XMLHttpRequest-send"><a href="#dom-xmlhttprequest-send">send()</a></code> method section.</p>
+
+
+  <p class="note">For non <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#same-origin">same origin</a> requests using the HTTP
+  <code>GET</code> method a preflight request is made when headers other
+  than <code>Accept</code> and <code>Accept-Language</code> are set.</p>
+
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-setrequestheader" title="dom-XMLHttpRequest-setRequestHeader"><code>setRequestHeader(<var title="">header</var>, <var title="">value</var>)</code></dfn>
+  method must run these steps:</p>
+
+  <ol>
+   <li><p>If the state is not
+   <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a>,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.
+
+   <li><p>If the <a href="#send-flag"><code>send()</code> flag</a> is set,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.
+
+   <li><p>If <var>header</var> does not match the
+   <a class="external" href="http://tools.ietf.org/html/rfc2616/#section-4.2">field-name</a> production,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> a JavaScript <code class="external"><a href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-predefined-exception">TypeError</a></code>.
+
+   <li>
+    <p>If <var>value</var> does not match the
+    <a class="external" href="http://tools.ietf.org/html/rfc2616/#section-4.2">field-value</a> production,
+    <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> a JavaScript <code class="external"><a href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-predefined-exception">TypeError</a></code>.
+
+    <p class="note">An empty string represents an empty header field value.
+
+   <li>
+    <p>Terminate these steps if <var>header</var> is a case-insensitive
+    match for one of the following headers:</p>
+
+    <ul>
+     <li><code>Accept-Charset</code></li>
+     <li><code>Accept-Encoding</code></li>
+     <li><code>Access-Control-Request-Headers</code></li>
+     <li><code>Access-Control-Request-Method</code></li>
+     <li><code>Connection</code></li>
+     <li><code>Content-Length</code></li>
+     <li><code>Cookie</code></li>
+     <li><code>Cookie2</code></li>
+     <li><code>Date</code></li>
+     <li><code>DNT</code></li>
+     <li><code>Expect</code></li>
+     <li><code>Host</code></li>
+     <li><code>Keep-Alive</code></li>
+     <li><code title="">Origin</code></li>
+     <li><code>Referer</code></li>
+     <li><code>TE</code></li>
+     <li><code>Trailer</code></li>
+     <li><code>Transfer-Encoding</code></li>
+     <li><code>Upgrade</code></li>
+     <li><code>User-Agent</code></li>
+     <li><code>Via</code></li>
+    </ul>
+
+    <p>&mldr; or if the start of <var>header</var> is a case-insensitive
+    match for <code>Proxy-</code> or <code>Sec-</code> (including when
+    <var>header</var> is just <code>Proxy-</code> or <code>Sec-</code>).</p>
+
+    <p class="note">The above headers are controlled by the user agent to
+    let it control those aspects of transport. This guarantees data
+    integrity to some extent. Header names starting with <code>Sec-</code>
+    are not allowed to be set to allow new headers to be minted that are
+    guaranteed not to come from <code><a href="#xmlhttprequest">XMLHttpRequest</a></code>.</p>
+   </li>
+
+   <li><p>If <var>header</var> is not in the
+   <a href="#author-request-headers">author request headers</a> list, append <var>header</var> with
+   its associated <var>value</var> to the list and terminate these
+   steps.</li>
+
+   <li>
+    <p>If <var title="">header</var> is in the <a href="#author-request-headers">author request headers</a> list, append
+    "<code>,</code>", followed by U+0020, followed by <var title="">value</var>, to the
+    value of the header matching <var title="">header</var>.
+ 
+    <p class="note">The XMLHttpRequest standard intentionally constraints the
+    use of HTTP here in line with contemporary implementations.
+  </ol>
+
+  <div class="example">
+   <p>Some simple code demonstrating what happens when setting the same
+   header twice:</p>
+
+   <pre><code>// The following script:
+var client = new XMLHttpRequest();
+client.open('GET', 'demo.cgi');
+client.setRequestHeader('X-Test', 'one');
+client.setRequestHeader('X-Test', 'two');
+client.send();
+
+// &mldr;results in the following header being sent:
+X-Test: one, two</code></pre>
+  </div>
+
+
+  <h4 id="the-timeout-attribute"><span class="secno">4.6.3 </span>The <code title="">timeout</code> attribute</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-timeout" title="dom-XMLHttpRequest-timeout">timeout</a></code>
+   <dd>
+    <p>Can be set to a time in milliseconds. When set to a non-zero value
+    will cause <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#fetch" title="fetch">fetching</a> to
+    terminate after the given time has passed. When the time has passed, the request has
+    not yet completed, and the <a href="#synchronous-flag">synchronous flag</a> is unset, a 
+    <code title="event-xhr-timeout"><a href="#event-xhr-timeout">timeout</a></code> event will then be
+    <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-event-dispatch" title="concept-event-dispatch">dispatched</a>,
+    or a "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#timeouterror">TimeoutError</a></code>" exception will be
+    <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">thrown</a> otherwise
+    (for the <code title="dom-XMLHttpRequest"><a href="#dom-xmlhttprequest">send()</a></code> method).
+    <p>When set: throws an
+    "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidaccesserror">InvalidAccessError</a></code>" exception if
+    the <a href="#synchronous-flag">synchronous flag</a> is set and the
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a>.
+   </dd>
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-timeout" title="dom-XMLHttpRequest-timeout"><code>timeout</code></dfn>
+  attribute must return its value. Initially its value must be zero.</p>
+
+  <p>Setting the <code title="dom-XMLHttpRequest-timeout"><a href="#dom-xmlhttprequest-timeout">timeout</a></code>
+  attribute must run these steps:
+
+  <ol>
+   <li><p>If the
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a> and the
+   <a href="#synchronous-flag">synchronous flag</a> is set,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidaccesserror">InvalidAccessError</a></code>" exception.
+
+   <li><p>Set its value to the new value.
+  </ol>
+
+  <p class="note">This implies that the
+  <code title="dom-XMLHttpRequest-timeout"><a href="#dom-xmlhttprequest-timeout">timeout</a></code> attribute can be
+  set while <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#fetch" title="fetch">fetching</a> is in
+  progress. If that occurs it will still be measured relative to the start
+  of <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#fetch" title="fetch">fetching</a>.
+
+
+  <h4 id="the-withcredentials-attribute"><span class="secno">4.6.4 </span>The <code title="">withCredentials</code> attribute</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-withcredentials" title="dom-XMLHttpRequest-withCredentials">withCredentials</a></code>
+   <dd>
+    <p>True when <a href="#user-credentials">user credentials</a> are to be included in a
+    cross-origin request. False when they are to be excluded in a
+    cross-origin request and when cookies are to be ignored in its response.
+    Initially false.
+
+    <p>When set: throws an
+    "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception if the
+    state is not <a href="#dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT">UNSENT</a> or
+    <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a>, or if
+    the <a href="#send-flag"><code>send()</code> flag</a> is set.</p>
+    <p>When set: throws an
+    "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidaccesserror">InvalidAccessError</a></code>" exception if
+    either the <a href="#synchronous-flag">synchronous flag</a> is set and the
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a> or if the
+    <a href="#anonymous-flag">anonymous flag</a> is set.</p>
+   </dd>
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-withcredentials" title="dom-XMLHttpRequest-withCredentials"><code>withCredentials</code></dfn>
+  attribute must return its value. Initially its value must be false.
+
+  <p>Setting the
+  <code title="dom-XMLHttpRequest-withCredentials"><a href="#dom-xmlhttprequest-withcredentials">withCredentials</a></code>
+  attribute must run these steps:</p>
+
+  <ol>
+   <li><p>If the state is not
+   <a href="#dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT">UNSENT</a> or
+   <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a>,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.
+
+   <li><p>If the <a href="#send-flag"><code>send()</code> flag</a> is set,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.
+
+   <li><p>If the <a href="#anonymous-flag">anonymous flag</a> is set,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidaccesserror">InvalidAccessError</a></code>" exception.
+
+   <li><p>If the
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a> and the
+   <a href="#synchronous-flag">synchronous flag</a> is set,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidaccesserror">InvalidAccessError</a></code>" exception.
+
+   <li><p>Set the
+   <code title="dom-XMLHttpRequest-withCredentials"><a href="#dom-xmlhttprequest-withcredentials">withCredentials</a></code>
+   attribute's value to the given value.</li>
+  </ol>
+
+  <p class="note">The
+  <code title="dom-XMLHttpRequest-withCredentials"><a href="#dom-xmlhttprequest-withcredentials">withCredentials</a></code>
+  attribute has no effect when
+  <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#fetch" title="fetch">fetching</a>
+  <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#same-origin" title="same origin">same-origin</a>
+  resources.</p>
+
+
+  <h4 id="the-upload-attribute"><span class="secno">4.6.5 </span>The <code title="">upload</code> attribute</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-upload" title="dom-XMLHttpRequest-upload">upload</a></code>
+   <dd><p>Returns the associated <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code>
+   object. It can be used to gather transmission information when data is
+   transferred to a server.
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-upload" title="dom-XMLHttpRequest-upload"><code>upload</code></dfn>
+  attribute must return the associated
+  <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.</p>
+
+  <p class="note">As indicated earlier, each <code><a href="#xmlhttprequest">XMLHttpRequest</a></code>
+  object has an associated <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.
+
+
+  <h4 id="the-send()-method"><span class="secno">4.6.6 </span>The <code title="">send()</code> method</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-send" title="dom-XMLHttpRequest-send">send</a>([<var title="">data</var> = null])</code>
+   <dd>
+    <p>Initiates the request. The optional argument provides the
+    <a href="#request-entity-body">request entity body</a>. The argument is ignored if
+    <a href="#request-method">request method</a> is <code>GET</code> or
+    <code>HEAD</code>.</p>
+
+    <p>Throws an "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>"
+    exception if the state is not
+    <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a> or if the
+    <a href="#send-flag"><code>send()</code> flag</a> is set.</p>
+   </dd>
+  </dl>
+
+<p>The <dfn id="dom-xmlhttprequest-send" title="dom-XMLHttpRequest-send"><code>send(<var>data</var>)</code></dfn> 
+method must run these steps:
+
+  <ol>
+   <li><p>If the state is not
+   <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a>,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.
+
+   <li><p>If the <a href="#send-flag"><code>send()</code> flag</a> is set,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.
+
+   <li><p>If the <a href="#request-method">request method</a> is <code>GET</code> or
+   <code>HEAD</code>, set <var title="">data</var> to null.
+
+   <li>
+    <p>If <var title="">data</var> is null, do not include a
+    <a href="#request-entity-body">request entity body</a> and go to the next step.
+
+    <p>Otherwise, let <var>encoding</var> be null, <var>mime type</var> be
+    null, and then follow these rules, depending on <var title="">data</var>:
+
+    <dl class="switch">
+
+     <dt id="dom-XMLHttpRequest-send-ArrayBufferView"><code class="external"><a href="http://www.khronos.org/registry/typedarray/specs/latest/#ARRAYBUFFERVIEW">ArrayBufferView</a></code>
+     <dd><p>Let the <a href="#request-entity-body">request entity body</a> be the raw data
+     represented by <var title="">data</var>.</dd>
+
+     <dt id="dom-XMLHttpRequest-send-Blob"><code class="external"><a href="http://dev.w3.org/2006/webapi/FileAPI/#blob">Blob</a></code>
+     <dd>
+      <p>If the object's
+      <code class="external" title="dom-Blob-type"><a href="http://dev.w3.org/2006/webapi/FileAPI/#dfn-type">type</a></code>
+      attribute is not the empty string let <var>mime type</var> be its
+      value.</p>
+
+      <p>Let the <a href="#request-entity-body">request entity body</a> be the raw data
+      represented by <var>data</var>.</p>
+     </dd>
+
+
+     <dt id="dom-XMLHttpRequest-send-document"><a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-document" title="concept-document">document</a>
+     <dd>
+      <p>Let <var>encoding</var> be "<code title="">UTF-8</code>".
+
+      <p>If <var title="">data</var> is an <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#html-document">HTML document</a>, let
+      <var>mime type</var> be "<code>text/html</code>", or let <var>mime type</var> be
+      "<code>application/xml</code>" otherwise. Then append "<code>;charset=UTF-8</code>" to
+      <var>mime type</var>.
+
+      <p>Let the <a href="#request-entity-body">request entity body</a> be <var title="">data</var>,
+      <a class="external" href="http://html5.org/specs/dom-parsing.html#concept-serialize" title="concept-serialize">serialized</a>, 
+      <a class="external" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-obtain-unicode" title="convert a DOMString to a sequence of Unicode characters">converted to Unicode</a>, 
+      and <a class="external" href="http://encoding.spec.whatwg.org/#utf-8-encode" title="utf-8 encode">utf-8 encoded</a>.
+      Re-throw any exception
+      <a class="external" href="http://html5.org/specs/dom-parsing.html#concept-serialize" title="concept-serialize">serializing</a> throws.
+
+      <p class="note">If <var title="">data</var> cannot be
+      <a class="external" href="http://html5.org/specs/dom-parsing.html#concept-serialize" title="concept-serialize">serialized</a>, an
+      "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception is thrown.
+
+     <dt id="dom-XMLHttpRequest-send-a-string">a string
+     <dd>
+      <p>Let <var>encoding</var> be "<code title="">UTF-8</code>".
+
+      <p>Let <var>mime type</var> be "<code>text/plain;charset=UTF-8</code>".</p>
+
+      <p>Let the <a href="#request-entity-body">request entity body</a> be <var title="">data</var>,
+      <a class="external" href="http://encoding.spec.whatwg.org/#utf-8-encode" title="utf-8 encode">utf-8 encoded</a>. 
+
+     <dt id="dom-XMLHttpRequest-send-FormData"><code><a href="#formdata">FormData</a></code>
+     <dd>
+      <p>Let the <a href="#request-entity-body">request entity body</a> be the result of running
+      the
+      <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/constraints.html#multipart/form-data-encoding-algorithm"><code>multipart/form-data</code> encoding algorithm</a>
+      with <var>data</var> as <var>form data set</var> and with
+      <a class="external" href="http://encoding.spec.whatwg.org/#utf-8">utf-8</a> as the
+      explicit character encoding.
+      <!-- need to provide explicit character encoding because otherwise the
+           encoding of the document is used -->
+
+      <p>Let <var>mime type</var> be the concatenation of
+      "<code title="">multipart/form-data;</code>",
+      a U+0020 SPACE character,
+      "<code title="">boundary=</code>", and the
+      <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/constraints.html#multipart/form-data-boundary-string"><code>multipart/form-data</code> boundary string</a>
+      generated by the
+      <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/constraints.html#multipart/form-data-encoding-algorithm"><code>multipart/form-data</code> encoding algorithm</a>.
+     </dd>
+
+    </dl>
+
+    <p>If a <code>Content-Type</code> header is in
+    <a href="#author-request-headers">author request headers</a> and its value is a
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#valid-mime-type">valid MIME type</a> that has a
+    <code>charset</code> parameter whose value is not a case-insensitive
+    match for <var title="">encoding</var>, and <var title="">encoding</var>
+    is not null, set all the <code>charset</code> parameters of that
+    <code>Content-Type</code> header to <var title="">encoding</var>.
+
+    <p>If no <code>Content-Type</code> header is in
+    <a href="#author-request-headers">author request headers</a> and <var title="">mime type</var> is
+    not null, append a <code>Content-Type</code> header with value
+    <var title="">mime type</var> to <a href="#author-request-headers">author request headers</a>.
+
+    <!-- reminder: if we ever change this to always include charset it has
+    to be included as the first parameter for compatibility reasons -->
+   </li>
+
+   <li><p>If the <a href="#synchronous-flag">synchronous flag</a> is set, release the
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#storage-mutex">storage mutex</a>.</li>
+
+   <li><p>Unset the <a href="#error-flag">error flag</a>,
+   <a href="#upload-complete-flag">upload complete flag</a> and <a href="#upload-events-flag">upload events flag</a>.
+
+   <li><p>If there is no <a href="#request-entity-body">request entity body</a> or if it is empty,
+   set the <a href="#upload-complete-flag">upload complete flag</a>.
+
+   <li><p>If the <a href="#synchronous-flag">synchronous flag</a> is unset and one or more
+   event listeners are registered on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code>
+   object, set the <a href="#upload-events-flag">upload events flag</a>.
+
+   <li>
+    <p>If the <a href="#synchronous-flag">synchronous flag</a> is unset, run these substeps:</p>
+
+    <ol>
+     <li><p>Set the <a href="#send-flag"><code>send()</code> flag</a>.
+
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-loadstart"><a href="#event-xhr-loadstart">loadstart</a></code>.</li>
+
+     <li><p>If the <a href="#upload-complete-flag">upload complete flag</a> is unset,
+     <a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">fire a progress event</a> named <code title="event-xhr-loadstart"><a href="#event-xhr-loadstart">loadstart</a></code>
+     on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.</li>
+
+     <li><p>Return the <code title="dom-XMLHttpRequest-send"><a href="#dom-xmlhttprequest-send">send()</a></code>
+     method call, but continue running the steps in this algorithm.</li>
+    </ol>
+   </li>
+
+   <li>
+    <dl class="switch">
+     <dt>If the <a href="#source-origin">source origin</a> and the <a href="#request-url">request URL</a>
+     are <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#same-origin">same origin</a></dt>
+     
+     <dd>
+      <p>These are the <dfn id="same-origin-request-steps">same-origin request steps</dfn>.</p>
+
+      <p><a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#fetch">Fetch</a> the
+      <a href="#request-url">request URL</a> from <i title="">origin</i>
+      <a href="#source-origin">source origin</a>, using
+      <a href="#referrer-source">referrer source</a> as
+      <i title="">override referrer source</i>, with the
+      <i title="">synchronous flag</i> set if the
+      <a href="#synchronous-flag">synchronous flag</a> is set, using HTTP method
+      <a href="#request-method">request method</a>, taking into account the
+      <a href="#request-entity-body">request entity body</a>, list of
+      <a href="#author-request-headers">author request headers</a>, and the rules listed at the end of
+      this section.</p>
+
+      <dl class="switch">
+       <dt>If the <a href="#synchronous-flag">synchronous flag</a> is set</dt>
+       <dd>
+        <p>While making the request also follow the
+        <a href="#same-origin-request-event-rules">same-origin request event rules</a>.</p>
+
+        <!--
+         This cannot involve any task queue whatsoever because that would
+         mean other tasks on the task queue might get processed as well
+         which is counter to the whole idea of doing things synchronous.
+        -->
+
+        <p class="note">The
+        <code title="dom-XMLHttpRequest-send"><a href="#dom-xmlhttprequest-send">send()</a></code> method call will
+        now be returned by virtue of this algorithm ending.</p>
+       </dd>
+
+       <dt>If the <a href="#synchronous-flag">synchronous flag</a> is unset</dt>
+       <dd>
+
+        <p><a href="#make-upload-progress-notifications">Make upload progress notifications</a>.</p>
+
+        <p><a href="#make-progress-notifications">Make progress notifications</a>.</p>
+
+
+        <p>While processing the request, as data becomes available and when
+        the user interferes with the request,
+        <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#queue-a-task" title="queue a task">queue tasks</a>
+        to update the <a href="#response-entity-body">response entity body</a> and follow the
+        <a href="#same-origin-request-event-rules">same-origin request event rules</a>.</p>
+       </dd>
+      </dl>
+     </dd>
+
+     <dt>Otherwise</dt>
+     <dd>
+      <p>These are the <dfn id="cross-origin-request-steps">cross-origin request steps</dfn>.</p>
+
+
+
+
+      <p>Make a <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request">cross-origin request</a>,
+      passing these as parameters:</p>
+
+      <dl>
+       <dt>request URL</dt>
+       <dd>The <a href="#request-url">request URL</a>.</dd>
+
+       <dt>request method</dt>
+       <dd>The <a href="#request-method">request method</a>.</dd>
+
+       <dt>author request headers</dt>
+       <dd>The list of <a href="#author-request-headers">author request headers</a>.</dd>
+
+       <dt>request entity body</dt>
+       <dd>The <a href="#request-entity-body">request entity body</a>.</dd>
+
+       <dt>source origin</dt>
+       <dd>The <a href="#source-origin">source origin</a>.</dd>
+
+       <dt>referrer source
+       <dd>If the <a href="#anonymous-flag">anonymous flag</a> is set, the
+       <a class="external" href="http://url.spec.whatwg.org/#url">URL</a>
+       "<code title="">about:blank</code>", and the
+       <a href="#referrer-source">referrer source</a> otherwise.
+
+       <dt>omit credentials flag</dt>
+       <dd>Set if
+       <code title="dom-XMLHttpRequest-withCredentials"><a href="#dom-xmlhttprequest-withcredentials">withCredentials</a></code>
+       attribute's value is false.
+
+       <dt>force preflight flag</dt>
+       <dd>Set if the <a href="#upload-events-flag">upload events flag</a> is set.
+      </dl>
+
+      <dl class="switch">
+       <dt>If the <a href="#synchronous-flag">synchronous flag</a> is set</dt>
+       <dd>
+        <p>While making the request also follow the
+        <a href="#cross-origin-request-event-rules">cross-origin request event rules</a>.</p>
+
+        <!--
+         This cannot involve any task queue whatsoever because that would
+         mean other tasks on the task queue might get processed as well
+         which is counter to the whole idea of doing things synchronous.
+        -->
+
+        <p class="note">The
+        <code title="dom-XMLHttpRequest-send"><a href="#dom-xmlhttprequest-send">send()</a></code> method call will
+        now be returned by virtue of this algorithm ending.</p>
+       </dd>
+
+       <dt>If the <a href="#synchronous-flag">synchronous flag</a> is unset</dt>
+       <dd>
+        <p>While processing the request, as data becomes available and when
+        the end user interferes with the request,
+        <span title="queue a task">queue tasks</span> to update the
+        <a href="#response-entity-body">response entity body</a> and follow the
+        <a href="#cross-origin-request-event-rules">cross-origin request event rules</a>.</p>
+       </dd>
+      </dl>
+
+     </dd>
+    </dl>
+   </li>
+  </ol>
+
+  <hr>
+
+  <p>If the user agent allows the end user to configure a proxy it
+  should modify the request appropriately; i.e., connect
+  to the proxy host instead of the origin server, modify the
+  <code>Request-Line</code> and send <code>Proxy-Authorization</code>
+  headers as specified.</p>
+
+  <hr>
+
+  <p>If the user agent supports HTTP Authentication and
+  <code title="http-authorization">Authorization</code> is not in the list
+  of <a href="#author-request-headers">author request headers</a>, it should
+  consider requests originating from the <code><a href="#xmlhttprequest">XMLHttpRequest</a></code> object
+  to be part of the protection space that includes the accessed URIs and
+  send <code title="http-authorization">Authorization</code> headers and
+  handle <code>401 Unauthorized</code> requests appropriately.</p>
+
+  <p>If authentication fails,
+  <a href="#source-origin">source origin</a> and the
+  <a href="#request-url">request URL</a> are <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#same-origin">same origin</a>,
+  <code title="http-authorization">Authorization</code> is not in the list
+  of <a href="#author-request-headers">author request headers</a>,
+  <a href="#request-url">request URL</a>'s
+  <a class="external" href="http://url.spec.whatwg.org/#concept-url-username" title="concept-url-username">username</a> is
+  the empty string and <a href="#request-url">request URL</a>'s
+  <a class="external" href="http://url.spec.whatwg.org/#concept-url-password" title="concept-url-password">password</a> is
+  null, user agents should prompt the end user for their username and
+  password.</p>
+
+  <p>Otherwise, if authentication fails, user agents
+  must not prompt the end user for their username and
+  password. <a href="#refsHTTPAUTH">[HTTPAUTH]</a>
+
+  <p class="note">Unfortunately end users are prompted because of legacy
+  content constraints. However, when possible this behavior is prohibited,
+  as it is bad UI. E.g. that is why the
+  <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#same-origin">same origin</a> restriction is made above.
+
+  <hr>
+
+  <p>If the user agent supports HTTP State Management it
+  should persist, discard and send cookies (as received
+  in the <code>Set-Cookie</code> response header, and sent in the
+  <code>Cookie</code> header) as applicable.
+  <a href="#refsCOOKIES">[COOKIES]</a>
+
+  <hr>
+
+  <p>If the user agent implements a HTTP cache it should
+  respect <code>Cache-Control</code> headers in
+  <a href="#author-request-headers">author request headers</a>
+  (e.g. <code>Cache-Control: no-cache</code> bypasses the cache). It
+  must not send <code>Cache-Control</code> or
+  <code>Pragma</code> request headers automatically unless the end user
+  explicitly requests such behavior (e.g. by reloading the page).</p>
+
+  <p>For <code>304 Not Modified</code> responses that are a result of a
+  user agent generated conditional request the user agent
+  must act as if the server gave a <code>200 OK</code>
+  response with the appropriate content. The user agent
+  must allow <a href="#author-request-headers">author request headers</a> to override automatic cache
+  validation (e.g. <code>If-None-Match</code> or
+  <code>If-Modified-Since</code>), in which case
+  <code>304 Not Modified</code> responses must be passed through.
+  <a href="#refsHTTP">[HTTP]</a>
+
+  <hr>
+
+  <p>If the user agent implements server-driven content-negotiation
+  it must follow these constraints for the
+  <code>Accept</code> and <code>Accept-Language</code> request headers:</p>
+
+  <ul>
+   <li><p>Both headers must not be modified if they are in
+   <a href="#author-request-headers">author request headers</a>.
+
+   <li><p>If not in <a href="#author-request-headers">author request headers</a>,
+   <code>Accept-Language</code> with an appropriate value should be appended
+   to it.
+
+   <li><p>If not in <a href="#author-request-headers">author request headers</a>, <code>Accept</code>
+   with value <code>*/*</code> must be appended to it.
+  </ul>
+
+  <p>Responses must have the content-encodings
+  automatically decoded. <a href="#refsHTTP">[HTTP]</a>
+
+  <hr>
+
+  <p>Besides the <a href="#author-request-headers">author request headers</a>, user agents
+  should not include additional request headers other than those mentioned
+  above or other than those authors are not allowed to set using
+  <code title="dom-XMLHttpRequest-setRequestHeader"><a href="#dom-xmlhttprequest-setrequestheader">setRequestHeader()</a></code>.
+  This ensures that authors have a predictable API.</p>
+
+
+  <h4 id="infrastructure-for-the-send()-method"><span class="secno">4.6.7 </span>Infrastructure for the <code title="">send()</code> method</h4>
+
+  <p>The <dfn id="same-origin-request-event-rules">same-origin request event rules</dfn> are as follows:</p>
+
+  <dl class="switch">
+   <dt>If the <a href="#error-flag">error flag</a> is set
+   <dd><p>Terminate these steps.
+
+   <dt>If the response has an HTTP status code of 301, 302, 303, 307, or 308</dt>
+   <dd>
+    <p>If the redirect violates infinite loop precautions this is a
+    <a href="#network-error">network error</a>.</p>
+
+    <p>Otherwise, run these steps:</p>
+
+    <ol>
+     <li><p>Set the <a href="#request-url">request URL</a> to the
+     <a class="external" href="http://url.spec.whatwg.org/#url">URL</a> conveyed by the
+     <code>Location</code> header.</li>
+
+     <li><p>If the <a href="#source-origin">source origin</a> and the
+     <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#origin">origin</a> of <a href="#request-url">request URL</a>
+     are <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#same-origin">same origin</a> transparently follow
+     the redirect while observing the
+     <a href="#same-origin-request-event-rules">same-origin request event rules</a>.
+
+     <li><p>Otherwise, follow the <a href="#cross-origin-request-steps">cross-origin request steps</a>
+     and terminate the steps for this algorithm.</li>
+    </ol>
+
+    <p class="note">HTTP places requirements on the user agent regarding the
+    preservation of the <a href="#request-method">request method</a> and
+    <a href="#request-entity-body">request entity body</a> during redirects, and also requires end
+    users to be notified of certain kinds of automatic redirections.</p>
+    <!-- XXX HTTP needs fixing here -->
+   </dd>
+
+   <dt>If the end user cancels the request</dt>
+   <dd><p>This is an <a href="#abort-error">abort error</a>.</dd>
+
+   <dt>If there is a network error</dt>
+   <dd>
+    <p>In case of DNS errors, TLS negotiation failure, or other type of
+    network errors, this is a <a href="#network-error">network error</a>. Do not request any
+    kind of end user interaction.</p>
+
+    <p class="note">This does not include HTTP responses that indicate
+    some type of error, such as HTTP status code 410.</p>
+   </dd>
+
+
+   <dt>If <code title="dom-XMLHttpRequest-timeout"><a href="#dom-xmlhttprequest-timeout">timeout</a></code> is not 0
+   and since the request started the amount of milliseconds specified by
+   <code title="dom-XMLHttpRequest-timeout"><a href="#dom-xmlhttprequest-timeout">timeout</a></code> has passed</dt>
+   <dd><p>This is a <a href="#timeout-error">timeout error</a>.</dd>
+
+
+   <dt>Once all HTTP headers have been received, the
+   <a href="#synchronous-flag">synchronous flag</a> is unset, and the HTTP status code of the
+   response is not one of 301, 302, 303, 307, and 308</dt>
+   <dd><p><a href="#switch-headers-received">Switch to the HEADERS_RECEIVED state</a>.</dd>
+
+   <dt>Once the first byte (or more) of the
+   <a href="#response-entity-body">response entity body</a> has been received and the
+   <a href="#synchronous-flag">synchronous flag</a> is unset</dt>
+   <dt>If there is no <a href="#response-entity-body">response entity body</a> and the
+   <a href="#synchronous-flag">synchronous flag</a> is unset</dt>
+   <dd><p><a href="#switch-loading">Switch to the LOADING state</a>.</dd>
+
+   <dt>Once the whole <a href="#response-entity-body">response entity body</a> has been
+   received</dt>
+   <dt>If there is no <a href="#response-entity-body">response entity body</a> and the state is
+   <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a></dt>
+   <dt>If there is no <a href="#response-entity-body">response entity body</a> and the
+   <a href="#synchronous-flag">synchronous flag</a> is set</dt>
+   <dd><p><a href="#switch-done">Switch to the DONE state</a>.</dd>
+  </dl>
+
+
+  <hr>
+
+  <p>The <dfn id="cross-origin-request-event-rules">cross-origin request event rules</dfn> are as follows:</p>
+
+  <dl class="switch">
+   <dt>If the <a href="#error-flag">error flag</a> is set
+   <dd><p>Terminate these steps.
+
+   <dt>If the <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request-status">cross-origin request status</a>
+   is <i>preflight complete</i> and the <a href="#synchronous-flag">synchronous flag</a> is
+   unset</dt>
+   <dd><p><a href="#make-upload-progress-notifications">Make upload progress notifications</a>.</dd>
+
+   <dt>If the <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request-status">cross-origin request status</a>
+   is <i title="">network error</i></dt>
+   <dd><p>This is a <a href="#network-error">network error</a>.</dd>
+
+   <dt>If the <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request-status">cross-origin request status</a>
+   is <i title="">abort error</i></dt>
+   <dd><p>This is an <a href="#abort-error">abort error</a>.</dd>
+
+   <dt>If <code title="dom-XMLHttpRequest-timeout"><a href="#dom-xmlhttprequest-timeout">timeout</a></code> is not 0
+   and since the request started the amount of milliseconds specified by
+   <code title="dom-XMLHttpRequest-timeout"><a href="#dom-xmlhttprequest-timeout">timeout</a></code> has passed</dt>
+   <dd><p>This is a <a href="#timeout-error">timeout error</a>.</dd>
+
+   <dt>Once all HTTP headers have been received, the
+   <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request-status">cross-origin request status</a> is
+   <i>success</i>, and the <a href="#synchronous-flag">synchronous flag</a> is unset</dt>
+   <dd>
+    <p><a href="#switch-headers-received">Switch to the HEADERS_RECEIVED state</a>.</p>
+
+    <p><a href="#make-progress-notifications">Make progress notifications</a>.</p>
+   </dd>
+
+   <dt>Once the first byte (or more) of the
+   <a href="#response-entity-body">response entity body</a> has been received, the
+   <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request-status">cross-origin request status</a> is
+   <i>success</i>, and the <a href="#synchronous-flag">synchronous flag</a> is unset</dt>
+   <dt>If there is no <a href="#response-entity-body">response entity body</a>, the
+   <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request-status">cross-origin request status</a> is
+   <i>success</i>, and the <a href="#synchronous-flag">synchronous flag</a> is unset</dt>
+   <dd><p><a href="#switch-loading">Switch to the LOADING state</a>.</dd>
+
+   <dt>Once the whole <a href="#response-entity-body">response entity body</a> has been received
+   and the <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request-status">cross-origin request status</a> is
+   <i>success</i></dt>
+   <dt>If there is no <a href="#response-entity-body">response entity body</a>, the
+   <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request-status">cross-origin request status</a> is
+   <i>success</i>, and the state is
+   <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a></dt>
+   <dt>If there is no <a href="#response-entity-body">response entity body</a>, the
+   <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request-status">cross-origin request status</a> is
+   <i>success</i>, and the <a href="#synchronous-flag">synchronous flag</a> is set</dt>
+   <dd><p><a href="#switch-done">Switch to the DONE state</a>.</dd>
+  </dl>
+
+
+  <hr>
+
+  <p>When something is said to be a <dfn id="network-error">network error</dfn> run the
+  <a href="#request-error">request error</a> steps for exception
+  "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#networkerror">NetworkError</a></code>" and
+  event <code title="event-xhr-error"><a href="#event-xhr-error">error</a></code>.</p>
+
+  <p>When something is said to be an <dfn id="abort-error">abort error</dfn> run the
+  <a href="#request-error">request error</a> steps for exception
+  "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#aborterror">AbortError</a></code>" and event
+  <code title="event-xhr-abort"><a href="#event-xhr-abort">abort</a></code>.</p>
+
+
+  <p>When something is said to be an <dfn id="timeout-error">timeout error</dfn> run the
+  <a href="#request-error">request error</a> steps for exception
+  "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#timeouterror">TimeoutError</a></code>" and event
+  <code title="event-xhr-timeout"><a href="#event-xhr-timeout">timeout</a></code>.</p>
+
+
+  <p>When something is said to be a <dfn id="request-error">request error</dfn> for
+  exception <var>exception</var> and event <var title="">event</var> run these
+  steps:</p>
+
+  <ol>
+   <li><p><a href="#terminate-the-request">Terminate the request</a>.
+
+   <li><p>Change the state to <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>.</li>
+
+   <li><p>If the <a href="#synchronous-flag">synchronous flag</a> is set,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   <var>exception</var> exception.</li>
+
+   <li>
+    <p><a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-event-fire" title="concept-event-fire">Fire an event</a> named <code title="event-xhr-readystatechange"><a href="#event-xhr-readystatechange">readystatechange</a></code>.</p>
+
+    <p class="note">At this point it is clear that the
+    <a href="#synchronous-flag">synchronous flag</a> is unset.</p>
+   </li>
+
+
+   <li>
+    <p>If the <a href="#upload-complete-flag">upload complete flag</a> is unset, follow these
+    substeps:</p>
+
+    <ol>
+     <li><p>Set the <a href="#upload-complete-flag">upload complete flag</a>.
+
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named
+     <code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code> on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.
+
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named
+     <var title="">event</var> on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.
+
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named
+     <code title="event-xhr-loadend"><a href="#event-xhr-loadend">loadend</a></code> on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.
+    </ol>
+   </li>
+
+   <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code>.
+
+   <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <var title="">event</var>.
+
+   <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-loadend"><a href="#event-xhr-loadend">loadend</a></code>.
+  </ol>
+
+  <hr>
+
+  <p>When it is said to
+  <dfn id="switch-headers-received">switch to the HEADERS_RECEIVED state</dfn>
+  run these steps:</p>
+
+  <ol>
+   <li><p>Change the state to <a href="#dom-xmlhttprequest-headers_received" title="dom-XMLHttpRequest-HEADERS_RECEIVED">HEADERS_RECEIVED</a>.</li>
+
+   <li><p><a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-event-fire" title="concept-event-fire">Fire an event</a> named <code title="event-xhr-readystatechange"><a href="#event-xhr-readystatechange">readystatechange</a></code>.</li>
+  </ol>
+
+  <p>When it is said to
+  <dfn id="switch-loading">switch to the LOADING state</dfn> run these
+  steps:</p>
+
+  <ol>
+   <li><p>Change the state to <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a>.</li>
+
+   <li><p><a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-event-fire" title="concept-event-fire">Fire an event</a> named <code title="event-xhr-readystatechange"><a href="#event-xhr-readystatechange">readystatechange</a></code>.</li>
+  </ol>
+
+  <p>When it is said to
+  <dfn id="switch-done">switch to the DONE state</dfn> run these steps:</p>
+
+  <ol>
+   <li><p>If the <a href="#synchronous-flag">synchronous flag</a> is set, update the
+   <a href="#response-entity-body">response entity body</a>.</li>
+
+   <li><p>Unset the <a href="#synchronous-flag">synchronous flag</a>.
+
+   <li><p>Change the state to <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>.</li>
+
+   <li><p><a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-event-fire" title="concept-event-fire">Fire an event</a> named <code title="event-xhr-readystatechange"><a href="#event-xhr-readystatechange">readystatechange</a></code>.</li>
+
+   <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code>.
+
+   <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-load"><a href="#event-xhr-load">load</a></code>.</li>
+
+   <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-loadend"><a href="#event-xhr-loadend">loadend</a></code>.</li>
+
+  </ol>
+
+
+  <hr>
+
+  <p>When it is said to <dfn id="make-progress-notifications">make progress notifications</dfn>, while the
+  download is progressing, <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#queue-a-task">queue a task</a> to
+  <a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">fire a progress event</a> named <code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code>
+  about every 50ms or for every byte received, whichever is <em>least</em>
+  frequent.</p>
+
+  <hr>
+
+  <p>When it is said to <dfn id="make-upload-progress-notifications">make upload progress notifications</dfn> run
+  these steps:</p>
+
+  <ul>
+   <li><p>While the request entity body is being transmitted and the
+   <a href="#upload-complete-flag">upload complete flag</a> is unset,
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#queue-a-task">queue a task</a> to
+   <a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">fire a progress event</a> named <code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code> on
+   the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object about every 50ms or for
+   every byte transmitted, whichever is <em>least</em> frequent.</li>
+
+   <li>
+    <p>If the <a href="#request-entity-body">request entity body</a> has been fully transmitted
+    (irrespective of whether the server has started transmitting a response
+    or the status code of such a response) and the
+    <a href="#upload-complete-flag">upload complete flag</a> is still unset,
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#queue-a-task">queue a task</a> to run these substeps:
+
+    <ol>
+     <li><p>Set the <a href="#upload-complete-flag">upload complete flag</a>.
+
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code>
+     on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.
+
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-load"><a href="#event-xhr-load">load</a></code>
+     on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.
+
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-loadend"><a href="#event-xhr-loadend">loadend</a></code>
+     on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.
+    </ol>
+  </ul>
+
+
+
+  <h4 id="the-abort()-method"><span class="secno">4.6.8 </span>The <code title="">abort()</code> method</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-abort" title="dom-XMLHttpRequest-abort">abort</a>()</code>
+   <dd>Cancels any network activity.
+  </dl>
+
+<p>The <dfn id="dom-xmlhttprequest-abort" title="dom-XMLHttpRequest-abort"><code>abort()</code></dfn> method must run 
+these steps:
+
+  <ol>
+   <li><p><a href="#terminate-the-request">Terminate the request</a>.
+
+   <li>
+    <p>If the state is <a href="#dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT">UNSENT</a>,
+    <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a> with the
+    <a href="#send-flag"><code>send()</code> flag</a> being unset, or
+    <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a> go to the next step.</p>
+
+    <p>Otherwise, run these substeps:</p>
+
+    <ol>
+     <li><p>Change the state to <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>.</li>
+
+     <li><p>Unset the <a href="#send-flag"><code>send()</code> flag</a>.
+
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-event-fire" title="concept-event-fire">Fire an event</a> named <code title="event-xhr-readystatechange"><a href="#event-xhr-readystatechange">readystatechange</a></code>.</li>
+
+     <li>
+      <p>If the <a href="#upload-complete-flag">upload complete flag</a> is false run these
+      substeps:</p>
+
+      <ol>
+       <li><p>Set the <a href="#upload-complete-flag">upload complete flag</a> to true.</li>
+
+       <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code>
+       on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.
+
+       <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-abort"><a href="#event-xhr-abort">abort</a></code>
+       on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.</li>
+
+       <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-loadend"><a href="#event-xhr-loadend">loadend</a></code>
+       on the <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> object.</li>
+      </ol>
+     </li>
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-progress"><a href="#event-xhr-progress">progress</a></code>.
+ 
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-abort"><a href="#event-xhr-abort">abort</a></code>.
+
+     <li><p><a class="external" href="http://dev.w3.org/2006/webapi/progress/#concept-event-fire-progress" title="concept-event-fire-progress">Fire a progress event</a> named <code title="event-xhr-loadend"><a href="#event-xhr-loadend">loadend</a></code>. 
+    </ol>
+   </li>
+
+   <li>
+    <p>Change the state to <a href="#dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT">UNSENT</a>.</p>
+
+    <p class="note">No <code title="event-xhr-readystatechange"><a href="#event-xhr-readystatechange">readystatechange</a></code> event is dispatched.</p>
+   </li>
+  </ol>
+
+
+
+  <h3 id="response"><span class="secno">4.7 </span>Response</h3>
+
+  <p>A <dfn id="concept-response-header" title="concept-response-header">response header</dfn> is a HTTP response header
+  transmitted before the <a href="#response-entity-body">response entity body</a>.
+  <a href="#refsHTTP">[HTTP]</a>
+
+  <p class="note">This excludes trailer fields ("trailers").
+
+ 
+  <h4 id="the-status-attribute"><span class="secno">4.7.1 </span>The <code title="">status</code> attribute</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-status" title="dom-XMLHttpRequest-status">status</a></code>
+   <dd><p>Returns the HTTP status code.
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-status" title="dom-XMLHttpRequest-status"><code>status</code></dfn>
+  attribute must return the result of running these
+  steps:</p>
+
+  <ol>
+   <li><p>If the state is
+   <a href="#dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT">UNSENT</a> or
+   <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a>, return 0.
+
+   <li><p>If the <a href="#error-flag">error flag</a> is set, return 0.</li>
+
+   <li><p>Return the HTTP status code.</li>
+  </ol>
+
+
+  <h4 id="the-statustext-attribute"><span class="secno">4.7.2 </span>The <code title="">statusText</code> attribute</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-statustext" title="dom-XMLHttpRequest-statusText">statusText</a></code>
+   <dd><p>Returns the HTTP status text.
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-statustext" title="dom-XMLHttpRequest-statusText"><code>statusText</code></dfn>
+  attribute must return the result of running these steps:
+
+  <ol>
+   <li><p>If the state is
+   <a href="#dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT">UNSENT</a> or
+   <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a>, return the empty string.
+
+   <li><p>If the <a href="#error-flag">error flag</a> is set, return the empty string.
+
+   <li><p>Return the HTTP status text.
+  </ol>
+
+
+  <h4 id="the-getresponseheader()-method"><span class="secno">4.7.3 </span>The <code title="">getResponseHeader()</code> method</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-getresponseheader" title="dom-XMLHttpRequest-getResponseHeader">getResponseHeader</a>(<var title="">header</var>)</code>
+   <dd><p>Returns the header field value from the response of which the
+   field name matches <var title="">header</var>, unless the field name is
+   <code>Set-Cookie</code> or <code>Set-Cookie2</code>.
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-getresponseheader" title="dom-XMLHttpRequest-getResponseHeader"><code>getResponseHeader(<var title="">header</var>)</code></dfn>
+  method must run these steps:
+
+  <ol>
+   <li><p>If the state is
+   <a href="#dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT">UNSENT</a> or
+   <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a>, return null.
+
+   <li><p>If the <a href="#error-flag">error flag</a> is set, return null.
+
+   <li><p>If <var>header</var> is a case-insensitive match for
+   <code>Set-Cookie</code> or <code>Set-Cookie2</code>, return null.</li>
+
+   <li><p>If <var>header</var> is a case-insensitive match for multiple
+   <a href="#concept-response-header" title="concept-response-header">response headers</a>, return the values of these
+   headers as a single concatenated string separated from each other by a    
+   U+002C COMMA U+0020 SPACE character pair.
+
+   <li><p>If <var>header</var> is a case-insensitive match for a single
+   <a href="#concept-response-header" title="concept-response-header">response header</a>, return the value of that header.    
+
+   <li><p>Return null.</li>
+  </ol>
+
+  <p class="note">The Cross-Origin Resource Sharing specification filters
+  <a href="#concept-response-header" title="concept-response-header">response headers</a> exposed by
+  <code title="dom-XMLHttpRequest-getResponseHeader"><a href="#dom-xmlhttprequest-getresponseheader">getResponseHeader()</a></code>
+  for <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request" title="cross-origin request">cross-origin requests</a>.
+  <a href="#refsCORS">[CORS]</a>
+
+  <div class="example">
+
+   <p>For the following script:</p>
+
+   <pre><code>var client = new XMLHttpRequest();
+client.open("GET", "unicorns-are-teh-awesome.txt", true);
+client.send();
+client.onreadystatechange = function() {
+  if(this.readyState == 2) {
+    print(client.getResponseHeader("Content-Type"));
+  }
+}</code></pre>
+
+   <p>The <code>print()</code> function will get to process something
+   like:</p>
+
+   <pre><code>text/plain; charset=UTF-8</code></pre>
+  </div>
+
+
+  <h4 id="the-getallresponseheaders()-method"><span class="secno">4.7.4 </span>The <code title="">getAllResponseHeaders()</code> method</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-getallresponseheaders" title="dom-XMLHttpRequest-getAllResponseHeaders">getAllResponseHeaders</a>()</code>
+   <dd><p>Returns all headers from the response, with the exception of those
+   whose field name is <code>Set-Cookie</code> or
+   <code>Set-Cookie2</code>.
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-getallresponseheaders" title="dom-XMLHttpRequest-getAllResponseHeaders"><code>getAllResponseHeaders()</code></dfn>
+  method must run these steps:</p>
+
+  <ol>
+   <li><p>If the state is
+   <a href="#dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT">UNSENT</a> or
+   <a href="#dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED">OPENED</a>, return the empty string.
+
+   <li><p>If the <a href="#error-flag">error flag</a> is set, return the empty string.
+
+   <li><p>Return all <a href="#concept-response-header" title="concept-response-header">response headers</a>, excluding headers that are a
+   case-insensitive match for <code>Set-Cookie</code> or
+   <code>Set-Cookie2</code>, as a single string, with each header line
+   separated by a U+000D CR U+000A LF pair, excluding the status line, and
+   with each header name and header value separated by a
+   U+003A COLON U+0020 SPACE pair.</li>
+  </ol>
+
+  <p class="note">The Cross-Origin Resource Sharing specification filters
+  <a href="#concept-response-header" title="concept-response-header">response headers</a> exposed by
+  <code title="dom-XMLHttpRequest-getAllResponseHeaders"><a href="#dom-xmlhttprequest-getallresponseheaders">getAllResponseHeaders()</a></code>
+  for <a class="external" href="http://www.w3.org/TR/cors/#cross-origin-request" title="cross-origin request">cross-origin requests</a>.
+  <a href="#refsCORS">[CORS]</a> 
+
+  <div class="example">
+   <p>For the following script:</p>
+
+   <pre><code>var client = new XMLHttpRequest();
+client.open("GET", "narwhals-too.txt", true);
+client.send();
+client.onreadystatechange = function() {
+  if(this.readyState == 2) {
+    print(this.getAllResponseHeaders());
+  }
+}</code></pre>
+
+   <p>The <code>print()</code> function will get to process something
+   like:</p>
+
+   <pre><code>Date: Sun, 24 Oct 2004 04:58:38 GMT
+Server: Apache/1.3.31 (Unix)
+Keep-Alive: timeout=15, max=99
+Connection: Keep-Alive
+Transfer-Encoding: chunked
+Content-Type: text/plain; charset=utf-8</code></pre>
+  </div>
+
+
+
+  <h4 id="response-entity-body-0"><span class="secno">4.7.5 </span>Response entity body</h4>
+
+  <p>The <dfn id="response-mime-type">response MIME type</dfn> is the
+  MIME type the <code>Content-Type</code> header contains excluding any
+  parameters and
+  <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#converted-to-ascii-lowercase">converted to ASCII lowercase</a>, or null if
+  the response header can not be parsed or was omitted. The
+  <dfn id="override-mime-type">override MIME type</dfn> is initially null
+  and can get a value if
+  <code title="dom-XMLHttpRequest-overrideMimeType"><a href="#dom-xmlhttprequest-overridemimetype">overrideMimeType()</a></code>
+  is invoked. <dfn id="final-mime-type">Final MIME type</dfn> is the
+  <a href="#override-mime-type">override MIME type</a> unless that is null in which case it is
+  the <a href="#response-mime-type">response MIME type</a>.
+
+  <p>The <dfn id="response-charset">response charset</dfn> is the value of
+  the <code>charset</code> parameter of the <code>Content-Type</code> header
+  or null if there was no <code>charset</code> parameter or the header could
+  not be parsed or was omitted. The
+  <dfn id="override-charset">override charset</dfn> is initially null and
+  can get a value if <code title="dom-XMLHttpRequest-overrideMimeType"><a href="#dom-xmlhttprequest-overridemimetype">overrideMimeType()</a></code> is invoked.
+  <dfn id="final-charset">Final charset</dfn> is the
+  <a href="#override-charset">override charset</a> unless
+  that is null in which case it is the <a href="#response-charset">response charset</a>.</p>
+
+
+
+  <hr>
+
+  <p>The <dfn id="response-entity-body">response entity body</dfn> is the
+  fragment of the <a class="external" href="http://tools.ietf.org/html/rfc2616/#section-7.2">entity body</a> of the
+  response received so far
+  (<a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a>) or the complete
+  <a class="external" href="http://tools.ietf.org/html/rfc2616/#section-7.2">entity body</a> of the response
+  (<a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>). If the response
+  does not have an <a class="external" href="http://tools.ietf.org/html/rfc2616/#section-7.2">entity body</a>, the
+  <a href="#response-entity-body">response entity body</a> is null.</p>
+
+  <p class="note">The <a href="#response-entity-body">response entity body</a> is updated as part
+  of the <code title="dom-XMLHttpRequest-send"><a href="#dom-xmlhttprequest-send">send()</a></code> method and reset by the
+  <code title="dom-XMLHttpRequest-open"><a href="#dom-xmlhttprequest-open">open()</a></code> method.</p>
+
+  <hr>
+
+  <p>The
+  <dfn id="arraybuffer-response-entity-body">arraybuffer response entity body</dfn>
+  is either an <code class="external"><a href="http://www.khronos.org/registry/typedarray/specs/latest/#ARRAYBUFFER">ArrayBuffer</a></code> representing
+  the <a href="#response-entity-body">response entity body</a> or null. If the
+  <a href="#arraybuffer-response-entity-body">arraybuffer response entity body</a> is null, let it be the return value of the
+  following algorithm:</p>
+
+  <ol>
+   <li><p>If the <a href="#response-entity-body">response entity body</a> is null, return an empty
+   <code class="external"><a href="http://www.khronos.org/registry/typedarray/specs/latest/#ARRAYBUFFER">ArrayBuffer</a></code> object.</li>
+
+   <li><p>Return an <code class="external"><a href="http://www.khronos.org/registry/typedarray/specs/latest/#ARRAYBUFFER">ArrayBuffer</a></code>
+   object representing the <a href="#response-entity-body">response entity body</a>.</li>
+  </ol>
+
+
+  <p>The
+  <dfn id="blob-response-entity-body">blob response entity body</dfn> is either a
+  <code class="external"><a href="http://dev.w3.org/2006/webapi/FileAPI/#blob">Blob</a></code> representing the
+  <a href="#response-entity-body">response entity body</a> or null. If the <a href="#blob-response-entity-body">blob response entity body</a>
+  is null, let it be the return value of the following algorithm:</p>
+
+  <ol>
+   <li><p>If the <a href="#response-entity-body">response entity body</a> is null, return an empty
+   <code class="external"><a href="http://dev.w3.org/2006/webapi/FileAPI/#blob">Blob</a></code> object.</li>
+
+   <li><p>Return a <code class="external"><a href="http://dev.w3.org/2006/webapi/FileAPI/#blob">Blob</a></code> object
+   representing the <a href="#response-entity-body">response entity body</a>.
+  </ol>
+
+
+
+  <p>The
+  <dfn id="document-response-entity-body">document response entity body</dfn>
+  is either a <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-document" title="concept-document">document</a>
+  representing the <a href="#response-entity-body">response entity body</a> or null. If the
+  <a href="#document-response-entity-body">document response entity body</a> is null, let it be the return value of the
+  following algorithm:</p>
+
+  <ol>
+   <li><p>If the <a href="#response-entity-body">response entity body</a> is null, return null.</li>
+
+   <li><p>If the
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#worker-environment">worker environment</a>, return null.
+
+   <li><p>If <a href="#final-mime-type">final MIME type</a> is not null,
+   <code>text/html</code>, <code>text/xml</code>,
+   <code>application/xml</code>, or does not end in
+   <code title="">+xml</code>, return null.
+
+   <li>
+    <p>If <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> is
+    the empty string and <a href="#final-mime-type">final MIME type</a> is
+    <code>text/html</code>, return null.
+
+    <p class="note">This is restricted to
+    <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> being
+    "<code title="">document</code>" in order to prevent breaking legacy
+    content.
+
+   <li>
+    <p>If <a href="#final-mime-type">final MIME type</a> is <code>text/html</code>, run these
+    substeps:
+
+    <ol>
+     <li><p>Let <var>charset</var> be the <a href="#final-charset">final charset</a>.
+
+     <li><p>If <var>charset</var> is null,
+     <span title="prescan a byte stream to determine its encoding">prescan</span>
+     the first 1024 bytes of the <a href="#response-entity-body">response entity body</a> and if
+     that does not terminate unsuccessfully then let <var>charset</var> be
+     the return value.
+
+     <li><p>If <var>charset</var> is null, set <var>charset</var> to
+     <a class="external" href="http://encoding.spec.whatwg.org/#utf-8">utf-8</a>.
+
+     <li><p>Let <var title="">document</var> be a 
+     <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-document" title="concept-document">document</a> that
+     represents the result parsing <a href="#response-entity-body">response entity body</a> following the rules set
+     forth in the HTML specification for an HTML parser with scripting disabled and
+     <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/syntax.html#a-known-definite-encoding">a known definite encoding</a> <var>charset</var>.
+     <a href="#refsHTML">[HTML]</a>
+
+     <li><p>Set <var title="">document</var>'s
+     <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-document-encoding" title="concept-document-encoding">encoding</a>
+     to <var>charset</var>.
+     <!-- This might be redundant with HTML. --> 
+    </ol>
+
+   <li>
+    <p>Otherwise, let <var title="">document</var> be a
+    <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-document" title="concept-document">document</a>
+    that represents the result of parsing the
+    <a href="#response-entity-body">response entity body</a> following the rules set forth in the
+    XML specifications. If that fails (unsupported character encoding,
+    namespace well-formedness error, etc.), return null.
+    <a href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a>
+
+    <p class="note">Scripts in the resulting document tree will not be
+    executed, resources referenced will not be loaded and no associated XSLT
+    will be applied.</p> <!-- XXX more formally?! -->
+
+   <!-- XXX what about document's encoding? -->
+
+   <li><p>Set <var title="">document</var>'s
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-document-content-type" title="concept-document-content-type">content type</a>
+   to <a href="#final-mime-type">final MIME type</a>.
+
+   <li><p>Set <var title="">document</var>'s
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-document-url" title="concept-document-url">URL</a> to
+   <a href="#request-url">request URL</a>.
+
+   <li><p>Set <var title="">document</var>'s
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#origin">origin</a> to
+   <a href="#source-origin">source origin</a>.
+
+   <li><p>Return <var title="">document</var>.
+  </ol>
+
+  <p>The <dfn id="text-response-entity-body">text response entity body</dfn> is either a
+  string representing the <a href="#response-entity-body">response entity body</a> or null. If the
+  <a href="#text-response-entity-body">text response entity body</a> is null, let it be the return value of the 
+  following algorithm:</p>
+
+  <ol>
+   <li><p>If the <a href="#response-entity-body">response entity body</a> is null, return the empty string.</p>
+
+   <li><p>Let <var>charset</var> be the <a href="#final-charset">final charset</a>.
+
+   <li>
+    <p>If <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> is
+    the empty string, <var>charset</var> is null, and
+    <a href="#final-mime-type">final MIME type</a> is either null, <code>text/xml</code>,
+    <code>application/xml</code> or ends in <code title="">+xml</code>, use the
+    rules set forth in the XML specifications to determine the encoding. Let
+    <var>charset</var> be the determined encoding.
+    <a href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a>
+
+    <p class="note">This is restricted to
+    <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> being
+    the empty string to keep the non-legacy
+    <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> value
+    "<code title="">text</code>" simple.
+
+   <li><p>If <var>charset</var> is null, set <var>charset</var> to
+   <a class="external" href="http://encoding.spec.whatwg.org/#utf-8">utf-8</a>.
+
+   <li><p>Return the result of running
+   <a class="external" href="http://encoding.spec.whatwg.org/#decode">decode</a> on byte stream
+   <a href="#response-entity-body">response entity body</a> using fallback encoding
+   <var>charset</var>.
+  </ol>
+
+  <p class="note">Authors are strongly encouraged to always encode their
+  resources using <a class="external" href="http://encoding.spec.whatwg.org/#utf-8">utf-8</a>.
+
+
+
+  <h4 id="the-overridemimetype()-method"><span class="secno">4.7.6 </span>The <code title="">overrideMimeType()</code> method</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-overridemimetype" title="dom-XMLHttpRequest-overrideMimeType">overrideMimeType</a>(<var title="">mime</var>)</code>
+   <dd>
+    <p>Sets the <code>Content-Type</code> header for the response to
+    <var title="">mime</var>.</p>
+
+    <p>Throws an "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>"
+    exception if the state is
+    <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a> or
+    <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>.
+
+    <p>Throws a JavaScript <code class="external"><a href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-predefined-exception">TypeError</a></code> if
+    <var title="">mime</var> is not a valid media type.</p>
+   </dd>
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-overridemimetype" title="dom-XMLHttpRequest-overrideMimeType"><code>overrideMimeType(<var title="">mime</var>)</code></dfn>
+  method must run these steps:
+
+  <ol>
+   <li><p>If the state is
+   <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a> or
+   <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.
+
+   <li><p>If parsing <var title="">mime</var> analogously to the value of
+   the <code>Content-Type</code> header fails,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> a JavaScript <code class="external"><a href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-predefined-exception">TypeError</a></code>.
+
+   <li><p>If <var title="">mime</var> is successfully parsed, set
+   <a href="#override-mime-type">override MIME type</a> to its MIME type,
+   excluding any parameters, and
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#converted-to-ascii-lowercase">converted to ASCII lowercase</a>.
+
+   <li><p>If a <code>charset</code> parameter is successfully parsed, set
+   <a href="#override-charset">override charset</a> to its value.</li>
+  </ol>
+
+
+
+  <h4 id="the-responsetype-attribute"><span class="secno">4.7.7 </span>The <code title="">responseType</code> attribute</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-responsetype" title="dom-XMLHttpRequest-responseType">responseType</a></code><code> [ = <var title="">value</var> ]</code>
+   <dd>
+    <p>Returns the response type.</p>
+    <p>Can be set to change the response type. Values are:
+    the empty string (default),
+    "<code title="">arraybuffer</code>",
+    "<code title="">blob</code>",
+    "<code title="">document</code>", and
+    "<code title="">text</code>".</p>
+    <p>When set: setting to "<code title="">document</code>" is ignored if the
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#worker-environment">worker environment</a>
+    <p>When set: throws an
+    "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception if the
+    state is <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a> or
+    <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>.
+    <p>When set: throws an
+    "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidaccesserror">InvalidAccessError</a></code>" exception if the
+    <a href="#synchronous-flag">synchronous flag</a> is set and the
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+    <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a>.
+  </dl>
+
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-responsetype" title="dom-XMLHttpRequest-responseType"><code>responseType</code></dfn>
+  attribute must return its value. Initially its value must be the empty
+  string.
+
+  <p>Setting the
+  <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code>
+  attribute must run these steps:
+
+  <ol>
+   <li><p>If the state is
+   <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a> or
+   <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.
+
+   <li><p>If the
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#document-environment">document environment</a> and the
+   <a href="#synchronous-flag">synchronous flag</a> is set,
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidaccesserror">InvalidAccessError</a></code>" exception.
+
+   <li><p>If the
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#worker-environment">worker environment</a> and the given
+   value is "<code title="">document</code>", terminate these steps.
+
+   <li><p>Set the
+   <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code>
+   attribute's value to the given value.</li>
+  </ol>
+
+
+
+
+  <h4 id="the-response-attribute"><span class="secno">4.7.8 </span>The <code title="">response</code> attribute</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-response" title="dom-XMLHttpRequest-response">response</a></code>
+   <dd><p>Returns the <a href="#response-entity-body">response entity body</a>.
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-response" title="dom-XMLHttpRequest-response"><code>response</code></dfn>
+  attribute must return the result of running these
+  steps:</p>
+
+  <dl class="switch">
+   <dt>If <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code>
+   is the empty string or "<code title="">text</code>"</dt>
+   <dd>
+    <ol>
+     <li><p>If the state is not
+     <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a> or
+     <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>, return the empty string.</li>
+
+     <li><p>If the <a href="#error-flag">error flag</a> is set, return the empty string.</li>
+
+     <li><p>Return the <a href="#text-response-entity-body">text response entity body</a>.</li>
+    </ol>
+   </dd>
+   <dt>Otherwise</dt>
+   <dd>
+    <ol>
+     <li><p>If the state is not
+     <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>, return null.</li>
+
+     <li><p>If the <a href="#error-flag">error flag</a> is set, return null.</li>
+
+     <li>
+      <dl class="switch">
+       <dt>If
+       <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> is
+       "<code title="">arraybuffer</code>"</dt>
+       <dd><p>Return the
+       <a href="#arraybuffer-response-entity-body">arraybuffer response entity body</a>.</dd>
+
+       <dt>If
+       <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> is
+       "<code title="">blob</code>"</dt>
+       <dd><p>Return the
+       <a href="#blob-response-entity-body">blob response entity body</a>.</dd>
+
+       <dt>If
+       <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> is
+       "<code title="">document</code>"</dt>
+       <dd><p>Return the
+       <a href="#document-response-entity-body">document response entity body</a>.</dd>
+      </dl>
+     </li>
+    </ol>
+   </dd>
+  </dl>
+
+
+
+  <h4 id="the-responsetext-attribute"><span class="secno">4.7.9 </span>The <code title="">responseText</code> attribute</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-responsetext" title="dom-XMLHttpRequest-responseText">responseText</a></code>
+   <dd>
+    <p>Returns the <a href="#text-response-entity-body">text response entity body</a>.
+
+    <p>Throws an "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>"
+    exception if
+    <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> is not
+    the empty string or "<code title="">text</code>".
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-responsetext" title="dom-XMLHttpRequest-responseText"><code>responseText</code></dfn>
+  attribute must return the result of running these
+  steps:</p>
+
+  <ol>
+
+   <li><p>If
+   <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> is not
+   the empty string or "<code title="">text</code>",
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.
+
+
+   <li><p>If the state is not
+   <a href="#dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING">LOADING</a> or
+   <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>, return the empty string.</li>
+
+   <li><p>If the <a href="#error-flag">error flag</a> is set, return the empty string.</li>
+
+   <li><p>Return the <a href="#text-response-entity-body">text response entity body</a>.</li>
+  </ol>
+
+
+  <h4 id="the-responsexml-attribute"><span class="secno">4.7.10 </span>The <code title="">responseXML</code> attribute</h4>
+
+  <dl class="domintro">
+   <dt><code><var title="">client</var> . <a href="#dom-xmlhttprequest-responsexml" title="dom-XMLHttpRequest-responseXML">responseXML</a></code>
+   <dd>
+    <p>Returns the <a href="#document-response-entity-body">document response entity body</a>.</p>
+
+    <p>Throws an "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>"
+    exception if
+    <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> is not
+    the empty string or "<code title="">document</code>".
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-responsexml" title="dom-XMLHttpRequest-responseXML"><code>responseXML</code></dfn>
+  attribute must return the result of running these steps:</p>
+
+  <ol>
+
+   <li><p>If
+   <code title="dom-XMLHttpRequest-responseType"><a href="#dom-xmlhttprequest-responsetype">responseType</a></code> is not
+   the empty string or "<code title="">document</code>",
+   <a class="external" href="http://dev.w3.org/2006/webapi/DOM4Core/#concept-throw" title="concept-throw">throw</a> an
+   "<code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#invalidstateerror">InvalidStateError</a></code>" exception.</li>
+
+
+   <li><p>If the state is not
+   <a href="#dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE">DONE</a>, return null.
+
+   <li><p>If the <a href="#error-flag">error flag</a> is set, return null.
+
+   <li><p>Return the <a href="#document-response-entity-body">document response entity body</a>.</li>
+  </ol>
+
+
+  <p class="note">The
+  <code title="dom-XMLHttpRequest-responseXML"><a href="#dom-xmlhttprequest-responsexml">responseXML</a></code> attribute
+  has XML in its name for historical reasons. It also returns HTML resources
+  as documents.</p>
+
+
+  <h3 id="events"><span class="secno">4.8 </span>Events summary</h3>
+
+  <p><em>This section is non-normative.</em></p>
+
+  <p>The following events are dispatched on <code><a href="#xmlhttprequest">XMLHttpRequest</a></code>
+  and/or <code><a href="#xmlhttprequestupload">XMLHttpRequestUpload</a></code> objects:</p>
+
+  <table>
+   <thead>
+    <tr>
+     <th>Event name</th>
+     <th>Interface</th>
+     <th>Dispatched when&mldr;</th>
+    </tr>
+   </thead>
+   <tbody>
+    <tr>
+     <td><dfn id="event-xhr-readystatechange" title="event-xhr-readystatechange"><code>readystatechange</code></dfn></td>
+     <td><code class="external"><a href="http://dev.w3.org/2006/webapi/DOM4Core/#event">Event</a></code></td>
+     <td>The <code title="dom-XMLHttpRequest-readyState"><a href="#dom-xmlhttprequest-readystate">readyState</a></code> attribute changes
+     value, except when it changes to <a href="#dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT">UNSENT</a>.
+    </tr>
+    <tr>
+     <td><dfn id="event-xhr-loadstart" title="event-xhr-loadstart"><code>loadstart</code></dfn></td>
+     <td><code class="external"><a href="http://dev.w3.org/2006/webapi/progress/#progressevent">ProgressEvent</a></code></td>
+     <td>The request starts.</td>
+    </tr>
+    <tr>
+     <td><dfn id="event-xhr-progress" title="event-xhr-progress"><code>progress</code></dfn></td>
+     <td><code class="external"><a href="http://dev.w3.org/2006/webapi/progress/#progressevent">ProgressEvent</a></code></td>
+     <td>Transmitting data.</td>
+    </tr>
+    <tr>
+     <td><dfn id="event-xhr-abort" title="event-xhr-abort"><code>abort</code></dfn></td>
+     <td><code class="external"><a href="http://dev.w3.org/2006/webapi/progress/#progressevent">ProgressEvent</a></code></td>
+     <td>The request has been aborted. For instance, by invoking the
+     <code title="dom-XMLHttpRequest-abort"><a href="#dom-xmlhttprequest-abort">abort()</a></code> method.</td>
+    </tr>
+    <tr>
+     <td><dfn id="event-xhr-error" title="event-xhr-error"><code>error</code></dfn></td>
+     <td><code class="external"><a href="http://dev.w3.org/2006/webapi/progress/#progressevent">ProgressEvent</a></code></td>
+     <td>The request has failed.</td>
+    </tr>
+    <tr>
+     <td><dfn id="event-xhr-load" title="event-xhr-load"><code>load</code></dfn></td>
+     <td><code class="external"><a href="http://dev.w3.org/2006/webapi/progress/#progressevent">ProgressEvent</a></code></td>
+     <td>The request has successfully completed.</td>
+    </tr>
+    <tr>
+     <td><dfn id="event-xhr-timeout" title="event-xhr-timeout"><code>timeout</code></dfn></td>
+     <td><code class="external"><a href="http://dev.w3.org/2006/webapi/progress/#progressevent">ProgressEvent</a></code></td>
+     <td>The author specified timeout has passed before the request
+     completed.</td>
+    </tr>
+    <tr>
+     <td><dfn id="event-xhr-loadend" title="event-xhr-loadend"><code>loadend</code></dfn></td>
+     <td><code class="external"><a href="http://dev.w3.org/2006/webapi/progress/#progressevent">ProgressEvent</a></code></td>
+     <td>The request has completed (either in success or failure).</td>
+    </tr>
+   </tbody>
+  </table>
+
+
+
+<h2 id="interface-formdata"><span class="secno">5 </span>Interface <code title="">FormData</code></h2>
+
+<pre class="idl">[<a href="#dom-formdata" title="dom-FormData">Constructor</a>(optional <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/the-form-element.html#htmlformelement">HTMLFormElement</a> <var>form</var>)]
+interface <dfn id="formdata">FormData</dfn> {
+  void <a href="#dom-formdata-append" title="dom-FormData-append">append</a>([EnsureUTF16] DOMString <var>name</var>, <a class="external" href="http://dev.w3.org/2006/webapi/FileAPI/#blob">Blob</a> <var>value</var>, optional [EnsureUTF16] DOMString <var>filename</var>);
+  void <a href="#dom-formdata-append" title="dom-FormData-append">append</a>([EnsureUTF16] DOMString <var>name</var>, [EnsureUTF16] DOMString <var>value</var>); 
+};</pre>
+
+<p>If the <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#javascript-global-environment">JavaScript global environment</a> is a
+<a class="external" href="http://www.w3.org/html/wg/drafts/html/master/webappapis.html#worker-environment">worker environment</a>, <code><a href="#formdata">FormData</a></code> must be
+<a class="external" href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#exposed-to-javascript">exposed to JavaScript</a> as if the constructor part of the
+IDL reads <code title="">[Constructor]</code> (i.e. has no arguments).
+<!-- maybe move this into IDL at some point -->
+
+<p>The <code><a href="#formdata">FormData</a></code> object represents an ordered list of
+<dfn id="concept-formdata-entry" title="concept-FormData-entry">entries</dfn>. Each
+<a href="#concept-formdata-entry" title="concept-FormData-entry">entry</a> consists of a
+<dfn id="concept-formdata-entry-name" title="concept-FormData-entry-name">name</dfn> and a
+<dfn id="concept-formdata-entry-value" title="concept-FormData-entry-value">value</dfn>.
+
+<p>For the purposes of interaction with other algorithms, an
+<a href="#concept-formdata-entry" title="concept-FormData-entry">entry</a>'s type is "string" if
+<a href="#concept-formdata-entry-value" title="concept-FormData-entry-value">value</a> is a string and "file" otherwise. If
+an <a href="#concept-formdata-entry" title="concept-FormData-entry">entry</a>'s type is "file", its filename is the
+value of <a href="#concept-formdata-entry" title="concept-FormData-entry">entry</a>'s
+<a href="#concept-formdata-entry-value" title="concept-FormData-entry-value">value</a>'s
+<code class="external" title="dom-File-name"><a href="http://dev.w3.org/2006/webapi/FileAPI/#dfn-name">name</a></code> attribute.
+
+<dl class="domintro">
+ <dt><code><var title="">fd</var> = new <a href="#dom-formdata" title="dom-FormData">FormData</a>([<var title="">form</var>])</code>
+ <dd><p>Returns a new <code><a href="#formdata">FormData</a></code> object, optionally initialized with the
+ <a href="#concept-formdata-entry" title="concept-FormData-entry">entries</a> from <var title="">form</var> (if given).
+
+ <dt><code><var title="">fd</var> . <a href="#dom-formdata-append" title="dom-FormData-append">append</a>(<var title="">name</var>, <var title="">value</var> [, <var title="">filename</var>])</code>
+ <dd><p>Appends a new <a href="#concept-formdata-entry" title="concept-FormData-entry">entry</a> to the
+ <code><a href="#formdata">FormData</a></code> object. 
+</dl>
+
+  <p>The
+  <dfn id="dom-formdata" title="dom-FormData"><code>FormData(<var>form</var>)</code></dfn>
+  constructor must run these steps:
+
+  <ol>
+   <li><p>Let <var title="">fd</var> be a new <code><a href="#formdata">FormData</a></code> object.
+
+   <li><p>If <var>form</var> is given, set <var title="">fd</var>'s
+   <a href="#concept-formdata-entry" title="concept-FormData-entry">entries</a> to the result of
+   <a class="external" href="http://www.w3.org/html/wg/drafts/html/master/constraints.html#constructing-form-data-set">constructing the form data set</a> for <var>form</var>.
+
+   <li><p>Return <var title="">fd</var>.
+  </ol>
+
+<p>The
+<dfn id="dom-formdata-append" title="dom-FormData-append"><code>append(<var>name</var>, <var>value</var>, <var>filename</var>)</code></dfn>
+method must run these steps:
+
+<ol>
+ <li><p>Let <var title="">entry</var> be a new
+ <a href="#concept-formdata-entry" title="concept-FormData-entry">entry</a>.
+
+ <li><p>Set <var title="">entry</var>'s <a href="#concept-formdata-entry-name" title="concept-FormData-entry-name">name</a>
+ to <var>name</var>.
+
+ <li><p>If <var>value</var> is a <code class="external"><a href="http://dev.w3.org/2006/webapi/FileAPI/#blob">Blob</a></code>, set
+ <var>value</var> to a new <code class="external"><a href="http://dev.w3.org/2006/webapi/FileAPI/#file">File</a></code> object whose
+ <code class="external" title="dom-File-name"><a href="http://dev.w3.org/2006/webapi/FileAPI/#dfn-name">name</a></code> attribute value is
+ "<code title="">blob</code>". 
+
+ <li><p>If <var>value</var> is a <code class="external"><a href="http://dev.w3.org/2006/webapi/FileAPI/#file">File</a></code> and
+ <var title="">filename</var> is given, set <var>value</var>'s
+ <code class="external" title="dom-File-name"><a href="http://dev.w3.org/2006/webapi/FileAPI/#dfn-name">name</a></code> attribute value to
+ <var title="">filename</var>.
+
+ <li><p>Set <var title="">entry</var>'s <a href="#concept-formdata-entry-value" title="concept-FormData-entry-value">value</a>
+ to <var>value</var>. 
+
+ <li><p>Append <var title="">entry</var> to <code><a href="#formdata">FormData</a></code> object's list of
+ <a href="#concept-formdata-entry" title="concept-FormData-entry">entries</a>.
+</ol> 
+
+<h2 class="no-num" id="references">References</h2>
+<div id="anolis-references"><dl><dt id="refsCOOKIES">[COOKIES]
+<dd><cite><a href="http://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a></cite>, Adam Barth. IETF.
+
+<dt id="refsCORS">[CORS]
+<dd><cite><a href="http://www.w3.org/TR/cors/">Cross-Origin Resource Sharing</a></cite>, Anne van Kesteren. W3C.
+
+<dt id="refsDOM">[DOM]
+<dd><cite><a href="http://www.w3.org/TR/dom/">DOM</a></cite>, Anne van Kesteren, Aryeh Gregor and Ms2ger. W3C.
+
+<dt id="refsDOMPS">[DOMPS]
+<dd><cite><a href="http://www.w3.org/TR/DOM-Parsing/">DOM Parsing and Serialization</a></cite>, Travis Leithead and Ms2ger. W3C.
+
+<dt id="refsECMASCRIPT">[ECMASCRIPT]
+<dd>(Non-normative) <cite><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">ECMAScript Language Specification</a></cite>. ECMA.
+
+<dt id="refsENCODING">[ENCODING]
+<dd><cite><a href="http://encoding.spec.whatwg.org/">Encoding Standard</a></cite>, Anne van Kesteren. WHATWG.
+
+<dt id="refsFILEAPI">[FILEAPI]
+<dd><cite><a href="http://www.w3.org/TR/FileAPI/">File API</a></cite>, Arun Ranganathan and Jonas Sicking. W3C.
+
+<dt id="refsHTML">[HTML]
+<dd><cite><a href="http://www.w3.org/TR/html5/">HTML</a></cite>, Robin Berjon, Travis Leithead, Erika Doyle Navara et al.. W3C.
+
+<dt id="refsHTTP">[HTTP]
+<dd><cite><a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, Roy Fielding, James Gettys, Jeffrey Mogul et al.. IETF.
+
+<dt id="refsHTTPAUTH">[HTTPAUTH]
+<dd><cite><a href="http://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a></cite>, J. Franks, Phillip Hallam-Baker, J. Hostetler et al.. IETF.
+
+<dt id="refsHTTPVERBSEC">[HTTPVERBSEC]
+<dd><cite><a href="http://www.kb.cert.org/vuls/id/867593">Multiple vendors' web servers enable HTTP TRACE method by default</a></cite>. US-CERT.
+
+<dd><cite><a href="http://www.kb.cert.org/vuls/id/288308">Microsoft Internet Information Server (IIS) vulnerable to cross-site scripting via HTTP TRACK method</a></cite>. US-CERT.
+
+<dd><cite><a href="http://www.kb.cert.org/vuls/id/150227">HTTP proxy default configurations allow arbitrary TCP connections</a></cite>. US-CERT.
+
+<dt id="refsPROGRESSEVENTS">[PROGRESSEVENTS]
+<dd><cite><a href="http://www.w3.org/TR/progress-events/">Progress Events</a></cite>, Anne van Kesteren and Charles McCathieNevile. W3C.
+
+<dt id="refsRFC2119">[RFC2119]
+<dd><cite><a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a></cite>, Scott Bradner. IETF.
+
+<dt id="refsTYPEDARRAY">[TYPEDARRAY]
+<dd><cite><a href="http://www.khronos.org/registry/typedarray/specs/latest/">Typed Array</a></cite>, David Herman and Kenneth Russell. Khronos.
+
+<dt id="refsURL">[URL]
+<dd><cite><a href="http://url.spec.whatwg.org/">URL Standard</a></cite>, Anne van Kesteren. WHATWG.
+
+<dt id="refsWEBIDL">[WEBIDL]
+<dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web IDL</a></cite>, Cameron McCormack. W3C.
+
+<dt id="refsXML">[XML]
+<dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup Language</a></cite>, Tim Bray, Jean Paoli, C. M. Sperberg-McQueen et al.. W3C.
+
+<dt id="refsXMLNS">[XMLNS]
+<dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in XML</a></cite>, Tim Bray, Dave Hollander, Andrew Layman et al.. W3C.
+
+</dl></div>
+
+
+  <h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
+
+  <p>The editor would like to thank
+
+  Addison Phillips,
+  Ahmed Kamel,
+  Alex Hopmann,
+  Alex Vincent,
+  Alexey Proskuryakov,
+  Andrea Marchesini,
+  Asbj&oslash;rn Ulsberg,
+  Boris Zbarsky,
+  Bj&ouml;rn H&ouml;hrmann,
+  Cameron McCormack,
+  Chris Marrin,
+  Christophe Jolif,
+  Charles McCathieNevile,
+  Dan Winship,
+  David Andersson,
+  David Flanagan,
+  David H&aring;s&auml;ther,
+  David Levin,
+  Dean Jackson,
+  Denis Sureau,
+  Dominik R&ouml;ttsches,
+  Doug Schepers,
+  Douglas Livingstone,
+  Elliott Sprehn,
+  Elliotte Harold,
+  Eric Lawrence,
+  Eric Uhrhane,
+  Erik Dahlstr&ouml;m,
+  Geoffrey Sneddon,
+  Gideon Cohn,
+  Glenn Adams,
+  Gorm Haug Eriksen,
+  H&aring;kon Wium Lie,
+  Hallvord R. M. Steen,
+  Henri Sivonen,
+  Huub Schaeks,
+  Ian Davis,
+  Ian Hickson,
+  Ivan Herman,
+  Jarred Nicholls,
+  Jeff Walden,
+  Jens Lindstr&ouml;m,
+  Jim Deegan,
+  Jim Ley,
+  Joe Farro,
+  Jonas Sicking,
+  Julian Reschke,
+  &#x5442;&#x5eb7;&#x8c6a; (Kang-Hao Lu),
+  Karl Dubost,
+  Lachlan Hunt,
+  Maciej Stachowiak,
+  Magnus Kristiansen,
+  Marc Hadley,
+  Marcos Caceres,
+  Mark Baker,
+  Mark Birbeck,
+  Mark Nottingham,
+  Mark S. Miller,
+  Martin Hassman,
+  Mohamed Zergaoui,
+  Ms2ger,
+  Odin H&oslash;rthe Omdal,
+  Olli Pettay,
+  Pawel Glowacki,
+  Peter Michaux,
+  Philip Taylor,
+  Robin Berjon,
+  Rune Halvorsen,
+  Ruud Steltenpool,
+  Sergiu Dumitriu,
+  Sigbj&oslash;rn Finne,
+  Simon Pieters,
+  Stewart Brodie,
+  Sunava Dutta,
+  Thomas Roessler,
+  Tom Magliery,
+  Yehuda Katz, and
+  Zhenbin Xu
+
+  for their contributions to this specification.</p>
+
+  <p>Special thanks to the Microsoft employees who first implemented the
+  <code title="">XMLHttpRequest</code> interface, which was first widely
+  deployed by the Windows Internet Explorer browser.</p>
+
+  <p>Special thanks also to the WHATWG for drafting an initial version of
+  this specification in their Web Applications 1.0 document (now renamed to
+  HTML). <a href="#refsHTML">[HTML]</a></p>
+
+  <p>Special thanks to Anne van Kesteren who has provided nearly all the contents until he stepped down as a W3C editor and is now in succession providing discussions and contents as the editor of the XMLHttpRequest Living Standard in WHATWG which this version of the specification pursues convergence.</p>
+
+  <p>Thanks also to all those who have helped to improve this specification
+  by sending suggestions and corrections. (Please, keep bugging us with your
+  issues!)</p>
+ 
+
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/xhr-1/Overview.src.html	Wed Oct 23 21:47:37 2013 +0900
@@ -0,0 +1,2752 @@
+<!doctype html>
+<html lang="en-US">
+ <head>
+  <meta charset=utf-8>
+  <title>XMLHttpRequest Level 1</title>
+  <style>
+   pre.idl { border:solid thin; background:#eee; color:#000; padding:0.5em }
+   pre.idl :link, pre.idl :visited { color:inherit; background:transparent }
+   pre code { color:inherit; background:transparent }
+   .example { margin-left:1em; padding-left:1em; border-left:double; color:#222; background:#fcfcfc }
+   .note { margin-left:2em; font-weight:bold; font-style:italic; color:#008000 }
+   p.note::before { content:"Note: " }
+   .XXX { padding:.5em; border:solid #f00 }
+   p.XXX::before { content:"Issue: " }
+   dl.switch { padding-left:2em }
+   dl.switch > dt { text-indent:-1.5em }
+   dl.switch > dt:before { content:'\21AA'; padding:0 0.5em 0 0; display:inline-block; width:1em; text-align:right; line-height:0.5em }
+   dl.domintro { color: green; margin: 2em 0 2em 2em; padding: 0.5em 1em; border: none; background: #DDFFDD; }
+   dl.domintro dt, dl.domintro dt * { color: black; text-decoration: none; }
+   dl.domintro dd { margin: 0.5em 0 1em 2em; padding: 0; }
+   dl.domintro dd p { margin: 0.5em 0; }
+   dl.domintro:before { display: table; margin: -1em -0.5em -0.5em auto; width: auto; content: 'This box is non-normative. Implementation requirements are given below this box.'; color: red; border: solid 2px; background: white; padding: 0 0.25em; }
+   em.ct { text-transform:lowercase; font-variant:small-caps; font-style:normal }
+   dfn { font-weight:bold; font-style:normal }
+   code { color:orangered }
+   code :link, code :visited { color:inherit }
+   hr:not(.top) { display:block; background:none; border:none; padding:0; margin:2em 0; height:auto }
+   table { border-collapse:collapse; border-style:hidden hidden none hidden }
+   table thead { border-bottom:solid }
+   table tbody th:first-child { border-left:solid }
+   table td, table th { border-left:solid; border-right:solid; border-bottom:solid thin; vertical-align:top; padding:0.2em }
+  </style>
+  <link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-[STATUS]">
+ </head>
+ <body>
+  <div class="head">
+<!--logo-->
+
+
+   <h1 class="head" id="xmlhttprequest-ls">XMLHttpRequest Level 1</h1>
+
+   <h2 class="no-num no-toc" id="w3c-doctype">[LONGSTATUS] [DATE: 3 August 2002]</h2>
+
+   <dl>
+    <dt>This Version:</dt>
+    <dd class=dontpublish><a href="http://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html">http://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html</a></dd>
+    <dd class=publish><a href="[VERSION]">[VERSION]</a></dd>
+
+    <dt class=dontpublish>Participate:</dt>
+    <dd class=dontpublish>Send feedback to
+    <a href="mailto:[email protected]?subject=%5BXHR%5D%20">[email protected]</a>
+    (<a href="http://lists.w3.org/Archives/Public/public-webapps/">archives</a>) or
+    <a href="https://www.w3.org/Bugs/Public/enter_bug.cgi?product=WebAppsWG&amp;component=XHR">file a bug</a>
+    (<a href="https://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWG&amp;component=XHR&amp;resolution=---">open bugs</a>)
+    <dd class=dontpublish><a href="http://wiki.whatwg.org/wiki/IRC">IRC: #whatwg on Freenode</a>
+
+    <dt class=dontpublish>Version History:
+    <dd class=dontpublish><a href="http://dvcs.w3.org/hg/xhr/shortlog">http://dvcs.w3.org/hg/xhr/xhr-1/shortlog</a>
+
+    <dt class=publish>Latest Version:</dt>
+    <dd class=publish><a href="[LATEST]">[LATEST]</a></dd>
+
+    <dt class=publish>Latest Editor Draft:</dt>
+    <dd class=publish><a href="http://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html">http://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html</a></dd>
+
+    <dt>Previous Versions:</dt>
+    <dd><a href="http://www.w3.org/TR/2012/WD-XMLHttpRequest-20121206/">http://www.w3.org/TR/2012/WD-XMLHttpRequest-20121206/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2012/WD-XMLHttpRequest-20120117/">http://www.w3.org/TR/2012/WD-XMLHttpRequest-20120117/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2011/WD-XMLHttpRequest2-20110816/">http://www.w3.org/TR/2011/WD-XMLHttpRequest2-20110816/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2010/WD-XMLHttpRequest2-20100907/">http://www.w3.org/TR/2010/WD-XMLHttpRequest2-20100907/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2009/WD-XMLHttpRequest2-20090820/">http://www.w3.org/TR/2009/WD-XMLHttpRequest2-20090820/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080930/">http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080930/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080225/">http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080225/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2007/WD-XMLHttpRequest-20071026/">http://www.w3.org/TR/2007/WD-XMLHttpRequest-20071026/</a>
+    <dd><a href="http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070618/">http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070618/</a>
+    <dd><a href="http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070227/">http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070227/</a>
+    <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060927/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060927/</a>
+    <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060619/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060619/</a>
+    <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/</a>
+
+    <dt>Editor:</dt>
+    <dd><a href="http://jaubourg.net/">Julian Aubourg</a>
+     (<a href="http://www.creative-area.net/">Creative Area</a>)
+     &lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</dd>
+    <dd><a href="mailto:[email protected]">송정기(Jungkee Song)</a>
+     (<a href="http://www.samsung.com/sec/">Samsung Electronics Co., Ltd.</a>)
+     &lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</dd>
+    <dd><a href="http://www.hallvord.com/">Hallvord R. M. Steen</a>
+     (<a href="http://www.mozilla.org/">Mozilla</a>)
+     &lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</dd>
+
+    <dt>Previous Editor:</dt>
+    <dd><a href="http://annevankesteren.nl/">Anne van Kesteren</a>
+     (<a href="http://www.mozilla.org/">Mozilla</a>)
+     &lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</dd>
+   </dl>
+  </div>
+
+<div class=w3conly><!--copyright--></div>
+
+  
+
+  <hr class="top">
+
+
+<div class=dontpublish><!-- ED version -->
+  <h2 class="no-num no-toc" id="specabstract">Abstract</h2>
+
+  <p>The XMLHttpRequest specification defines an API that provides scripted
+  client functionality for transferring data between a client and a server.
+
+  <h2 class="no-num no-toc" id="sotd">Status of this Document</h2>
+
+  <p><em>This section describes the status of this document at the time of its
+  publication. Other documents may supersede this document. A list of current
+  W3C publications and the latest revision of this technical report can be
+  found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>
+  at http://www.w3.org/TR/.</em></p>
+
+  <p>If you wish to make comments regarding this document in a manner
+  that is tracked by the W3C, please submit them via using <a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=WebAppsWG">our public bug database</a>, or please send comments to
+  <a href="mailto:[email protected]?subject=%5BXHR%5D%20">[email protected]</a>
+  (<a href="http://lists.w3.org/Archives/Public/public-webapps/">archived</a>)
+  with <samp>[XHR]</samp> at the start of the subject line.</p>
+
+  <p>The bulk of the text of this specification is also
+   available in the WHATWG <a href="http://xhr.spec.whatwg.org/">XMLHttpRequest Living Standard</a>, under a license that permits reuse of the specification text.</p>
+
+  <p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications Working
+  Group</a> is the W3C working group responsible for this specification's progress along the W3C Recommendation track. This specification is the [DATE: 8 October 2012] Editor's Draft.</p>
+  
+  <p>Publication as an Editor's Draft does not imply endorsement by the W3C
+  Membership. This is a draft document and may be updated, replaced or
+  obsoleted by other documents at any time. It is inappropriate to cite this
+  document as other than work in progress.</p>
+
+  <p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C Web Applications working group actively pursues convergence of XMLHttpRequest specification with the WHATWG.</p>
+
+  <p>This document was produced by a group operating under the
+  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004
+  W3C Patent Policy</a>. W3C maintains a
+  <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/42538/status">public
+  list of any patent disclosures</a> made in connection with the deliverables of
+  the group; that page also includes instructions for disclosing a patent. An
+  individual who has actual knowledge of a patent which the individual believes
+  contains
+  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
+  Claim(s)</a> must disclose the information in accordance with
+  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+  6 of the W3C Patent Policy</a>.</p>
+
+</div>
+
+<div class=publish><!-- publication version -->
+  <h2 class="no-num no-toc" id="specabstract">Abstract</h2>
+
+  <p>The XMLHttpRequest specification defines an API that provides scripted
+  client functionality for transferring data between a client and a server.
+
+  <h2 class="no-num no-toc" id="sotd">Status of this Document</h2>
+
+  <p><em>This section describes the status of this document at the time of its
+  publication. Other documents may supersede this document. A list of current
+  W3C publications and the latest revision of this technical report can be
+  found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>
+  at http://www.w3.org/TR/.</em></p>
+
+  <p>If you wish to make comments regarding this document in a manner
+  that is tracked by the W3C, please submit them via using <a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=WebAppsWG">our public bug database</a>, or please send comments to
+  <a href="mailto:[email protected]?subject=%5BXHR%5D%20">[email protected]</a>
+  (<a href="http://lists.w3.org/Archives/Public/public-webapps/">archived</a>)
+  with <samp>[XHR]</samp> at the start of the subject line.</p>
+
+  <p>The bulk of the text of this specification is also
+   available in the WHATWG <a href="http://xhr.spec.whatwg.org/">XMLHttpRequest Living Standard</a>, under a license that permits reuse of the specification text.</p>
+
+  <p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications Working
+  Group</a> is the W3C working group responsible for this specification's progress along the W3C Recommendation track. This specification is the [DATE: 8 October 2012] Working Draft.</p>
+  
+  <p>Publication as a Working Draft does not imply endorsement by the W3C
+  Membership. This is a draft document and may be updated, replaced or
+  obsoleted by other documents at any time. It is inappropriate to cite this
+  document as other than work in progress.</p>
+
+  <p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C Web Applications working group actively pursues convergence of XMLHttpRequest specification with the WHATWG.</p>
+
+  <p>This document was produced by a group operating under the
+  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004
+  W3C Patent Policy</a>. W3C maintains a
+  <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/42538/status">public
+  list of any patent disclosures</a> made in connection with the deliverables of
+  the group; that page also includes instructions for disclosing a patent. An
+  individual who has actual knowledge of a patent which the individual believes
+  contains
+  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
+  Claim(s)</a> must disclose the information in accordance with
+  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+  6 of the W3C Patent Policy</a>.</p>
+
+</div>
+
+
+  <h2 class="no-num no-toc" id="toc">Table of Contents</h2>
+
+  <!--toc-->
+
+
+
+  <h2 class="no-test" id="introduction">Introduction</h2>
+
+  <p><em>This section is non-normative.</em></p>
+
+  <p>The <code>XMLHttpRequest</code> object is the ECMAScript HTTP API.
+  <span data-anolis-ref class=informative>ECMASCRIPT</span>
+  <!-- XXX elaborate on options -->
+
+  <p>The name of the object is <code>XMLHttpRequest</code> for compatibility
+  with the Web, though each component of this name is potentially
+  misleading. First, the object supports any text based format, including
+  XML. Second, it can be used to make requests over both HTTP and HTTPS
+  (some implementations support protocols in addition to HTTP and HTTPS, but
+  that functionality is not covered by this specification). Finally, it
+  supports "requests" in a broad sense of the term as it pertains to HTTP;
+  namely all activity involved with HTTP requests or responses for the
+  defined HTTP methods.</p>
+  <!-- XXX need to improve point 2 -->
+
+  <div class="example">
+   <p>Some simple code to do something with data from an XML document
+   fetched over the network:</p>
+
+   <pre><code>function processData(data) {
+  // taking care of data
+}
+
+function handler() {
+  if(this.readyState == this.DONE) {
+    if(this.status == 200 &amp;&amp;
+       this.responseXML != null &amp;&amp;
+       this.responseXML.getElementById('test').textContent) {
+      // success!
+      processData(this.responseXML.getElementById('test').textContent);
+      return;
+    }
+    // something went wrong
+    processData(null);
+  }
+}
+
+var client = new XMLHttpRequest();
+client.onreadystatechange = handler;
+client.open("GET", "unicorn.xml");
+client.send();</code></pre>
+
+   <p>If you just want to log a message to the server:</p>
+
+   <pre><code>function log(message) {
+  var client = new XMLHttpRequest();
+  client.open("POST", "/log");
+  client.setRequestHeader("Content-Type", "text/plain;charset=UTF-8");
+  client.send(message);
+}</code></pre>
+
+   <p>Or if you want to check the status of a document on the server:</p>
+
+   <pre><code>function fetchStatus(address) {
+  var client = new XMLHttpRequest();
+  client.onreadystatechange = function() {
+    // in case of network errors this might not give reliable results
+    if(this.readyState == this.DONE)
+      returnStatus(this.status);
+  }
+  client.open("HEAD", address);
+  client.send();
+}</code></pre>
+  </div>
+
+
+<h3 class="no-test">Specification history</h3>
+
+<p>The <code>XMLHttpRequest</code> object was initially defined as part of
+the WHATWG's HTML effort. (Long after Microsoft shipped an implementation.)
+It moved to the W3C in 2006. Extensions (e.g. progress events and
+cross-origin requests) to <code>XMLHttpRequest</code> were developed in a
+separate draft (XMLHttpRequest Level 2) until end of 2011, at which point
+the two drafts were merged and <code>XMLHttpRequest</code> became a single
+entity again from a standards perspective.
+
+<p>Historical discussion can be found in the following mailing list
+archives:
+
+<ul>
+ <li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/">[email protected]</a>
+ <li><a href="http://lists.w3.org/Archives/Public/public-webapi/">[email protected]</a>
+ <li><a href="http://lists.w3.org/Archives/Public/public-appformats/">[email protected]</a>
+ <li><a href="http://lists.w3.org/Archives/Public/public-webapps/">[email protected]</a>
+</ul>
+
+
+
+<h2 class="no-test" id="conformance">Conformance</h2>
+
+<p>All diagrams, examples, and notes in this specification are
+non-normative, as are all sections explicitly marked non-normative.
+Everything else in this specification is normative.
+
+<p>The key words "MUST", "MUST NOT", "REQUIRED", <!--"SHALL", "SHALL
+NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
+"OPTIONAL" in the normative parts of this specification are to be
+interpreted as described in RFC2119. For readability, these words do
+not appear in all uppercase letters in this specification.
+<span data-anolis-ref>RFC2119</span>
+
+
+  <h3 class="no-test" id="dependencies">Dependencies</h3>
+
+  <p>This specification relies on several underlying specifications.</p>
+
+  <dl>
+   <dt>Cross-Origin Resource Sharing</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support the algorithms of the Cross-Origin Resource Sharing
+   specification. <span data-anolis-ref>CORS</span></p></dd>
+
+   <dt>DOM4</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support at least the subset of the functionality defined in DOM4 that
+   this specification relies upon, such as various exceptions and
+   <code data-anolis-spec=dom>EventTarget</code>. <span data-anolis-ref>DOM</span></p></dd>
+
+   <dt>DOM Parsing and Serialization
+   <dd><p>A <span>conforming user agent</span> must support at least the
+   <span data-anolis-spec=domps title=concept-serialize>serialize</span>
+   concept from DOM Parsing and Serialization.
+   <span data-anolis-ref>DOMPS</span>
+
+   <dt>Encoding Standard
+   <dd><p>A <span>conforming user agent</span> must 
+   support at least the subset of the functionality defined in Encoding Standard that
+   this specification relies upon, such as the <code data-anolis-spec=encoding title=utf-8>utf-8</code> <code data-anolis-spec=encoding title=encoding>encoding</code>.
+   <span data-anolis-ref>ENCODING</span>
+
+   <dt>File API</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support at least the subset of the functionality defined in File API that
+   this specification relies upon, such as the <code data-anolis-spec=fileapi>Blob</code> and
+   <code data-anolis-spec=fileapi>File</code> interfaces. <span data-anolis-ref>FILEAPI</span></p>
+
+   <dt>HTML</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support at least the subset of the functionality defined in HTML that
+   this specification relies upon, such as the basics of the
+   <code data-anolis-spec=html>Window</code> object and serializing a <code data-anolis-spec=dom>Document</code>
+   object. <span data-anolis-ref>HTML</span>
+
+   <dt>HTTP</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support some version of the HTTP protocol. Requirements regarding HTTP
+   are made throughout the specification. <span data-anolis-ref>HTTP</span>
+
+   <dt>Progress Events</dt>
+   <dd><p>A <span>conforming user agent</span> must support the
+   Progress Events specification.
+   <span data-anolis-ref>PROGRESSEVENTS</span>
+
+   <dt>Typed Array</dt>
+   <dd><p>A <span>conforming user agent</span> must support the
+   <code data-anolis-spec=typedarray>ArrayBuffer</code> and
+   <code data-anolis-spec=typedarray>ArrayBufferView</code> objects.
+   <span data-anolis-ref>TYPEDARRAY</span>
+
+   <dt>URL</dt>
+   <dd><p>A <span>conforming user agent</span> must
+   support the URL parsing algorithm of the URL
+   specification. <span data-anolis-ref>URL</span></p></dd>
+
+   <dt>Web IDL</dt>
+   <dd><p>A <span>conforming user agent</span> must also
+   be a conforming implementation of the IDL fragments in this
+   specification, as described in the Web IDL specification.
+   <span data-anolis-ref>WEBIDL</span>
+
+   <dt>XML</dt>
+   <dd><p>A <span>conforming user agent</span> must be a
+   conforming XML processor that reports violations of namespace
+   well-formedness. <span data-anolis-ref>XML</span>
+   <span data-anolis-ref>XMLNS</span>
+  </dl>
+
+
+  <h3 class="no-test" id="extensibility">Extensibility</h3>
+
+  <p>User agents, Working Groups, and other interested parties are
+  <em>strongly encouraged</em> to discuss new features on a relevant public
+  forum, preferably
+  <a href="mailto:[email protected]">[email protected]</a>. If this
+  is for some reason not possible prefix the extension in some way. E.g. if
+  company Foo wants to add a proprietary method <code>bar()</code> it could
+  be named <code>fooBar()</code> to prevent clashes with a potential
+  non-proprietary method <code>bar()</code>.</p>
+
+
+
+  <h2 class="no-test" id="terminology">Terminology</h2>
+
+
+  <p>The term <dfn>user credentials</dfn> for the purposes of this
+  specification means cookies, HTTP authentication, and client-side SSL
+  certificates. Specifically it does not refer to proxy authentication or
+  the <code title="http-origin">Origin</code> header.
+  <span data-anolis-ref>COOKIES</span> <!-- XXX ref? --></p>
+
+
+  <h2>Interface <code title>XMLHttpRequest</code></h2>
+
+  <pre class="idl">[NoInterfaceObject]
+interface <dfn id="xmlhttprequesteventtarget">XMLHttpRequestEventTarget</dfn> : <span data-anolis-spec=dom>EventTarget</span> {
+  // <a href="#event-handlers">event handlers</a>
+  attribute <span data-anolis-spec=html>EventHandler</span> <span title="handler-xhr-onloadstart">onloadstart</span>;
+  attribute <span data-anolis-spec=html>EventHandler</span> <span title="handler-xhr-onprogress">onprogress</span>;
+  attribute <span data-anolis-spec=html>EventHandler</span> <span title="handler-xhr-onabort">onabort</span>;
+  attribute <span data-anolis-spec=html>EventHandler</span> <span title="handler-xhr-onerror">onerror</span>;
+  attribute <span data-anolis-spec=html>EventHandler</span> <span title="handler-xhr-onload">onload</span>;
+  attribute <span data-anolis-spec=html>EventHandler</span> <span title="handler-xhr-ontimeout">ontimeout</span>;
+  attribute <span data-anolis-spec=html>EventHandler</span> <span title="handler-xhr-onloadend">onloadend</span>;
+};
+
+interface <dfn id="xmlhttprequestupload">XMLHttpRequestUpload</dfn> : <span>XMLHttpRequestEventTarget</span> {
+
+};
+
+enum <dfn>XMLHttpRequestResponseType</dfn> {
+  "",
+  "arraybuffer",
+  "blob",
+  "document",
+  "text"
+};
+
+dictionary <dfn>XMLHttpRequestOptions</dfn> {
+  boolean anonymous = false;
+};
+
+[<span title="dom-XMLHttpRequest">Constructor</span>(optional <span>XMLHttpRequestOptions</span> <var title>options</var>)]
+interface <dfn id="xmlhttprequest">XMLHttpRequest</dfn> : <span>XMLHttpRequestEventTarget</span> {
+  // <a href="#event-handlers">event handler</a>
+  attribute <span data-anolis-spec=html>EventHandler</span> <span title="handler-xhr-onreadystatechange">onreadystatechange</span>;
+
+  // <a href="#states">states</a>
+  const unsigned short <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> = 0;
+  const unsigned short <span title="dom-XMLHttpRequest-OPENED">OPENED</span> = 1;
+  const unsigned short <span title="dom-XMLHttpRequest-HEADERS_RECEIVED">HEADERS_RECEIVED</span> = 2;
+  const unsigned short <span title="dom-XMLHttpRequest-LOADING">LOADING</span> = 3;
+  const unsigned short <span title="dom-XMLHttpRequest-DONE">DONE</span> = 4;
+  readonly attribute unsigned short <span title="dom-XMLHttpRequest-readyState">readyState</span>;
+
+  // <a href="#request">request</a>
+  void <span title="dom-XMLHttpRequest-open">open</span>(ByteString <var>method</var>, [EnsureUTF16] DOMString <var title>url</var>, optional boolean <var>async</var> = true, optional [EnsureUTF16] DOMString? <var>username</var> = null, optional [EnsureUTF16] DOMString? <var>password</var> = null);
+  void <span title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader</span>(ByteString <var>header</var>, ByteString <var>value</var>);
+           attribute unsigned long <span title="dom-XMLHttpRequest-timeout">timeout</span>;
+           attribute boolean <span title="dom-XMLHttpRequest-withCredentials">withCredentials</span>;
+  readonly attribute <span>XMLHttpRequestUpload</span> <span title="dom-XMLHttpRequest-upload">upload</span>;
+  void <span title="dom-XMLHttpRequest-send">send</span>(optional (<span data-anolis-spec=typedarray>ArrayBufferView</span> or <span data-anolis-spec=fileapi>Blob</span> or <span data-anolis-spec=dom>Document</span> or [EnsureUTF16] DOMString or <span>FormData</span>)? <var>data</var> = null);
+  void <span title="dom-XMLHttpRequest-abort">abort</span>();
+
+  // <a href="#response">response</a>
+  readonly attribute unsigned short <span title="dom-XMLHttpRequest-status">status</span>;
+  readonly attribute ByteString <span title="dom-XMLHttpRequest-statusText">statusText</span>;
+  ByteString? <span title="dom-XMLHttpRequest-getResponseHeader">getResponseHeader</span>(ByteString <var>header</var>);
+  ByteString <span title="dom-XMLHttpRequest-getAllResponseHeaders">getAllResponseHeaders</span>();
+  void <span title="dom-XMLHttpRequest-overrideMimeType">overrideMimeType</span>(DOMString <var>mime</var>);
+           attribute <span>XMLHttpRequestResponseType</span> <span title="dom-XMLHttpRequest-responseType">responseType</span>;
+  readonly attribute any <span title="dom-XMLHttpRequest-response">response</span>;
+  readonly attribute DOMString <span title="dom-XMLHttpRequest-responseText">responseText</span>;
+  readonly attribute <span data-anolis-spec=dom>Document</span>? <span title="dom-XMLHttpRequest-responseXML">responseXML</span>;
+};</pre>
+
+<p>Each <code>XMLHttpRequest</code> object has a unique, associated
+<code>XMLHttpRequestUpload</code> object.
+
+<p>If the <span data-anolis-spec=html>JavaScript global environment</span> is a
+<span data-anolis-spec=html>worker environment</span>, implementations must act as if
+<code title>Document</code> and <code title>Document?</code> in the above IDL were not
+exposed. I.e. <code title=dom-XMLHttpRequest-send>send()</code> is not overloaded with it
+and <code title=dom-XMLHttpRequest-responseXML>responseXML</code> always returns null (as
+required by its definition, too).
+
+
+<h3>Task sources</h3>
+
+<p>Each <code>XMLHttpRequest</code> object has its own
+<span data-anolis-spec=html>task source</span>. Namely, the
+<dfn><code>XMLHttpRequest</code> task source</dfn>.
+
+
+  <h3 id="constructors">Constructors</h3>
+
+  <p>The <code>XMLHttpRequest</code> object has an associated
+  <dfn>anonymous flag</dfn>. If the <span>anonymous flag</span> is set,
+  <span>user credentials</span> and the
+  <span>source origin</span> are not exposed when
+  <span data-anolis-spec=html title=fetch>fetching</span> resources.
+
+  <p>When the <span data-anolis-spec=html>JavaScript global environment</span>
+  is a <span data-anolis-spec=html>document environment</span>, the
+  <code>XMLHttpRequest</code> object has an associated
+  <dfn title=concept-XMLHttpRequest-document>document</dfn>.
+
+  <dl class=domintro>
+    <dt><code><var title>client</var> = new <span title=dom-XMLHttpRequest>XMLHttpRequest</span>()</code>
+    <dd>Returns a new <code>XMLHttpRequest</code> object.
+
+    <dt><code><var title>client</var> = new <span title=dom-XMLHttpRequest>XMLHttpRequest</span>({anonymous:true})</code>
+    <dd>Returns a new <code>XMLHttpRequest</code> object that has its
+    <span>anonymous flag</span> set.
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest"><code>XMLHttpRequest(<var title>options</var>)</code></dfn>
+  constructor must run these steps:
+
+  <ol>
+    <li><p>Let <var title>xhr</var> be a new <code>XMLHttpRequest</code>
+    object.
+
+    <li><p>If <var title>options</var>'s <code title>anonymous</code> member is
+    true, set <var title>xhr</var>'s <span>anonymous flag</span>.
+
+    <li><p>If the
+    <span data-anolis-spec=html>JavaScript global environment</span> is a
+    <span data-anolis-spec=html>document environment</span>, set <var title>xhr</var>'s
+    <span title=concept-XMLHttpRequest-document>document</span> to the
+    <span data-anolis-spec=dom title=concept-document>document</span>
+    associated with the global object of <var title>xhr</var>'s interface
+    object.
+
+    <li><p>Return <var title>xhr</var>.
+  </ol>
+
+
+<h3>Garbage collection</h3>
+
+<!-- Based on EventSource and WebSocket. Not sure what I am doing. -->
+
+<p>An <code>XMLHttpRequest</code> object must not be garbage collected if
+its state is <span title=dom-XMLHttpRequest-OPENED>OPENED</span> and the
+<span><code>send()</code> flag</span> is set, its state is
+<span title=dom-XMLHttpRequest-HEADERS_RECEIVED>HEADERS_RECEIVED</span>, or
+its state is <span title=dom-XMLHttpRequest-LOADING>LOADING</span>, and
+one of the following is true:
+
+<ul>
+ <li><p>It has one or more
+ <span data-anolis-spec=dom title=concept-event-listener>event listeners</span>
+ registered whose <b>type</b> is
+ <code title=event-xhr-readystatechange>readystatechange</code>,
+ <code title=event-xhr-progress>progress</code>,
+ <code title=event-xhr-abort>abort</code>,
+ <code title=event-xhr-error>error</code>,
+ <code title=event-xhr-load>load</code>,
+ <code title=event-xhr-timeout>timeout</code>, or
+ <code title=event-xhr-loadend>loadend</code>.
+ <li><p>The <span>upload complete flag</span> is unset and the associated
+ <code>XMLHttpRequestUpload</code> object has one or more
+ <span data-anolis-spec=dom title=concept-event-listener>event listeners</span>
+ registered whose <b>type</b> is
+ <code title=event-xhr-progress>progress</code>,
+ <code title=event-xhr-abort>abort</code>,
+ <code title=event-xhr-error>error</code>,
+ <code title=event-xhr-load>load</code>,
+ <code title=event-xhr-timeout>timeout</code>, or
+ <code title=event-xhr-loadend>loadend</code>.
+</ul>
+
+<p>If an <code>XMLHttpRequest</code> object is garbage collected while its
+connection is still open, the user agent must <span>terminate the request</span>.</p>
+
+
+
+  <h3 id="event-handlers">Event handlers</h3>
+
+
+  <p>The following are the
+  <span data-anolis-spec=html>event handlers</span> (and their corresponding
+  <span data-anolis-spec=html title="event handler event type">event handler event types</span>)
+  that must be supported on objects implementing an interface that inherits
+  from <code>XMLHttpRequestEventTarget</code> as attributes:</p>
+
+  <table>
+   <thead>
+    <tr>
+     <th><span data-anolis-spec=html title="event handlers">event handler</span>
+     <th><span data-anolis-spec=html>event handler event type</span>
+   <tbody>
+    <tr>
+     <td><dfn title="handler-xhr-onloadstart"><code>onloadstart</code></dfn>
+     <td><code title="event-xhr-loadstart">loadstart</code>
+    <tr>
+     <td><dfn title="handler-xhr-onprogress"><code>onprogress</code></dfn>
+     <td><code title="event-xhr-progress">progress</code>
+    <tr>
+     <td><dfn title="handler-xhr-onabort"><code>onabort</code></dfn>
+     <td><code title="event-xhr-abort">abort</code>
+    <tr>
+     <td><dfn title="handler-xhr-onerror"><code>onerror</code></dfn>
+     <td><code title="event-xhr-error">error</code>
+    <tr>
+     <td><dfn title="handler-xhr-onload"><code>onload</code></dfn>
+     <td><code title="event-xhr-load">load</code>
+    <tr>
+     <td><dfn title="handler-xhr-ontimeout"><code>ontimeout</code></dfn>
+     <td><code title="event-xhr-timeout">timeout</code>
+    <tr>
+     <td><dfn title="handler-xhr-onloadend"><code>onloadend</code></dfn>
+     <td><code title="event-xhr-loadend">loadend</code>
+  </table>
+
+
+  <p>The following is the
+  <span data-anolis-spec=html title="event handlers">event handler</span>
+  (and its corresponding
+  <span data-anolis-spec=html>event handler event type</span>) that must be
+  supported as attribute solely by the
+  <code>XMLHttpRequest</code> object:</p>
+
+  <table>
+   <thead>
+    <tr>
+     <th><span data-anolis-spec=html title="event handlers">event handler</span>
+     <th><span data-anolis-spec=html>event handler event type</span>
+   <tbody>
+    <tr>
+     <td><dfn title="handler-xhr-onreadystatechange"><code>onreadystatechange</code></dfn>
+     <td><code title="event-xhr-readystatechange">readystatechange</code></td>
+  </table>
+
+
+  <h3 id="states">States</h3>
+
+  <dl class=domintro>
+    <dt><code><var title>client</var> . <span title="dom-XMLHttpRequest-readyState">readyState</span></code>
+    <dd><p>Returns the current state.
+  </dl>
+
+  <p>The <code>XMLHttpRequest</code> object can be in several states. The
+  <dfn title="dom-XMLHttpRequest-readyState"><code>readyState</code></dfn>
+  attribute must return the current state, which must be one of the
+  following values:</p>
+
+  <dl>
+   <dt><dfn title="dom-XMLHttpRequest-UNSENT"><code>UNSENT</code></dfn>
+   (numeric value 0)</dt>
+   <dd><p>The object has been constructed.</p></dd>
+
+   <dt><dfn title="dom-XMLHttpRequest-OPENED"><code>OPENED</code></dfn>
+   (numeric value 1)</dt>
+   <dd><p>The <code title="dom-XMLHttpRequest-open">open()</code> method has been successfully invoked.
+   During this state request headers can be set using
+   <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>
+   and the request can be made using the
+   <code title="dom-XMLHttpRequest-send">send()</code> method.</p></dd>
+
+   <dt><dfn title="dom-XMLHttpRequest-HEADERS_RECEIVED"><code>HEADERS_RECEIVED</code></dfn>
+   (numeric value 2)</dt>
+   <dd><p>All redirects (if any) have been followed and all HTTP headers of
+   the final response have been received. Several response members of the
+   object are now available.</p></dd>
+
+   <dt><dfn title="dom-XMLHttpRequest-LOADING"><code>LOADING</code></dfn>
+   (numeric value 3)</dt>
+   <dd><p>The <span>response entity body</span> is being received.</p></dd>
+
+   <dt><dfn title="dom-XMLHttpRequest-DONE"><code>DONE</code></dfn>
+   (numeric value 4)</dt>
+   <dd><p>The data transfer has been completed or something went wrong
+   during the transfer (e.g. infinite redirects).</p></dd>
+  </dl>
+
+  <p>The <dfn id="send-flag"><code>send()</code> flag</dfn> indicates
+  that the <code title="dom-XMLHttpRequest-send">send()</code> method has
+  been invoked. It is initially unset and is used during the
+  <span title="dom-XMLHttpRequest-OPENED">OPENED</span> state.
+
+  <p>The <dfn id="error-flag">error flag</dfn> indicates some type of
+  network error or fetch termination. It is initially unset.
+
+<h3 id="request">Request</h3>
+
+<p>Each <code>XMLHttpRequest</code> object has the following
+request-associated concepts:
+
+<dfn>request method</dfn>,
+<dfn>request URL</dfn>,
+<dfn id="author-request-headers">author request headers</dfn>,
+<dfn>request entity body</dfn>,
+<dfn>source origin</dfn>,
+<dfn>referrer source</dfn>,
+<dfn>synchronous flag</dfn>,
+<dfn id="upload-complete-flag">upload complete flag</dfn>, and
+<dfn id="upload-events-flag">upload events flag</dfn>.
+
+<p>The <span>author request headers</span> is a list of HTTP header names
+and corresponding header values. Comparisons against the HTTP header names
+must be done in a case-insensitive manner. Initially it must be empty.
+
+<p>The <span>request entity body</span> must initially be null.
+
+<p>The <span>synchronous flag</span>,
+<span>upload complete flag</span>, and
+<span>upload events flag</span> must be initially unset.
+
+<hr>
+
+<p>To <dfn>terminate the request</dfn> run these steps:
+
+<ol>
+ <li><p>Set the <span>error flag</span>.
+
+ <li><p>Cancel any instance of the <span data-anolis-spec=html>fetch</span> algorithm
+ opened by this object.
+
+ <li><p>If there are any <span data-anolis-spec=html title=concept-task>tasks</span> from
+ the object's <span><code>XMLHttpRequest</code> task source</span> in one of the
+ <span data-anolis-spec=html title="task queue">task queues</span>, then remove them.
+</ol>
+
+
+  <h4>The <code title>open()</code> method</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-open>open</span>(<var title>method</var>, <var title>url</var> [, <var title>async</var> = true [, <var title>username</var> = null [, <var title>password</var> = null]]])</code>
+
+   <dd>
+    <p>Sets the <span>request method</span>, <span>request URL</span>, and
+    <span>synchronous flag</span>.</p>
+
+    <p>Throws a JavaScript <code data-anolis-spec=webidl>TypeError</code> if
+    either <var title>method</var> is not a valid HTTP method or
+    <var title>url</var> cannot be parsed.
+
+    <p>Throws a "<code data-anolis-spec=dom>SecurityError</code>" exception
+    if <var title>method</var> is a case-insensitive match for
+    <code>CONNECT</code>, <code>TRACE</code> or <code>TRACK</code>.</p>
+
+    <p>Throws an "<code data-anolis-spec=dom>InvalidAccessError</code>"
+    exception if <var title>async</var> is false, the
+    <span data-anolis-spec=html>JavaScript global environment</span> is a
+    <span data-anolis-spec=html>document environment</span>, and either the
+    <span>anonymous flag</span> is set, the
+    <code title=dom-XMLHttpRequest-timeout>timeout</code> attribute is not
+    zero, the
+    <code title=dom-XMLHttpRequest-withCredentials>withCredentials</code>
+    attribute is true, or the
+    <code title=dom-XMLHttpRequest-responseType>responseType</code>
+    attribute is not the empty string.
+  </dl>
+
+<p>The 
+<dfn id="dom-xmlhttprequest-open" title="dom-XMLHttpRequest-open"><code>open(<var title>method</var>, <var title>url</var>, <var title>async</var>, <var title>username</var>, <var title>password</var>)</code></dfn>
+method must run these steps:
+
+<ol>
+ <li><p>Let <var title>base</var> be null.
+
+ <li>
+  <p>If the <span data-anolis-spec=html>JavaScript global environment</span> is a
+  <span data-anolis-spec=html>document environment</span>, run these steps:
+
+  <ol>
+   <li><p>If <span title=concept-XMLHttpRequest-document>document</span> is not 
+   <span data-anolis-spec=html>fully active</span>, 
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an 
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.
+
+   <li><p>Set <var title>base</var> to the 
+   <span data-anolis-spec=html>document base URL</span> of
+   <span title=concept-XMLHttpRequest-document>document</span>.
+
+   <li><p>Set <span>source origin</span> to a globally unique identifier if the 
+   <span>anonymous flag</span> is set, and the <span data-anolis-spec=html>origin</span> 
+   of <span title=concept-XMLHttpRequest-document>document</span> otherwise.
+
+   <li><p>Set <span>referrer source</span> to 
+   <span title=concept-XMLHttpRequest-document>document</span>.
+  </ol>
+
+ <li>
+  <p>If the <span data-anolis-spec=html>JavaScript global environment</span> is a
+  <span data-anolis-spec=html>worker environment</span>, run these steps:
+
+  <ol>
+   <li><p>Set <var title>base</var> to the 
+   <span data-anolis-spec=html>script's base URL</span>.
+
+   <li><p>Set <span>source origin</span> to the 
+   <span data-anolis-spec=html title=concept-script>script</span>'s
+   <span data-anolis-spec=html>origin</span>.
+
+   <li><p>Set <span>referrer source</span> to the 
+   <span data-anolis-spec=html>script's referrer source</span>.
+  </ol>
+
+ <li><p>If <var>method</var> does not match the <span data-anolis-spec=http>Method</span> 
+ token production, <span data-anolis-spec=dom title=concept-throw>throw</span> a JavaScript <code data-anolis-spec=webidl>TypeError</code>.
+
+ <li>
+  <p>If <var>method</var> is a case-insensitive match for <code>CONNECT</code>, 
+  <code>DELETE</code>, <code>GET</code>, <code>HEAD</code>, <code>OPTIONS</code>, 
+  <code>POST</code>, <code>PUT</code>, <code>TRACE</code>, or <code>TRACK</code>, subtract 
+  0x20 from each byte in the range 0x61 (ASCII a) to 0x7A (ASCII z).
+ 
+  <p class=note>If it does not match any of the above, it is passed 
+  through <em>literally</em>, including in the final request.
+  <!-- WebKit (and supposedly Gecko) also uppercase: COPY, INDEX, LOCK, 
+  M-POST, MKCOL, MOVE, PROPFIND, PROPPATCH, and UNLOCK. -->
+
+ <li>
+  <p>If <var>method</var> is a case-sensitive match for <code>CONNECT</code>, 
+  <code>TRACE</code>, or <code>TRACK</code>, 
+  <span data-anolis-spec=dom title=concept-throw>throw</span> a 
+  "<code data-anolis-spec=dom>SecurityError</code>" exception.
+
+  <p class=note>Allowing these methods would pose a security risk. 
+  <span data-anolis-ref>HTTPVERBSEC</span>
+
+ <li><p>Let <var title>parsed URL</var> be the result of 
+ <span data-anolis-spec=url title=concept-url-parser>parsing</span> <var title>url</var> 
+ with <var title>base</var>.
+
+ <li><p>If <var title>parsed URL</var> is failure, 
+ <span data-anolis-spec=dom title=concept-throw>throw</span> a JavaScript <code data-anolis-spec=webidl>TypeError</code>.
+
+ <li>
+  <p>If <var title>parsed URL</var>'s <span data-anolis-spec=url>relative flag</span> is 
+  set, run these substeps:
+
+  <ol>
+   <li><p>If the <var title>username</var> argument is not null, set 
+   <var title>parsed URL</var>'s 
+   <span data-anolis-spec=url title=concept-url-username>username</span> to 
+   <var>username</var>.
+
+   <li><p>If the <var title>password</var> argument is not null, set 
+   <var title>parsed URL</var>'s 
+   <span data-anolis-spec=url title=concept-url-password>password</span> to
+   <var>password</var>.
+  </ol>
+
+ <li><p>If <var>async</var> is false, the
+ <span data-anolis-spec=html>JavaScript global environment</span> is a
+ <span data-anolis-spec=html>document environment</span>, and either the
+ <span>anonymous flag</span> is set, the
+ <code title=dom-XMLHttpRequest-timeout>timeout</code> attribute value is not zero, the
+ <code title=dom-XMLHttpRequest-withCredentials>withCredentials</code> attribute value is 
+ true, or the <code title=dom-XMLHttpRequest-responseType>responseType</code> attribute 
+ value is not the empty string, 
+ <span data-anolis-spec=dom title=concept-throw>throw</span> an
+ "<code data-anolis-spec=dom>InvalidAccessError</code>" exception.
+
+ <li>
+  <p><span>Terminate the request</span>.
+
+  <p class=note>After all, a request can be ongoing at this point. 
+
+ <li>
+  <p>Set variables associated with the object as follows:</p>
+
+  <ul>
+   <li><p>Set <span>request method</span> to <var>method</var>.
+   <li><p>Set <span>request URL</span> to <var title>parsed URL</var>.
+   <li><p>If <var>async</var> is false, set the <span>synchronous flag</span>.
+   <li><p>Set <span>author request headers</span> to the empty list.
+   <li><p>Unset the <span><code>send()</code> flag</span>.
+   <li><p>Set <span>response entity body</span> to null.
+   <li><p>Set <span>arraybuffer response entity body</span> to null.
+   <li><p>Set <span>blob response entity body</span> to null.
+   <li><p>Set <span>document response entity body</span> to null.
+   <li><p>Set <span>text response entity body</span> to null.
+  </ul>
+
+ <li>
+  <p>If the state is not <span title="dom-XMLHttpRequest-OPENED">OPENED</span>, run these
+  substeps:
+
+  <ol>
+   <li><p>Change the state to <span title="dom-XMLHttpRequest-OPENED">OPENED</span>.
+
+   <li><p><span data-anolis-spec=dom title=concept-event-fire>Fire an event</span> named <code title=event-xhr-readystatechange>readystatechange</code>.
+  </ol>
+</ol>
+
+  <h4>The <code title>setRequestHeader()</code> method</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-setRequestHeader>setRequestHeader</span>(<var title>header</var>, <var title>value</var>)</code>
+
+   <dd>
+    <p>Appends an header to the list of
+    <span>author request headers</span>, or if <var>header</var> is already
+    in the list of <span>author request headers</span>, combines its value
+    with <var>value</var>.</p>
+
+    <p>Throws an "<code data-anolis-spec=dom>InvalidStateError</code>"
+    exception if the state is not
+    <span title="dom-XMLHttpRequest-OPENED">OPENED</span> or if the
+    <span><code>send()</code> flag</span> is set.</p>
+
+    <p>Throws a JavaScript <code data-anolis-spec=webidl>TypeError</code> if
+    <var title>header</var> is not a valid HTTP header field name or if
+    <var title>value</var> is not a valid HTTP header field value.</p>
+   </dd>
+  </dl>
+
+  <p class=note>As indicated in the algorithm below certain headers cannot
+  be set and are left up to the user agent. In addition there are certain
+  other headers the user agent will take control of if they are not set by
+  the author as indicated at the end of the
+  <code title="dom-XMLHttpRequest-send">send()</code> method section.</p>
+
+
+  <p class=note>For non <span data-anolis-spec=html>same origin</span> requests using the HTTP
+  <code>GET</code> method a preflight request is made when headers other
+  than <code>Accept</code> and <code>Accept-Language</code> are set.</p>
+
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-setrequestheader" title="dom-XMLHttpRequest-setRequestHeader"><code>setRequestHeader(<var title>header</var>, <var title>value</var>)</code></dfn>
+  method must run these steps:</p>
+
+  <ol>
+   <li><p>If the state is not
+   <span title="dom-XMLHttpRequest-OPENED">OPENED</span>,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.
+
+   <li><p>If the <span><code>send()</code> flag</span> is set,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.
+
+   <li><p>If <var>header</var> does not match the
+   <span data-anolis-spec=http>field-name</span> production,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> a JavaScript <code data-anolis-spec=webidl>TypeError</code>.
+
+   <li>
+    <p>If <var>value</var> does not match the
+    <span data-anolis-spec=http>field-value</span> production,
+    <span data-anolis-spec=dom title=concept-throw>throw</span> a JavaScript <code data-anolis-spec=webidl>TypeError</code>.
+
+    <p class=note>An empty string represents an empty header field value.
+
+   <li>
+    <p>Terminate these steps if <var>header</var> is a case-insensitive
+    match for one of the following headers:</p>
+
+    <ul>
+     <li><code>Accept-Charset</code></li>
+     <li><code>Accept-Encoding</code></li>
+     <li><code>Access-Control-Request-Headers</code></li>
+     <li><code>Access-Control-Request-Method</code></li>
+     <li><code>Connection</code></li>
+     <li><code>Content-Length</code></li>
+     <li><code>Cookie</code></li>
+     <li><code>Cookie2</code></li>
+     <li><code>Date</code></li>
+     <li><code>DNT</code></li>
+     <li><code>Expect</code></li>
+     <li><code>Host</code></li>
+     <li><code>Keep-Alive</code></li>
+     <li><code title>Origin</code></li>
+     <li><code>Referer</code></li>
+     <li><code>TE</code></li>
+     <li><code>Trailer</code></li>
+     <li><code>Transfer-Encoding</code></li>
+     <li><code>Upgrade</code></li>
+     <li><code>User-Agent</code></li>
+     <li><code>Via</code></li>
+    </ul>
+
+    <p>&hellip; or if the start of <var>header</var> is a case-insensitive
+    match for <code>Proxy-</code> or <code>Sec-</code> (including when
+    <var>header</var> is just <code>Proxy-</code> or <code>Sec-</code>).</p>
+
+    <p class=note>The above headers are controlled by the user agent to
+    let it control those aspects of transport. This guarantees data
+    integrity to some extent. Header names starting with <code>Sec-</code>
+    are not allowed to be set to allow new headers to be minted that are
+    guaranteed not to come from <code>XMLHttpRequest</code>.</p>
+   </li>
+
+   <li><p>If <var>header</var> is not in the
+   <span>author request headers</span> list, append <var>header</var> with
+   its associated <var>value</var> to the list and terminate these
+   steps.</p></li>
+
+   <li>
+    <p>If <var title>header</var> is in the <span>author request headers</span> list, append
+    "<code>,</code>", followed by U+0020, followed by <var title>value</var>, to the
+    value of the header matching <var title>header</var>.
+ 
+    <p class=note>The XMLHttpRequest standard intentionally constraints the
+    use of HTTP here in line with contemporary implementations.
+  </ol>
+
+  <div class="example">
+   <p>Some simple code demonstrating what happens when setting the same
+   header twice:</p>
+
+   <pre><code>// The following script:
+var client = new XMLHttpRequest();
+client.open('GET', 'demo.cgi');
+client.setRequestHeader('X-Test', 'one');
+client.setRequestHeader('X-Test', 'two');
+client.send();
+
+// &hellip;results in the following header being sent:
+X-Test: one, two</code></pre>
+  </div>
+
+
+  <h4>The <code title>timeout</code> attribute</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title="dom-XMLHttpRequest-timeout">timeout</span></code>
+   <dd>
+    <p>Can be set to a time in milliseconds. When set to a non-zero value
+    will cause <span title=fetch data-anolis-spec=html>fetching</span> to
+    terminate after the given time has passed. When the time has passed, the request has
+    not yet completed, and the <span>synchronous flag</span> is unset, a 
+    <code title=event-xhr-timeout>timeout</code> event will then be
+    <span title=concept-event-dispatch data-anolis-spec=dom>dispatched</span>,
+    or a "<code data-anolis-spec=dom>TimeoutError</code>" exception will be
+    <span data-anolis-spec=dom title=concept-throw>thrown</span> otherwise
+    (for the <code title=dom-XMLHttpRequest>send()</code> method).
+    <p>When set: throws an
+    "<code data-anolis-spec=dom>InvalidAccessError</code>" exception if
+    the <span>synchronous flag</span> is set and the
+    <span data-anolis-spec=html>JavaScript global environment</span> is a
+    <span data-anolis-spec=html>document environment</span>.
+   </dd>
+  </dl>
+
+  <p>The
+  <dfn id="dom-xmlhttprequest-timeout" title="dom-XMLHttpRequest-timeout"><code>timeout</code></dfn>
+  attribute must return its value. Initially its value must be zero.</p>
+
+  <p>Setting the <code title="dom-XMLHttpRequest-timeout">timeout</code>
+  attribute must run these steps:
+
+  <ol>
+   <li><p>If the
+   <span data-anolis-spec=html>JavaScript global environment</span> is a
+   <span data-anolis-spec=html>document environment</span> and the
+   <span>synchronous flag</span> is set,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidAccessError</code>" exception.
+
+   <li><p>Set its value to the new value.
+  </ol>
+
+  <p class=note>This implies that the
+  <code title="dom-XMLHttpRequest-timeout">timeout</code> attribute can be
+  set while <span data-anolis-spec=html title=fetch>fetching</span> is in
+  progress. If that occurs it will still be measured relative to the start
+  of <span data-anolis-spec=html title=fetch>fetching</span>.
+
+
+  <h4>The <code title>withCredentials</code> attribute</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-withCredentials>withCredentials</span></code>
+   <dd>
+    <p>True when <span>user credentials</span> are to be included in a
+    cross-origin request. False when they are to be excluded in a
+    cross-origin request and when cookies are to be ignored in its response.
+    Initially false.
+
+    <p>When set: throws an
+    "<code data-anolis-spec=dom>InvalidStateError</code>" exception if the
+    state is not <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> or
+    <span title="dom-XMLHttpRequest-OPENED">OPENED</span>, or if
+    the <span><code>send()</code> flag</span> is set.</p>
+    <p>When set: throws an
+    "<code data-anolis-spec=dom>InvalidAccessError</code>" exception if
+    either the <span>synchronous flag</span> is set and the
+    <span data-anolis-spec=html>JavaScript global environment</span> is a
+    <span data-anolis-spec=html>document environment</span> or if the
+    <span>anonymous flag</span> is set.</p>
+   </dd>
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-withCredentials"><code>withCredentials</code></dfn>
+  attribute must return its value. Initially its value must be false.
+
+  <p>Setting the
+  <code title="dom-XMLHttpRequest-withCredentials">withCredentials</code>
+  attribute must run these steps:</p>
+
+  <ol>
+   <li><p>If the state is not
+   <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> or
+   <span title="dom-XMLHttpRequest-OPENED">OPENED</span>,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.
+
+   <li><p>If the <span><code>send()</code> flag</span> is set,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.
+
+   <li><p>If the <span>anonymous flag</span> is set,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidAccessError</code>" exception.
+
+   <li><p>If the
+   <span data-anolis-spec=html>JavaScript global environment</span> is a
+   <span data-anolis-spec=html>document environment</span> and the
+   <span>synchronous flag</span> is set,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidAccessError</code>" exception.
+
+   <li><p>Set the
+   <code title="dom-XMLHttpRequest-withCredentials">withCredentials</code>
+   attribute's value to the given value.</p></li>
+  </ol>
+
+  <p class=note>The
+  <code title="dom-XMLHttpRequest-withCredentials">withCredentials</code>
+  attribute has no effect when
+  <span data-anolis-spec=html title=fetch>fetching</span>
+  <span data-anolis-spec=html title="same origin">same-origin</span>
+  resources.</p>
+
+
+  <h4>The <code title>upload</code> attribute</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-upload>upload</span></code>
+   <dd><p>Returns the associated <code>XMLHttpRequestUpload</code>
+   object. It can be used to gather transmission information when data is
+   transferred to a server.
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-upload"><code>upload</code></dfn>
+  attribute must return the associated
+  <code>XMLHttpRequestUpload</code> object.</p>
+
+  <p class=note>As indicated earlier, each <code>XMLHttpRequest</code>
+  object has an associated <code>XMLHttpRequestUpload</code> object.
+
+
+  <h4>The <code title>send()</code> method</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-send>send</span>([<var title>data</var> = null])</code>
+   <dd>
+    <p>Initiates the request. The optional argument provides the
+    <span>request entity body</span>. The argument is ignored if
+    <span>request method</span> is <code>GET</code> or
+    <code>HEAD</code>.</p>
+
+    <p>Throws an "<code data-anolis-spec=dom>InvalidStateError</code>"
+    exception if the state is not
+    <span title="dom-XMLHttpRequest-OPENED">OPENED</span> or if the
+    <span><code>send()</code> flag</span> is set.</p>
+   </dd>
+  </dl>
+
+<p>The <dfn title="dom-XMLHttpRequest-send"><code>send(<var>data</var>)</code></dfn> 
+method must run these steps:
+
+  <ol>
+   <li><p>If the state is not
+   <span title="dom-XMLHttpRequest-OPENED">OPENED</span>,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.
+
+   <li><p>If the <span><code>send()</code> flag</span> is set,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.
+
+   <li><p>If the <span>request method</span> is <code>GET</code> or
+   <code>HEAD</code>, set <var title>data</var> to null.
+
+   <li>
+    <p>If <var title>data</var> is null, do not include a
+    <span>request entity body</span> and go to the next step.
+
+    <p>Otherwise, let <var>encoding</var> be null, <var>mime type</var> be
+    null, and then follow these rules, depending on <var title>data</var>:
+
+    <dl class=switch>
+
+     <dt id="dom-XMLHttpRequest-send-ArrayBufferView"><code data-anolis-spec=typedarray>ArrayBufferView</code>
+     <dd><p>Let the <span>request entity body</span> be the raw data
+     represented by <var title>data</var>.</p></dd>
+
+     <dt id="dom-XMLHttpRequest-send-Blob"><code data-anolis-spec=fileapi>Blob</code>
+     <dd>
+      <p>If the object's
+      <code data-anolis-spec=fileapi title=dom-Blob-type>type</code>
+      attribute is not the empty string let <var>mime type</var> be its
+      value.</p>
+
+      <p>Let the <span>request entity body</span> be the raw data
+      represented by <var>data</var>.</p>
+     </dd>
+
+
+     <dt id="dom-XMLHttpRequest-send-document"><span data-anolis-spec=dom title=concept-document>document</span>
+     <dd>
+      <p>Let <var>encoding</var> be "<code title>UTF-8</code>".
+
+      <p>If <var title>data</var> is an <span data-anolis-spec=dom>HTML document</span>, let
+      <var>mime type</var> be "<code>text/html</code>", or let <var>mime type</var> be
+      "<code>application/xml</code>" otherwise. Then append "<code>;charset=UTF-8</code>" to
+      <var>mime type</var>.
+
+      <p>Let the <span>request entity body</span> be <var title>data</var>,
+      <span data-anolis-spec=domps title=concept-serialize>serialized</span>, 
+      <span data-anolis-spec=webidl title="convert a DOMString to a sequence of Unicode characters">converted to Unicode</span>, 
+      and <span data-anolis-spec=encoding title="utf-8 encode">utf-8 encoded</span>.
+      Re-throw any exception
+      <span data-anolis-spec=domps title=concept-serialize>serializing</span> throws.
+
+      <p class=note>If <var title>data</var> cannot be
+      <span data-anolis-spec=domps title=concept-serialize>serialized</span>, an
+      "<code data-anolis-spec=dom>InvalidStateError</code>" exception is thrown.
+
+     <dt id="dom-XMLHttpRequest-send-a-string">a string
+     <dd>
+      <p>Let <var>encoding</var> be "<code title>UTF-8</code>".
+
+      <p>Let <var>mime type</var> be "<code>text/plain;charset=UTF-8</code>".</p>
+
+      <p>Let the <span>request entity body</span> be <var title>data</var>,
+      <span data-anolis-spec=encoding title="utf-8 encode">utf-8 encoded</span>. 
+
+     <dt id="dom-XMLHttpRequest-send-FormData"><code>FormData</code>
+     <dd>
+      <p>Let the <span>request entity body</span> be the result of running
+      the
+      <span data-anolis-spec=html><code>multipart/form-data</code> encoding algorithm</span>
+      with <var>data</var> as <var>form data set</var> and with
+      <span data-anolis-spec=encoding>utf-8</span> as the
+      explicit character encoding.
+      <!-- need to provide explicit character encoding because otherwise the
+           encoding of the document is used -->
+
+      <p>Let <var>mime type</var> be the concatenation of
+      "<code title>multipart/form-data;</code>",
+      a U+0020 SPACE character,
+      "<code title>boundary=</code>", and the
+      <span data-anolis-spec=html><code>multipart/form-data</code> boundary string</span>
+      generated by the
+      <span data-anolis-spec=html><code>multipart/form-data</code> encoding algorithm</span>.
+     </dd>
+
+    </dl>
+
+    <p>If a <code>Content-Type</code> header is in
+    <span>author request headers</span> and its value is a
+    <span data-anolis-spec=html>valid MIME type</span> that has a
+    <code>charset</code> parameter whose value is not a case-insensitive
+    match for <var title>encoding</var>, and <var title>encoding</var>
+    is not null, set all the <code>charset</code> parameters of that
+    <code>Content-Type</code> header to <var title>encoding</var>.
+
+    <p>If no <code>Content-Type</code> header is in
+    <span>author request headers</span> and <var title>mime type</var> is
+    not null, append a <code>Content-Type</code> header with value
+    <var title>mime type</var> to <span>author request headers</span>.
+
+    <!-- reminder: if we ever change this to always include charset it has
+    to be included as the first parameter for compatibility reasons -->
+   </li>
+
+   <li><p>If the <span>synchronous flag</span> is set, release the
+   <span data-anolis-spec=html>storage mutex</span>.</p></li>
+
+   <li><p>Unset the <span>error flag</span>,
+   <span>upload complete flag</span> and <span>upload events flag</span>.
+
+   <li><p>If there is no <span>request entity body</span> or if it is empty,
+   set the <span>upload complete flag</span>.
+
+   <li><p>If the <span>synchronous flag</span> is unset and one or more
+   event listeners are registered on the <code>XMLHttpRequestUpload</code>
+   object, set the <span>upload events flag</span>.
+
+   <li>
+    <p>If the <span>synchronous flag</span> is unset, run these substeps:</p>
+
+    <ol>
+     <li><p>Set the <span><code>send()</code> flag</span>.
+
+     <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title="event-xhr-loadstart">loadstart</code>.</p></li>
+
+     <li><p>If the <span>upload complete flag</span> is unset,
+     <span data-anolis-spec=progress-events title=concept-event-fire-progress>fire a progress event</span> named <code title="event-xhr-loadstart">loadstart</code>
+     on the <code>XMLHttpRequestUpload</code> object.</p></li>
+
+     <li><p>Return the <code title="dom-XMLHttpRequest-send">send()</code>
+     method call, but continue running the steps in this algorithm.</p></li>
+    </ol>
+   </li>
+
+   <li>
+    <dl class=switch>
+     <dt>If the <span>source origin</span> and the <span>request URL</span>
+     are <span data-anolis-spec=html>same origin</span></dt>
+     
+     <dd>
+      <p>These are the <dfn>same-origin request steps</dfn>.</p>
+
+      <p><span data-anolis-spec=html>Fetch</span> the
+      <span>request URL</span> from <i title>origin</i>
+      <span>source origin</span>, using
+      <span>referrer source</span> as
+      <i title>override referrer source</i>, with the
+      <i title>synchronous flag</i> set if the
+      <span>synchronous flag</span> is set, using HTTP method
+      <span>request method</span>, taking into account the
+      <span>request entity body</span>, list of
+      <span>author request headers</span>, and the rules listed at the end of
+      this section.</p>
+
+      <dl class=switch>
+       <dt>If the <span>synchronous flag</span> is set</dt>
+       <dd>
+        <p>While making the request also follow the
+        <span>same-origin request event rules</span>.</p>
+
+        <!--
+         This cannot involve any task queue whatsoever because that would
+         mean other tasks on the task queue might get processed as well
+         which is counter to the whole idea of doing things synchronous.
+        -->
+
+        <p class=note>The
+        <code title="dom-XMLHttpRequest-send">send()</code> method call will
+        now be returned by virtue of this algorithm ending.</p>
+       </dd>
+
+       <dt>If the <span>synchronous flag</span> is unset</dt>
+       <dd>
+
+        <p><span>Make upload progress notifications</span>.</p>
+
+        <p><span>Make progress notifications</span>.</p>
+
+
+        <p>While processing the request, as data becomes available and when
+        the user interferes with the request,
+        <span data-anolis-spec=html title="queue a task">queue tasks</span>
+        to update the <span>response entity body</span> and follow the
+        <span>same-origin request event rules</span>.</p>
+       </dd>
+      </dl>
+     </dd>
+
+     <dt>Otherwise</dt>
+     <dd>
+      <p>These are the <dfn>cross-origin request steps</dfn>.</p>
+
+
+
+
+      <p>Make a <span data-anolis-spec=cors>cross-origin request</span>,
+      passing these as parameters:</p>
+
+      <dl>
+       <dt>request URL</dt>
+       <dd>The <span>request URL</span>.</dd>
+
+       <dt>request method</dt>
+       <dd>The <span>request method</span>.</dd>
+
+       <dt>author request headers</dt>
+       <dd>The list of <span>author request headers</span>.</dd>
+
+       <dt>request entity body</dt>
+       <dd>The <span>request entity body</span>.</dd>
+
+       <dt>source origin</dt>
+       <dd>The <span>source origin</span>.</dd>
+
+       <dt>referrer source
+       <dd>If the <span>anonymous flag</span> is set, the
+       <span data-anolis-spec=url>URL</span>
+       "<code title>about:blank</code>", and the
+       <span>referrer source</span> otherwise.
+
+       <dt>omit credentials flag</dt>
+       <dd>Set if
+       <code title="dom-XMLHttpRequest-withCredentials">withCredentials</code>
+       attribute's value is false.
+
+       <dt>force preflight flag</dt>
+       <dd>Set if the <span>upload events flag</span> is set.
+      </dl>
+
+      <dl class=switch>
+       <dt>If the <span>synchronous flag</span> is set</dt>
+       <dd>
+        <p>While making the request also follow the
+        <span>cross-origin request event rules</span>.</p>
+
+        <!--
+         This cannot involve any task queue whatsoever because that would
+         mean other tasks on the task queue might get processed as well
+         which is counter to the whole idea of doing things synchronous.
+        -->
+
+        <p class=note>The
+        <code title="dom-XMLHttpRequest-send">send()</code> method call will
+        now be returned by virtue of this algorithm ending.</p>
+       </dd>
+
+       <dt>If the <span>synchronous flag</span> is unset</dt>
+       <dd>
+        <p>While processing the request, as data becomes available and when
+        the end user interferes with the request,
+        <span title="queue a task">queue tasks</span> to update the
+        <span>response entity body</span> and follow the
+        <span>cross-origin request event rules</span>.</p>
+       </dd>
+      </dl>
+
+     </dd>
+    </dl>
+   </li>
+  </ol>
+
+  <hr>
+
+  <p>If the user agent allows the end user to configure a proxy it
+  should modify the request appropriately; i.e., connect
+  to the proxy host instead of the origin server, modify the
+  <code>Request-Line</code> and send <code>Proxy-Authorization</code>
+  headers as specified.</p>
+
+  <hr>
+
+  <p>If the user agent supports HTTP Authentication and
+  <code title="http-authorization">Authorization</code> is not in the list
+  of <span>author request headers</span>, it should
+  consider requests originating from the <code>XMLHttpRequest</code> object
+  to be part of the protection space that includes the accessed URIs and
+  send <code title="http-authorization">Authorization</code> headers and
+  handle <code>401 Unauthorized</code> requests appropriately.</p>
+
+  <p>If authentication fails,
+  <span>source origin</span> and the
+  <span>request URL</span> are <span data-anolis-spec=html>same origin</span>,
+  <code title="http-authorization">Authorization</code> is not in the list
+  of <span>author request headers</span>,
+  <span>request URL</span>'s
+  <span data-anolis-spec=url title=concept-url-username>username</span> is
+  the empty string and <span>request URL</span>'s
+  <span data-anolis-spec=url title=concept-url-password>password</span> is
+  null, user agents should prompt the end user for their username and
+  password.</p>
+
+  <p>Otherwise, if authentication fails, user agents
+  must not prompt the end user for their username and
+  password. <span data-anolis-ref>HTTPAUTH</span>
+
+  <p class=note>Unfortunately end users are prompted because of legacy
+  content constraints. However, when possible this behavior is prohibited,
+  as it is bad UI. E.g. that is why the
+  <span data-anolis-spec=html>same origin</span> restriction is made above.
+
+  <hr>
+
+  <p>If the user agent supports HTTP State Management it
+  should persist, discard and send cookies (as received
+  in the <code>Set-Cookie</code> response header, and sent in the
+  <code>Cookie</code> header) as applicable.
+  <span data-anolis-ref>COOKIES</span>
+
+  <hr>
+
+  <p>If the user agent implements a HTTP cache it should
+  respect <code>Cache-Control</code> headers in
+  <span>author request headers</span>
+  (e.g. <code>Cache-Control: no-cache</code> bypasses the cache). It
+  must not send <code>Cache-Control</code> or
+  <code>Pragma</code> request headers automatically unless the end user
+  explicitly requests such behavior (e.g. by reloading the page).</p>
+
+  <p>For <code>304 Not Modified</code> responses that are a result of a
+  user agent generated conditional request the user agent
+  must act as if the server gave a <code>200 OK</code>
+  response with the appropriate content. The user agent
+  must allow <span>author request headers</span> to override automatic cache
+  validation (e.g. <code>If-None-Match</code> or
+  <code>If-Modified-Since</code>), in which case
+  <code>304 Not Modified</code> responses must be passed through.
+  <span data-anolis-ref>HTTP</span>
+
+  <hr>
+
+  <p>If the user agent implements server-driven content-negotiation
+  it must follow these constraints for the
+  <code>Accept</code> and <code>Accept-Language</code> request headers:</p>
+
+  <ul>
+   <li><p>Both headers must not be modified if they are in
+   <span>author request headers</span>.
+
+   <li><p>If not in <span>author request headers</span>,
+   <code>Accept-Language</code> with an appropriate value should be appended
+   to it.
+
+   <li><p>If not in <span>author request headers</span>, <code>Accept</code>
+   with value <code>*/*</code> must be appended to it.
+  </ul>
+
+  <p>Responses must have the content-encodings
+  automatically decoded. <span data-anolis-ref>HTTP</span>
+
+  <hr>
+
+  <p>Besides the <span>author request headers</span>, user agents
+  should not include additional request headers other than those mentioned
+  above or other than those authors are not allowed to set using
+  <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>.
+  This ensures that authors have a predictable API.</p>
+
+
+  <h4>Infrastructure for the <code title>send()</code> method</h4>
+
+  <p>The <dfn>same-origin request event rules</dfn> are as follows:</p>
+
+  <dl class=switch>
+   <dt>If the <span>error flag</span> is set
+   <dd><p>Terminate these steps.
+
+   <dt>If the response has an HTTP status code of 301, 302, 303, 307, or 308</dt>
+   <dd>
+    <p>If the redirect violates infinite loop precautions this is a
+    <span>network error</span>.</p>
+
+    <p>Otherwise, run these steps:</p>
+
+    <ol>
+     <li><p>Set the <span>request URL</span> to the
+     <span data-anolis-spec=url>URL</span> conveyed by the
+     <code>Location</code> header.</p></li>
+
+     <li><p>If the <span>source origin</span> and the
+     <span data-anolis-spec=html>origin</span> of <span>request URL</span>
+     are <span data-anolis-spec=html>same origin</span> transparently follow
+     the redirect while observing the
+     <span>same-origin request event rules</span>.
+
+     <li><p>Otherwise, follow the <span>cross-origin request steps</span>
+     and terminate the steps for this algorithm.</p></li>
+    </ol>
+
+    <p class=note>HTTP places requirements on the user agent regarding the
+    preservation of the <span>request method</span> and
+    <span>request entity body</span> during redirects, and also requires end
+    users to be notified of certain kinds of automatic redirections.</p>
+    <!-- XXX HTTP needs fixing here -->
+   </dd>
+
+   <dt>If the end user cancels the request</dt>
+   <dd><p>This is an <span>abort error</span>.</p></dd>
+
+   <dt>If there is a network error</dt>
+   <dd>
+    <p>In case of DNS errors, TLS negotiation failure, or other type of
+    network errors, this is a <span>network error</span>. Do not request any
+    kind of end user interaction.</p>
+
+    <p class=note>This does not include HTTP responses that indicate
+    some type of error, such as HTTP status code 410.</p>
+   </dd>
+
+
+   <dt>If <code title="dom-XMLHttpRequest-timeout">timeout</code> is not 0
+   and since the request started the amount of milliseconds specified by
+   <code title="dom-XMLHttpRequest-timeout">timeout</code> has passed</dt>
+   <dd><p>This is a <span>timeout error</span>.</p></dd>
+
+
+   <dt>Once all HTTP headers have been received, the
+   <span>synchronous flag</span> is unset, and the HTTP status code of the
+   response is not one of 301, 302, 303, 307, and 308</dt>
+   <dd><p><span>Switch to the HEADERS_RECEIVED state</span>.</p></dd>
+
+   <dt>Once the first byte (or more) of the
+   <span>response entity body</span> has been received and the
+   <span>synchronous flag</span> is unset</dt>
+   <dt>If there is no <span>response entity body</span> and the
+   <span>synchronous flag</span> is unset</dt>
+   <dd><p><span>Switch to the LOADING state</span>.</p></dd>
+
+   <dt>Once the whole <span>response entity body</span> has been
+   received</dt>
+   <dt>If there is no <span>response entity body</span> and the state is
+   <span title="dom-XMLHttpRequest-LOADING">LOADING</span></dt>
+   <dt>If there is no <span>response entity body</span> and the
+   <span>synchronous flag</span> is set</dt>
+   <dd><p><span>Switch to the DONE state</span>.</p></dd>
+  </dl>
+
+
+  <hr>
+
+  <p>The <dfn>cross-origin request event rules</dfn> are as follows:</p>
+
+  <dl class=switch>
+   <dt>If the <span>error flag</span> is set
+   <dd><p>Terminate these steps.
+
+   <dt>If the <span data-anolis-spec=cors>cross-origin request status</span>
+   is <i>preflight complete</i> and the <span>synchronous flag</span> is
+   unset</dt>
+   <dd><p><span>Make upload progress notifications</span>.</p></dd>
+
+   <dt>If the <span data-anolis-spec=cors>cross-origin request status</span>
+   is <i title>network error</i></dt>
+   <dd><p>This is a <span>network error</span>.</p></dd>
+
+   <dt>If the <span data-anolis-spec=cors>cross-origin request status</span>
+   is <i title>abort error</i></dt>
+   <dd><p>This is an <span>abort error</span>.</p></dd>
+
+   <dt>If <code title="dom-XMLHttpRequest-timeout">timeout</code> is not 0
+   and since the request started the amount of milliseconds specified by
+   <code title="dom-XMLHttpRequest-timeout">timeout</code> has passed</dt>
+   <dd><p>This is a <span>timeout error</span>.</p></dd>
+
+   <dt>Once all HTTP headers have been received, the
+   <span data-anolis-spec=cors>cross-origin request status</span> is
+   <i>success</i>, and the <span>synchronous flag</span> is unset</dt>
+   <dd>
+    <p><span>Switch to the HEADERS_RECEIVED state</span>.</p>
+
+    <p><span>Make progress notifications</span>.</p>
+   </dd>
+
+   <dt>Once the first byte (or more) of the
+   <span>response entity body</span> has been received, the
+   <span data-anolis-spec=cors>cross-origin request status</span> is
+   <i>success</i>, and the <span>synchronous flag</span> is unset</dt>
+   <dt>If there is no <span>response entity body</span>, the
+   <span data-anolis-spec=cors>cross-origin request status</span> is
+   <i>success</i>, and the <span>synchronous flag</span> is unset</dt>
+   <dd><p><span>Switch to the LOADING state</span>.</p></dd>
+
+   <dt>Once the whole <span>response entity body</span> has been received
+   and the <span data-anolis-spec=cors>cross-origin request status</span> is
+   <i>success</i></dt>
+   <dt>If there is no <span>response entity body</span>, the
+   <span data-anolis-spec=cors>cross-origin request status</span> is
+   <i>success</i>, and the state is
+   <span title="dom-XMLHttpRequest-LOADING">LOADING</span></dt>
+   <dt>If there is no <span>response entity body</span>, the
+   <span data-anolis-spec=cors>cross-origin request status</span> is
+   <i>success</i>, and the <span>synchronous flag</span> is set</dt>
+   <dd><p><span>Switch to the DONE state</span>.</p></dd>
+  </dl>
+
+
+  <hr>
+
+  <p>When something is said to be a <dfn>network error</dfn> run the
+  <span>request error</span> steps for exception
+  "<code data-anolis-spec=dom>NetworkError</code>" and
+  event <code title="event-xhr-error">error</code>.</p>
+
+  <p>When something is said to be an <dfn>abort error</dfn> run the
+  <span>request error</span> steps for exception
+  "<code data-anolis-spec=dom>AbortError</code>" and event
+  <code title="event-xhr-abort">abort</code>.</p>
+
+
+  <p>When something is said to be an <dfn>timeout error</dfn> run the
+  <span>request error</span> steps for exception
+  "<code data-anolis-spec=dom>TimeoutError</code>" and event
+  <code title="event-xhr-timeout">timeout</code>.</p>
+
+
+  <p>When something is said to be a <dfn>request error</dfn> for
+  exception <var>exception</var> and event <var title>event</var> run these
+  steps:</p>
+
+  <ol>
+   <li><p><span>Terminate the request</span>.
+
+   <li><p>Change the state to <span title="dom-XMLHttpRequest-DONE">DONE</span>.</p></li>
+
+   <li><p>If the <span>synchronous flag</span> is set,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   <var>exception</var> exception.</p></li>
+
+   <li>
+    <p><span data-anolis-spec=dom title=concept-event-fire>Fire an event</span> named <code title=event-xhr-readystatechange>readystatechange</code>.</p>
+
+    <p class=note>At this point it is clear that the
+    <span>synchronous flag</span> is unset.</p>
+   </li>
+
+
+   <li>
+    <p>If the <span>upload complete flag</span> is unset, follow these
+    substeps:</p>
+
+    <ol>
+     <li><p>Set the <span>upload complete flag</span>.
+
+     <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named
+     <code title=event-xhr-progress>progress</code> on the <code>XMLHttpRequestUpload</code> object.
+
+     <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named
+     <var title>event</var> on the <code>XMLHttpRequestUpload</code> object.
+
+     <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named
+     <code title="event-xhr-loadend">loadend</code> on the <code>XMLHttpRequestUpload</code> object.
+    </ol>
+   </li>
+
+   <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title=event-xhr-progress>progress</code>.
+
+   <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <var title>event</var>.
+
+   <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title="event-xhr-loadend">loadend</code>.
+  </ol>
+
+  <hr>
+
+  <p>When it is said to
+  <dfn id="switch-headers-received">switch to the HEADERS_RECEIVED state</dfn>
+  run these steps:</p>
+
+  <ol>
+   <li><p>Change the state to <span title="dom-XMLHttpRequest-HEADERS_RECEIVED">HEADERS_RECEIVED</span>.</p></li>
+
+   <li><p><span data-anolis-spec=dom title=concept-event-fire>Fire an event</span> named <code title=event-xhr-readystatechange>readystatechange</code>.</p></li>
+  </ol>
+
+  <p>When it is said to
+  <dfn id="switch-loading">switch to the LOADING state</dfn> run these
+  steps:</p>
+
+  <ol>
+   <li><p>Change the state to <span title="dom-XMLHttpRequest-LOADING">LOADING</span>.</p></li>
+
+   <li><p><span data-anolis-spec=dom title=concept-event-fire>Fire an event</span> named <code title=event-xhr-readystatechange>readystatechange</code>.</p></li>
+  </ol>
+
+  <p>When it is said to
+  <dfn id="switch-done">switch to the DONE state</dfn> run these steps:</p>
+
+  <ol>
+   <li><p>If the <span>synchronous flag</span> is set, update the
+   <span>response entity body</span>.</p></li>
+
+   <li><p>Unset the <span>synchronous flag</span>.
+
+   <li><p>Change the state to <span title="dom-XMLHttpRequest-DONE">DONE</span>.</p></li>
+
+   <li><p><span data-anolis-spec=dom title=concept-event-fire>Fire an event</span> named <code title=event-xhr-readystatechange>readystatechange</code>.</p></li>
+
+   <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title=event-xhr-progress>progress</code>.
+
+   <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title="event-xhr-load">load</code>.</p></li>
+
+   <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title="event-xhr-loadend">loadend</code>.</p></li>
+
+  </ol>
+
+
+  <hr>
+
+  <p>When it is said to <dfn>make progress notifications</dfn>, while the
+  download is progressing, <span data-anolis-spec=html>queue a task</span> to
+  <span data-anolis-spec=progress-events title=concept-event-fire-progress>fire a progress event</span> named <code title="event-xhr-progress">progress</code>
+  about every 50ms or for every byte received, whichever is <em>least</em>
+  frequent.</p>
+
+  <hr>
+
+  <p>When it is said to <dfn>make upload progress notifications</dfn> run
+  these steps:</p>
+
+  <ul>
+   <li><p>While the request entity body is being transmitted and the
+   <span>upload complete flag</span> is unset,
+   <span data-anolis-spec=html>queue a task</span> to
+   <span data-anolis-spec=progress-events title=concept-event-fire-progress>fire a progress event</span> named <code title="event-xhr-progress">progress</code> on
+   the <code>XMLHttpRequestUpload</code> object about every 50ms or for
+   every byte transmitted, whichever is <em>least</em> frequent.</p></li>
+
+   <li>
+    <p>If the <span>request entity body</span> has been fully transmitted
+    (irrespective of whether the server has started transmitting a response
+    or the status code of such a response) and the
+    <span>upload complete flag</span> is still unset,
+    <span data-anolis-spec=html>queue a task</span> to run these substeps:
+
+    <ol>
+     <li><p>Set the <span>upload complete flag</span>.
+
+     <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title=event-xhr-progress>progress</code>
+     on the <code>XMLHttpRequestUpload</code> object.
+
+     <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title="event-xhr-load">load</code>
+     on the <code>XMLHttpRequestUpload</code> object.
+
+     <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title="event-xhr-loadend">loadend</code>
+     on the <code>XMLHttpRequestUpload</code> object.
+    </ol>
+  </ul>
+
+
+
+  <h4>The <code title>abort()</code> method</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-abort>abort</span>()</code>
+   <dd>Cancels any network activity.
+  </dl>
+
+<p>The <dfn title="dom-XMLHttpRequest-abort"><code>abort()</code></dfn> method must run 
+these steps:
+
+  <ol>
+   <li><p><span>Terminate the request</span>.
+
+   <li>
+    <p>If the state is <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span>,
+    <span title="dom-XMLHttpRequest-OPENED">OPENED</span> with the
+    <span><code>send()</code> flag</span> being unset, or
+    <span title="dom-XMLHttpRequest-DONE">DONE</span> go to the next step.</p>
+
+    <p>Otherwise, run these substeps:</p>
+
+    <ol>
+     <li><p>Change the state to <span title="dom-XMLHttpRequest-DONE">DONE</span>.</p></li>
+
+     <li><p>Unset the <span><code>send()</code> flag</span>.
+
+     <li><p><span data-anolis-spec=dom title=concept-event-fire>Fire an event</span> named <code title=event-xhr-readystatechange>readystatechange</code>.</p></li>
+
+     <li>
+      <p>If the <span>upload complete flag</span> is false run these
+      substeps:</p>
+
+      <ol>
+       <li><p>Set the <span>upload complete flag</span> to true.</p></li>
+
+       <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title=event-xhr-progress>progress</code>
+       on the <code>XMLHttpRequestUpload</code> object.
+
+       <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title="event-xhr-abort">abort</code>
+       on the <code>XMLHttpRequestUpload</code> object.</p></li>
+
+       <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title="event-xhr-loadend">loadend</code>
+       on the <code>XMLHttpRequestUpload</code> object.</p></li>
+      </ol>
+     </li>
+     <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title=event-xhr-progress>progress</code>.
+ 
+     <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title="event-xhr-abort">abort</code>.
+
+     <li><p><span data-anolis-spec=progress-events title=concept-event-fire-progress>Fire a progress event</span> named <code title="event-xhr-loadend">loadend</code>. 
+    </ol>
+   </li>
+
+   <li>
+    <p>Change the state to <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span>.</p>
+
+    <p class=note>No <code title="event-xhr-readystatechange">readystatechange</code> event is dispatched.</p>
+   </li>
+  </ol>
+
+
+
+  <h3 id="response">Response</h3>
+
+  <p>A <dfn title=concept-response-header>response header</dfn> is a HTTP response header
+  transmitted before the <span>response entity body</span>.
+  <span data-anolis-ref>HTTP</span>
+
+  <p class=note>This excludes trailer fields ("trailers").
+
+ 
+  <h4>The <code title>status</code> attribute</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-status>status</span></code>
+   <dd><p>Returns the HTTP status code.
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-status"><code>status</code></dfn>
+  attribute must return the result of running these
+  steps:</p>
+
+  <ol>
+   <li><p>If the state is
+   <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> or
+   <span title="dom-XMLHttpRequest-OPENED">OPENED</span>, return 0.
+
+   <li><p>If the <span>error flag</span> is set, return 0.</p></li>
+
+   <li><p>Return the HTTP status code.</p></li>
+  </ol>
+
+
+  <h4>The <code title>statusText</code> attribute</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-statusText>statusText</span></code>
+   <dd><p>Returns the HTTP status text.
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-statusText"><code>statusText</code></dfn>
+  attribute must return the result of running these steps:
+
+  <ol>
+   <li><p>If the state is
+   <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> or
+   <span title="dom-XMLHttpRequest-OPENED">OPENED</span>, return the empty string.
+
+   <li><p>If the <span>error flag</span> is set, return the empty string.
+
+   <li><p>Return the HTTP status text.
+  </ol>
+
+
+  <h4>The <code title>getResponseHeader()</code> method</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-getResponseHeader>getResponseHeader</span>(<var title>header</var>)</code>
+   <dd><p>Returns the header field value from the response of which the
+   field name matches <var title>header</var>, unless the field name is
+   <code>Set-Cookie</code> or <code>Set-Cookie2</code>.
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-getResponseHeader"><code>getResponseHeader(<var title>header</var>)</code></dfn>
+  method must run these steps:
+
+  <ol>
+   <li><p>If the state is
+   <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> or
+   <span title="dom-XMLHttpRequest-OPENED">OPENED</span>, return null.
+
+   <li><p>If the <span>error flag</span> is set, return null.
+
+   <li><p>If <var>header</var> is a case-insensitive match for
+   <code>Set-Cookie</code> or <code>Set-Cookie2</code>, return null.</p></li>
+
+   <li><p>If <var>header</var> is a case-insensitive match for multiple
+   <span title=concept-response-header>response headers</span>, return the values of these
+   headers as a single concatenated string separated from each other by a    
+   U+002C COMMA U+0020 SPACE character pair.
+
+   <li><p>If <var>header</var> is a case-insensitive match for a single
+   <span title=concept-response-header>response header</span>, return the value of that header.    
+
+   <li><p>Return null.</p></li>
+  </ol>
+
+  <p class=note>The Cross-Origin Resource Sharing specification filters
+  <span title=concept-response-header>response headers</span> exposed by
+  <code title="dom-XMLHttpRequest-getResponseHeader">getResponseHeader()</code>
+  for <span data-anolis-spec=cors title="cross-origin request">cross-origin requests</span>.
+  <span data-anolis-ref>CORS</span>
+
+  <div class="example">
+
+   <p>For the following script:</p>
+
+   <pre><code>var client = new XMLHttpRequest();
+client.open("GET", "unicorns-are-teh-awesome.txt", true);
+client.send();
+client.onreadystatechange = function() {
+  if(this.readyState == 2) {
+    print(client.getResponseHeader("Content-Type"));
+  }
+}</code></pre>
+
+   <p>The <code>print()</code> function will get to process something
+   like:</p>
+
+   <pre><code>text/plain; charset=UTF-8</code></pre>
+  </div>
+
+
+  <h4>The <code title>getAllResponseHeaders()</code> method</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-getAllResponseHeaders>getAllResponseHeaders</span>()</code>
+   <dd><p>Returns all headers from the response, with the exception of those
+   whose field name is <code>Set-Cookie</code> or
+   <code>Set-Cookie2</code>.
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-getAllResponseHeaders"><code>getAllResponseHeaders()</code></dfn>
+  method must run these steps:</p>
+
+  <ol>
+   <li><p>If the state is
+   <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> or
+   <span title="dom-XMLHttpRequest-OPENED">OPENED</span>, return the empty string.
+
+   <li><p>If the <span>error flag</span> is set, return the empty string.
+
+   <li><p>Return all <span title=concept-response-header>response headers</span>, excluding headers that are a
+   case-insensitive match for <code>Set-Cookie</code> or
+   <code>Set-Cookie2</code>, as a single string, with each header line
+   separated by a U+000D CR U+000A LF pair, excluding the status line, and
+   with each header name and header value separated by a
+   U+003A COLON U+0020 SPACE pair.</p></li>
+  </ol>
+
+  <p class=note>The Cross-Origin Resource Sharing specification filters
+  <span title=concept-response-header>response headers</span> exposed by
+  <code title="dom-XMLHttpRequest-getAllResponseHeaders">getAllResponseHeaders()</code>
+  for <span data-anolis-spec=cors title="cross-origin request">cross-origin requests</span>.
+  <span data-anolis-ref>CORS</span> 
+
+  <div class="example">
+   <p>For the following script:</p>
+
+   <pre><code>var client = new XMLHttpRequest();
+client.open("GET", "narwhals-too.txt", true);
+client.send();
+client.onreadystatechange = function() {
+  if(this.readyState == 2) {
+    print(this.getAllResponseHeaders());
+  }
+}</code></pre>
+
+   <p>The <code>print()</code> function will get to process something
+   like:</p>
+
+   <pre><code>Date: Sun, 24 Oct 2004 04:58:38 GMT
+Server: Apache/1.3.31 (Unix)
+Keep-Alive: timeout=15, max=99
+Connection: Keep-Alive
+Transfer-Encoding: chunked
+Content-Type: text/plain; charset=utf-8</code></pre>
+  </div>
+
+
+
+  <h4>Response entity body</h4>
+
+  <p>The <dfn id="response-mime-type">response MIME type</dfn> is the
+  MIME type the <code>Content-Type</code> header contains excluding any
+  parameters and
+  <span data-anolis-spec=dom>converted to ASCII lowercase</span>, or null if
+  the response header can not be parsed or was omitted. The
+  <dfn id="override-mime-type">override MIME type</dfn> is initially null
+  and can get a value if
+  <code title="dom-XMLHttpRequest-overrideMimeType">overrideMimeType()</code>
+  is invoked. <dfn id="final-mime-type">Final MIME type</dfn> is the
+  <span>override MIME type</span> unless that is null in which case it is
+  the <span>response MIME type</span>.
+
+  <p>The <dfn id="response-charset">response charset</dfn> is the value of
+  the <code>charset</code> parameter of the <code>Content-Type</code> header
+  or null if there was no <code>charset</code> parameter or the header could
+  not be parsed or was omitted. The
+  <dfn id="override-charset">override charset</dfn> is initially null and
+  can get a value if <code title="dom-XMLHttpRequest-overrideMimeType">overrideMimeType()</code> is invoked.
+  <dfn id="final-charset">Final charset</dfn> is the
+  <span>override charset</span> unless
+  that is null in which case it is the <span>response charset</span>.</p>
+
+
+
+  <hr>
+
+  <p>The <dfn id="response-entity-body">response entity body</dfn> is the
+  fragment of the <span data-anolis-spec=http>entity body</span> of the
+  response received so far
+  (<span title="dom-XMLHttpRequest-LOADING">LOADING</span>) or the complete
+  <span data-anolis-spec=http>entity body</span> of the response
+  (<span title="dom-XMLHttpRequest-DONE">DONE</span>). If the response
+  does not have an <span data-anolis-spec=http>entity body</span>, the
+  <span>response entity body</span> is null.</p>
+
+  <p class=note>The <span>response entity body</span> is updated as part
+  of the <code title=dom-XMLHttpRequest-send>send()</code> method and reset by the
+  <code title=dom-XMLHttpRequest-open>open()</code> method.</p>
+
+  <hr>
+
+  <p>The
+  <dfn id="arraybuffer-response-entity-body">arraybuffer response entity body</dfn>
+  is either an <code data-anolis-spec=typedarray>ArrayBuffer</code> representing
+  the <span>response entity body</span> or null. If the
+  <span>arraybuffer response entity body</span> is null, let it be the return value of the
+  following algorithm:</p>
+
+  <ol>
+   <li><p>If the <span>response entity body</span> is null, return an empty
+   <code data-anolis-spec=typedarray>ArrayBuffer</code> object.</p></li>
+
+   <li><p>Return an <code data-anolis-spec=typedarray>ArrayBuffer</code>
+   object representing the <span>response entity body</span>.</p></li>
+  </ol>
+
+
+  <p>The
+  <dfn id="blob-response-entity-body">blob response entity body</dfn> is either a
+  <code data-anolis-spec=fileapi>Blob</code> representing the
+  <span>response entity body</span> or null. If the <span>blob response entity body</span>
+  is null, let it be the return value of the following algorithm:</p>
+
+  <ol>
+   <li><p>If the <span>response entity body</span> is null, return an empty
+   <code data-anolis-spec=fileapi>Blob</code> object.</p></li>
+
+   <li><p>Return a <code data-anolis-spec=fileapi>Blob</code> object
+   representing the <span>response entity body</span>.
+  </ol>
+
+
+
+  <p>The
+  <dfn id="document-response-entity-body">document response entity body</dfn>
+  is either a <span data-anolis-spec=dom title=concept-document>document</span>
+  representing the <span>response entity body</span> or null. If the
+  <span>document response entity body</span> is null, let it be the return value of the
+  following algorithm:</p>
+
+  <ol>
+   <li><p>If the <span>response entity body</span> is null, return null.</p></li>
+
+   <li><p>If the
+   <span data-anolis-spec=html>JavaScript global environment</span> is a
+   <span data-anolis-spec=html>worker environment</span>, return null.
+
+   <li><p>If <span>final MIME type</span> is not null,
+   <code>text/html</code>, <code>text/xml</code>,
+   <code>application/xml</code>, or does not end in
+   <code title>+xml</code>, return null.
+
+   <li>
+    <p>If <code title=dom-XMLHttpRequest-responseType>responseType</code> is
+    the empty string and <span>final MIME type</span> is
+    <code>text/html</code>, return null.
+
+    <p class=note>This is restricted to
+    <code title=dom-XMLHttpRequest-responseType>responseType</code> being
+    "<code title>document</code>" in order to prevent breaking legacy
+    content.
+
+   <li>
+    <p>If <span>final MIME type</span> is <code>text/html</code>, run these
+    substeps:
+
+    <ol>
+     <li><p>Let <var>charset</var> be the <span>final charset</span>.
+
+     <li><p>If <var>charset</var> is null,
+     <span title="prescan a byte stream to determine its encoding">prescan</span>
+     the first 1024 bytes of the <span>response entity body</span> and if
+     that does not terminate unsuccessfully then let <var>charset</var> be
+     the return value.
+
+     <li><p>If <var>charset</var> is null, set <var>charset</var> to
+     <span data-anolis-spec=encoding>utf-8</span>.
+
+     <li><p>Let <var title>document</var> be a 
+     <span data-anolis-spec=dom title=concept-document>document</span> that
+     represents the result parsing <span>response entity body</span> following the rules set
+     forth in the HTML specification for an HTML parser with scripting disabled and
+     <span data-anolis-spec=html>a known definite encoding</span> <var>charset</var>.
+     <span data-anolis-ref>HTML</span>
+
+     <li><p>Set <var title>document</var>'s
+     <span data-anolis-spec=dom title=concept-document-encoding>encoding</span>
+     to <var>charset</var>.
+     <!-- This might be redundant with HTML. --> 
+    </ol>
+
+   <li>
+    <p>Otherwise, let <var title>document</var> be a
+    <span data-anolis-spec=dom title=concept-document>document</span>
+    that represents the result of parsing the
+    <span>response entity body</span> following the rules set forth in the
+    XML specifications. If that fails (unsupported character encoding,
+    namespace well-formedness error, etc.), return null.
+    <span data-anolis-ref>XML</span> <span data-anolis-ref>XMLNS</span>
+
+    <p class=note>Scripts in the resulting document tree will not be
+    executed, resources referenced will not be loaded and no associated XSLT
+    will be applied.</p> <!-- XXX more formally?! -->
+
+   <!-- XXX what about document's encoding? -->
+
+   <li><p>Set <var title>document</var>'s
+   <span data-anolis-spec=dom title=concept-document-content-type>content type</span>
+   to <span>final MIME type</span>.
+
+   <li><p>Set <var title>document</var>'s
+   <span data-anolis-spec=dom title=concept-document-url>URL</span> to
+   <span>request URL</span>.
+
+   <li><p>Set <var title>document</var>'s
+   <span data-anolis-spec=html>origin</span> to
+   <span>source origin</span>.
+
+   <li><p>Return <var title>document</var>.
+  </ol>
+
+  <p>The <dfn id="text-response-entity-body">text response entity body</dfn> is either a
+  string representing the <span>response entity body</span> or null. If the
+  <span>text response entity body</span> is null, let it be the return value of the 
+  following algorithm:</p>
+
+  <ol>
+   <li><p>If the <span>response entity body</span> is null, return the empty string.</p>
+
+   <li><p>Let <var>charset</var> be the <span>final charset</span>.
+
+   <li>
+    <p>If <code title=dom-XMLHttpRequest-responseType>responseType</code> is
+    the empty string, <var>charset</var> is null, and
+    <span>final MIME type</span> is either null, <code>text/xml</code>,
+    <code>application/xml</code> or ends in <code title>+xml</code>, use the
+    rules set forth in the XML specifications to determine the encoding. Let
+    <var>charset</var> be the determined encoding.
+    <span data-anolis-ref>XML</span> <span data-anolis-ref>XMLNS</span>
+
+    <p class=note>This is restricted to
+    <code title=dom-XMLHttpRequest-responseType>responseType</code> being
+    the empty string to keep the non-legacy
+    <code title=dom-XMLHttpRequest-responseType>responseType</code> value
+    "<code title>text</code>" simple.
+
+   <li><p>If <var>charset</var> is null, set <var>charset</var> to
+   <span data-anolis-spec=encoding>utf-8</span>.
+
+   <li><p>Return the result of running
+   <span data-anolis-spec=encoding>decode</span> on byte stream
+   <span>response entity body</span> using fallback encoding
+   <var>charset</var>.
+  </ol>
+
+  <p class=note>Authors are strongly encouraged to always encode their
+  resources using <span data-anolis-spec=encoding>utf-8</span>.
+
+
+
+  <h4>The <code title>overrideMimeType()</code> method</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-overrideMimeType>overrideMimeType</span>(<var title>mime</var>)</code>
+   <dd>
+    <p>Sets the <code>Content-Type</code> header for the response to
+    <var title>mime</var>.</p>
+
+    <p>Throws an "<code data-anolis-spec=dom>InvalidStateError</code>"
+    exception if the state is
+    <span title="dom-XMLHttpRequest-LOADING">LOADING</span> or
+    <span title="dom-XMLHttpRequest-DONE">DONE</span>.
+
+    <p>Throws a JavaScript <code data-anolis-spec=webidl>TypeError</code> if
+    <var title>mime</var> is not a valid media type.</p>
+   </dd>
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-overrideMimeType"><code>overrideMimeType(<var title>mime</var>)</code></dfn>
+  method must run these steps:
+
+  <ol>
+   <li><p>If the state is
+   <span title="dom-XMLHttpRequest-LOADING">LOADING</span> or
+   <span title="dom-XMLHttpRequest-DONE">DONE</span>,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.
+
+   <li><p>If parsing <var title>mime</var> analogously to the value of
+   the <code>Content-Type</code> header fails,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> a JavaScript <code data-anolis-spec=webidl>TypeError</code>.
+
+   <li><p>If <var title>mime</var> is successfully parsed, set
+   <span>override MIME type</span> to its MIME type,
+   excluding any parameters, and
+   <span data-anolis-spec=dom>converted to ASCII lowercase</span>.
+
+   <li><p>If a <code>charset</code> parameter is successfully parsed, set
+   <span>override charset</span> to its value.</p></li>
+  </ol>
+
+
+
+  <h4>The <code title>responseType</code> attribute</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-responseType>responseType</code><code> [ = <var title>value</var> ]</code>
+   <dd>
+    <p>Returns the response type.</p>
+    <p>Can be set to change the response type. Values are:
+    the empty string (default),
+    "<code title>arraybuffer</code>",
+    "<code title>blob</code>",
+    "<code title>document</code>", and
+    "<code title>text</code>".</p>
+    <p>When set: setting to "<code title>document</code>" is ignored if the
+    <span data-anolis-spec=html>JavaScript global environment</span> is a
+    <span data-anolis-spec=html>worker environment</span>
+    <p>When set: throws an
+    "<code data-anolis-spec=dom>InvalidStateError</code>" exception if the
+    state is <span title="dom-XMLHttpRequest-LOADING">LOADING</span> or
+    <span title="dom-XMLHttpRequest-DONE">DONE</span>.
+    <p>When set: throws an
+    "<code data-anolis-spec=dom>InvalidAccessError</code>" exception if the
+    <span>synchronous flag</span> is set and the
+    <span data-anolis-spec=html>JavaScript global environment</span> is a
+    <span data-anolis-spec=html>document environment</span>.
+  </dl>
+
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-responseType"><code>responseType</code></dfn>
+  attribute must return its value. Initially its value must be the empty
+  string.
+
+  <p>Setting the
+  <code title="dom-XMLHttpRequest-responseType">responseType</code>
+  attribute must run these steps:
+
+  <ol>
+   <li><p>If the state is
+   <span title="dom-XMLHttpRequest-LOADING">LOADING</span> or
+   <span title="dom-XMLHttpRequest-DONE">DONE</span>,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.
+
+   <li><p>If the
+   <span data-anolis-spec=html>JavaScript global environment</span> is a
+   <span data-anolis-spec=html>document environment</span> and the
+   <span>synchronous flag</span> is set,
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidAccessError</code>" exception.
+
+   <li><p>If the
+   <span data-anolis-spec=html>JavaScript global environment</span> is a
+   <span data-anolis-spec=html>worker environment</span> and the given
+   value is "<code title>document</code>", terminate these steps.
+
+   <li><p>Set the
+   <code title="dom-XMLHttpRequest-responseType">responseType</code>
+   attribute's value to the given value.</p></li>
+  </ol>
+
+
+
+
+  <h4>The <code title>response</code> attribute</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-response>response</span></code>
+   <dd><p>Returns the <span>response entity body</span>.
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-response"><code>response</code></dfn>
+  attribute must return the result of running these
+  steps:</p>
+
+  <dl class=switch>
+   <dt>If <code title="dom-XMLHttpRequest-responseType">responseType</code>
+   is the empty string or "<code title>text</code>"</dt>
+   <dd>
+    <ol>
+     <li><p>If the state is not
+     <span title="dom-XMLHttpRequest-LOADING">LOADING</span> or
+     <span title="dom-XMLHttpRequest-DONE">DONE</span>, return the empty string.</p></li>
+
+     <li><p>If the <span>error flag</span> is set, return the empty string.</p></li>
+
+     <li><p>Return the <span>text response entity body</span>.</p></li>
+    </ol>
+   </dd>
+   <dt>Otherwise</dt>
+   <dd>
+    <ol>
+     <li><p>If the state is not
+     <span title="dom-XMLHttpRequest-DONE">DONE</span>, return null.</p></li>
+
+     <li><p>If the <span>error flag</span> is set, return null.</p></li>
+
+     <li>
+      <dl class=switch>
+       <dt>If
+       <code title="dom-XMLHttpRequest-responseType">responseType</code> is
+       "<code title>arraybuffer</code>"</dt>
+       <dd><p>Return the
+       <span>arraybuffer response entity body</span>.</p></dd>
+
+       <dt>If
+       <code title="dom-XMLHttpRequest-responseType">responseType</code> is
+       "<code title>blob</code>"</dt>
+       <dd><p>Return the
+       <span>blob response entity body</span>.</p></dd>
+
+       <dt>If
+       <code title="dom-XMLHttpRequest-responseType">responseType</code> is
+       "<code title>document</code>"</dt>
+       <dd><p>Return the
+       <span>document response entity body</span>.</p></dd>
+      </dl>
+     </li>
+    </ol>
+   </dd>
+  </dl>
+
+
+
+  <h4>The <code title>responseText</code> attribute</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title="dom-XMLHttpRequest-responseText">responseText</span></code>
+   <dd>
+    <p>Returns the <span>text response entity body</span>.
+
+    <p>Throws an "<code data-anolis-spec=dom>InvalidStateError</code>"
+    exception if
+    <code title="dom-XMLHttpRequest-responseType">responseType</code> is not
+    the empty string or "<code title>text</code>".
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-responseText"><code>responseText</code></dfn>
+  attribute must return the result of running these
+  steps:</p>
+
+  <ol>
+
+   <li><p>If
+   <code title="dom-XMLHttpRequest-responseType">responseType</code> is not
+   the empty string or "<code title>text</code>",
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.
+
+
+   <li><p>If the state is not
+   <span title="dom-XMLHttpRequest-LOADING">LOADING</span> or
+   <span title="dom-XMLHttpRequest-DONE">DONE</span>, return the empty string.</p></li>
+
+   <li><p>If the <span>error flag</span> is set, return the empty string.</p></li>
+
+   <li><p>Return the <span>text response entity body</span>.</p></li>
+  </ol>
+
+
+  <h4>The <code title>responseXML</code> attribute</h4>
+
+  <dl class=domintro>
+   <dt><code><var title>client</var> . <span title=dom-XMLHttpRequest-responseXML>responseXML</span></code>
+   <dd>
+    <p>Returns the <span>document response entity body</span>.</p>
+
+    <p>Throws an "<code data-anolis-spec=dom>InvalidStateError</code>"
+    exception if
+    <code title="dom-XMLHttpRequest-responseType">responseType</code> is not
+    the empty string or "<code title>document</code>".
+  </dl>
+
+  <p>The
+  <dfn title="dom-XMLHttpRequest-responseXML"><code>responseXML</code></dfn>
+  attribute must return the result of running these steps:</p>
+
+  <ol>
+
+   <li><p>If
+   <code title="dom-XMLHttpRequest-responseType">responseType</code> is not
+   the empty string or "<code title>document</code>",
+   <span data-anolis-spec=dom title=concept-throw>throw</span> an
+   "<code data-anolis-spec=dom>InvalidStateError</code>" exception.</p></li>
+
+
+   <li><p>If the state is not
+   <span title="dom-XMLHttpRequest-DONE">DONE</span>, return null.
+
+   <li><p>If the <span>error flag</span> is set, return null.
+
+   <li><p>Return the <span>document response entity body</span>.</p></li>
+  </ol>
+
+
+  <p class=note>The
+  <code title="dom-XMLHttpRequest-responseXML">responseXML</code> attribute
+  has XML in its name for historical reasons. It also returns HTML resources
+  as documents.</p>
+
+
+  <h3 id="events">Events summary</h3>
+
+  <p><em>This section is non-normative.</em></p>
+
+  <p>The following events are dispatched on <code>XMLHttpRequest</code>
+  and/or <code>XMLHttpRequestUpload</code> objects:</p>
+
+  <table>
+   <thead>
+    <tr>
+     <th>Event name</th>
+     <th>Interface</th>
+     <th>Dispatched when&hellip;</th>
+    </tr>
+   </thead>
+   <tbody>
+    <tr>
+     <td><dfn title="event-xhr-readystatechange"><code>readystatechange</code></dfn></td>
+     <td><code data-anolis-spec=dom>Event</code></td>
+     <td>The <code title="dom-XMLHttpRequest-readyState">readyState</code> attribute changes
+     value, except when it changes to <span title=dom-XMLHttpRequest-UNSENT>UNSENT</span>.
+    </tr>
+    <tr>
+     <td><dfn title="event-xhr-loadstart"><code>loadstart</code></dfn></td>
+     <td><code data-anolis-spec=progress-events>ProgressEvent</code></td>
+     <td>The request starts.</td>
+    </tr>
+    <tr>
+     <td><dfn title="event-xhr-progress"><code>progress</code></dfn></td>
+     <td><code data-anolis-spec=progress-events>ProgressEvent</code></td>
+     <td>Transmitting data.</td>
+    </tr>
+    <tr>
+     <td><dfn title="event-xhr-abort"><code>abort</code></dfn></td>
+     <td><code data-anolis-spec=progress-events>ProgressEvent</code></td>
+     <td>The request has been aborted. For instance, by invoking the
+     <code title="dom-XMLHttpRequest-abort">abort()</code> method.</td>
+    </tr>
+    <tr>
+     <td><dfn title="event-xhr-error"><code>error</code></dfn></td>
+     <td><code data-anolis-spec=progress-events>ProgressEvent</code></td>
+     <td>The request has failed.</td>
+    </tr>
+    <tr>
+     <td><dfn title="event-xhr-load"><code>load</code></dfn></td>
+     <td><code data-anolis-spec=progress-events>ProgressEvent</code></td>
+     <td>The request has successfully completed.</td>
+    </tr>
+    <tr>
+     <td><dfn title="event-xhr-timeout"><code>timeout</code></dfn></td>
+     <td><code data-anolis-spec=progress-events>ProgressEvent</code></td>
+     <td>The author specified timeout has passed before the request
+     completed.</td>
+    </tr>
+    <tr>
+     <td><dfn title="event-xhr-loadend"><code>loadend</code></dfn></td>
+     <td><code data-anolis-spec=progress-events>ProgressEvent</code></td>
+     <td>The request has completed (either in success or failure).</td>
+    </tr>
+   </tbody>
+  </table>
+
+
+
+<h2>Interface <code title>FormData</code></h2>
+
+<pre class="idl">[<span title="dom-FormData">Constructor</span>(optional <span data-anolis-spec=html>HTMLFormElement</span> <var>form</var>)]
+interface <dfn>FormData</dfn> {
+  void <span title="dom-FormData-append">append</span>([EnsureUTF16] DOMString <var>name</var>, <span data-anolis-spec=fileapi>Blob</span> <var>value</var>, optional [EnsureUTF16] DOMString <var>filename</var>);
+  void <span title="dom-FormData-append">append</span>([EnsureUTF16] DOMString <var>name</var>, [EnsureUTF16] DOMString <var>value</var>); 
+};</pre>
+
+<p>If the <span data-anolis-spec=html>JavaScript global environment</span> is a
+<span data-anolis-spec=html>worker environment</span>, <code>FormData</code> must be
+<span data-anolis-spec=html>exposed to JavaScript</span> as if the constructor part of the
+IDL reads <code title>[Constructor]</code> (i.e. has no arguments).
+<!-- maybe move this into IDL at some point -->
+
+<p>The <code>FormData</code> object represents an ordered list of
+<dfn title=concept-FormData-entry>entries</dfn>. Each
+<span title=concept-FormData-entry>entry</span> consists of a
+<dfn title=concept-FormData-entry-name>name</dfn> and a
+<dfn title=concept-FormData-entry-value>value</dfn>.
+
+<p>For the purposes of interaction with other algorithms, an
+<span title=concept-FormData-entry>entry</span>'s type is "string" if
+<span title=concept-FormData-entry-value>value</span> is a string and "file" otherwise. If
+an <span title=concept-FormData-entry>entry</span>'s type is "file", its filename is the
+value of <span title=concept-FormData-entry>entry</span>'s
+<span title=concept-FormData-entry-value>value</span>'s
+<code data-anolis-spec=fileapi title=dom-File-name>name</code> attribute.
+
+<dl class=domintro>
+ <dt><code><var title>fd</var> = new <span title="dom-FormData">FormData</span>([<var title>form</var>])</code>
+ <dd><p>Returns a new <code>FormData</code> object, optionally initialized with the
+ <span title=concept-FormData-entry>entries</span> from <var title>form</var> (if given).
+
+ <dt><code><var title>fd</var> . <span title=dom-FormData-append>append</span>(<var title>name</var>, <var title>value</var> [, <var title>filename</var>])</code>
+ <dd><p>Appends a new <span title=concept-FormData-entry>entry</span> to the
+ <code>FormData</code> object. 
+</dl>
+
+  <p>The
+  <dfn title="dom-FormData"><code>FormData(<var>form</var>)</code></dfn>
+  constructor must run these steps:
+
+  <ol>
+   <li><p>Let <var title>fd</var> be a new <code>FormData</code> object.
+
+   <li><p>If <var>form</var> is given, set <var title>fd</var>'s
+   <span title=concept-FormData-entry>entries</span> to the result of
+   <span data-anolis-spec=html>constructing the form data set</span> for <var>form</var>.
+
+   <li><p>Return <var title>fd</var>.
+  </ol>
+
+<p>The
+<dfn title="dom-FormData-append" id="dom-formdata-append"><code>append(<var>name</var>, <var>value</var>, <var>filename</var>)</code></dfn>
+method must run these steps:
+
+<ol>
+ <li><p>Let <var title>entry</var> be a new
+ <span title=concept-FormData-entry>entry</span>.
+
+ <li><p>Set <var title>entry</var>'s <span title=concept-FormData-entry-name>name</span>
+ to <var>name</var>.
+
+ <li><p>If <var>value</var> is a <code data-anolis-spec=fileapi>Blob</code>, set
+ <var>value</var> to a new <code data-anolis-spec=fileapi>File</code> object whose
+ <code data-anolis-spec=fileapi title=dom-File-name>name</code> attribute value is
+ "<code title>blob</code>". 
+
+ <li><p>If <var>value</var> is a <code data-anolis-spec=fileapi>File</code> and
+ <var title>filename</var> is given, set <var>value</var>'s
+ <code data-anolis-spec=fileapi title=dom-File-name>name</code> attribute value to
+ <var title>filename</var>.
+
+ <li><p>Set <var title>entry</var>'s <span title=concept-FormData-entry-value>value</span>
+ to <var>value</var>. 
+
+ <li><p>Append <var title>entry</var> to <code>FormData</code> object's list of
+ <span title=concept-FormData-entry>entries</span>.
+</ol> 
+
+<h2 class=no-num>References</h2>
+<div id=anolis-references></div>
+
+
+  <h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
+
+  <p>The editor would like to thank
+
+  Addison Phillips,
+  Ahmed Kamel,
+  Alex Hopmann,
+  Alex Vincent,
+  Alexey Proskuryakov,
+  Andrea Marchesini,
+  Asbj&oslash;rn Ulsberg,
+  Boris Zbarsky,
+  Bj&ouml;rn H&ouml;hrmann,
+  Cameron McCormack,
+  Chris Marrin,
+  Christophe Jolif,
+  Charles McCathieNevile,
+  Dan Winship,
+  David Andersson,
+  David Flanagan,
+  David H&aring;s&auml;ther,
+  David Levin,
+  Dean Jackson,
+  Denis Sureau,
+  Dominik Röttsches,
+  Doug Schepers,
+  Douglas Livingstone,
+  Elliott Sprehn,
+  Elliotte Harold,
+  Eric Lawrence,
+  Eric Uhrhane,
+  Erik Dahlstr&ouml;m,
+  Geoffrey Sneddon,
+  Gideon Cohn,
+  Glenn Adams,
+  Gorm Haug Eriksen,
+  H&aring;kon Wium Lie,
+  Hallvord R. M. Steen,
+  Henri Sivonen,
+  Huub Schaeks,
+  Ian Davis,
+  Ian Hickson,
+  Ivan Herman,
+  Jarred Nicholls,
+  Jeff Walden,
+  Jens Lindstr&ouml;m,
+  Jim Deegan,
+  Jim Ley,
+  Joe Farro,
+  Jonas Sicking,
+  Julian Reschke,
+  呂康豪 (Kang-Hao Lu),
+  Karl Dubost,
+  Lachlan Hunt,
+  Maciej Stachowiak,
+  Magnus Kristiansen,
+  Marc Hadley,
+  Marcos Caceres,
+  Mark Baker,
+  Mark Birbeck,
+  Mark Nottingham,
+  Mark S. Miller,
+  Martin Hassman,
+  Mohamed Zergaoui,
+  Ms2ger,
+  Odin H&oslash;rthe Omdal,
+  Olli Pettay,
+  Pawel Glowacki,
+  Peter Michaux,
+  Philip Taylor,
+  Robin Berjon,
+  Rune Halvorsen,
+  Ruud Steltenpool,
+  Sergiu Dumitriu,
+  Sigbj&oslash;rn Finne,
+  Simon Pieters,
+  Stewart Brodie,
+  Sunava Dutta,
+  Thomas Roessler,
+  Tom Magliery,
+  Yehuda Katz, and
+  Zhenbin Xu
+
+  for their contributions to this specification.</p>
+
+  <p>Special thanks to the Microsoft employees who first implemented the
+  <code title>XMLHttpRequest</code> interface, which was first widely
+  deployed by the Windows Internet Explorer browser.</p>
+
+  <p>Special thanks also to the WHATWG for drafting an initial version of
+  this specification in their Web Applications 1.0 document (now renamed to
+  HTML). <span data-anolis-ref>HTML</span></p>
+
+  <p>Special thanks to Anne van Kesteren who has provided nearly all the contents until he stepped down as a W3C editor and is now in succession providing discussions and contents as the editor of the XMLHttpRequest Living Standard in WHATWG which this version of the specification pursues convergence.</p>
+
+  <p>Thanks also to all those who have helped to improve this specification
+  by sending suggestions and corrections. (Please, keep bugging us with your
+  issues!)</p>
+ </body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/xhr-1/README.markdown	Wed Oct 23 21:47:37 2013 +0900
@@ -0,0 +1,1 @@
+The repository for [XMLHttpRequest Level 1] (http://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html).
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/xhr-1/data/RFCs.json	Wed Oct 23 21:47:37 2013 +0900
@@ -0,0 +1,32636 @@
+{
+  "RFC1": {
+    "title": "Host Software",
+    "href": "http://tools.ietf.org/html/rfc1",
+    "authors": ["S. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC2": {
+    "title": "Host software",
+    "href": "http://tools.ietf.org/html/rfc2",
+    "authors": ["B. Duvall"],
+    "publisher": "IETF"
+  },
+  "RFC3": {
+    "title": "Documentation conventions",
+    "href": "http://tools.ietf.org/html/rfc3",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC4": {
+    "title": "Network timetable",
+    "href": "http://tools.ietf.org/html/rfc4",
+    "authors": ["E.B. Shapiro"],
+    "publisher": "IETF"
+  },
+  "RFC5": {
+    "title": "Decode Encode Language (DEL)",
+    "href": "http://tools.ietf.org/html/rfc5",
+    "authors": ["J. Rulifson"],
+    "publisher": "IETF"
+  },
+  "RFC6": {
+    "title": "Conversation with Bob Kahn",
+    "href": "http://tools.ietf.org/html/rfc6",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC7": {
+    "title": "Host-IMP interface",
+    "href": "http://tools.ietf.org/html/rfc7",
+    "authors": ["G. Deloche"],
+    "publisher": "IETF"
+  },
+  "RFC8": {
+    "title": "ARPA Network Functional Specifications",
+    "href": "http://tools.ietf.org/html/rfc8",
+    "authors": ["G. Deloche"],
+    "publisher": "IETF"
+  },
+  "RFC9": {
+    "title": "Host Software",
+    "href": "http://tools.ietf.org/html/rfc9",
+    "authors": ["G. Deloche"],
+    "publisher": "IETF"
+  },
+  "RFC10": {
+    "title": "Documentation conventions",
+    "href": "http://tools.ietf.org/html/rfc10",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC11": {
+    "title": "Implementation of the Host - Host Software Procedures in GORDO",
+    "href": "http://tools.ietf.org/html/rfc11",
+    "authors": ["G. Deloche"],
+    "publisher": "IETF"
+  },
+  "RFC12": {
+    "title": "IMP-Host interface flow diagrams",
+    "href": "http://tools.ietf.org/html/rfc12",
+    "authors": ["M. Wingfield"],
+    "publisher": "IETF"
+  },
+  "RFC13": {
+    "title": "Zero Text Length EOF Message",
+    "href": "http://tools.ietf.org/html/rfc13",
+    "authors": ["V. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC15": {
+    "title": "Network subsystem for time sharing hosts",
+    "href": "http://tools.ietf.org/html/rfc15",
+    "authors": ["C.S. Carr"],
+    "publisher": "IETF"
+  },
+  "RFC16": {
+    "title": "M.I.T",
+    "href": "http://tools.ietf.org/html/rfc16",
+    "authors": ["S. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC17": {
+    "title": "Some questions re: Host-IMP Protocol",
+    "href": "http://tools.ietf.org/html/rfc17",
+    "authors": ["J.E. Kreznar"],
+    "publisher": "IETF"
+  },
+  "RFC18": {
+    "title": "IMP-IMP and HOST-HOST Control Links",
+    "href": "http://tools.ietf.org/html/rfc18",
+    "authors": ["V. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC19": {
+    "title": "Two protocol suggestions to reduce congestion at swap bound nodes",
+    "href": "http://tools.ietf.org/html/rfc19",
+    "authors": ["J.E. Kreznar"],
+    "publisher": "IETF"
+  },
+  "RFC20": {
+    "title": "ASCII format for network interchange",
+    "href": "http://tools.ietf.org/html/rfc20",
+    "authors": ["V.G. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC21": {
+    "title": "Network meeting",
+    "href": "http://tools.ietf.org/html/rfc21",
+    "authors": ["V.G. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC22": {
+    "title": "Host-host control message formats",
+    "href": "http://tools.ietf.org/html/rfc22",
+    "authors": ["V.G. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC23": {
+    "title": "Transmission of Multiple Control Messages",
+    "href": "http://tools.ietf.org/html/rfc23",
+    "authors": ["G. Gregg"],
+    "publisher": "IETF"
+  },
+  "RFC24": {
+    "title": "Documentation Conventions",
+    "href": "http://tools.ietf.org/html/rfc24",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC25": {
+    "title": "No High Link Numbers",
+    "href": "http://tools.ietf.org/html/rfc25",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC27": {
+    "title": "Documentation Conventions",
+    "href": "http://tools.ietf.org/html/rfc27",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC28": {
+    "title": "Time Standards",
+    "href": "http://tools.ietf.org/html/rfc28",
+    "authors": ["W.K. English"],
+    "publisher": "IETF"
+  },
+  "RFC29": {
+    "title": "Response to RFC 28",
+    "href": "http://tools.ietf.org/html/rfc29",
+    "authors": ["R.E. Kahn"],
+    "publisher": "IETF"
+  },
+  "RFC30": {
+    "title": "Documentation Conventions",
+    "href": "http://tools.ietf.org/html/rfc30",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC31": {
+    "title": "Binary Message Forms in Computer",
+    "href": "http://tools.ietf.org/html/rfc31",
+    "authors": ["D. Bobrow", "W.R. Sutherland"],
+    "publisher": "IETF"
+  },
+  "RFC32": {
+    "title": "Some Thoughts on SRI's Proposed Real Time Clock",
+    "href": "http://tools.ietf.org/html/rfc32",
+    "authors": ["J. Cole"],
+    "publisher": "IETF"
+  },
+  "RFC33": {
+    "title": "New Host-Host Protocol",
+    "href": "http://tools.ietf.org/html/rfc33",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC34": {
+    "title": "Some Brief Preliminary Notes on the Augmentation Research Center Clock",
+    "href": "http://tools.ietf.org/html/rfc34",
+    "authors": ["W.K. English"],
+    "publisher": "IETF"
+  },
+  "RFC35": {
+    "title": "Network Meeting",
+    "href": "http://tools.ietf.org/html/rfc35",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC36": {
+    "title": "Protocol Notes",
+    "href": "http://tools.ietf.org/html/rfc36",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC37": {
+    "title": "Network Meeting Epilogue, etc",
+    "href": "http://tools.ietf.org/html/rfc37",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC38": {
+    "title": "Comments on Network Protocol from NWG/RFC #36",
+    "href": "http://tools.ietf.org/html/rfc38",
+    "authors": ["S.M. Wolfe"],
+    "publisher": "IETF"
+  },
+  "RFC39": {
+    "title": "Comments on Protocol Re: NWG/RFC #36",
+    "href": "http://tools.ietf.org/html/rfc39",
+    "authors": ["E. Harslem", "J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC40": {
+    "title": "More Comments on the Forthcoming Protocol",
+    "href": "http://tools.ietf.org/html/rfc40",
+    "authors": ["E. Harslem", "J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC41": {
+    "title": "IMP-IMP Teletype Communication",
+    "href": "http://tools.ietf.org/html/rfc41",
+    "authors": ["J.T. Melvin"],
+    "publisher": "IETF"
+  },
+  "RFC42": {
+    "title": "Message Data Types",
+    "href": "http://tools.ietf.org/html/rfc42",
+    "authors": ["E. Ancona"],
+    "publisher": "IETF"
+  },
+  "RFC43": {
+    "title": "Proposed Meeting",
+    "href": "http://tools.ietf.org/html/rfc43",
+    "authors": ["A.G. Nemeth"],
+    "publisher": "IETF"
+  },
+  "RFC44": {
+    "title": "Comments on NWG/RFC 33 and 36",
+    "href": "http://tools.ietf.org/html/rfc44",
+    "authors": ["A. Shoshani", "R. Long", "A. Landsberg"],
+    "publisher": "IETF"
+  },
+  "RFC45": {
+    "title": "New Protocol is Coming",
+    "href": "http://tools.ietf.org/html/rfc45",
+    "authors": ["J. Postel", "S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC46": {
+    "title": "ARPA Network protocol notes",
+    "href": "http://tools.ietf.org/html/rfc46",
+    "authors": ["E. Meyer"],
+    "publisher": "IETF"
+  },
+  "RFC47": {
+    "title": "BBN's Comments on NWG/RFC #33",
+    "href": "http://tools.ietf.org/html/rfc47",
+    "authors": ["J. Postel", "S. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC48": {
+    "title": "Possible protocol plateau",
+    "href": "http://tools.ietf.org/html/rfc48",
+    "authors": ["J. Postel", "S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC49": {
+    "title": "Conversations with S",
+    "href": "http://tools.ietf.org/html/rfc49",
+    "authors": ["Crocker (UCLA). E. Meyer"],
+    "publisher": "IETF"
+  },
+  "RFC50": {
+    "title": "Comments on the Meyer Proposal",
+    "href": "http://tools.ietf.org/html/rfc50",
+    "authors": ["E. Harslen", "J. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC51": {
+    "title": "Proposal for a Network Interchange Language",
+    "href": "http://tools.ietf.org/html/rfc51",
+    "authors": ["M. Elie"],
+    "publisher": "IETF"
+  },
+  "RFC52": {
+    "title": "Updated distribution list",
+    "href": "http://tools.ietf.org/html/rfc52",
+    "authors": ["J. Postel", "S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC53": {
+    "title": "Official protocol mechanism",
+    "href": "http://tools.ietf.org/html/rfc53",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC54": {
+    "title": "Official Protocol Proffering",
+    "href": "http://tools.ietf.org/html/rfc54",
+    "authors": ["S.D. Crocker", "J. Postel", "J. Newkirk", "M. Kraley"],
+    "publisher": "IETF"
+  },
+  "RFC55": {
+    "title": "Prototypical implementation of the NCP",
+    "href": "http://tools.ietf.org/html/rfc55",
+    "authors": ["J. Newkirk", "M. Kraley", "J. Postel", "S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC56": {
+    "title": "Third Level Protocol: Logger Protocol",
+    "href": "http://tools.ietf.org/html/rfc56",
+    "authors": ["E. Belove", "D. Black", "R. Flegal", "L.G. Farquar"],
+    "publisher": "IETF"
+  },
+  "RFC57": {
+    "title": "Thoughts and Reflections on NWG/RFC 54",
+    "href": "http://tools.ietf.org/html/rfc57",
+    "authors": ["M. Kraley", "J. Newkirk"],
+    "publisher": "IETF"
+  },
+  "RFC58": {
+    "title": "Logical Message Synchronization",
+    "href": "http://tools.ietf.org/html/rfc58",
+    "authors": ["T.P. Skinner"],
+    "publisher": "IETF"
+  },
+  "RFC59": {
+    "title": "Flow Control - Fixed Versus Demand Allocation",
+    "href": "http://tools.ietf.org/html/rfc59",
+    "authors": ["E. Meyer"],
+    "publisher": "IETF"
+  },
+  "RFC60": {
+    "title": "Simplified NCP Protocol",
+    "href": "http://tools.ietf.org/html/rfc60",
+    "authors": ["R.B. Kalin"],
+    "publisher": "IETF"
+  },
+  "RFC61": {
+    "title": "Note on Interprocess Communication in a Resource Sharing Computer Network",
+    "href": "http://tools.ietf.org/html/rfc61",
+    "authors": ["D.C. Walden"],
+    "publisher": "IETF"
+  },
+  "RFC62": {
+    "title": "Systems for Interprocess Communication in a Resource Sharing Computer Network",
+    "href": "http://tools.ietf.org/html/rfc62",
+    "authors": ["D.C. Walden"],
+    "publisher": "IETF"
+  },
+  "RFC63": {
+    "title": "Belated Network Meeting Report",
+    "href": "http://tools.ietf.org/html/rfc63",
+    "authors": ["V.G. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC64": {
+    "title": "Getting rid of marking",
+    "href": "http://tools.ietf.org/html/rfc64",
+    "authors": ["M. Elie"],
+    "publisher": "IETF"
+  },
+  "RFC65": {
+    "title": "Comments on Host/Host Protocol document #1",
+    "href": "http://tools.ietf.org/html/rfc65",
+    "authors": ["D.C. Walden"],
+    "publisher": "IETF"
+  },
+  "RFC66": {
+    "title": "NIC - third level ideas and other noise",
+    "href": "http://tools.ietf.org/html/rfc66",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC67": {
+    "title": "Proposed Change to Host/IMP Spec to Eliminate Marking",
+    "href": "http://tools.ietf.org/html/rfc67",
+    "authors": ["W.R. Crowther"],
+    "publisher": "IETF"
+  },
+  "RFC68": {
+    "title": "Comments on Memory Allocation Control Commands: CEASE, ALL, GVB, RET, and RFNM",
+    "href": "http://tools.ietf.org/html/rfc68",
+    "authors": ["M. Elie"],
+    "publisher": "IETF"
+  },
+  "RFC69": {
+    "title": "Distribution List Change for MIT",
+    "href": "http://tools.ietf.org/html/rfc69",
+    "authors": ["A.K. Bhushan"],
+    "publisher": "IETF"
+  },
+  "RFC70": {
+    "title": "Note on Padding",
+    "href": "http://tools.ietf.org/html/rfc70",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC71": {
+    "title": "Reallocation in Case of Input Error",
+    "href": "http://tools.ietf.org/html/rfc71",
+    "authors": ["T. Schipper"],
+    "publisher": "IETF"
+  },
+  "RFC72": {
+    "title": "Proposed Moratorium on Changes to Network Protocol",
+    "href": "http://tools.ietf.org/html/rfc72",
+    "authors": ["R.D. Bressler"],
+    "publisher": "IETF"
+  },
+  "RFC73": {
+    "title": "Response to NWG/RFC 67",
+    "href": "http://tools.ietf.org/html/rfc73",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC74": {
+    "title": "Specifications for Network Use of the UCSB On-Line System",
+    "href": "http://tools.ietf.org/html/rfc74",
+    "authors": ["J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC75": {
+    "title": "Network Meeting",
+    "href": "http://tools.ietf.org/html/rfc75",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC76": {
+    "title": "Connection by name: User oriented protocol",
+    "href": "http://tools.ietf.org/html/rfc76",
+    "authors": ["J. Bouknight", "J. Madden", "G.R. Grossman"],
+    "publisher": "IETF"
+  },
+  "RFC77": {
+    "title": "Network meeting report",
+    "href": "http://tools.ietf.org/html/rfc77",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC78": {
+    "title": "NCP Status Report: UCSB/Rand",
+    "href": "http://tools.ietf.org/html/rfc78",
+    "authors": ["E. Harslem", "J.F. Heafner", "J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC79": {
+    "title": "Logger Protocol error",
+    "href": "http://tools.ietf.org/html/rfc79",
+    "authors": ["E. Meyer"],
+    "publisher": "IETF"
+  },
+  "RFC80": {
+    "title": "Protocols and Data Formats",
+    "href": "http://tools.ietf.org/html/rfc80",
+    "authors": ["E. Harslem", "J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC81": {
+    "title": "Request for Reference Information",
+    "href": "http://tools.ietf.org/html/rfc81",
+    "authors": ["J. Bouknight"],
+    "publisher": "IETF"
+  },
+  "RFC82": {
+    "title": "Network Meeting Notes",
+    "href": "http://tools.ietf.org/html/rfc82",
+    "authors": ["E. Meyer"],
+    "publisher": "IETF"
+  },
+  "RFC83": {
+    "title": "Language-machine for data reconfiguration",
+    "href": "http://tools.ietf.org/html/rfc83",
+    "authors": ["R.H. Anderson", "E. Harslem", "J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC84": {
+    "title": "List of NWG/RFC's 1-80",
+    "href": "http://tools.ietf.org/html/rfc84",
+    "authors": ["J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC85": {
+    "title": "Network Working Group meeting",
+    "href": "http://tools.ietf.org/html/rfc85",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC86": {
+    "title": "Proposal for a Network Standard Format for a Data Stream to Control Graphics Display",
+    "href": "http://tools.ietf.org/html/rfc86",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC87": {
+    "title": "Topic for Discussion at the Next Network Working Group Meeting",
+    "href": "http://tools.ietf.org/html/rfc87",
+    "authors": ["A. Vezza"],
+    "publisher": "IETF"
+  },
+  "RFC88": {
+    "title": "NETRJS: A third level protocol for Remote Job Entry",
+    "href": "http://tools.ietf.org/html/rfc88",
+    "authors": ["R.T. Braden", "S.M. Wolfe"],
+    "publisher": "IETF"
+  },
+  "RFC89": {
+    "title": "Some historic moments in networking",
+    "href": "http://tools.ietf.org/html/rfc89",
+    "authors": ["R.M. Metcalfe"],
+    "publisher": "IETF"
+  },
+  "RFC90": {
+    "title": "CCN as a Network Service Center",
+    "href": "http://tools.ietf.org/html/rfc90",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC91": {
+    "title": "Proposed User-User Protocol",
+    "href": "http://tools.ietf.org/html/rfc91",
+    "authors": ["G.H. Mealy"],
+    "publisher": "IETF"
+  },
+  "RFC93": {
+    "title": "Initial Connection Protocol",
+    "href": "http://tools.ietf.org/html/rfc93",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC94": {
+    "title": "Some thoughts on Network Graphics",
+    "href": "http://tools.ietf.org/html/rfc94",
+    "authors": ["E. Harslem", "J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC95": {
+    "title": "Distribution of NWG/RFC's through the NIC",
+    "href": "http://tools.ietf.org/html/rfc95",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC96": {
+    "title": "An Interactive Network Experiment to Study Modes of Access the Network Information Center",
+    "href": "http://tools.ietf.org/html/rfc96",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC97": {
+    "title": "First Cut at a Proposed Telnet Protocol",
+    "href": "http://tools.ietf.org/html/rfc97",
+    "authors": ["J.T. Melvin", "R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC98": {
+    "title": "Logger Protocol Proposal",
+    "href": "http://tools.ietf.org/html/rfc98",
+    "authors": ["E. Meyer", "T. Skinner"],
+    "publisher": "IETF"
+  },
+  "RFC99": {
+    "title": "Network Meeting",
+    "href": "http://tools.ietf.org/html/rfc99",
+    "authors": ["P.M. Karp"],
+    "publisher": "IETF"
+  },
+  "RFC100": {
+    "title": "Categorization and guide to NWG/RFCs",
+    "href": "http://tools.ietf.org/html/rfc100",
+    "authors": ["P.M. Karp"],
+    "publisher": "IETF"
+  },
+  "RFC101": {
+    "title": "Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971",
+    "href": "http://tools.ietf.org/html/rfc101",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC102": {
+    "title": "Output of the Host-Host Protocol glitch cleaning committee",
+    "href": "http://tools.ietf.org/html/rfc102",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC103": {
+    "title": "Implementation of Interrupt Keys",
+    "href": "http://tools.ietf.org/html/rfc103",
+    "authors": ["R.B. Kalin"],
+    "publisher": "IETF"
+  },
+  "RFC104": {
+    "title": "Link 191",
+    "href": "http://tools.ietf.org/html/rfc104",
+    "authors": ["J.B. Postel", "S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC105": {
+    "title": "Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB",
+    "href": "http://tools.ietf.org/html/rfc105",
+    "authors": ["J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC106": {
+    "title": "User/Server Site Protocol Network Host Questionnaire",
+    "href": "http://tools.ietf.org/html/rfc106",
+    "authors": ["T.C. O'Sullivan"],
+    "publisher": "IETF"
+  },
+  "RFC107": {
+    "title": "Output of the Host-Host Protocol Glitch Cleaning Committee",
+    "href": "http://tools.ietf.org/html/rfc107",
+    "authors": ["R.D. Bressler", "S.D. Crocker", "W.R. Crowther", "G.R. Grossman", "R.S. Tomlinson", "J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC108": {
+    "title": "Attendance list at the Urbana NWG meeting, February 17-19, 1971",
+    "href": "http://tools.ietf.org/html/rfc108",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC109": {
+    "title": "Level III Server Protocol for the Lincoln Laboratory NIC 360/67 Host",
+    "href": "http://tools.ietf.org/html/rfc109",
+    "authors": ["J.M. Winett"],
+    "publisher": "IETF"
+  },
+  "RFC110": {
+    "title": "Conventions for Using an IBM 2741 Terminal as a User Console for Access to Network Server Hosts",
+    "href": "http://tools.ietf.org/html/rfc110",
+    "authors": ["J.M. Winett"],
+    "publisher": "IETF"
+  },
+  "RFC111": {
+    "title": "Pressure from the Chairman",
+    "href": "http://tools.ietf.org/html/rfc111",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC112": {
+    "title": "User/Server Site Protocol: Network Host Questionnaire",
+    "href": "http://tools.ietf.org/html/rfc112",
+    "authors": ["T.C. O'Sullivan"],
+    "publisher": "IETF"
+  },
+  "RFC113": {
+    "title": "Network activity report: UCSB Rand",
+    "href": "http://tools.ietf.org/html/rfc113",
+    "authors": ["E. Harslem", "J.F. Heafner", "J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC114": {
+    "title": "File Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc114",
+    "authors": ["A.K. Bhushan"],
+    "publisher": "IETF"
+  },
+  "RFC115": {
+    "title": "Some Network Information Center policies on handling documents",
+    "href": "http://tools.ietf.org/html/rfc115",
+    "authors": ["R.W. Watson", "J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC116": {
+    "title": "Structure of the May NWG Meeting",
+    "href": "http://tools.ietf.org/html/rfc116",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC117": {
+    "title": "Some comments on the official protocol",
+    "href": "http://tools.ietf.org/html/rfc117",
+    "authors": ["J. Wong"],
+    "publisher": "IETF"
+  },
+  "RFC118": {
+    "title": "Recommendations for facility documentation",
+    "href": "http://tools.ietf.org/html/rfc118",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC119": {
+    "title": "Network Fortran Subprograms",
+    "href": "http://tools.ietf.org/html/rfc119",
+    "authors": ["M. Krilanovich"],
+    "publisher": "IETF"
+  },
+  "RFC120": {
+    "title": "Network PL1 subprograms",
+    "href": "http://tools.ietf.org/html/rfc120",
+    "authors": ["M. Krilanovich"],
+    "publisher": "IETF"
+  },
+  "RFC121": {
+    "title": "Network on-line operators",
+    "href": "http://tools.ietf.org/html/rfc121",
+    "authors": ["M. Krilanovich"],
+    "publisher": "IETF"
+  },
+  "RFC122": {
+    "title": "Network specifications for UCSB's Simple-Minded File System",
+    "href": "http://tools.ietf.org/html/rfc122",
+    "authors": ["J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC123": {
+    "title": "Proffered Official ICP",
+    "href": "http://tools.ietf.org/html/rfc123",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC124": {
+    "title": "Typographical error in RFC 107",
+    "href": "http://tools.ietf.org/html/rfc124",
+    "authors": ["J.T. Melvin"],
+    "publisher": "IETF"
+  },
+  "RFC125": {
+    "title": "Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream",
+    "href": "http://tools.ietf.org/html/rfc125",
+    "authors": ["J. McConnell"],
+    "publisher": "IETF"
+  },
+  "RFC126": {
+    "title": "Graphics Facilities at Ames Research Center",
+    "href": "http://tools.ietf.org/html/rfc126",
+    "authors": ["J. McConnell"],
+    "publisher": "IETF"
+  },
+  "RFC127": {
+    "title": "Comments on RFC 123",
+    "href": "http://tools.ietf.org/html/rfc127",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC128": {
+    "title": "Bytes",
+    "href": "http://tools.ietf.org/html/rfc128",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC129": {
+    "title": "Request for comments on socket name structure",
+    "href": "http://tools.ietf.org/html/rfc129",
+    "authors": ["E. Harslem", "J. Heafner", "E. Meyer"],
+    "publisher": "IETF"
+  },
+  "RFC130": {
+    "title": "Response to RFC 111: Pressure from the chairman",
+    "href": "http://tools.ietf.org/html/rfc130",
+    "authors": ["J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC131": {
+    "title": "Response to RFC 116: May NWG meeting",
+    "href": "http://tools.ietf.org/html/rfc131",
+    "authors": ["E. Harslem", "J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC132": {
+    "title": "Typographical Error in RFC 107",
+    "href": "http://tools.ietf.org/html/rfc132",
+    "authors": ["J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC133": {
+    "title": "File Transfer and Error Recovery",
+    "href": "http://tools.ietf.org/html/rfc133",
+    "authors": ["R.L. Sunberg"],
+    "publisher": "IETF"
+  },
+  "RFC134": {
+    "title": "Network Graphics meeting",
+    "href": "http://tools.ietf.org/html/rfc134",
+    "authors": ["A. Vezza"],
+    "publisher": "IETF"
+  },
+  "RFC135": {
+    "title": "Response to NWG/RFC 110",
+    "href": "http://tools.ietf.org/html/rfc135",
+    "authors": ["W. Hathaway"],
+    "publisher": "IETF"
+  },
+  "RFC136": {
+    "title": "Host accounting and administrative procedures",
+    "href": "http://tools.ietf.org/html/rfc136",
+    "authors": ["R.E. Kahn"],
+    "publisher": "IETF"
+  },
+  "RFC137": {
+    "title": "Telnet Protocol - a proposed document",
+    "href": "http://tools.ietf.org/html/rfc137",
+    "authors": ["T.C. O'Sullivan"],
+    "publisher": "IETF"
+  },
+  "RFC138": {
+    "title": "Status report on proposed Data Reconfiguration Service",
+    "href": "http://tools.ietf.org/html/rfc138",
+    "authors": ["R.H. Anderson", "V.G. Cerf", "E. Harslem", "J.F. Heafner", "J. Madden", "R.M. Metcalfe", "A. Shoshani", "J.E. White", "D.C.M. Wood"],
+    "publisher": "IETF"
+  },
+  "RFC139": {
+    "title": "Discussion of Telnet Protocol",
+    "href": "http://tools.ietf.org/html/rfc139",
+    "authors": ["T.C. O'Sullivan"],
+    "publisher": "IETF"
+  },
+  "RFC140": {
+    "title": "Agenda for the May NWG meeting",
+    "href": "http://tools.ietf.org/html/rfc140",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC141": {
+    "title": "Comments on RFC 114: A File Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc141",
+    "authors": ["E. Harslem", "J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC142": {
+    "title": "Time-Out Mechanism in the Host-Host Protocol",
+    "href": "http://tools.ietf.org/html/rfc142",
+    "authors": ["C. Kline", "J. Wong"],
+    "publisher": "IETF"
+  },
+  "RFC143": {
+    "title": "Regarding proffered official ICP",
+    "href": "http://tools.ietf.org/html/rfc143",
+    "authors": ["W. Naylor", "J. Wong", "C. Kline", "J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC144": {
+    "title": "Data sharing on computer networks",
+    "href": "http://tools.ietf.org/html/rfc144",
+    "authors": ["A. Shoshani"],
+    "publisher": "IETF"
+  },
+  "RFC145": {
+    "title": "Initial Connection Protocol Control Commands",
+    "href": "http://tools.ietf.org/html/rfc145",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC146": {
+    "title": "Views on issues relevant to data sharing on computer networks",
+    "href": "http://tools.ietf.org/html/rfc146",
+    "authors": ["P.M. Karp", "D.B. McKay", "D.C.M. Wood"],
+    "publisher": "IETF"
+  },
+  "RFC147": {
+    "title": "Definition of a socket",
+    "href": "http://tools.ietf.org/html/rfc147",
+    "authors": ["J.M. Winett"],
+    "publisher": "IETF"
+  },
+  "RFC148": {
+    "title": "Comments on RFC 123",
+    "href": "http://tools.ietf.org/html/rfc148",
+    "authors": ["A.K. Bhushan"],
+    "publisher": "IETF"
+  },
+  "RFC149": {
+    "title": "Best Laid Plans",
+    "href": "http://tools.ietf.org/html/rfc149",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC150": {
+    "title": "Use of IPC Facilities: A Working Paper",
+    "href": "http://tools.ietf.org/html/rfc150",
+    "authors": ["R.B. Kalin"],
+    "publisher": "IETF"
+  },
+  "RFC151": {
+    "title": "Comments on a proffered official ICP: RFCs 123, 127",
+    "href": "http://tools.ietf.org/html/rfc151",
+    "authors": ["A. Shoshani"],
+    "publisher": "IETF"
+  },
+  "RFC152": {
+    "title": "SRI Artificial Intelligence status report",
+    "href": "http://tools.ietf.org/html/rfc152",
+    "authors": ["M. Wilber"],
+    "publisher": "IETF"
+  },
+  "RFC153": {
+    "title": "SRI ARC-NIC status",
+    "href": "http://tools.ietf.org/html/rfc153",
+    "authors": ["J.T. Melvin", "R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC154": {
+    "title": "Exposition Style",
+    "href": "http://tools.ietf.org/html/rfc154",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC155": {
+    "title": "ARPA Network mailing lists",
+    "href": "http://tools.ietf.org/html/rfc155",
+    "authors": ["J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC156": {
+    "title": "Status of the Illinois site: Response to RFC 116",
+    "href": "http://tools.ietf.org/html/rfc156",
+    "authors": ["J. Bouknight"],
+    "publisher": "IETF"
+  },
+  "RFC157": {
+    "title": "Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems",
+    "href": "http://tools.ietf.org/html/rfc157",
+    "authors": ["V.G. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC158": {
+    "title": "Telnet Protocol: A Proposed Document",
+    "href": "http://tools.ietf.org/html/rfc158",
+    "authors": ["T.C. O'Sullivan"],
+    "publisher": "IETF"
+  },
+  "RFC160": {
+    "title": "RFC brief list",
+    "href": "http://tools.ietf.org/html/rfc160",
+    "authors": ["Network Information Center. Stanford Research Institute"],
+    "publisher": "IETF"
+  },
+  "RFC161": {
+    "title": "Solution to the race condition in the ICP",
+    "href": "http://tools.ietf.org/html/rfc161",
+    "authors": ["A. Shoshani"],
+    "publisher": "IETF"
+  },
+  "RFC162": {
+    "title": "NETBUGGER3",
+    "href": "http://tools.ietf.org/html/rfc162",
+    "authors": ["M. Kampe"],
+    "publisher": "IETF"
+  },
+  "RFC163": {
+    "title": "Data transfer protocols",
+    "href": "http://tools.ietf.org/html/rfc163",
+    "authors": ["V.G. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC164": {
+    "title": "Minutes of Network Working Group meeting, 5/16 through 5/19/71",
+    "href": "http://tools.ietf.org/html/rfc164",
+    "authors": ["J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC165": {
+    "title": "Proffered Official Initial Connection Protocol",
+    "href": "http://tools.ietf.org/html/rfc165",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC166": {
+    "title": "Data Reconfiguration Service: An implementation specification",
+    "href": "http://tools.ietf.org/html/rfc166",
+    "authors": ["R.H. Anderson", "V.G. Cerf", "E. Harslem", "J.F. Heafner", "J. Madden", "R.M. Metcalfe", "A. Shoshani", "J.E. White", "D.C.M. Wood"],
+    "publisher": "IETF"
+  },
+  "RFC167": {
+    "title": "Socket conventions reconsidered",
+    "href": "http://tools.ietf.org/html/rfc167",
+    "authors": ["A.K. Bhushan", "R.M. Metcalfe", "J.M. Winett"],
+    "publisher": "IETF"
+  },
+  "RFC168": {
+    "title": "ARPA Network mailing lists",
+    "href": "http://tools.ietf.org/html/rfc168",
+    "authors": ["J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC169": {
+    "title": "COMPUTER NETWORKS",
+    "href": "http://tools.ietf.org/html/rfc169",
+    "authors": ["S.D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC170": {
+    "title": "RFC List by Number",
+    "href": "http://tools.ietf.org/html/rfc170",
+    "authors": ["Network Information Center. Stanford Research Institute"],
+    "publisher": "IETF"
+  },
+  "RFC171": {
+    "title": "The Data Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc171",
+    "authors": ["A. Bhushan", "B. Braden", "W. Crowther", "E. Harslem", "J. Heafner", "A. McKenize", "J. Melvin", "B. Sundberg", "D. Watson", "J. White"],
+    "publisher": "IETF"
+  },
+  "RFC172": {
+    "title": "The File Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc172",
+    "authors": ["A. Bhushan", "B. Braden", "W. Crowther", "E. Harslem", "J. Heafner", "A. McKenzie", "J. Melvin", "B. Sundberg", "D. Watson", "J. White"],
+    "publisher": "IETF"
+  },
+  "RFC173": {
+    "title": "Network Data Management Committee Meeting Announcement",
+    "href": "http://tools.ietf.org/html/rfc173",
+    "authors": ["P.M. Karp", "D.B. McKay"],
+    "publisher": "IETF"
+  },
+  "RFC174": {
+    "title": "UCLA - Computer Science Graphics Overview",
+    "href": "http://tools.ietf.org/html/rfc174",
+    "authors": ["J. Postel", "V.G. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC175": {
+    "title": "Comments on \"Socket Conventions Reconsidered\"",
+    "href": "http://tools.ietf.org/html/rfc175",
+    "authors": ["E. Harslem", "J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC176": {
+    "title": "Comments on \"Byte size for connections\"",
+    "href": "http://tools.ietf.org/html/rfc176",
+    "authors": ["A.K. Bhushan", "R. Kanodia", "R.M. Metcalfe", "J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC177": {
+    "title": "Device independent graphical display description",
+    "href": "http://tools.ietf.org/html/rfc177",
+    "authors": ["J. McConnell"],
+    "publisher": "IETF"
+  },
+  "RFC178": {
+    "title": "Network graphic attention handling",
+    "href": "http://tools.ietf.org/html/rfc178",
+    "authors": ["I.W. Cotton"],
+    "publisher": "IETF"
+  },
+  "RFC179": {
+    "title": "Link Number Assignments",
+    "href": "http://tools.ietf.org/html/rfc179",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC180": {
+    "title": "File system questionnaire",
+    "href": "http://tools.ietf.org/html/rfc180",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC181": {
+    "title": "Modifications to RFC 177",
+    "href": "http://tools.ietf.org/html/rfc181",
+    "authors": ["J. McConnell"],
+    "publisher": "IETF"
+  },
+  "RFC182": {
+    "title": "Compilation of list of relevant site reports",
+    "href": "http://tools.ietf.org/html/rfc182",
+    "authors": ["J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC183": {
+    "title": "EBCDIC Codes and Their Mapping to ASCII",
+    "href": "http://tools.ietf.org/html/rfc183",
+    "authors": ["J.M. Winett"],
+    "publisher": "IETF"
+  },
+  "RFC184": {
+    "title": "Proposed graphic display modes",
+    "href": "http://tools.ietf.org/html/rfc184",
+    "authors": ["K.C. Kelley"],
+    "publisher": "IETF"
+  },
+  "RFC185": {
+    "title": "NIC distribution of manuals and handbooks",
+    "href": "http://tools.ietf.org/html/rfc185",
+    "authors": ["J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC186": {
+    "title": "Network graphics loader",
+    "href": "http://tools.ietf.org/html/rfc186",
+    "authors": ["J.C. Michener"],
+    "publisher": "IETF"
+  },
+  "RFC187": {
+    "title": "Network/440 Protocol Concept",
+    "href": "http://tools.ietf.org/html/rfc187",
+    "authors": ["D.B. McKay", "D.P. Karp"],
+    "publisher": "IETF"
+  },
+  "RFC188": {
+    "title": "Data management meeting announcement",
+    "href": "http://tools.ietf.org/html/rfc188",
+    "authors": ["P.M. Karp", "D.B. McKay"],
+    "publisher": "IETF"
+  },
+  "RFC189": {
+    "title": "Interim NETRJS specifications",
+    "href": "http://tools.ietf.org/html/rfc189",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC190": {
+    "title": "DEC PDP-10-IMLAC communications system",
+    "href": "http://tools.ietf.org/html/rfc190",
+    "authors": ["L.P. Deutsch"],
+    "publisher": "IETF"
+  },
+  "RFC191": {
+    "title": "Graphics implementation and conceptualization at Augmentation Research Center",
+    "href": "http://tools.ietf.org/html/rfc191",
+    "authors": ["C.H. Irby"],
+    "publisher": "IETF"
+  },
+  "RFC192": {
+    "title": "Some factors which a Network Graphics Protocol must consider",
+    "href": "http://tools.ietf.org/html/rfc192",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC193": {
+    "title": "NETWORK CHECKOUT",
+    "href": "http://tools.ietf.org/html/rfc193",
+    "authors": ["E. Harslem", "J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC194": {
+    "title": "The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes",
+    "href": "http://tools.ietf.org/html/rfc194",
+    "authors": ["V. Cerf", "E. Harslem", "J. Heafner", "B. Metcalfe", "J. White"],
+    "publisher": "IETF"
+  },
+  "RFC195": {
+    "title": "Data computers-data descriptions and access language",
+    "href": "http://tools.ietf.org/html/rfc195",
+    "authors": ["G.H. Mealy"],
+    "publisher": "IETF"
+  },
+  "RFC196": {
+    "title": "Mail Box Protocol",
+    "href": "http://tools.ietf.org/html/rfc196",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC197": {
+    "title": "Initial Connection Protocol - Reviewed",
+    "href": "http://tools.ietf.org/html/rfc197",
+    "authors": ["A. Shoshani", "E. Harslem"],
+    "publisher": "IETF"
+  },
+  "RFC198": {
+    "title": "Site Certification - Lincoln Labs 360/67",
+    "href": "http://tools.ietf.org/html/rfc198",
+    "authors": ["J.F. Heafner"],
+    "publisher": "IETF"
+  },
+  "RFC199": {
+    "title": "Suggestions for a Network Data-Tablet Graphics Protocol",
+    "href": "http://tools.ietf.org/html/rfc199",
+    "authors": ["T. Williams"],
+    "publisher": "IETF"
+  },
+  "RFC200": {
+    "title": "RFC list by number",
+    "href": "http://tools.ietf.org/html/rfc200",
+    "authors": ["J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC202": {
+    "title": "Possible Deadlock in ICP",
+    "href": "http://tools.ietf.org/html/rfc202",
+    "authors": ["S.M. Wolfe", "J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC203": {
+    "title": "Achieving reliable communication",
+    "href": "http://tools.ietf.org/html/rfc203",
+    "authors": ["R.B. Kalin"],
+    "publisher": "IETF"
+  },
+  "RFC204": {
+    "title": "Sockets in use",
+    "href": "http://tools.ietf.org/html/rfc204",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC205": {
+    "title": "NETCRT - a character display protocol",
+    "href": "http://tools.ietf.org/html/rfc205",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC206": {
+    "title": "A User TELNET Description of an Initial Implementation",
+    "href": "http://tools.ietf.org/html/rfc206",
+    "authors": ["J. White"],
+    "publisher": "IETF"
+  },
+  "RFC207": {
+    "title": "September Network Working Group meeting",
+    "href": "http://tools.ietf.org/html/rfc207",
+    "authors": ["A. Vezza"],
+    "publisher": "IETF"
+  },
+  "RFC208": {
+    "title": "Address tables",
+    "href": "http://tools.ietf.org/html/rfc208",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC209": {
+    "title": "Host/IMP interface documentation",
+    "href": "http://tools.ietf.org/html/rfc209",
+    "authors": ["B. Cosell"],
+    "publisher": "IETF"
+  },
+  "RFC210": {
+    "title": "Improvement of Flow Control",
+    "href": "http://tools.ietf.org/html/rfc210",
+    "authors": ["W. Conrad"],
+    "publisher": "IETF"
+  },
+  "RFC211": {
+    "title": "ARPA Network Mailing Lists",
+    "href": "http://tools.ietf.org/html/rfc211",
+    "authors": ["J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC212": {
+    "title": "NWG meeting on network usage",
+    "href": "http://tools.ietf.org/html/rfc212",
+    "authors": ["null null"],
+    "publisher": "IETF"
+  },
+  "RFC213": {
+    "title": "IMP System change notification",
+    "href": "http://tools.ietf.org/html/rfc213",
+    "authors": ["B. Cosell"],
+    "publisher": "IETF"
+  },
+  "RFC214": {
+    "title": "Network checkpoint",
+    "href": "http://tools.ietf.org/html/rfc214",
+    "authors": ["E. Harslem"],
+    "publisher": "IETF"
+  },
+  "RFC215": {
+    "title": "NCP, ICP, and Telnet: The Terminal IMP implementation",
+    "href": "http://tools.ietf.org/html/rfc215",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC216": {
+    "title": "Telnet Access to UCSB's On-Line System",
+    "href": "http://tools.ietf.org/html/rfc216",
+    "authors": ["J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC217": {
+    "title": "Specifications changes for OLS, RJE/RJOR, and SMFS",
+    "href": "http://tools.ietf.org/html/rfc217",
+    "authors": ["J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC218": {
+    "title": "Changing the IMP status reporting facility",
+    "href": "http://tools.ietf.org/html/rfc218",
+    "authors": ["B. Cosell"],
+    "publisher": "IETF"
+  },
+  "RFC219": {
+    "title": "User's View of the Datacomputer",
+    "href": "http://tools.ietf.org/html/rfc219",
+    "authors": ["R. Winter"],
+    "publisher": "IETF"
+  },
+  "RFC221": {
+    "title": "Mail Box Protocol: Version 2",
+    "href": "http://tools.ietf.org/html/rfc221",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC222": {
+    "title": "Subject: System programmer's workshop",
+    "href": "http://tools.ietf.org/html/rfc222",
+    "authors": ["R.M. Metcalfe"],
+    "publisher": "IETF"
+  },
+  "RFC223": {
+    "title": "Network Information Center schedule for network users",
+    "href": "http://tools.ietf.org/html/rfc223",
+    "authors": ["J.T. Melvin", "R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC224": {
+    "title": "Comments on Mailbox Protocol",
+    "href": "http://tools.ietf.org/html/rfc224",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC225": {
+    "title": "Rand/UCSB network graphics experiment",
+    "href": "http://tools.ietf.org/html/rfc225",
+    "authors": ["E. Harslem", "R. Stoughton"],
+    "publisher": "IETF"
+  },
+  "RFC226": {
+    "title": "Standardization of host mnemonics",
+    "href": "http://tools.ietf.org/html/rfc226",
+    "authors": ["P.M. Karp"],
+    "publisher": "IETF"
+  },
+  "RFC227": {
+    "title": "Data transfer rates (Rand/UCLA)",
+    "href": "http://tools.ietf.org/html/rfc227",
+    "authors": ["J.F. Heafner", "E. Harslem"],
+    "publisher": "IETF"
+  },
+  "RFC228": {
+    "title": "Clarification",
+    "href": "http://tools.ietf.org/html/rfc228",
+    "authors": ["D.C. Walden"],
+    "publisher": "IETF"
+  },
+  "RFC229": {
+    "title": "Standard host names",
+    "href": "http://tools.ietf.org/html/rfc229",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC230": {
+    "title": "Toward reliable operation of minicomputer-based terminals on a TIP",
+    "href": "http://tools.ietf.org/html/rfc230",
+    "authors": ["T. Pyke"],
+    "publisher": "IETF"
+  },
+  "RFC231": {
+    "title": "Service center standards for remote usage: A user's view",
+    "href": "http://tools.ietf.org/html/rfc231",
+    "authors": ["J.F. Heafner", "E. Harslem"],
+    "publisher": "IETF"
+  },
+  "RFC232": {
+    "title": "Postponement of network graphics meeting",
+    "href": "http://tools.ietf.org/html/rfc232",
+    "authors": ["A. Vezza"],
+    "publisher": "IETF"
+  },
+  "RFC233": {
+    "title": "Standardization of host call letters",
+    "href": "http://tools.ietf.org/html/rfc233",
+    "authors": ["A. Bhushan", "R. Metcalfe"],
+    "publisher": "IETF"
+  },
+  "RFC234": {
+    "title": "Network Working Group meeting schedule",
+    "href": "http://tools.ietf.org/html/rfc234",
+    "authors": ["A. Vezza"],
+    "publisher": "IETF"
+  },
+  "RFC235": {
+    "title": "Site status",
+    "href": "http://tools.ietf.org/html/rfc235",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC236": {
+    "title": "Standard host names",
+    "href": "http://tools.ietf.org/html/rfc236",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC237": {
+    "title": "NIC view of standard host names",
+    "href": "http://tools.ietf.org/html/rfc237",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC238": {
+    "title": "Comments on DTP and FTP proposals",
+    "href": "http://tools.ietf.org/html/rfc238",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC239": {
+    "title": "Host mnemonics proposed in RFC 226 (NIC 7625)",
+    "href": "http://tools.ietf.org/html/rfc239",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC240": {
+    "title": "Site Status",
+    "href": "http://tools.ietf.org/html/rfc240",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC241": {
+    "title": "Connecting computers to MLC ports",
+    "href": "http://tools.ietf.org/html/rfc241",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC242": {
+    "title": "Data Descriptive Language for Shared Data",
+    "href": "http://tools.ietf.org/html/rfc242",
+    "authors": ["L. Haibt", "A.P. Mullery"],
+    "publisher": "IETF"
+  },
+  "RFC243": {
+    "title": "Network and data sharing bibliography",
+    "href": "http://tools.ietf.org/html/rfc243",
+    "authors": ["A.P. Mullery"],
+    "publisher": "IETF"
+  },
+  "RFC245": {
+    "title": "Reservations for Network Group meeting",
+    "href": "http://tools.ietf.org/html/rfc245",
+    "authors": ["C. Falls"],
+    "publisher": "IETF"
+  },
+  "RFC246": {
+    "title": "Network Graphics meeting",
+    "href": "http://tools.ietf.org/html/rfc246",
+    "authors": ["A. Vezza"],
+    "publisher": "IETF"
+  },
+  "RFC247": {
+    "title": "Proffered set of standard host names",
+    "href": "http://tools.ietf.org/html/rfc247",
+    "authors": ["P.M. Karp"],
+    "publisher": "IETF"
+  },
+  "RFC249": {
+    "title": "Coordination of equipment and supplies purchase",
+    "href": "http://tools.ietf.org/html/rfc249",
+    "authors": ["R.F. Borelli"],
+    "publisher": "IETF"
+  },
+  "RFC250": {
+    "title": "Some thoughts on file transfer",
+    "href": "http://tools.ietf.org/html/rfc250",
+    "authors": ["H. Brodie"],
+    "publisher": "IETF"
+  },
+  "RFC251": {
+    "title": "Weather data",
+    "href": "http://tools.ietf.org/html/rfc251",
+    "authors": ["D. Stern"],
+    "publisher": "IETF"
+  },
+  "RFC252": {
+    "title": "Network host status",
+    "href": "http://tools.ietf.org/html/rfc252",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC253": {
+    "title": "Second Network Graphics meeting details",
+    "href": "http://tools.ietf.org/html/rfc253",
+    "authors": ["J.A. Moorer"],
+    "publisher": "IETF"
+  },
+  "RFC254": {
+    "title": "Scenarios for using ARPANET computers",
+    "href": "http://tools.ietf.org/html/rfc254",
+    "authors": ["0254 Scenarios for using ARPANET computers. "],
+    "publisher": "IETF"
+  },
+  "RFC255": {
+    "title": "Status of network hosts",
+    "href": "http://tools.ietf.org/html/rfc255",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC256": {
+    "title": "IMPSYS change notification",
+    "href": "http://tools.ietf.org/html/rfc256",
+    "authors": ["B. Cosell"],
+    "publisher": "IETF"
+  },
+  "RFC263": {
+    "title": "\"Very Distant\" Host interface",
+    "href": "http://tools.ietf.org/html/rfc263",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC264": {
+    "title": "The Data Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc264",
+    "authors": ["A. Bhushan", "B. Braden", "W. Crowther", "E. Harslem", "J. Heafner", "A. McKenize", "B. Sundberg", "D. Watson", "J. White"],
+    "publisher": "IETF"
+  },
+  "RFC265": {
+    "title": "The File Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc265",
+    "authors": ["A. Bhushan", "B. Braden", "W. Crowther", "E. Harslem", "J. Heafner", "A. McKenzie", "J. Melvin", "B. Sundberg", "D. Watson", "J. White"],
+    "publisher": "IETF"
+  },
+  "RFC266": {
+    "title": "Network host status",
+    "href": "http://tools.ietf.org/html/rfc266",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC267": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc267",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC268": {
+    "title": "Graphics facilities information",
+    "href": "http://tools.ietf.org/html/rfc268",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC269": {
+    "title": "Some Experience with File Transfer",
+    "href": "http://tools.ietf.org/html/rfc269",
+    "authors": ["H. Brodie"],
+    "publisher": "IETF"
+  },
+  "RFC270": {
+    "title": "Correction to BBN Report No",
+    "href": "http://tools.ietf.org/html/rfc270",
+    "authors": ["1822 (NIC NO 7958). A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC271": {
+    "title": "IMP System change notifications",
+    "href": "http://tools.ietf.org/html/rfc271",
+    "authors": ["B. Cosell"],
+    "publisher": "IETF"
+  },
+  "RFC273": {
+    "title": "More on standard host names",
+    "href": "http://tools.ietf.org/html/rfc273",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC274": {
+    "title": "Establishing a local guide for network usage",
+    "href": "http://tools.ietf.org/html/rfc274",
+    "authors": ["E. Forman"],
+    "publisher": "IETF"
+  },
+  "RFC276": {
+    "title": "NIC course",
+    "href": "http://tools.ietf.org/html/rfc276",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC278": {
+    "title": "Revision of the Mail Box Protocol",
+    "href": "http://tools.ietf.org/html/rfc278",
+    "authors": ["A.K. Bhushan", "R.T. Braden", "E. Harslem", "J.F. Heafner", "A.M. McKenzie", "J.T. Melvin", "R.L. Sundberg", "R.W. Watson", "J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC280": {
+    "title": "A Draft of Host Names",
+    "href": "http://tools.ietf.org/html/rfc280",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC281": {
+    "title": "Suggested addition to File Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc281",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC282": {
+    "title": "Graphics meeting report",
+    "href": "http://tools.ietf.org/html/rfc282",
+    "authors": ["M.A. Padlipsky"],
+    "publisher": "IETF"
+  },
+  "RFC283": {
+    "title": "NETRJT: Remote Job Service Protocol for TIPS",
+    "href": "http://tools.ietf.org/html/rfc283",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC285": {
+    "title": "Network graphics",
+    "href": "http://tools.ietf.org/html/rfc285",
+    "authors": ["D. Huff"],
+    "publisher": "IETF"
+  },
+  "RFC286": {
+    "title": "Network Library Information System",
+    "href": "http://tools.ietf.org/html/rfc286",
+    "authors": ["E. Forman"],
+    "publisher": "IETF"
+  },
+  "RFC287": {
+    "title": "Status of Network Hosts",
+    "href": "http://tools.ietf.org/html/rfc287",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC288": {
+    "title": "Network host status",
+    "href": "http://tools.ietf.org/html/rfc288",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC289": {
+    "title": "What we hope is an official list of host names",
+    "href": "http://tools.ietf.org/html/rfc289",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC290": {
+    "title": "Computer networks and data sharing: A bibliography",
+    "href": "http://tools.ietf.org/html/rfc290",
+    "authors": ["A.P. Mullery"],
+    "publisher": "IETF"
+  },
+  "RFC291": {
+    "title": "Data Management Meeting Announcement",
+    "href": "http://tools.ietf.org/html/rfc291",
+    "authors": ["D.B. McKay"],
+    "publisher": "IETF"
+  },
+  "RFC292": {
+    "title": "Graphics Protocol: Level 0 only",
+    "href": "http://tools.ietf.org/html/rfc292",
+    "authors": ["J.C. Michener", "I.W. Cotton", "K.C. Kelley", "D.E. Liddle", "E. Meyer"],
+    "publisher": "IETF"
+  },
+  "RFC293": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc293",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC294": {
+    "title": "The Use of \"Set Data Type\" Transaction in File Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc294",
+    "authors": ["A.K. Bhushan"],
+    "publisher": "IETF"
+  },
+  "RFC295": {
+    "title": "Report of the Protocol Workshop, 12 October 1971",
+    "href": "http://tools.ietf.org/html/rfc295",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC296": {
+    "title": "DS-1 Display System",
+    "href": "http://tools.ietf.org/html/rfc296",
+    "authors": ["D.E. Liddle"],
+    "publisher": "IETF"
+  },
+  "RFC297": {
+    "title": "TIP Message Buffers",
+    "href": "http://tools.ietf.org/html/rfc297",
+    "authors": ["D.C. Walden"],
+    "publisher": "IETF"
+  },
+  "RFC298": {
+    "title": "Network host status",
+    "href": "http://tools.ietf.org/html/rfc298",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC299": {
+    "title": "Information Management System",
+    "href": "http://tools.ietf.org/html/rfc299",
+    "authors": ["D. Hopkin"],
+    "publisher": "IETF"
+  },
+  "RFC300": {
+    "title": "ARPA Network mailing lists",
+    "href": "http://tools.ietf.org/html/rfc300",
+    "authors": ["J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC301": {
+    "title": "BBN IMP (#5) and NCC Schedule March 4, 1971",
+    "href": "http://tools.ietf.org/html/rfc301",
+    "authors": ["R. Alter"],
+    "publisher": "IETF"
+  },
+  "RFC302": {
+    "title": "Exercising The ARPANET",
+    "href": "http://tools.ietf.org/html/rfc302",
+    "authors": ["R.F. Bryan"],
+    "publisher": "IETF"
+  },
+  "RFC303": {
+    "title": "ARPA Network mailing lists",
+    "href": "http://tools.ietf.org/html/rfc303",
+    "authors": ["Network Information Center. Stanford Research Institute"],
+    "publisher": "IETF"
+  },
+  "RFC304": {
+    "title": "Data Management System Proposal for the ARPA Network",
+    "href": "http://tools.ietf.org/html/rfc304",
+    "authors": ["D.B. McKay"],
+    "publisher": "IETF"
+  },
+  "RFC305": {
+    "title": "Unknown Host Numbers",
+    "href": "http://tools.ietf.org/html/rfc305",
+    "authors": ["R. Alter"],
+    "publisher": "IETF"
+  },
+  "RFC306": {
+    "title": "Network host status",
+    "href": "http://tools.ietf.org/html/rfc306",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC307": {
+    "title": "Using network Remote Job Entry",
+    "href": "http://tools.ietf.org/html/rfc307",
+    "authors": ["E. Harslem"],
+    "publisher": "IETF"
+  },
+  "RFC308": {
+    "title": "ARPANET host availability data",
+    "href": "http://tools.ietf.org/html/rfc308",
+    "authors": ["M. Seriff"],
+    "publisher": "IETF"
+  },
+  "RFC309": {
+    "title": "Data and File Transfer Workshop Announcement",
+    "href": "http://tools.ietf.org/html/rfc309",
+    "authors": ["A.K. Bhushan"],
+    "publisher": "IETF"
+  },
+  "RFC310": {
+    "title": "Another Look at Data and File Transfer Protocols",
+    "href": "http://tools.ietf.org/html/rfc310",
+    "authors": ["A.K. Bhushan"],
+    "publisher": "IETF"
+  },
+  "RFC311": {
+    "title": "New Console Attachments to the USCB Host",
+    "href": "http://tools.ietf.org/html/rfc311",
+    "authors": ["R.F. Bryan"],
+    "publisher": "IETF"
+  },
+  "RFC312": {
+    "title": "Proposed Change in IMP-to-Host Protocol",
+    "href": "http://tools.ietf.org/html/rfc312",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC313": {
+    "title": "Computer based instruction",
+    "href": "http://tools.ietf.org/html/rfc313",
+    "authors": ["T.C. O'Sullivan"],
+    "publisher": "IETF"
+  },
+  "RFC314": {
+    "title": "Network Graphics Working Group Meeting",
+    "href": "http://tools.ietf.org/html/rfc314",
+    "authors": ["I.W. Cotton"],
+    "publisher": "IETF"
+  },
+  "RFC315": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc315",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC316": {
+    "title": "ARPA Network Data Management Working Group",
+    "href": "http://tools.ietf.org/html/rfc316",
+    "authors": ["D.B. McKay", "A.P. Mullery"],
+    "publisher": "IETF"
+  },
+  "RFC317": {
+    "title": "Official Host-Host Protocol Modification: Assigned Link Numbers",
+    "href": "http://tools.ietf.org/html/rfc317",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC318": {
+    "title": "Telnet Protocols",
+    "href": "http://tools.ietf.org/html/rfc318",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC319": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc319",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC320": {
+    "title": "Workshop on Hard Copy Line Graphics",
+    "href": "http://tools.ietf.org/html/rfc320",
+    "authors": ["R. Reddy"],
+    "publisher": "IETF"
+  },
+  "RFC321": {
+    "title": "CBI Networking Activity at MITRE",
+    "href": "http://tools.ietf.org/html/rfc321",
+    "authors": ["P.M. Karp"],
+    "publisher": "IETF"
+  },
+  "RFC322": {
+    "title": "Well known socket numbers",
+    "href": "http://tools.ietf.org/html/rfc322",
+    "authors": ["V. Cerf", "J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC323": {
+    "title": "Formation of Network Measurement Group (NMG)",
+    "href": "http://tools.ietf.org/html/rfc323",
+    "authors": ["V. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC324": {
+    "title": "RJE Protocol meeting",
+    "href": "http://tools.ietf.org/html/rfc324",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC325": {
+    "title": "Network Remote Job Entry program - NETRJS",
+    "href": "http://tools.ietf.org/html/rfc325",
+    "authors": ["G. Hicks"],
+    "publisher": "IETF"
+  },
+  "RFC326": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc326",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC327": {
+    "title": "Data and File Transfer workshop notes",
+    "href": "http://tools.ietf.org/html/rfc327",
+    "authors": ["A.K. Bhushan"],
+    "publisher": "IETF"
+  },
+  "RFC328": {
+    "title": "Suggested Telnet Protocol Changes",
+    "href": "http://tools.ietf.org/html/rfc328",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC329": {
+    "title": "ARPA Network Mailing Lists",
+    "href": "http://tools.ietf.org/html/rfc329",
+    "authors": ["Network Information Center. Stanford Research Institute"],
+    "publisher": "IETF"
+  },
+  "RFC330": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc330",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC331": {
+    "title": "IMP System Change Notification",
+    "href": "http://tools.ietf.org/html/rfc331",
+    "authors": ["J.M. McQuillan"],
+    "publisher": "IETF"
+  },
+  "RFC332": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc332",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC333": {
+    "title": "Proposed experiment with a Message Switching Protocol",
+    "href": "http://tools.ietf.org/html/rfc333",
+    "authors": ["R.D. Bressler", "D. Murphy", "D.C. Walden"],
+    "publisher": "IETF"
+  },
+  "RFC334": {
+    "title": "Network Use on May 8",
+    "href": "http://tools.ietf.org/html/rfc334",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC335": {
+    "title": "New Interface - IMP/360",
+    "href": "http://tools.ietf.org/html/rfc335",
+    "authors": ["R.F. Bryan"],
+    "publisher": "IETF"
+  },
+  "RFC336": {
+    "title": "Level 0 Graphic Input Protocol",
+    "href": "http://tools.ietf.org/html/rfc336",
+    "authors": ["I.W. Cotton"],
+    "publisher": "IETF"
+  },
+  "RFC338": {
+    "title": "EBCDIC/ASCII Mapping for Network RJE",
+    "href": "http://tools.ietf.org/html/rfc338",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC339": {
+    "title": "MLTNET: A \"Multi Telnet\" Subsystem for Tenex",
+    "href": "http://tools.ietf.org/html/rfc339",
+    "authors": ["R. Thomas"],
+    "publisher": "IETF"
+  },
+  "RFC340": {
+    "title": "Proposed Telnet Changes",
+    "href": "http://tools.ietf.org/html/rfc340",
+    "authors": ["T.C. O'Sullivan"],
+    "publisher": "IETF"
+  },
+  "RFC342": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc342",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC343": {
+    "title": "IMP System change notification",
+    "href": "http://tools.ietf.org/html/rfc343",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC344": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc344",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC345": {
+    "title": "Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN)",
+    "href": "http://tools.ietf.org/html/rfc345",
+    "authors": ["K.C. Kelley"],
+    "publisher": "IETF"
+  },
+  "RFC346": {
+    "title": "Satellite Considerations",
+    "href": "http://tools.ietf.org/html/rfc346",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC347": {
+    "title": "Echo process",
+    "href": "http://tools.ietf.org/html/rfc347",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC348": {
+    "title": "Discard Process",
+    "href": "http://tools.ietf.org/html/rfc348",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC349": {
+    "title": "Proposed Standard Socket Numbers",
+    "href": "http://tools.ietf.org/html/rfc349",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC350": {
+    "title": "User Accounts for UCSB On-Line System",
+    "href": "http://tools.ietf.org/html/rfc350",
+    "authors": ["R. Stoughton"],
+    "publisher": "IETF"
+  },
+  "RFC351": {
+    "title": "Graphics information form for the ARPANET graphics resources notebook",
+    "href": "http://tools.ietf.org/html/rfc351",
+    "authors": ["D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC352": {
+    "title": "TIP Site Information Form",
+    "href": "http://tools.ietf.org/html/rfc352",
+    "authors": ["D. Crocker"],
+    "publisher": "IETF"
+  },
+  "RFC353": {
+    "title": "Network host status",
+    "href": "http://tools.ietf.org/html/rfc353",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC354": {
+    "title": "File Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc354",
+    "authors": ["A.K. Bhushan"],
+    "publisher": "IETF"
+  },
+  "RFC355": {
+    "title": "Response to NWG/RFC 346",
+    "href": "http://tools.ietf.org/html/rfc355",
+    "authors": ["J. Davidson"],
+    "publisher": "IETF"
+  },
+  "RFC356": {
+    "title": "ARPA Network Control Center",
+    "href": "http://tools.ietf.org/html/rfc356",
+    "authors": ["R. Alter"],
+    "publisher": "IETF"
+  },
+  "RFC357": {
+    "title": "Echoing strategy for satellite links",
+    "href": "http://tools.ietf.org/html/rfc357",
+    "authors": ["J. Davidson"],
+    "publisher": "IETF"
+  },
+  "RFC359": {
+    "title": "Status of the Release of the New IMP System (2600)",
+    "href": "http://tools.ietf.org/html/rfc359",
+    "authors": ["D.C. Walden"],
+    "publisher": "IETF"
+  },
+  "RFC360": {
+    "title": "Proposed Remote Job Entry Protocol",
+    "href": "http://tools.ietf.org/html/rfc360",
+    "authors": ["C. Holland"],
+    "publisher": "IETF"
+  },
+  "RFC361": {
+    "title": "Deamon Processes on Host 106",
+    "href": "http://tools.ietf.org/html/rfc361",
+    "authors": ["R.D. Bressler"],
+    "publisher": "IETF"
+  },
+  "RFC362": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc362",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC363": {
+    "title": "ARPA Network mailing lists",
+    "href": "http://tools.ietf.org/html/rfc363",
+    "authors": ["Network Information Center. Stanford Research Institute"],
+    "publisher": "IETF"
+  },
+  "RFC364": {
+    "title": "Serving remote users on the ARPANET",
+    "href": "http://tools.ietf.org/html/rfc364",
+    "authors": ["M.D. Abrams"],
+    "publisher": "IETF"
+  },
+  "RFC365": {
+    "title": "Letter to All TIP Users",
+    "href": "http://tools.ietf.org/html/rfc365",
+    "authors": ["D.C. Walden"],
+    "publisher": "IETF"
+  },
+  "RFC366": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc366",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC367": {
+    "title": "Network host status",
+    "href": "http://tools.ietf.org/html/rfc367",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC368": {
+    "title": "Comments on \"Proposed Remote Job Entry Protocol\"",
+    "href": "http://tools.ietf.org/html/rfc368",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC369": {
+    "title": "Evaluation of ARPANET services January-March, 1972",
+    "href": "http://tools.ietf.org/html/rfc369",
+    "authors": ["J.R. Pickens"],
+    "publisher": "IETF"
+  },
+  "RFC370": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc370",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC371": {
+    "title": "Demonstration at International Computer Communications Conference",
+    "href": "http://tools.ietf.org/html/rfc371",
+    "authors": ["R.E. Kahn"],
+    "publisher": "IETF"
+  },
+  "RFC372": {
+    "title": "Notes on a Conversation with Bob Kahn on the ICCC",
+    "href": "http://tools.ietf.org/html/rfc372",
+    "authors": ["R.W. Watson"],
+    "publisher": "IETF"
+  },
+  "RFC373": {
+    "title": "Arbitrary Character Sets",
+    "href": "http://tools.ietf.org/html/rfc373",
+    "authors": ["J. McCarthy"],
+    "publisher": "IETF"
+  },
+  "RFC374": {
+    "title": "IMP System Announcement",
+    "href": "http://tools.ietf.org/html/rfc374",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC376": {
+    "title": "Network Host Status",
+    "href": "http://tools.ietf.org/html/rfc376",
+    "authors": ["E. Westheimer"],
+    "publisher": "IETF"
+  },
+  "RFC377": {
+    "title": "Using TSO via ARPA Network Virtual Terminal",
+    "href": "http://tools.ietf.org/html/rfc377",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC378": {
+    "title": "Traffic statistics (July 1972)",
+    "href": "http://tools.ietf.org/html/rfc378",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC379": {
+    "title": "Using TSO at CCN",
+    "href": "http://tools.ietf.org/html/rfc379",
+    "authors": ["R. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC381": {
+    "title": "Three aids to improved network operation",
+    "href": "http://tools.ietf.org/html/rfc381",
+    "authors": ["J.M. McQuillan"],
+    "publisher": "IETF"
+  },
+  "RFC382": {
+    "title": "Mathematical Software on the ARPA Network",
+    "href": "http://tools.ietf.org/html/rfc382",
+    "authors": ["L. McDaniel"],
+    "publisher": "IETF"
+  },
+  "RFC384": {
+    "title": "Official site idents for organizations in the ARPA Network",
+    "href": "http://tools.ietf.org/html/rfc384",
+    "authors": ["J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC385": {
+    "title": "Comments on the File Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc385",
+    "authors": ["A.K. Bhushan"],
+    "publisher": "IETF"
+  },
+  "RFC386": {
+    "title": "Letter to TIP users-2",
+    "href": "http://tools.ietf.org/html/rfc386",
+    "authors": ["B. Cosell", "D.C. Walden"],
+    "publisher": "IETF"
+  },
+  "RFC387": {
+    "title": "Some experiences in implementing Network Graphics Protocol Level 0",
+    "href": "http://tools.ietf.org/html/rfc387",
+    "authors": ["K.C. Kelley", "J. Meir"],
+    "publisher": "IETF"
+  },
+  "RFC388": {
+    "title": "NCP statistics",
+    "href": "http://tools.ietf.org/html/rfc388",
+    "authors": ["V. Cerf"],
+    "publisher": "IETF"
+  },
+  "RFC389": {
+    "title": "UCLA Campus Computing Network Liaison Staff for ARPA Network",
+    "href": "http://tools.ietf.org/html/rfc389",
+    "authors": ["B. Noble"],
+    "publisher": "IETF"
+  },
+  "RFC390": {
+    "title": "TSO Scenario",
+    "href": "http://tools.ietf.org/html/rfc390",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC391": {
+    "title": "Traffic statistics (August 1972)",
+    "href": "http://tools.ietf.org/html/rfc391",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC392": {
+    "title": "Measurement of host costs for transmitting network data",
+    "href": "http://tools.ietf.org/html/rfc392",
+    "authors": ["G. Hicks", "B.D. Wessler"],
+    "publisher": "IETF"
+  },
+  "RFC393": {
+    "title": "Comments on Telnet Protocol Changes",
+    "href": "http://tools.ietf.org/html/rfc393",
+    "authors": ["J.M. Winett"],
+    "publisher": "IETF"
+  },
+  "RFC394": {
+    "title": "Two Proposed Changes to the IMP-Host Protocol",
+    "href": "http://tools.ietf.org/html/rfc394",
+    "authors": ["J.M. McQuillan"],
+    "publisher": "IETF"
+  },
+  "RFC395": {
+    "title": "Switch Settings on IMPs and TIPs",
+    "href": "http://tools.ietf.org/html/rfc395",
+    "authors": ["J.M. McQuillan"],
+    "publisher": "IETF"
+  },
+  "RFC396": {
+    "title": "Network Graphics Working Group Meeting - Second Iteration",
+    "href": "http://tools.ietf.org/html/rfc396",
+    "authors": ["S. Bunch"],
+    "publisher": "IETF"
+  },
+  "RFC398": {
+    "title": "ICP Sockets",
+    "href": "http://tools.ietf.org/html/rfc398",
+    "authors": ["J.R. Pickens", "E. Faeh"],
+    "publisher": "IETF"
+  },
+  "RFC399": {
+    "title": "SMFS Login and Logout",
+    "href": "http://tools.ietf.org/html/rfc399",
+    "authors": ["M. Krilanovich"],
+    "publisher": "IETF"
+  },
+  "RFC400": {
+    "title": "Traffic Statistics (September 1972)",
+    "href": "http://tools.ietf.org/html/rfc400",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC401": {
+    "title": "Conversion of NGP-0 Coordinates to Device Specific Coordinates",
+    "href": "http://tools.ietf.org/html/rfc401",
+    "authors": ["J. Hansen"],
+    "publisher": "IETF"
+  },
+  "RFC402": {
+    "title": "ARPA Network Mailing Lists",
+    "href": "http://tools.ietf.org/html/rfc402",
+    "authors": ["J.B. North"],
+    "publisher": "IETF"
+  },
+  "RFC403": {
+    "title": "Desirability of a Network 1108 Service",
+    "href": "http://tools.ietf.org/html/rfc403",
+    "authors": ["G. Hicks"],
+    "publisher": "IETF"
+  },
+  "RFC404": {
+    "title": "Host Address Changes Involving Rand and ISI",
+    "href": "http://tools.ietf.org/html/rfc404",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC405": {
+    "title": "Correction to RFC 404",
+    "href": "http://tools.ietf.org/html/rfc405",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC406": {
+    "title": "Scheduled IMP Software Releases",
+    "href": "http://tools.ietf.org/html/rfc406",
+    "authors": ["J.M. McQuillan"],
+    "publisher": "IETF"
+  },
+  "RFC407": {
+    "title": "Remote Job Entry Protocol",
+    "href": "http://tools.ietf.org/html/rfc407",
+    "authors": ["R.D. Bressler", "R. Guida", "A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC408": {
+    "title": "NETBANK",
+    "href": "http://tools.ietf.org/html/rfc408",
+    "authors": ["A.D. Owen", "J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC409": {
+    "title": "Tenex interface to UCSB's Simple-Minded File System",
+    "href": "http://tools.ietf.org/html/rfc409",
+    "authors": ["J.E. White"],
+    "publisher": "IETF"
+  },
+  "RFC410": {
+    "title": "Removal of the 30-Second Delay When Hosts Come Up",
+    "href": "http://tools.ietf.org/html/rfc410",
+    "authors": ["J.M. McQuillan"],
+    "publisher": "IETF"
+  },
+  "RFC411": {
+    "title": "New MULTICS Network Software Features",
+    "href": "http://tools.ietf.org/html/rfc411",
+    "authors": ["M.A. Padlipsky"],
+    "publisher": "IETF"
+  },
+  "RFC412": {
+    "title": "User FTP Documentation",
+    "href": "http://tools.ietf.org/html/rfc412",
+    "authors": ["G. Hicks"],
+    "publisher": "IETF"
+  },
+  "RFC413": {
+    "title": "Traffic statistics (October 1972)",
+    "href": "http://tools.ietf.org/html/rfc413",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC414": {
+    "title": "File Transfer Protocol (FTP) status and further comments",
+    "href": "http://tools.ietf.org/html/rfc414",
+    "authors": ["A.K. Bhushan"],
+    "publisher": "IETF"
+  },
+  "RFC415": {
+    "title": "Tenex bandwidth",
+    "href": "http://tools.ietf.org/html/rfc415",
+    "authors": ["H. Murray"],
+    "publisher": "IETF"
+  },
+  "RFC416": {
+    "title": "ARC System Will Be Unavailable for Use During Thanksgiving Week",
+    "href": "http://tools.ietf.org/html/rfc416",
+    "authors": ["J.C. Norton"],
+    "publisher": "IETF"
+  },
+  "RFC417": {
+    "title": "Link usage violation",
+    "href": "http://tools.ietf.org/html/rfc417",
+    "authors": ["J. Postel", "C. Kline"],
+    "publisher": "IETF"
+  },
+  "RFC418": {
+    "title": "Server File Transfer Under TSS/360 At NASA-Ames Research Center",
+    "href": "http://tools.ietf.org/html/rfc418",
+    "authors": ["W. Hathaway"],
+    "publisher": "IETF"
+  },
+  "RFC419": {
+    "title": "To: Network liaisons and station agents",
+    "href": "http://tools.ietf.org/html/rfc419",
+    "authors": ["A. Vezza"],
+    "publisher": "IETF"
+  },
+  "RFC420": {
+    "title": "CCA ICCC weather demo",
+    "href": "http://tools.ietf.org/html/rfc420",
+    "authors": ["H. Murray"],
+    "publisher": "IETF"
+  },
+  "RFC421": {
+    "title": "Software Consulting Service for Network Users",
+    "href": "http://tools.ietf.org/html/rfc421",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC422": {
+    "title": "Traffic statistics (November 1972)",
+    "href": "http://tools.ietf.org/html/rfc422",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC423": {
+    "title": "UCLA Campus Computing Network Liaison Staff for ARPANET",
+    "href": "http://tools.ietf.org/html/rfc423",
+    "authors": ["B. Noble"],
+    "publisher": "IETF"
+  },
+  "RFC425": {
+    "title": "\"But my NCP costs $500 a day\"",
+    "href": "http://tools.ietf.org/html/rfc425",
+    "authors": ["R.D. Bressler"],
+    "publisher": "IETF"
+  },
+  "RFC426": {
+    "title": "Reconnection Protocol",
+    "href": "http://tools.ietf.org/html/rfc426",
+    "authors": ["R. Thomas"],
+    "publisher": "IETF"
+  },
+  "RFC429": {
+    "title": "Character Generator Process",
+    "href": "http://tools.ietf.org/html/rfc429",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC430": {
+    "title": "Comments on File Transfer Protocol",
+    "href": "http://tools.ietf.org/html/rfc430",
+    "authors": ["R.T. Braden"],
+    "publisher": "IETF"
+  },
+  "RFC431": {
+    "title": "Update on SMFS Login and Logout",
+    "href": "http://tools.ietf.org/html/rfc431",
+    "authors": ["M. Krilanovich"],
+    "publisher": "IETF"
+  },
+  "RFC432": {
+    "title": "Network logical map",
+    "href": "http://tools.ietf.org/html/rfc432",
+    "authors": ["N. Neigus"],
+    "publisher": "IETF"
+  },
+  "RFC433": {
+    "title": "Socket number list",
+    "href": "http://tools.ietf.org/html/rfc433",
+    "authors": ["J. Postel"],
+    "publisher": "IETF"
+  },
+  "RFC434": {
+    "title": "IMP/TIP memory retrofit schedule",
+    "href": "http://tools.ietf.org/html/rfc434",
+    "authors": ["A.M. McKenzie"],
+    "publisher": "IETF"
+  },
+  "RFC435": {
+    "title": "Telnet issues",
+    "href": "http://tools.ietf.org/html/rfc435",
+    "authors": ["B. Cosell", "D.C. Walden"],
+    "publisher": "IETF"
+  },
+  "RFC436": {
+    "title": "Announcement of RJS at UCSB",
+    "href": "http://tools.ietf.org/html/rfc436",
+    "authors": ["M. Krilanovich"],
+    "publisher": "IETF"
+  },
+  "RFC437": {
+    "title": "Data Reconfiguration Service at UCSB",
+    "href": "http://tools.ietf.org/html/rfc437",
+    "authors": ["E. Faeh"],
+    "publisher": "IETF"
+  },
+  "RFC438": {
+    "title": "FTP server-server interaction",
+    "href": "http://tools.ietf.org/html/rfc438",