Editorial
Routing
Every request received by a Ruby on Rails application is first processed by the Rails routing engine, which is configured by the routes.rb file. The routing rules determine which controller in loaded, and which action in that controller is invoked. The routing engine also works in reverse, mapping requested actions to URLs when generating URLs in Rails code.Enhancing Conditional Routing in Rails
Rails' routing infrastructure supports the concept of conditional routes: preconditions that must be satisfied before a particular route will trigger. Rails 2.1 supports one built-in condition, HTTP method checking, which is of some use but rather limited. What I needed was to be able to limit certain routes to only trigger when a particular host-name was used to access the application. I show one implementation in this article. continue...
Articles
New Articles
from around the Web
-
Ruby on Rails routing demystified
Article on Rails routing, excerpted from the excellent book The Rails Way.
-
Monkey-patching Rails: Extending Routes #2
Shows how to extend Rails routing to enable recognition by host, domain, or subdomain.
- Almost Effortless >> Redirect old URLs in Rails
Books
Sorry, no books yet
for this category
Have one to suggest? Enter in the form on the right.
Links
Links by Type
Documentation (1)
- Ryan's Scraps: What's New in Edge Rails: Shallow Routes
Now you can access your nested routes directly or through the complete nested resource path without specifying multiple manual routes.
Screencasts (4)
Blogs
Top Blogs
Sorry, no relevant blogs yet.
Have one to suggest? Enter in the form on the right.
