HTTP and Your Angry Dog
summary
Explains concrete HTTP mechanics: using the Accept header for content negotiation instead of URL extensions, teaching how the response Vary header lets proxies like Varnish cache correctly, and how ETag with If-None-Match yields 304 not modified savings while If-Match enables optimistic concurrency that returns 412 precondition failed on stale edits. Compares Cache-Control vs Expires, warns about gzip and mobile quirks, and demos tooling (Charles proxy, mentions Guzzle) with HTTP/1.1 practical guidance.
AI-written summary · about
chapters (22)
- 0:00Start
- 0:27About Myself
- 4:16Headers
- 6:02Content Negotiation
- 8:29Accept Header
- 9:26Server Driven Negotiation
- 10:09Content Type Header
- 11:51Double Wild Card
- 12:16Accept Headers
- 13:31Difference between Resource and Representation
- 14:12Best Way to Version Your Api
- 22:25Caching
- 24:02Cache Control
- 26:33Conditional Requests
- 32:29Recap
- 32:59The Concrete Benefits to this Type of Caching
- 36:05Optimistic Concurrency Control
- 38:45Scary Precondition Errors
- 39:48Tooling
- 41:43Words of Advice
- 43:47Charles Proxy
- 47:27What's Your Preferred Technique for a Client-Side Caching Validation Especially after Deployments or Changing Assets
related talks
33mTaming the Beast: Understanding and Harnessing the Power of HTTP Proxies
38mHTTP Headers that Make Your Website Go Faster
34mHow HTTP already solved all your performance problems 10 years ago
26mWhat’s next in the HTTP caching world
39mHTTP headers for the responsible developer
16mWhat's next in the HTTP caching world
44m#BackToBasics: The HTTP Cache
39mCaching the Uncacheable