Web API routing constraint Patch missing in HttpMethod

14,787

EDIT: Update to the latest version of WebAPI currently 5.2.7 (https://www.nuget.org/packages/Microsoft.AspNet.WebApi/)

ORIGINAL:

If you cannot use instead:

new HttpMethod("PATCH")

See the following example use in Web API source code

https://github.com/aspnetwebstack/aspnetwebstack/blob/master/src/System.Web.Http/HttpPatchAttribute.cs

Share:
14,787

Related videos on Youtube

Stay Foolish
Author by

Stay Foolish

Updated on June 14, 2022

Comments

  • Stay Foolish
    Stay Foolish almost 2 years

    I am building some restful api using .net Web API V1.

    We are trying to define some routing for the web api. I am having some issue in defining the route for 'Put' and 'patch'.

    They have the same URL and the only different is in the HttpMethod. In the HttpMethod, there is no support for Patch http://msdn.microsoft.com/en-us/library/system.net.http.httpmethod(v=vs.118).aspx

    config.Routes.MapHttpRoute(
        "UpdateCustomer",
        "api/customers/id/{id}",
        new {controller = "Customers", action = "UpdateCustomer"},
        new {id = @"\d+", httpMethod = new HttpMethodConstraint(HttpMethod.Put)}
    );
    
    config.Routes.MapHttpRoute(
        "PatchCustomer",
        "api/customers/id/{id}",
         new {controller = "Customers", action = "PatchCustomer"},
         new {id = @"\d+", httpMethod = new HttpMethodConstraint(HttpMethod.**Patch**)}
    );
    
  • Yishai Galatzer
    Yishai Galatzer about 7 years
    You should really move to at least Web API 2.23 at this point (if you can)
  • joynoele
    joynoele over 5 years
    Link broken. PATCH has been added as a property in .NET Core starting at 2.1 but still does not appear to be available as a property in Standard nor Framework. [docs.microsoft.com/en-us/dotnet/api/…
  • Yishai Galatzer
    Yishai Galatzer over 5 years
    Elsa - Why are you still using WebAPI 1.0? This is now ancient software :). Updated the broken link
  • joynoele
    joynoele over 5 years
    Thank you for updating the link to latest version. WebAPi 1.0 documentation & questions are still relevant for working on legacy system - as you say above "if you can".