# Support for HTTP OPTIONS method and Microsoft Office Protocol Discovery

**URL:** <https://www.ruby-forum.com/t/support-for-http-options-method-and-microsoft-office-protocol-discovery/141888>\
**Category:** Rails\
**Created:** [July 1, 2008, 1:33pm UTC](https://www.ruby-forum.com/t/support-for-http-options-method-and-microsoft-office-protocol-discovery/141888 "2008-07-01T13:33:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![waddilove](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/b5ac83/32.png) [@waddilove](https://www.ruby-forum.com/u/waddilove)\
**Post date:** [July 1, 2008, 1:33pm UTC](https://www.ruby-forum.com/t/support-for-http-options-method-and-microsoft-office-protocol-discovery/141888/1 "2008-07-01T13:33:26Z")

</div>

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](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](http://localhost/asdf/asdf/as/dfff/ff)), generated  
an exception due to

> <https://github.com/rails/rails/commit/dcaa074abf5691a933b9c55159cc7d98a02b3b2f>
>
> git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@6862 5ecf4fe2-1ee6-031…0-87b1-e25e094e27de

with more information found out:  
[http://dev.rubyonrails.org/ticket/6953](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?