Ran into an issue where certain routes defined on attributes fail. It seems to b only certain cases and I've documented them in the following StackOverflow question.
http://stackoverflow.com/questions/21871471/http-put-failing-on-iis-8-5
In essence the "root" route does not seem to work with a prefix. So in my specific example I can't have a prefix of api on the products controller and thus define a route as "api/products" and to a PUT to it. Only the "products" will work.
Comments: Hi, We took a look at the information provided on stackoverflow post, but we suspect there might be something else going on and not really related to attribute routing. 1. When you receive a 405 Method Not Allowed response, you should see a "Allow" header in the response. Are you seeing that? if yes, what values does it have? 2. Are you using any Url rewriting module? 3. Can you give us the request details (Httpmethod used, Url etc) information in case of PUT request? We are specifically looking for the request Url coming into Web API and so for this, create a message handler and add it to HttpConfiguration. Inside this message handler you can inspect the incoming request's details. 4. Can you provide a standalone repro project for this? Thanks, Kiran
http://stackoverflow.com/questions/21871471/http-put-failing-on-iis-8-5
In essence the "root" route does not seem to work with a prefix. So in my specific example I can't have a prefix of api on the products controller and thus define a route as "api/products" and to a PUT to it. Only the "products" will work.
Comments: Hi, We took a look at the information provided on stackoverflow post, but we suspect there might be something else going on and not really related to attribute routing. 1. When you receive a 405 Method Not Allowed response, you should see a "Allow" header in the response. Are you seeing that? if yes, what values does it have? 2. Are you using any Url rewriting module? 3. Can you give us the request details (Httpmethod used, Url etc) information in case of PUT request? We are specifically looking for the request Url coming into Web API and so for this, create a message handler and add it to HttpConfiguration. Inside this message handler you can inspect the incoming request's details. 4. Can you provide a standalone repro project for this? Thanks, Kiran