(HyperText Transfer Protocol) is the underlying protocol of the World Wide Web. Developed by Tim Berners-Lee and his team between 1989-1991, HTTP has seen many changes, keeping most of the simplicity and further shaping its flexibility. HTTP has evolved from an early protocol to exchange files in a semi-trusted laboratory environment, to the modern maze of the Internet, now carrying images, videos in high resolution and 3D. HTTP Invention of the World Wide Web In 1989, while he was working at CERN, Tim Berners-Lee wrote a proposal to build a hypertext system over the Internet. Initially calling it the , it was later renamed to during its implementation in 1990. Built over the existing TCP and IP protocols, it consisted of 4 building blocks: Mesh World Wide Web A textual format to represent hypertext documents, the (HTML). HyperText Markup Language A simple protocol to exchange these documents, the (HTTP). HypertText Transfer Protocol A client to display (and accidentally edit) these documents, the first Web browser called . WorldWideWeb A server to give access to the document, an early version of . httpd These four building blocks were completed by the end of 1990, and the first servers were already running outside of CERN by early 1991. On August 6th 1991, Tim Berners-Lee's on the public newsgroup is now considered as the official start of the World Wide Web as a public project. post alt.hypertext The HTTP protocol used in those early phases was very simple, later dubbed HTTP/0.9, and sometimes as the one-line protocol. HTTP/0.9 – The one-line protocol The initial version of HTTP had no version number; it has been later called 0.9 to differentiate it from the later versions. HTTP/0.9 is extremely simple: requests consist of a single line and start with the only possible method followed by the path to the resource (not the URL as both the protocol, server, and port are unnecessary once connected to the server). GET GET /mypage.html The response is extremely simple too: it only consisted of the file itself. <HTML>
A very simple HTML page
< /HTML> Unlike subsequent evolutions, there were no HTTP headers, meaning that only HTML files could be transmitted, but no other type of documents. There were no status or error codes: in case of a problem, a specific HTML file was send back with the description of the problem contained in it, for human consumption. HTTP/1.0 – Building extensibility HTTP/0.9 was very limited and both browsers and servers quickly extended it to be more versatile: Versioning information is now sent within each request ( is appended to the GET line) HTTP/1.0 A status code line is also sent at the beginning of the response, allowing the browser itself to understand the success or failure of the request and to adapt its behavior in consequence (like in updating or using its local cache in a specific way) The notion of HTTP headers has been introduced, both for the requests and the responses, allowing metadata to be transmitted and making the protocol extremely flexible and extensible. With the help of the new HTTP headers, the ability to transmit other documents than plain HTML files has been added (thanks to the header). Content-Type At this point, a typical request and response looked like this: GET /mypage.html HTTP/ User-Agent: NCSA_Mosaic/ (Windows ) OK : Tue, Nov : : GMT
Server: CERN/ libwww/ Content-Type: text/html
<HTML> 
A page an image
  <IMG SRC= > 1.0 2.0 3.1 200 Date 15 1994 08 12 31 3.0 2.17 with "/myimage.gif" </ > HTML Followed by a second connection and request to fetch the image (followed by a response to  that request): GET /myimage.gif HTTP/ User-Agent: NCSA_Mosaic/ (Windows ) OK : Tue, Nov : : GMT
Server: CERN/ libwww/ Content-Type: text/gif
(image content) 1.0 2.0 3.1 200 Date 15 1994 08 12 32 3.0 2.17 These novelties have not been introduced as concerted effort, but as a try-and-see approach over the 1991-1995 period: a server and a browser added one feature and it saw if it got traction. A lot of interoperability problems were common. In November 1996, in order to solve these annoyances, an informational document describing the common practices has been published, . This is the definition of HTTP/1.0 and it is notable that, in the narrow sense of the term, it isn't an official standard. RFC 1945 HTTP/1.1 – The standardized protocol In parallel to the somewhat chaotic use of the diverse implementations of HTTP/1.0, and since 1995, well before the publication of HTTP/1.0 document the next year, proper standardization was in progress. The first standardized version of HTTP, HTTP/1.1 was published in early 1997, only a few months after HTTP/1.0. HTTP/1.1 clarified ambiguities and introduced numerous improvements: A connection can be reused, saving the time to reopen it numerous times to display the resources embedded into the single original document retrieved. Pipelining has been added, allowing to send a second request before the answer for the first one is fully transmitted, lowering the latency of the communication. Chunked responses are now also supported. Additional cache control mechanisms have been introduced. Content negotiation, including language, encoding, or type, has been introduced, and allows a client and a server to agree on the most adequate content to exchange. Thanks to the header, the ability to host different domains at the same IP address now allows server colocation. Host A typical flow of requests, all through one single connection is now looking like this: GET /en-US/docs/Glossary/Simple_header HTTP/ Host: developer.mozilla.org
User-Agent: Mozilla/ (Macintosh; Intel Mac OS X ; rv: ) Gecko/ Firefox/ Accept: text/html,application/xhtml+xml,application/xml;q= ,* *
Accept-Language: en-US,en;q= Accept-Encoding: gzip, deflate, br
Referer: https: OK
Age: Cache-Control: public, max-age= Connection: keep-alive
Content-Length: Content-Type: image/png : Thu, Mar : : GMT
Last-Modified: Wed, Oct : : GMT
Server: Apache

