DELETE method

BarryStevens

Attempt to do a DELETE method in postman results in this error.
Can you shed any light on what the issue might be?

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.

Most likely causes:

• The request sent to the Web server used an HTTP verb that is not allowed by the module configured to handle the request.
• A request was sent to the server that contained an invalid HTTP verb.
• The request is for static content and contains an HTTP verb other than GET or HEAD.
• A request was sent to a virtual directory using the HTTP verb POST and the default document is a static file that does not support HTTP verbs other than GET or HEAD.

Things you can try:

• Verify the list of verbs enabled for the module handler this request was sent to, and ensure that this verb should be allowed for the Web site.
• Check the IIS log file to see which verb is not allowed for the request.
• Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click
  here.
  

DonBakke

I hate to ask the obvious, but does your API support the DELETE method? Did you build a hook for this?

BarryStevens

Yes.
I put in a debug=1 and it never got executed so it must be getting stopped before it gets there.
Tested OK on my dev PC and I checked that there is the same version

DonBakke

So this is an API that does work in development but is having problems in production? Is it your opinion that HTTP_MCP is never called as well? If the above are true, this would seem to be a problem with IIS. I honestly don't much about IIS so I can't help you here but others might have experience. I did a quick Google search for this issue and these pages seemed to be related:

https://stackoverflow.com/questions/10906411/asp-net-web-api-put-delete-verbs-not-allowed-iis-8

https://forums.iis.net/t/1154637.aspx?HTTP+Error+405+0+Method+Not+Allowed

BarryStevens

If I stop the oengineserver I get the exact same error, so I was right, it is not getting to the MCP yet.

BarryStevens

Mmm, looks way over my head.

AusMarkB

Barry,
I suspect Don is right and that IIS is the culprit.
I'm no IIS expert either but you could check this config on the production server

BarryStevens

Yep, actually worked that one out and checked it and was already set to 'All Verbs'

Thanks Mark for the effort.

BarryStevens

Another view of the error showed:
Detailed Error Information:
Module WebDAVModule
Notification MapRequestHandler
Handler OECGI3
Error Code 0x00000000
Requested URL http://192.168.0.7:80/cgi-bin/oecgi3.exe/funeralvaluables/16285P
Physical Path C:\inetpub\cgi-bin\oecgi3.exe\funeralvaluables\16285P
Logon Method Anonymous
Logon User Anonymous

Googling found a reference to WebDAVModule being a source of many problems.

I was able to work out where I can remove it and I did and it now works.

(I dont have that on my Dev PC IIS)