HTTP: History & Performance - Ana Balica

The Hypertext Transfer Protocol is one of the most popular protocols nowadays. It’s the language most servers, clients, and even teapots can speak. Learn how and why it became such an ubiquitous part of the web by following the evolution of HTTP.
In regards to web performance, have you ever wondered why are we using minimization, concatenation, image spriting, resource inlining and other little hacks? Befriend the browser and help it to help you deliver the best user experience possible. Find out how TLS and HTTPS affect performance and what to look forward in HTTP/2.
This talk will contain references to archaic RFCs, lots of diagrams and long lists of best practices.
NDC Conferences
ndc-london.com
ndcconferences.com

[@domaincontroller]

01:21 HTTP, Hypermedia Transport Protocol ========================================= HTTP 0.9 (1991) ========================================= 02:13 HTTP & HTML, 1991, no RFC 02:35 its possible to speak to many servers in the wild in HTTP 0.9, you can telnet 03:19 the main features, no content data, client request is a single ASCII character string terminated by a newline 03:33 the only verb was, get 03:43 the server response is similarly byte stream of ASCII text, or mark up HTML 03:55 the response message is terminated by closing the connection followed by space, followed by the document address 04:13 there was no metadata, you couldn't do any content negotiation either ========================================= HTTP 1.0 (1996) ========================================= 04:40 tools.ietf.org/html/rfc1945 a proper spec 05:04 curl -v0 twitter.com 06:06 request consists multilines 06:17 protocol version, future 06:36 has its own set of newlines, newline separated headers 06:42 the connections is still closed after single request 06:45 response

[@trungcommandoanh]

kooool evolution