This post originated from an RSS feed registered with Ruby Buzz by rwdaigle. Original Post: What's New in Edge Rails: RESTful Routes Get a New Custom Delimiter Feed Title: Ryan's Scraps Feed URL: http://feeds.feedburner.com/RyansScraps Feed Description: Ryan Daigle's various technically inclined rants along w/ the "What's new in Edge Rails" series. Latest Ruby Buzz Posts Latest Ruby Buzz Posts by rwdaigle Latest Posts From Ryan's Scraps

No really, I couldn���t think of any better way to title this post, and I apologize for that. However, if you actually clicked on this post from your feed reader, you are definitely a geek, and I like that in you.

So what���s this about? It���s really a tiny little change in RESTful routing, but it negates a lot of material out there, including my own. Whenever you have a custom action route defined in Rails:

map.resources :users, :collection => { :filter => :get }

the resulting route no longer uses a semi-colon (;) to delimit the custom action:

GET /users;filter

and instead will use your standard forward-slash (/):

GET /users/filter

Not a big change at all, but it has big repercussions if you���ve got remote clients accessing these URIs already. (And we all do now-a-days, right?).

tags: ruby, rubyonrails, REST