{"push_id":1229762803,"size":1,"distinct_size":0,"ref":"refs/heads/rel/1.0.1","head":"f0732e9e214d72db813acf6df4e7b2036ca1b8b0","before":"5092e75387f294ce89c7a0ce06d575edfd0848d2","commits":[{"sha":"f0732e9e214d72db813acf6df4e7b2036ca1b8b0","author":{"name":"jacalvar","email":"fd4383d25e6b032db41c6e618e146bb766410511@microsoft.com"},"message":"[Fixes #5038] HTTP Verbs mapping error GET and DELETE\n\nWhen an action contained an attribute derived from HttpMethodAttribute,\ndoesn't specify an attribute route and there is also another attribute\nextending HttpMethodAttribute that has a route defined on it; we ignored\nthe HttpMethodAttribute attribute without a defined route when building\nthe set of action selectors for the method.\n\nThis caused the resulting action to be unbounded and to accept requests\nfor other verbs not associated with it. The root cause of the problem was\nthat attributes override equality and do a field by field comparison but\nignore fields in the base classes of the type, so if an attribute is part\nof a class hierarchy (like Http*Attributes) there might be two different\nattributes that get considered equal.\n\nThe fix for the problem has been to change using Contains on a couple of\ncollections (that uses the equals method on the underlying object) and\ncheck for the existence of the attribute on the collection directly by\nusing reference equality.","distinct":false,"url":"https://api.github.com/repos/aspnet/Mvc/commits/f0732e9e214d72db813acf6df4e7b2036ca1b8b0"}]}
{"actor":{"display_login":"javiercn"}}