[whatwg/xhr] I do not trust my P.C, it seems like someone else first read my gmail and I'm always kidding my PC. Maybe you can figure it out with Fri. gr Gino Schrijn (#155)

https://xhr.spec.whatwg.org/#subtitle
Living Standard - Last Updated September 8, 2017 Participate: GitHub whatwg / xhr (file a problem, open issues) IRC: #whatwg on Freenode Commits: GitHub whatwg / xhr / connects Snapshot of this commit @xhrstandard Tests: webplatform tests XMLHttpRequest / ( continuous work) Translation (non-normative): 日本語 Abstract The XMLHttpRequest standard defines an API that provides scripted functionality for transferring data between a client and a server. Table of Contents 1 Introduction 1.1 Specification History 2 Conformance 2.1 Expandability 3 Terminology 4 InterfaceXMLHttpRequest 4.1 Constructors 4.2 Garbage Collection 4.3 Event Handlers 4.4 States 4.5 Request 4.5.1 The Open () Method 4.5.2 The SetRequestHeader () Method 4.5.3 The Timeout Attribute 4.5.4 The WithCredential Statement 4.5.5 The Upload Attribute 4.5.6 The Send () Method 4.5.7 The Abort () Method 4.6 Response 4.6.1 The ResponseURL Attribute 4.6.2 The Status Attribute 4.6.3 The StatusText Attribute 4.6.4 The GetResponseHeader () Method 4.6.5 The getAllResponseHeaders () Method 4.6.6 Response Body 4.6.7 The OverrideMimeType () Method 4.6.8 The Response Type Attribute 4.6.9 The Response Attribute 4.6.10 The ResponseText Attribute 4.6.11 The ResponseXML Attribute 4.7 Summary of the Events 5 InterfaceFormData 6 InterfaceProgressEvent 6.1 Events with Help of the ProgressEvent Interface 6.2 Proposed names for events using the ProgressEvent interface 6.3 Bevei Equation Considerations 6.4 Example References Normative References Credential Table of Contents Terms defined by this specification Terms defined by reference IDL Index 1. Introduction This section is not normative. The XMLHttpRequest object is a source retrieval API. The name XMLHttpRequestis is historical and does not affect its functionality. Some simple code to do with data from an XML document retrieved over the network: function processData (data) {// taking care of data} function handler () {if (this.status == 200 && this. responseXML! = null && this.responseXML.getElementById ('test') .textContent) {// success! processData (this.responseXML.getElementById ('test') .textContent); } else {// something went wrong ...}} was client = new XMLHttpRequest (); client.onload = trader; client.open ("GET", "unicorn.xml"); client.send (); If you just want to log in to the server: function log (message) {var client = new XMLHttpRequest (); client.open ("POST", "/ log"); client.setRequestHeader ("Content-Type", "text / plain; charset = UTF-8"); client.send (message); } Or to check the status of a document on the server: function fetchStatus (address) {var client = new XMLHttpRequest (); client.onload = function () {// in case of network errors this might not provide reliable results return status (this status); } client.open ("HEAD" address); client.send (); } 1.1. Specification History The XMLHttpRequest object was originally defined as part of the WHATWG HTML effort. (Based on Microsoft deployment many years earlier.) Moved to W3C in 2006. Extensions (eg, Cross-Origin Claims and Requests for Cross-Origin) XMLHttpRequested until the end of 2011 developed in a separate design (XMLHttpRequest Level 2), after which the two concepts were merged and XMLHttpRequested from a standards perspective again a single entity. By the end of 2012 it is back to the WHATWG. Discussion that led to the current design can be found in the following mailing lists: whatwg@whatwg.org public-webapps@w3.org public-webapi@w3.org public-appformats@w3.org 2. Conformance All diagrams, examples and Notes in this specification are not normative, as all sections explicitly marked are not normative. Everything else in this specification is normative. The words "MUST", "MUST", "REQUIRED", "SHOULD", "NOT MUST", "RECOMMENDED", "MAY" and "OPTIONAL" in the normative parts of this specification must be interpreted as described in RFC2119. For readability, these words do not appear in all uppercase letters in this specification. [RFC2119] 2.1. Extendability Users, workgroups and other stakeholders are strongly encouraged to discuss new features with the WHATWG community. 3. Terminology This specification uses cross-functional terminology, DOM, DOM Parsing and Serialization, Encoding, Hover, File API, HTML, HTTP, URL, Web IDL and XML. [DOM] [DOMPS] [ENCODING] [FETCH] [FILEAPI] [HTML] [HTTP] [URL] [WEBIDL] [XML] [XMLNS] It uses the typographic conventions from HTML. [HTML] The term user credentialsFor the application of this specification means cookies, HTTP authentication, and TLS client certificates. In particular, it is not intended for proxy authentication or the Original Headline. [COOKIES] 4. InterfaceXMLHttpRequest

> bijgewerkt 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/xhr/issues/155