3. HTTPbis
• IETF Working Group to clean up the mess.
• One 176 page spec -> Seven modular specs
• Mere mortals SHOULD now be able to
understand.
4. header i18n
• HTTP/1.1 makes headers Latin-1
• Can encode using RFC2231, but that’s
freaking MIME!
• Asia, rest of world: “pls fix this kthxbye.”
• draft-reschke-rfc2231-in-http
6. Stale Controls
• Two Cache-Control extensions:
• Hide latency by serving stale content
while doing an async refresh.
• Serve stale content if there’s a problem.
• RFC5861
7. Prefer
• Allow clients to ask for an empty response
• E.g., on a POST / PUT API
• draft-snell-http-prefer-02
8. Link
• HTTP header to express typed links
• Coordination between Atom, HTML5, W3C
TAG, RDF, IETF, IESG...
• Registry of link relation types
• Build protocols -- e.g., discovery
• draft-nottingham-http-link-header-10
9. PATCH
• Send a diff to a resource to update it
• Think of it as a partial PUT
• Requires client support
• RFC5789
14. Signed Responses
• Intermediaries should look but not touch.
• Signing the response bytes + some headers
• Allows caches to work without worrying
about integrity / modification.
• SINE