Download as PDF, PPTX
Uploaded byAlessandro Nadalin
HTTP colon slash slash: end of the road? @ CakeFest 2013 in San Francisco
The document provides a detailed overview of the evolution of HTTP protocols, focusing on the transition from HTTP/1.0 through HTTP/1.1 to HTTP/2.0. It discusses caching mechanisms, conditional requests, and the introduction of techniques like ESI and hinclude to optimize dynamic page serving. The presentation emphasizes the efficiency improvements and structural similarities maintained in the newer protocols while outlining their historical context and development.
More Related Content
Similar to HTTP colon slash slash: end of the road? @ CakeFest 2013 in San Francisco
![[BDD 2025 - Full-Stack Development] The Modern Stack: Building Web & AI Appli...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-themodernstackbuildingwebaiapplicationswithserverless-251124030844-388cf04f-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Mobile Development] Exploring Apple’s On-Device FoundationModels](https://cdn.slidesharecdn.com/ss_thumbnails/md-exploringappleson-devicefoundationmodels-251124030840-d690542c-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Full-Stack Development] Digital Accessibility: Why Developers nee...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-digitalaccessibilitywhydevelopersneedtoknowandcarein2025-251127011019-0674441d-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Artificial Intelligence] AI for the Underdogs: Innovation for Sma...](https://cdn.slidesharecdn.com/ss_thumbnails/ai-aifortheunderdogsinnovationforsmallbusinesses-251124030839-72a599a4-thumbnail.jpg?width=640&height=640&fit=bounds)
HTTP colon slash slash: end of the road? @ CakeFest 2013 in San Francisco
- 1.
- 2.
- 3.
- 4.
- 5.
- 6. AGENDA . History ofHTTP . Hidden features . HTTP/2.0 . SPDY
- 7.
- 8.
- 9.
- 10.
- 11. Any user caneasily interact with a Webpage.
- 12. ( except mymom )
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25. Web development? www Clients M2MServers Automation verbs domains workflows logic constraints Tim Berners-Lee RoyFielding GET separate connections POST HEAD1996
- 26.
- 27. Web development? www Clients M2MServers Automation verbs domains workflows logic constraints Tim Berners-Lee RoyFielding GET separate connections POST HEAD1996
- 28. Web development? www Clients M2MServers Automation verbs domains workflows logic constraints Tim Berners-Lee RoyFielding 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 RoyFielding 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 RoyFielding GET separate connections POST HEAD1996 DIFF PUT DELETE PATCH TRACE OPTIONS Cache
- 31.
- 32. GET /users/1 HTTP/1.1 Host: example.com HTTP/1.1200 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.
- 35. and here area few ways to do so, using expiration validation invalidation
- 36.
- 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.
- 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.
- 53. Calculating an Etagis cheaper than generating a full MVC response
- 54. HTTP/1.1 304 NotModified
- 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.
- 59. Calculating a dateis cheaper than retrieving an entire object
- 60. HTTP/1.1 304 NotModified
- 61. but hey, yousay
- 62. HTTP's cache failswhen 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.
- 64. ESI was builtfor that http://www.w3.org/TR/esi-lang
- 65. HInclude was builtfor that http://mnot.github.com/hinclude/
- 66. So what doesHTTP cache is meant to solve?
- 67.
- 68. because the hardwork is delegated to the browser/proxy http://www.flickr.com/photos/snakphotography/5004775320/sizes/o/in/photostream/
- 69.
- 70. because cache isabstracted from the application
- 71.
- 72. because caching isbound to the protocol, HTTP, not to your implementation ( Sf, RoR, Django )
- 73. We’ve just ignoredit so far
- 74.
- 75.
- 76. Nothing to seehere.
- 77.
- 79.
- 80.
- 85.
- 86.
- 87.
- 88.
- 89.
- 90.
- 91.
- 92.
- 93.
- 94.
- 95.
- 96.
- 97.
- 98.
- 99.
- 100.
- 101.
- 102.
- 103.
- 105.
- 106.
- 107.
- 108.
- 109. GET /index.html HTTP/1.1 Host:www.example.com SURPRISE!
- 110. it will bea binary protocol http://tech.slashdot.org/story/13/07/09/1455200/http-20-will-be-a-binary-protocol
- 111. 00 39 0105 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
- 112.
- 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.
- 116.
- 117.
- 118.
- 119. SPDY doesnt changethe protocol, it just changes the way messages are exchanged over the wire
- 120. Semantics are thesame.
- 121. Workflows are thesame.
- 122. Verbs are thesame.
- 123. The interface isthe same.
- 124. “The minimum barto 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 isbased on?
- 126.
- 127.
- 128. An architecture thatlasts 20 years is possible.
- 129.
- 130.
- 131.
- 132.
- 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