Explores the nature of HTTP1 requests and how it relates the design and implementation of Rack in ruby. Concludes with a discussion on the future of, and successors to, rack.
Center for Supercomputing Applications Allowed web servers to interact with executables and dynamically generate webpages Along with passed query params server also sets up a set of environmental variables
accepts a hash on CGI-like environment call returns an array containing: a status code a hash of response headers an object that represents the body that responds to .each and contains strings for the body
used by devise (the rails auth gem) redirects the user to a failure app with a 401 status code when not authenticated app can trigger auth failure by throwing a warden error: throw(:warden)
behind that env/request hash The env hash is setup like a CGI environment but we are getting farther and farther away from CGI environment NoMethodError on an Object vs. nil from a hash
Rails application. It allows for real-time features to be written in Ruby in the same style and form as the rest of your Rails application, while still being performant and scalable.”