routes

In Play 1, new actions you defined had a default route. * /{controller}/{action} {controller}.{action} (This appeared by default in new projects) What is the Play 2/2.1 equivalent? Why doesn't it appear in the default routes file? biesior Actually there is a catch-all route available. According to the routing doc in Play 2.0+ you can use Dynamic parts spanning several / so if you put it as exactly last route of given method it will catch every route that wasn't catch before. You can use this for further processing for an example if you have other 'routes' stored in DataBase. GET /*path

I've seen both being used and so I wonder, do they do the same thing or different things? If it's the latter, what's the difference? I tried answering it myself by having a look at the visual studio MVC 4 (rc) web api template, but sadly it uses both, so my confusion remains. Here's what the template contains: public class RouteConfig { public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapHttpRoute( name: "DefaultApi", routeTemplate: "api/{controller}/{id}", defaults: new { id = RouteParameter.Optional } ); routes.MapRoute(

In the Ruby on Rails 3 tutorial, the code uses: match '/signup', :to => 'users#new' match '/signin', :to => 'sessions#new' match '/signout', :to => 'sessions#destroy' match '/contact', :to => 'pages#contact' match '/about', :to => 'pages#about' match '/help', :to => 'pages#help' rather than get '/signup', :to => 'users#new' get '/signin', :to => 'sessions#new' get '/signout', :to => 'sessions#destroy' get '/contact', :to => 'pages#contact' get '/about', :to => 'pages#about' get '/help', :to => 'pages#help' even though all the routes only want the HTTP GET verb. Why not use get (or :via => [

I had a functioning redirect in my routes.rb like so; match "/invoices" => redirect("/dashboard") I now want to add a query string to this so that, e.g., /invoices?show=overdue will be redirected to /dashboard?show=overdue I've tried several things. The closest I have got is; match "/invoices?:string" => redirect("/dashboard?%{string}") which gives me the correct output but with the original URL still displayed in the browser. I'm sure I'm missing something pretty simple, but I can't see what. You can use request object in this case: match "/invoices" => redirect{ |p, request| "/dashboard?#

I'm trying to follow this tutorial to setup a modal containing a nested form in my Rails 4 app. I have models for Project and Invite. The associations are: Project has_many :invites Invite belongs_to :project In my views projects folder, I have made a partial called new_invitation.html.erb <div class="modal-header"> <button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button> <h3 id="myModalLabel">Modal header</h3> </div> <div class="modal-body"> **here comes whatever you want to show!** </div> <div class="modal-footer"> <button class="btn" data-dismiss="modal" aria

I am making a REST service in Rails. Here are my routes. resources :users match '/users', :controller => 'users', :action => 'options', :constraints => {:method => 'OPTIONS'} I am able to [GET] my users. I am trying to update my users and I get an error: ActionController::RoutingError (No route matches [OPTIONS] "/users/1"): When I run rake routes here are the routes that I am given: users GET /users(.:format) users#index POST /users(.:format) users#create new_user GET /users/new(.:format) users#new edit_user GET /users/:id/edit(.:format) users#edit user GET /users/:id(.:format) users#show PUT