Postman调用MVC Web API报错Post Not Allowed，路由异常求助

Hey David, let’s work through this frustrating "Post Not Allowed" error you’re facing with your Visual Studio MVC Web API. I’ve debugged similar issues dozens of times, so here are the most likely fixes to check step by step:

1. Confirm Postman is Using the Correct Request Method #

First things first—double-check that you’ve selected POST in Postman’s dropdown (not GET, PUT, or anything else). It’s easy to accidentally leave it on GET, which will immediately trigger a 405 "Method Not Allowed" error when hitting your POST-only endpoint.

Also, verify the Content-Type header in Postman (under the "Headers" tab) is set appropriately. Since you’re passing parameters in the URL, application/x-www-form-urlencoded or even just leaving it blank might work, but application/json is safe if you ever switch to body parameters later.

2. Fix Route Parameter Name Mismatches #

Looking at your code, there’s a case-sensitive mismatch between your route template and method parameters that’s probably breaking the route match:

• Your route uses lowercase parameters: {description}/{customerRef}/{contractTypeId}/...
• Your method uses uppercase starting letters: string Description, string CustomerRef, int ContractTypeId...

Web API requires route parameter names to exactly match method parameter names (unless you explicitly map them with attributes). You have two fixes here:

Option A: Align Route Template to Method Parameters #

Update your Route attribute to match the method’s parameter casing:

[System.Web.Http.Route("AddCustomer/{Description}/{CustomerRef}/{ContractTypeId}/{startDate}/{EndDate}")]

Option B: Explicitly Map Parameters with [FromUri] #

If you want to keep the route template lowercase, add the [FromUri] attribute to each method parameter to map it to the route variable:

public async Task AddCustomer(
    [FromUri(Name = "description")] string Description,
    [FromUri(Name = "customerRef")] string CustomerRef,
    [FromUri(Name = "contractTypeId")] int ContractTypeId,
    DateTime startDate,
    DateTime EndDate
)

3. Verify You’re Using the Correct HttpPost Attribute #

You mentioned using [System.Web.Http.HttpPost]—that’s the right one for Web API (MVC uses System.Web.Mvc.HttpPost, which won’t work here). Double-check that you haven’t accidentally imported the wrong namespace at the top of your controller file. If both namespaces are imported, you might be using the MVC attribute without realizing it, which Web API ignores (treating the method as a GET by default).

4. Ensure Attribute Routing is Enabled #

For your [Route] attributes to work at all, you need to enable attribute routing in your WebApiConfig.cs file. Make sure this line comes before your global route configuration:

public static class WebApiConfig
{
    public static void Register(HttpConfiguration config)
    {
        // Enable attribute routing FIRST
        config.MapHttpAttributeRoutes();

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

If you skip this step, your custom routes won’t be recognized, and Web API will try to match your request to the global route (which won’t find your method, leading to 405 or 404 errors).

5. Check Controller Route Prefix (If Used) #

If your controller has a [RoutePrefix] attribute, make sure your method’s route is relative to it. For example:

[RoutePrefix("api/CustomerContracts")]
public class CustomerContractsController : ApiController
{
    [System.Web.Http.HttpPost]
    // This route becomes api/CustomerContracts/AddCustomer/...
    [Route("AddCustomer/{Description}/{CustomerRef}/{ContractTypeId}/{startDate}/{EndDate}")]
    public async Task AddCustomer(...)
    {
        // Your code
    }
}

Without the RoutePrefix, your method’s route needs to include the full path: [Route("api/CustomerContracts/AddCustomer/{...}")] to match your Postman URL.

6. Test Date Parameter Formatting #

Web API can be picky about date formats in route parameters. Make sure you’re passing dates in a format it can parse, like yyyy-MM-dd (e.g., 2024-01-01) or yyyy-MM-ddTHH:mm:ss (e.g., 2024-01-01T14:30:00). If the date is malformed, it can break route matching and return a misleading "Post Not Allowed" error.

7. Simplify to Debug #

If none of the above works, create a stripped-down test endpoint to isolate the issue:

[System.Web.Http.HttpPost]
[Route("api/CustomerContracts/TestPost")]
public IHttpActionResult TestPost()
{
    return Ok("POST request succeeded!");
}

Call this URL in Postman with a POST request. If it works, the problem is specific to your AddCustomer method’s route or parameters. If it still fails, you have a broader issue with your Web API configuration (like missing WebApiConfig registration in Global.asax.cs).

内容的提问来源于stack exchange，提问作者David B