Skip to main content

DELETE or PUT not working with ASP.Net WebAPI

This is one of common issue one may face while working with Web API, there can be certain reasons due to which DELETE or PUT method not working with Web API. Here I’ll try to include three possible issues and there fixes:

Possible issues and solution:

Issue 1:
Error: HTTP Error 405.0 - Method Not Allowed The page you are looking for cannot be displayed because an invalid method (HTTP Verb) is being used

You are facing this issue because your application is not able to handles all types of HTTP requests. In order to execute HTTP requests for DELETE, PUT, etc., we need to add the below mentioned line in web.config file under <system.webServer>

<modules runallmanagedmodulesforallrequests="true">

Issue 2:
Error: Getting 404 for PUT and DELETE request:  Issue may be due to because Web API provides default GET, POST, PUT and DELETE methods but IIS restricts it. To fix the issue you need to manage the handler mappings in IIS and then need to add PUT and DELETE on the “Verbs” tab. check this post for solution of this issue

Issue 3:
Issue with “content-type: text/plain” (posted string parameter value is NULL): If you are posting data with “content-type: text/plain” to a Web API method that takes a string, you notice that the value in the string is null, this is because of your application not having support for the media type “text/plain”. You can fix the issue by creating custom MediaTypeFormatter in your application and then register your custom MediaTypeFormatter on Application_Start method in your Global.asax.cs file. Brian explained this solution here.

I hope that’ll solve your problem J
Labels:

Comments

Post a Comment

Popular posts from this blog

C#: Merging Excel cells with NPOI HSSFWorkbook

In this post we’ll see how to merge the two or more cell with each other while creating the excel sheet using NPOI . Mentioned below is code to merge multiple cells, in this example we are merging first cell to fifth cell of first row (you can adjust row or cell range by passing particular parameters in CellRangeAddress). //Created new Workbook var hwb = new NPOI.HSSF.UserModel. HSSFWorkbook (); //Create worksheet with name. var sheet = hwb.CreateSheet( "new sheet" ); //Create row and cell. var row = sheet.CreateRow(0); var cell = row.CreateCell(0); ; //Set text inside cell cell.SetCellValue( "This is Merged cell" ); cell.CellStyle.WrapText = true ; //define cell range address // parameters: -> first row to last and first cell to last cell var cra = new NPOI.SS.Util. CellRangeAddress (0, 0, 0, 4); //Add merged region to sheet. sheet.AddMergedRegion(cra); Hope this solution helps you J
4 comments
Read more

Error 405 : ASP.NET Core Web API PUT and DELETE Methods not allowed

Recently, while working with .Net core API I came across the issue of “Error 405 — Methods not Allowed” After some research, I found out that both GET and POST requests working fine but neither PUT nor DELETE requests working. Another thing is that the PUT and DELETE request was also working fine on my local machine but failed when we host on our Azure server. When I explored the issue on the web it led me to the conclusion that WebDAVModule seems to set PUT and DELETE request methods disabled by default and due to that PUT and DELETE throw 405 errors. To make the PUT and DELETE requests work, we need to override the WebDAVModule setting in web.config file by adding the below settings under “ system.webServer ”. < system.webServer >   < modules runAllManagedModulesForAllRequests = " false " >     < remove name = " WebDAVModule " />   </ modules > </ system.webServer > There may be 2 web.config files in y...
Post a Comment
Read more

How to set Swagger as the default start page for API hosted on the Azure web app?

I created an Asp.Net Core 2.x Web API and configured Swagger on it, below is the code added in Configure method under Startup.cs file, for full swagger configuration, check here //Add swagger configuration app.UseSwagger(); app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" ); }); On my local machine when I run the API it is automatically redirected to the Swagger page. However, when I hosted this API as an Azure web app it is not redirecting directly to the Swagger and to access the swagger, I had to append /swagger in the URL, for example, https://testapi.azurewebsites.net/swagger/ Solution: Set RoutePrefix to string.Empty under app.UseSwaggerUI like below: app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" );      c.RoutePrefix = string .Empty; // Set Swagger UI at apps root }); And that’s it, now when you b...
Post a Comment
Read more