How do you route [OPTIONS] in Rails?

Question

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    /users/:id(.:format)      users#update
          DELETE /users/:id(.:format)      users#destroy
                 /users(.:format)          users#options {:method=>"OPTIONS"}

Could someone please show me how to fix my routes so I can make any kind of REST call? Thanks.

score 11 · Answer 1 · answered Aug 26 '14 at 17:18

11

match '/users' => "users#options", via: :options

would also be a possible route if placed before the other routes.

answered Aug 26 '14 at 17:18

pensan

420
8
11

score 5 · Answer 2 · answered May 07 '15 at 01:12

5

If you don't want to create two additional routes for /users and for /users/id you can do this:

match 'users(/:id)' => 'users#options', via: [:options]

In this case, the id become optional, both /users and /users/id will respond to the same route.

answered May 07 '15 at 01:12

William Weckl

2,435
4
26
43

jhamm · Answer 3 · 2013-01-26T21:26:50.663

3

The reason that I could not route the request, was that my match did not have the user id in it. I added the line:

match '/users/:id', :controller => 'users', :action => 'options', :constraints => {:method => 'OPTIONS'}

and now I can route all of my GET request.

edited Jan 26 '13 at 21:26

answered Jan 26 '13 at 20:48

jhamm

24,124
39
105
179

score 1 · Answer 4 · answered Feb 03 '22 at 07:10

If you met this problem using javascript's ajax call, you maybe meet the cross-site problem. (e.g. your browser's current url is : http://a.xx.com and the ajax send a request to http://b.xx.com ) , then Rails / other-backend-server will get this kind of OPTIONS request.

To avoid this, besides changing your ruby code, I suggest you do one of these two solutions:

add CORS support using: https://github.com/cyu/rack-cors, lines of code just work.
send all the request to a.xx.com, then change your Nginx's config, redirect these requests to b.xx.com.

By the way, I don't suggest you change your routes.rb file to support OPTIONS request. This will mess your code up.

refer to: AXIOS request method changes to 'OPTIONS' instead of 'GET'

How do you route [OPTIONS] in Rails?

4 Answers4

Linked