Skip to content

Instantly share code, notes, and snippets.

@simeonwillbanks

simeonwillbanks/how-a-request-becomes-a-response.md

Last active August 29, 2015 14:02
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save simeonwillbanks/28dab6d66f4f7a628387 to your computer and use it in GitHub Desktop.
Save simeonwillbanks/28dab6d66f4f7a628387 to your computer and use it in GitHub Desktop.
Download ZIP
"How a Request Becomes a Response (In Rails)" Summary
Raw
how-a-request-becomes-a-response.md

How a Request Becomes a Response

A RailsConf 2013 intro talk by Aimee Simone & Christopher Green

Video | Slides

Summary:

  1. Request Made
    • GET https://www.codeschool.com/
  2. Request accepted by web server (apache), passed to application server (passenger)
  3. Application server gives request to Rails process
  4. Rails process runs through middleware stack and processes request
  5. Request path and method mapped to controller and action
  6. Controller action gathers information from models (activerecord, database) to supply the view
  7. View template creates HTML for HTTP response (headers, status, body)
  8. View writes HTML to response body
  9. Response travels back through middleware stack
  10. Response is returned to browser
  11. Response received!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment