Support for HTTP OPTIONS method and Microsoft Office Protocol Discovery

[Jonathan Wallace]

I ran across an interesting issue with Microsoft Office Protocol
Discovery. It was generating exception emails due to its use of the
OPTIONS method. See http://rails.learnhub.com/lesson/page/2329-dealing-with-microsoft-office-protocol-discovery-in-rails
for more information.

I implemented the solution there but soon found that every request for
a non-existent URI (http://localhost/asdf/asdf/as/dfff/ff), generated
an exception due to

http://github.com/rails/rails/commit/dcaa074abf5691a933b9c55159cc7d98a02b3b2f
with more information found out:
http://dev.rubyonrails.org/ticket/6953

It is strange to me that the route matching would throw an error
because the path matched but the method doesn't. Shouldn't the route
matching continue through the rest of the routes before making that
determination?

[Aymeric Bouzy]

I have had the same issue. It would be great if rails could automatically add routes for the OPTIONS http verb based on the config/routes.rb file.

I filed an issue on Github before discovering this list : https://github.com/rails/rails/issues/27655#issuecomment-272298609