Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Gotta Wear Shades: The Bright Future of HTTP (CoderFaire Nashville 2013)

Gotta Wear Shades: The Bright Future of HTTP (CoderFaire Nashville 2013)

Hypertext Transfer Protocol (HTTP) version 1.1 was published in June of 1999. Almost fifteen years have passed. In that time, the Web has seen many changes, but it would seem that, throughout this time, HTTP has remained fixed, stagnant. Yet, nothing could be further from the truth.

HTTP is evolving, like languages, through common usage and need. In this talk, Ben Ramsey discusses the past fifteen years of HTTP and how it has changed through the introduction of new methods and headers. He covers the current state of the protocol and the new HTTPbis Working Group that is drafting new RFCs to clarify HTTP. Finally, the talk will take a look at proposals for HTTP version 2 and what this means for web developers.

Ben Ramsey

August 17, 2013

More Decks by Ben Ramsey

Other Decks in Programming


  1. PATCH Allows a set of changes to be described, rather

    than the full entity body. RFC 5789
  2. OPTIONS /books/1984 HTTP/1.1 Host: example.org HTTP/1.1 200 OK Allow: GET,

    HEAD, PUT, PATCH, OPTIONS, DELETE Accept-Patch: application/json-patch+json, text/diff
  3. PATCH /books/1984 HTTP/1.1 Host: example.org Content-Length: 188 Content-Type: application/json-patch+json [

    { "op": "replace", "path": "/isbn", "value": "978-0452262935" }, { "op": "add", "path": "/asin", "value": "0452262933" } ]
  4. More Status Codes Defines new codes for a variety of

    common uses, to improve interoperability, and to avoid confusion. RFC 6585
  5. Web Linking Defines a framework for typed links not specific

    to an application, and introduced the Link header. RFC 5988
  6. GET /books/?page=2 HTTP/1.1 Host: example.org HTTP/1.1 200 OK Content-Type: text/html

    Link: <http://example.org/books/?page=1>; rel="previous"; title="Page 1", <http://example.org/books/?page=3>; rel="next"; title="Page 3"
  7. Prefer Header Defines a header used by the client to

    request certain server behaviors when processing a request. draft-snell-http-prefer-18
  8. POST /collection HTTP/1.1 Host: example.org Content-Type: text/plain Prefer: respond-async {Data}

    HTTP/1.1 202 Accepted Location: http://example.org/collection/ 123 Preference-Applied: respond-async
  9. POST /collection HTTP/1.1 Host: example.org Content-Type: text/plain Prefer: return=minimal {Data}

    HTTP/1.1 201 Created Location: http://example.org/collection/ 123 Preference-Applied: return=minimal
  10. A document (or set of documents) that is suitable to

    supersede RFC 2616 as the definition of HTTP/1.1 and move RFC 2817 to Historic status
  11. A document (or set of documents) that specifies HTTP/2.0, an

    improved binding of HTTP's semantics to an underlying transport.
  12. HTTP/2.0 A new message encapsulation to enable efficient use of

    network resources and reduced latency through header field compression and multiple concurrent messages on the same connection.
  13. Frames HTTP messages are encoded into frames. These frames are

    a more efficient serialization of the message.
  14. Server Push A server may send multiple resources to the

    client in response to a single request.
  15. Resources HTTP/0.9 (1991): http://www.w3.org/Protocols/HTTP/AsImplemented.html HTTP/1.0 (draft 1992): http://www.w3.org/Protocols/HTTP/HTTP2.html HTTP/1.0 (draft

    1994): http://tools.ietf.org/html/draft-fielding-http-spec-00 HTTP 1.0 (May 1996): http://tools.ietf.org/html/rfc1945 HTTP/1.1 (Jan 1997): http://tools.ietf.org/html/rfc2068 (obsoleted by RFC 2616) HTTP/1.1 (Jun 1999): http://tools.ietf.org/html/rfc2616
  16. Resources WebDAV: http://www.webdav.org/ Well-known URIs: http://tools.ietf.org/html/rfc5785 Additional HTTP Status Codes:

    http://tools.ietf.org/html/rfc6585 Web Linking: http://tools.ietf.org/html/rfc5988 Deprecating the "X-" Prefix header: http://tools.ietf.org/html/rfc6648 Use of Content-Disposition: http://tools.ietf.org/html/rfc6266
  17. Resources HTTP Header Fields Registrations: http://tools.ietf.org/html/rfc4229 Prefer Header: http://tools.ietf.org/html/draft-snell-http-prefer-18 Well-known

    URI Registry: http://www.iana.org/assignments/well-known-uris/ Method Header Fields Registry: http://www.iana.org/assignments/message-headers/ HTTP Status Codes Registry: https://www.iana.org/assignments/http-status-codes/ JSON Patch: http://tools.ietf.org/html/rfc6902
  18. Resources HTTP/1.1 Message Syntax and Routing: http://datatracker.ietf.org/doc/draft-ietf-httpbis-p1-messaging/ HTTP/1.1 Semantics and

    Content: http://datatracker.ietf.org/doc/draft-ietf-httpbis-p2-semantics/ HTTP/1.1 Conditional Requests: http://datatracker.ietf.org/doc/draft-ietf-httpbis-p4-conditional/ HTTP/1.1 Range Requests: http://datatracker.ietf.org/doc/draft-ietf-httpbis-p5-range/ HTTP/1.1 Caching: http://datatracker.ietf.org/doc/draft-ietf-httpbis-p6-cache/ HTTP/1.1 Authentication: http://datatracker.ietf.org/doc/draft-ietf-httpbis-p7-auth/
  19. Resources HTTP/2.0: http://datatracker.ietf.org/doc/draft-ietf-httpbis-http2/ HTTP/2.0 Header Compression: http://datatracker.ietf.org/doc/draft-ietf-httpbis-header-compression/ Web Socket Protocol:

    http://tools.ietf.org/html/rfc6455 SPDY Protocol: http://tools.ietf.org/html/draft-mbelshe-httpbis-spdy-00 Apache mod_spdy: https://code.google.com/p/mod-spdy/ Nginx SPDY Module: http://nginx.org/en/docs/http/ngx_http_spdy_module.html
  20. Gotta Wear Shades: The Bright Future of HTTP Copyright ©

    Ben Ramsey. Some rights reserved. This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported. For uses not covered under this license, please contact the author. Ramsey, Ben. “Gotta Wear Shades: The Bright Future of HTTP.” CoderFaire. Nashville School of Law, Nashville, TN. 17 August 2013. Conference Presentation.