I think that adding a bool to HttpGetAttribute that said to ignore an method when trying to determine the correct route would be helpful. Then you could have multiple GetSomething calls within the same controller and avoid the ambiguous route exception. This would probably also need to be coupled with some kind of special route in the routetable to handle using named routes.