gadimbaylisahil

desc 'Find routes that will raise a routing error when requested'
task unroutable_routes: :environment do
  # A lot of this code was taken from how `rake routes` works
  # https://github.com/rails/rails/blob/f95c0b7e96eb36bc3efc0c5beffbb9e84ea664e4/railties/lib/rails/commands/routes/routes_command.rb

  require 'action_dispatch/routing/inspector'

  unroutables = Rails.application.routes.routes.
     map { |r| ActionDispatch::Routing::RouteWrapper.new(r) }.
     reject { |r| r.internal? || r.engine? || r.path.starts_with?('/rails/') || !r.controller }.

gadimbaylisahil

Concept

• People talk about two servers: a web server (e.g. Nginx, Apache, etc.) and a app server (e.g. Language specific servers like Unicorn, Node.js, Tomcat, Http-Kit, etc.). There are exceptions where app servers not required at all (as web server itself provides preprocessors for handling), but let's not talk about now.
• Web servers are really fast and supports lot of standard and commonly used MIME-type requests. Concept of serving a file is -- forming and sending a response of bytes of data and labeling it with requested MIME-type by a client (e.g. web browser).
• Every response format (in layman's language, a file) is recognized by it's MIME-type, for e.g. a PNG image file has "image/png" MIME-type. JavaScript file has "text/javascript". HTML responses (or files) has "text/html". Plain text files have "text/plain".
• Modern Browsers supports a lot of standard MIME-types. Images, videos, text files (XML, HTML, SVG, JS), and they better know how to visualize it. Browser also knows unrec