(image content bytes) 1.1 5.0 10.9 50.0 20100101 50.0 0.9 /*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Referer: https://developer.mozilla.org/en-US/docs/Glossary/Simple_header

200 OK
Connection: Keep-Alive
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Date: Wed, 20 Jul 2016 10:55:30 GMT
Etag: "547fa7e369ef56031dd3bff2ace9fc0832eb251a"
Keep-Alive: timeout=5, max=1000
Last-Modified: Tue, 19 Jul 2016 00:59:33 GMT
Server: Apache
Transfer-Encoding: chunked
Vary: Cookie, Accept-Encoding

(content)


GET /static/img/header-background.png HTTP/1.1
Host: developer.cdn.mozilla.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
Accept: */ 0.5 //developer.mozilla.org/en-US/docs/Glossary/Simple_header 200 9578461 315360000 3077 Date 31 2016 13 34 46 21 2015 18 27 50 of 3077 HTTP/1.1 was first published as in January 1997. RFC 2068 More than 15 years of extensions Thanks to its extensibility – creating new headers or methods is easy – and even if the HTTP/1.1 protocol was refined over two revisions, published in June 1999 and the series of - published in June 2014 in prevision of the release of HTTP/2, this protocol has been extremely stable over more than 15 years. RFC 2616 RFC 7230 RFC 7235 The largest change that happened to HTTP was done as early as end of 1994. Instead of sending HTTP over a basic TCP/IP stack, Netscape Communication created an additional encrypted transmission layer on top of it: SSL. SSL 1.0 was never released outside the companies, but SSL 2.0 and its successors SSL 3.0 and SSL 3.1 allowed for the creation of e-commerce Web sites by encrypting and guaranteeing the authenticity of the messages exchanged between the server and client. SSL was put on the standards track and eventually became TLS, with version 1.0, 1.1, and 1.2 appearing successfully to close vulnerabilities. TLS 1.3 is currently in the making. Using HTTP for secure transmissions During the same time, the need for an encrypted transport layer raised: the Web left the relative trustiness of a mostly academic network, to a jungle where advertisers, random individuals or criminals compete to get as much private information about people, try to impersonate them or even to replace data transmitted by altered ones. As the applications built over HTTP became more and more powerful, having access to more and more private information like address books, e-mail, or the geographic position of the user, the need to have TLS became ubiquitous even outside the e-commerce use case. The original vision of Tim Berners-Lee for the Web wasn't a read-only medium. He envisioned a Web where people can add and move documents remotely, a kind of distributed file system. Around 1996, HTTP has been extended to allow authoring, and a standard called WebDAV was created. It has been further extended for specific applications like CardDAV to handle address book entries and CalDAV to deal with calendars. Using HTTP for complex applications But all these *DAV extensions had a flaw: they had to be implemented by the servers to be used, which was quite complex. Their use on Web realms stayed confidential. In 2000, a new pattern for using HTTP was designed: (or REST). The actions induced by the API were no more conveyed by new HTTP methods, but only by accessing specific URIs with basic HTTP/1.1 methods. This allowed any Web application to provide an API to allow retrieval and modification of its data without having to update the browsers or the servers: all what is needed was embedded in the files served by the Web sites through standard HTTP/1.1. representational state transfer The drawback of the REST model resides in the fact that each website defines its own non-standard RESTful API and has total control on it; unlike the *DAV extensions were clients and servers are interoperable. RESTful APIs became very common in the 2010s. Since 2005, the set of APIs available to Web pages greatly increased and several of these APIs created extensions, mostly new specific HTTP headers, to the HTTP protocol for specific purposes: , where the server can push occasional messages to the browser. Server-sent events , a new protocol that can be set up by upgrading an existing HTTP connection. WebSocket HTTP is independent of the security model of the Web, the . In fact, the current Web security model has been developed after the creation of HTTP! Over the years, it has proved useful to be able to be more lenient, by allowing under certain constraints to lift some of the restriction of this policy. Relaxing the security-model of the Web same-origin policy How much and when such restrictions are lifted is transmitted by the server to the client using a new bunch of HTTP headers. These are defined in specifications like (CORS) or the (CSP). Cross-Origin Resource Sharing Content Security Policy In addition to these large extensions, numerous other headers have been added, sometimes experimentally only. Notable headers are Do Not Track ( ) header to control privacy, , or but many more exist. DNT X-Frame-Options Upgrade-Insecure-Requests HTTP/2 – A protocol for greater performance Over the years, Web pages have become much more complex, even becoming applications in their own right. The amount of visual media displayed, the volume and size of  scripts adding interactivity, has also increased: much more data is transmitted over significantly more HTTP requests. HTTP/1.1 connections need requests sent in the correct order. Theoretically, several parallel connections could be used (typically between 5 and 8), bringing considerable overhead and complexity. For example, HTTP pipelining has emerged as a resource burden in Web development. In the first half of the 2010s, Google demonstrated an alternative way of exchanging data between client and server, by implementing an experimental protocol SPDY. This amassed interest from developers working on both browsers and servers. Defining an increase in responsiveness, and solving the problem of duplication of data transmitted, SPDY served as the foundations of the HTTP/2 protocol. The HTTP/2 protocol has several prime differences from the HTTP/1.1 version: It is a binary protocol rather than text. It can no longer be read and created manually.  Despite this hurdle, improved optimization techniques can now be implemented. It is a multiplexed protocol. Parallel requests can be handled over the same connection, removing the order and blocking constraints of the HTTP/1.x protocol. It compresses headers. As these are often similar among a set of requests, this removes duplication and overhead of data transmitted. It allows a server to populate data in a client cache, in advance of it being required, through a mechanism called the server push. Officially standardized, in May 2015, HTTP/2 has had much success. By July 2016, 8.7% of all Web sites were already using it, representing more than 68% of all requests . High-traffic Web sites showed the most rapid adoption, saving considerably on data transfer overheads and subsequent budgets. [1] [2] This rapid adoption rate was likely as HTTP/2 does not require adaptation of Web sites and applications: using HTTP/1.1 or HTTP/2 is transparent for them. Having an up-to-date server communicating with a recent browser is enough to enable its use: only a limited set of groups were needed to trigger adoption, and as legacy browser and server versions are renewed, usage has naturally increased, without further Web developer efforts. Post-HTTP/2 evolution HTTP didn't stop evolving upon the release of HTTP/2. Like with HTTP/1.x previously, HTTP's extensibility is still being used to add new features. Notably, we can cite new extensions of the HTTP protocol appearing in 2016: Support of allows the dissociation of the identification and the location of a given resource, allowing for a smarter caching mechanism. Alt-Svc CDN The introduction of allows the browser, or client, to proactively communicate information about its requirements, or hardware constraints, to the server. Client-Hints The introduction of security-related prefixes in the header, now helps guarantee a secure cookie has not been altered. Cookie This evolution of HTTP proves its extensibility and simplicity, liberating creation of many applications and compelling the adoption of the protocol. The environment in which HTTP is used today is quite different from that seen in the early 1990s. HTTP's original design proved to be a masterpiece, allowing the Web to evolve over a quarter of a century, without the need of a mutiny. By healing flaws, yet retaining the flexibility and extensibility which made HTTP such a success, the adoption of HTTP/2 hints at a bright future for the protocol. HTTP/3 - HTTP over QUIC This page is not complete. Draft Check the carefully before using this in production. This is an experimental technology Browser compatibility table The next major version of HTTP, HTTP/3, will use QUIC instead TCP/TLS for the transport layer portion. See for implementation status in Firefox. bug 1158011 Credits Source: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP Published under licence Open CC Attribution ShareAlike 3.0

STEPN

Flow

Apache

BUNCH

Fetch

Google

Intel

Mozilla

Read My Stories

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

Gradual Development of HTTP Protocol

Gradual Development of HTTP Protocol

Too Long; Didn't Read

Companies Mentioned

Coins Mentioned

Mozilla Contributors

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Gradual Development of HTTP Protocol

Too Long; Didn't Read

Companies Mentioned

Coins Mentioned

Mozilla Contributors

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES