The requested resource does not support HTTP method 'GET'

Question

My route is correctly configured, and my methods have the decorated tag. I still get "The requested resource does not support HTTP method 'GET'" message?

[System.Web.Mvc.AcceptVerbs("GET", "POST")]
[System.Web.Mvc.HttpGet]
public string Auth(string username, string password)
{
  // Décoder les paramètres reçue.
  string decodedUsername = username.DecodeFromBase64();
  string decodedPassword = password.DecodeFromBase64();

  return "value";
}

Here are my routes:

config.Routes.MapHttpRoute(
    name: "AuthentificateRoute",
    routeTemplate: "api/game/authentificate;{username};{password}",
    defaults: new { controller = "Game",
                    action = "Auth", 
                    username = RouteParameter.Optional, 
                    password = RouteParameter.Optional },
    constraints: new { httpMethod = new HttpMethodConstraint(HttpMethod.Get) }
);

config.Routes.MapHttpRoute(
    name: "DefaultApi",
    routeTemplate: "api/{controller}/{id}",
    defaults: new { controller = "Home", id = RouteParameter.Optional }
);

score 236 · Accepted Answer · edited Jul 26 '14 at 19:54

236

Please use the attributes from the System.Web.Http namespace on your WebAPI actions:

    [System.Web.Http.AcceptVerbs("GET", "POST")]
    [System.Web.Http.HttpGet]
    public string Auth(string username, string password)
    {...}

The reason why it doesn't work is because you were using the attributes that are from the MVC namespace System.Web.Mvc. The classes in the System.Web.Http namespace are for WebAPI.

edited Jul 26 '14 at 19:54

amiry jd

27,021
30
116
215

answered Oct 07 '12 at 05:45

Maggie Ying

10,095
2
33
36

12

Damn.. thanks ! i was about to get crazy lol incredible how you can waste time on such small things.. – Rushino Oct 07 '12 at 13:59
1

Indeed, an explanation of **why** this is the correct answer is certainly necessary here! – Jaxidian Jul 15 '13 at 03:44
6

Edited answer with explanation. – Maggie Ying Jul 16 '13 at 17:53
2

can I specify [System.Web.Http.AcceptVerbs("GET", "POST")] and [System.Web.Http.HttpGet] in RouteConfig.cs so that I no need add this in each API. – Girish Gupta Sep 03 '15 at 06:11
8

Why did I need to do this in only one of my 10 apis for this project? I created the api in exactly the same way as in the other 9 apis. How frustrating. – Dan Beaulieu Oct 28 '15 at 18:29
1

Why is it allowed to specify GET/POST in AcceptVerbs but not do [System.Web.Http.HttpPost] ? – John Zabroski Jun 01 '16 at 19:25
It worked. Is anybody else happy with Microsoft naming spree? I guess they must have very expensive training somewhere that explains the difference. – Janusz Grabis Nov 03 '17 at 09:52

score 7 · Answer 2 · answered Nov 30 '18 at 01:26

In my case, the route signature was different from the method parameter. I had id, but I was accepting documentId as parameter, that caused the problem.

[Route("Documents/{id}")]   <--- caused the webapi error
[Route("Documents/{documentId}")] <-- solved
public Document Get(string documentId)
{
  ..
}

score 5 · Answer 3 · answered Sep 03 '20 at 15:06

5

Resolved this issue by using http(s) when accessing the endpoint. The route I was accessing was not available over http. So I would say verify the protocols for which the route is available.

answered Sep 03 '20 at 15:06

Marquis103

395
3
8

score 3 · Answer 4 · answered Jul 30 '18 at 09:52

3

just use this attribute

[System.Web.Http.HttpGet]

not need this line of code:

[System.Web.Http.AcceptVerbs("GET", "POST")]

answered Jul 30 '18 at 09:52

Kashif Faraz

321
6
19

score 2 · Answer 5 · answered Jan 08 '19 at 22:52

I was experiencing the same issue.. I already had 4 controllers going and working just fine but when I added this one it returned "The requested resource does not support HTTP method 'GET'". I tried everything here and in a couple other relevant articles but was indifferent to the solution since, as Dan B. mentioned in response to the answer, I already had others working fine.

I walked away for a while, came back, and immediately realized that when I added the Controller it was nested under the "Controller" class and not "ApiController" class that my other Controllers were under. I'm assuming I chose the wrong scaffolding option to build the .cs file in Visual Studio. So I included the System.Web.Http namespace, changed the parent class, and everything works without the additional attributes or routing.

The requested resource does not support HTTP method 'GET'

5 Answers5

Linked