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

Making the Most of HTTP In Your Apps (php|tek 2...

Making the Most of HTTP In Your Apps (php|tek 2009)

200, 404, 302. Is it a lock combination? A phone number? No, they're HTTP status codes! As we develop Web applications, we encounter these status codes and others, and often we make decisions about which ones to return without giving much thought to their meaning or context. It's time to take a deeper look at HTTP. Knowing the methods, headers, and status codes, what they mean, and how to use them can help you develop richer Internet applications. Join Ben Ramsey as he takes you on a journey through RFC 2616 to discover some of the gems of HTTP.

Ben Ramsey

May 22, 2009
Tweet

More Decks by Ben Ramsey

Other Decks in Programming

Transcript

  1. ❖ A client-server architecture ❖ Atomic ❖ Cacheable ❖ A

    uniform interface ❖ Layered ❖ Code on demand
  2. Safe methods ❖ GET & HEAD should not take action

    other than retrieval ❖ These are considered safe ❖ Allows agents to represent POST, PUT, & DELETE in a special way
  3. Idempotence ❖ Side-effects of N > 0 identical requests is

    the same as for a single request ❖ GET, HEAD, PUT and DELETE share this property ❖ OPTIONS and TRACE are inherently idempotent
  4. ❖ Retrieval of information ❖ Transfers a representation of a

    resource from the server to the client ❖ Safe ❖ Idempotent GET
  5. HEAD ❖ Identical to GET, except... ❖ Returns only the

    headers, not the body ❖ Useful for getting details about a resource representation before retrieving the full representation ❖ Safe ❖ Idempotent
  6. POST ❖ The body content should be accepted as a

    new subordinate of the resource ❖ Append, annotate, paste after ❖ Not safe ❖ Non-idempotent
  7. PUT ❖ Opposite of GET ❖ Storage of information ❖

    Transfers a representation of a resource from the client to the server ❖ Not safe ❖ Idempotent
  8. DELETE ❖ Requests that the resource identified be removed from

    public access ❖ Not safe ❖ Idempotent
  9. 1. Client sends a request without a body and includes

    the Expect: 100-continue header and all other headers 2. Server determines whether it will accept the request and responds with 100 Continue (or a 4xx code on error) 3. Client sends the request again with the body and without the Expect header
  10. 2 HTTP/1.1 413 Request Entity Too Large Date: Thu, 21

    May 2009 23:05:15 GMT Server: Apache/2.2.11 (Unix) DAV/2 PHP/5.3.0RC2 X-Powered-By: PHP/5.3.0RC2 Content-Length: 0 Connection: close Content-Type: text/html Failure state
  11. 2 HTTP/1.1 100 Continue Date: Thu, 21 May 2009 23:05:15

    GMT Server: Apache/2.2.11 (Unix) DAV/2 PHP/5.3.0RC2 X-Powered-By: PHP/5.3.0RC2 Content-Length: 0 Content-Type: text/html Success state
  12. 4 HTTP/1.1 201 Created Date: Thu, 21 May 2009 23:05:34

    GMT Server: Apache/2.2.11 (Unix) DAV/2 PHP/5.3.0RC2 X-Powered-By: PHP/5.3.0RC2 Content-Length: 119 Content-Type: text/html Location: http://example.org/content/videos/1234 <html><body><p>Video uploaded! Go <a href="http://example.org/content/videos/ 1234">here</a> to see it.</p></body></html>
  13. 200 OK GET /content/videos/1234 HTTP/1.1 Host: example.org HTTP/1.x 200 OK

    Date: Thu, 21 May 2009 23:08:35 GMT Server: Apache/2.2.11 (Unix) DAV/2 PHP/5.3.0RC2 X-Powered-By: PHP/5.3.0RC2 Content-Type: video/mp4 Content-Length: 115910000 {binary data}
  14. 201 Created 1 POST /content/videos HTTP/1.1 Host: example.org Content-Type: video/mp4

    Content-Length: 115910000 Authorization: Basic bWFkZTp5b3VfbG9vaw== {binary video data}
  15. 201 Created 2 HTTP/1.x 201 Created Date: Thu, 21 May

    2009 23:05:34 GMT Server: Apache/2.2.11 (Unix) DAV/2 PHP/5.3.0RC2 X-Powered-By: PHP/5.3.0RC2 Content-Length: 119 Content-Type: text/html Location: http://example.org/content/videos/1234 <html><body><p>Video uploaded! Go <a href="http://example.org/content/videos/ 1234">here</a> to see it.</p></body></html>
  16. 202 Accepted 2 HTTP/1.x 202 Accepted Date: Thu, 21 May

    2009 23:05:34 GMT Server: Apache/2.2.11 (Unix) DAV/2 PHP/5.3.0RC2 X-Powered-By: PHP/5.3.0RC2 Content-Length: 137 Content-Type: text/html Location: http://example.org/content/videos/1234/status <html><body><p>Video processing! Check <a href="http://example.org/content/videos/1234/ status">here</a> for the status.</p></body></ html>
  17. 205 Reset Content “The server has fulfilled the request and

    the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action.”
  18. 206 Partial Content ❖ Used when requests are made for

    ranges of bytes from a resource ❖ Determine whether a server supports range requests by checking for the Accept-Ranges header with HEAD
  19. 2 HTTP/1.0 200 OK Date: Mon, 05 May 2008 00:33:14

    GMT Server: Apache/2.0.52 (Red Hat) Accept-Ranges: bytes Content-Length: 3980 Content-Type: image/jpeg
  20. 4 HTTP/1.0 206 Partial Content Date: Mon, 05 May 2008

    00:36:57 GMT Server: Apache/2.0.52 (Red Hat) Accept-Ranges: bytes Content-Length: 1000 Content-Range: bytes 0-999/3980 Content-Type: image/jpeg {binary data}
  21. 303 See Other ❖ The response to your request can

    be found at another URL identified by the Location header ❖ The client should make a GET request on that URL ❖ The Location is not a substitute for this URL
  22. 307 Temporary Redirect ❖ The resource resides temporarily at the

    URL identified by the Location ❖ The Location may change, so don’t update your links ❖ If the request is not GET or HEAD, then you must allow the user to confirm the action
  23. 302 Found ❖ The resource has been found at another

    URL identified by the Location header ❖ The new URL might be temporary, so the client should continue to use this URL ❖ Redirections SHOULD be confirmed by the user (in practice, browsers don’t respect this)
  24. 301 Moved Permanently ❖ The resource has moved permanently to

    the URL indicated by the Location header ❖ You should update your links accordingly ❖ Great for forcing search engines, etc. to index the new URL instead of this one
  25. ❖ 400 Bad Request ❖ 401 Unauthorized / 403 Forbidden

    ❖ 404 Not Found ❖ 405 Method Not Allowed ❖ 410 Gone
  26. ❖ 411 Length Required ❖ 413 Request Entity Too Large

    ❖ 415 Unsupported Media Type ❖ 416 Requested Range Not Satisfiable
  27. [bramsey@pippin ~] telnet phparch.com 80 Trying 64.34.173.96... Connected to phparch.com.

    Escape character is '^]'. HEAD / HTTP/1.1 Host: phparch.com
  28. [bramsey@pippin ~] telnet phparch.com 80 Trying 64.34.173.96... Connected to phparch.com.

    Escape character is '^]'. HEAD / HTTP/1.1 Host: phparch.com HTTP/1.1 200 OK Date: Thu, 21 May 2009 21:01:06 GMT Server: Apache/2.2.9 (Debian) PHP/5.2.5 mod_ssl/2.2.9 OpenSSL/0.9.8g X-Powered-By: PHP/5.2.5 Set-Cookie: PHPSESSID=eeeff50d3b6ae241c934a5c2671b0005; expires=Sun, 21 Jun 2009 21:01:07 GMT; path=/; domain=.phparch.com Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Content-Type: text/html; charset=utf-8 Connection closed by foreign host.
  29. ❖ header() function http://php.net/header ❖ Client URL library (cURL) http://php.net/curl

    ❖ Streams http://php.net/streams ❖ HTTP extension (pecl/http) http://php.net/http
  30. Questions? ❖ Slides posted at benramsey.com ❖ Rate this talk

    at joind.in/213 ❖ Read the HTTP spec at tools.ietf.org/html/rfc2616 ❖ My company is Schematic schematic.com