How many times have you re-implemented the same patterns for handling GETs, PUTs, POSTs, and DELETEs (if any)? Do you include headers specified by the HTTP RFCs or ignore them entirely? HTTP is a complicated beast. Wouldn't it be nice if you could leverage an engine to drive these mundane details for you? You can, and you've been able to do this for quite some time in languages like Erlang, Ruby, Clojure, node.js, and more. Freya recently brought the web machine approach to .NET, and it offers a few new bells and whistles, including pluggable machine graphs and mixins. This talk will highlight some of the challenges in building web apps and show how the machine approach can help you focus more on building your applications and less on getting the HTTP parts right.