mccalltd/AttributeRouting — pull request #82 by robertbeal (2012-05-30 16:07:17+00:00)
Title: OPTIONS verb

Hey, I don't know if this is the right way to implement it, but it would be really handy to allow OPTIONS on a resource (just as you do with GET and HEAD).

It does mean the consumer should implement their own OptionsActionFilter to modify the response, but this isn't too different from HEAD (as to be HTTP compliant the user should clear the response body, ideally done via an ActionFilter too).

The tests didn't ever seem to fail for my change when I added the new verb. Not sure if I've missed something.