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.
By clicking this button you are declaring that you are the speaker responsible for it and a claim request will be sent to the administrator of the event.
If the claim is approved you will be able to edit the information for this talk.
Great tips and tricks plus some basic overview information on HTTP and REST. Ben Ramsey definitely needs a tutorial session and/or there need to be more presentations on this topic. HTTP is what we all do every day without knowing it. We could all use some additional understanding of it.
When it comes to HTTP, this talk provides a good balance of "how it's defined", "what you should do", "what people have done", and "why you should/shouldn't do".
I could easily see this extended into a tutorial-length session that drills deeper into use cases for various status code event sequences and the rationale behind good and bad code sequences.
Know of an event happening? Let us know! We love to get the word out about events the community would be interested in and you can help us spread the word!
30.Sep.2009 at 13:52 by Benjamin Young
Great tips and tricks plus some basic overview information on HTTP and REST. Ben Ramsey definitely needs a tutorial session and/or there need to be more presentations on this topic. HTTP is what we all do every day without knowing it. We could all use some additional understanding of it.