HTTP colon slash slash: end of the road? @ CakeFest 2013 in San Francisco
•
3 likes•3,788 views
The HTTP protocol has been there for more than 20 years, almost untouched, but the current needs of the web are pushing towards adding some spices into the mix. In this talk we will have a brief look at the history of HTTP, what SPDY - the "new" protocol proposed by google - brings into the table and how HTTP/2.0 will look like.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to HTTP colon slash slash: end of the road? @ CakeFest 2013 in San Francisco
Similar to HTTP colon slash slash: end of the road? @ CakeFest 2013 in San Francisco (20)
More from Alessandro Nadalin
More from Alessandro Nadalin (20)
Recently uploaded
Recently uploaded (20)
HTTP colon slash slash: end of the road? @ CakeFest 2013 in San Francisco
- 2. WARNING
- 4. 2ND WARNING
- 6. AGENDA . History of HTTP . Hidden features . HTTP/2.0 . SPDY
- 7. HTTP/X.Y ?
- 8. HTTP/1.1?
- 11. Any user can easily interact with a Webpage.
- 12. ( except my mom )
- 14. They need rules.
- 18. PROTOCOLS
- 20. 1991
- 21. HTTP/0.9
- 22. HTTP/1.0
- 24. Web development? www Clients M2MServers Automation verbs domains workflows logic constraints Tim Berners-Lee Roy Fielding 1996
- 25. Web development? www Clients M2MServers Automation verbs domains workflows logic constraints Tim Berners-Lee Roy Fielding GET separate connections POST HEAD1996
- 26. HTTP/1.1
- 27. Web development? www Clients M2MServers Automation verbs domains workflows logic constraints Tim Berners-Lee Roy Fielding GET separate connections POST HEAD1996
- 28. Web development? www Clients M2MServers Automation verbs domains workflows logic constraints Tim Berners-Lee Roy Fielding GET separate connections POST HEAD1996 DIFF PUT DELETE PATCH TRACE OPTIONS
- 29. Web development? www Clients M2MServers Automation verbs domains workflows logic constraints Tim Berners-Lee Roy Fielding GET separate connections POST HEAD1996 DIFF PUT DELETE PATCH TRACE OPTIONS
- 30. Web development? www Clients M2MServers Automation verbs domains workflows logic constraints Tim Berners-Lee Roy Fielding GET separate connections POST HEAD1996 DIFF PUT DELETE PATCH TRACE OPTIONS Cache
- 31. CACHE
- 32. GET /users/1 HTTP/1.1 Host: example.com HTTP/1.1 200 Ok Etag: 123abc GET /users/1 HTTP/1.1 Host: example.com If-None-Match: 123abc HTTP/1.1 304 Not Modified POST /users/1 HTTP/1.1 Host: example.com Etag: 123abcdefgh ... HTTP/1.1 412 Precondition Failed
- 33. GET /users/1 HTTP/1.1 Host: example.com HTTP/1.1 200 Ok Cache-Control: max-age=60 GET /users/1 HTTP/1.1 Host: example.com
- 34. FOR FREE
- 35. and here are a few ways to do so, using expiration validation invalidation
- 36. Expiration
- 37. GET / HTTP/1.1 Host: www.example.com Expires: 0
- 38. GET / HTTP/1.1 Host: www.example.com Expires: 0
- 39. GET / HTTP/1.1 Host: www.example.com Expires: Tue, 15 Nov 1994 01:00 GMT
- 40. GET / HTTP/1.1 Host: www.example.com Cache-Control: max-age=60, public
- 41. GET / HTTP/1.1 Host: www.example.com Cache-Control: max-age=60, public
- 42. GET / HTTP/1.1 Host: www.example.com Cache-Control: max-age=60, public Cacheable for 60 seconds
- 43. GET / HTTP/1.1 Host: www.example.com Cache-Control: max-age=60, public Cacheable by both local and shared caches
- 44. GET / HTTP/1.1 Host: www.example.com Cache-Control: stale-if-error=600, stale-while-revalidate=600
- 45. GET / HTTP/1.1 Host: www.example.com Cache-Control: stale-if-error=600, stale-while-revalidate=600 fault-tolerant
- 46. GET / HTTP/1.1 Host: www.example.com Cache-Control: stale-if-error=600, stale-while-revalidate=600 available during downtime
- 47. GET / HTTP/1.1 Host: www.example.com Cache-Control: stale-if-error=600, stale-while-revalidate=600 available during revalidation
- 48. Validation
- 49. GET / HTTP/1.1 Host: www.example. com Etag: 1234
- 50. GET / HTTP/1.1 Host: www.example. com Etag: 1234 an identifier for your response
- 51. GET / HTTP/1.1 Host: www.example. com If-None-Match: 1234 the browsers asks you if it has been modified Conditional requests
- 52. Relax
- 53. Calculating an Etag is cheaper than generating a full MVC response
- 54. HTTP/1.1 304 Not Modified
- 55. GET / HTTP/1.1 Host: www.example.com Last-Modified: Tue, 15 Jan 2011 12:00:00 GMT
- 56. GET / HTTP/1.1 Host: www.example.com Last-Modified: Tue, 15 Jan 2011 12:00:00 GMT tell the client about the latest change
- 57. GET / HTTP/1.1 Host: www.example.com If-Modified-Since: Tue, 15 Jan 2011 12:00:00 GMT the client asks you if it has been modified since the last time Conditional requests
- 58. Relax
- 59. Calculating a date is cheaper than retrieving an entire object
- 60. HTTP/1.1 304 Not Modified
- 61. but hey, you say
- 62. HTTP's cache fails when dealing with really dynamic pages, because consumers will always have to hit the origin server, although a part of the page would be cacheable ( header and footer, for example )
- 63. Nope
- 64. ESI was built for that http://www.w3.org/TR/esi-lang
- 65. HInclude was built for that http://mnot.github.com/hinclude/
- 66. So what does HTTP cache is meant to solve?
- 67. Less work
- 68. because the hard work is delegated to the browser/proxy http://www.flickr.com/photos/snakphotography/5004775320/sizes/o/in/photostream/
- 69. evolve
- 70. because cache is abstracted from the application
- 71. loose coupling
- 72. because caching is bound to the protocol, HTTP, not to your implementation ( Sf, RoR, Django )
- 73. We’ve just ignored it so far
- 74. for 22 years
- 75. HTTP/2.0
- 76. Nothing to see here.
- 77. SPDY
- 80. You're already using it
- 85. HTTP on steroids
- 87. Client Server
- 88. Client Server
- 89. Client Server
- 90. Client Server
- 91. Compression
- 93. Multiplexing
- 102. Server push
- 103. Result?
- 105. Not-so-side effect?
- 106. 14 years later...
- 107. HTTP/2.0
- 109. GET /index.html HTTP/1.1 Host: www.example.com SURPRISE!
- 110. it will be a binary protocol http://tech.slashdot.org/story/13/07/09/1455200/http-20-will-be-a-binary-protocol
- 111. 00 39 01 05 00 00 00 01 84 83 42 11 77 77 77 2e 67 6f 6f 67 6c 65 2e 63 6f 6d 3a 38 30 4c 0d 6d 79 2d 75 73 65 72 2d 61 67 65 6e 74 40 0d 78 2d 73 6f 6d 65 2d 68 65 61 64 65 72 05 66 69 72 73 74
- 113. GET /default.htm HTTP/1.1 Host: server.example.com Connection: Upgrade, HTTP2-Settings Upgrade: HTTP/2.0 HTTP2-Settings: <base64url-encoded HTTP/2.0 settings>
- 114. GET /default.htm HTTP/1.1 Host: server.example.com Connection: Upgrade, HTTP2-Settings Upgrade: HTTP/2.0 HTTP2-Settings: <base64url-encoded HTTP/2.0 settings>
- 115. Based on?
- 117. Which is based on?
- 118. HTTP/1.1
- 119. SPDY doesnt change the protocol, it just changes the way messages are exchanged over the wire
- 120. Semantics are the same.
- 121. Workflows are the same.
- 122. Verbs are the same.
- 123. The interface is the same.
- 124. “The minimum bar to entry for replacing HTTP/1.1 is to exactly support its semantics and capabilities, while making it more efficient” Mark Nottingham http://www.mnot.net/blog/2009/11/13/flip
- 125. And HTTP/1.1 is based on?
- 126. HTTP/1.0
- 127. Published 17 years ago
- 128. An architecture that lasts 20 years is possible.
- 129. ( REST )
- 130. ...yawn...
- 131. Alessandro Nadalin
- 133. Alessandro Nadalin @_odino_ Namshi | Rocket Internet
- 134. Alessandro Nadalin @_odino_ Namshi | Rocket Internet VP Technology
- 135. Alessandro Nadalin @_odino_ Namshi | Rocket Internet VP Technology odino.org
- 136. Thanks! Alessandro Nadalin @_odino_ Namshi | Rocket Internet VP Technology odino.org