CORS is enabled but still get 405

Question

I'm writing a quick and dirty little script to log traffic on a static HTML page. I am making a POST to another server where I have the API hosted. The server has CORS enabled (see code below) but I still get a 405.

    <add name="Access-Control-Allow-Origin" value="*" />
    <add name="Access-Control-Allow-Headers" value="*" />
    <add name="Access-Control-Allow-Methods" value="GET, POST, PUT, PATCH, DELETE, OPTIONS" />

Here's my JavaScript:

  var host = window.location.host;
  var hostname = window.location.hostname;
  var href = window.location.href;
  var port = window.location.port;
  var path = window.location.pathname;
  var referrer = document.referrer;

  var obj = { 
    Host: host,
    HostName: hostname,
    Href: href,
    Port: port,
    Path: path,
    Referrer: referrer
  };

  $.ajax({
    type: 'POST',
    url: 'http://localhost/system/api/sp/logvisit',
    data: obj,
    dataType: 'json',
    contentType: 'application/json'
  });

Here is my controller:

namespace Gs.Api
{
    public class SPController : ApiController
    {
        [Route("api/sp/logvisit")]
        [HttpPost]
        public void LogVisit(LogVisitRequest request)
        {
            // do stuff with request
        }
    }
}

I tried the main answer here Handling CORS Preflight requests to ASP.NET MVC actions which got rid of the 405 but my method never actually got called. I tried several other fixes from various answers here and some got rid of the error but my posted object would be null.

@11thdimension Method works fine using ARC (Advanced REST Client - from Chrome App Store) — Timothy, Jul 28 '17 at 18:13
@11thdimension it got a 500 error but I changed to JSON.stringify(obj) and it worked from my local. If I add [HttpOptions] to the call it gets a 500 error because request is null. — Timothy, Jul 28 '17 at 18:30
@11thdimension I figured it out. Posting answer soon once I type it all up. Thanks for your help! — Timothy, Jul 28 '17 at 18:52

score 1 · Accepted Answer · answered Jul 28 '17 at 19:02

I figured this out on my own. I had to take a few other solutions and use them all together, but I got it finally.

I used this answer: https://stackoverflow.com/a/13646169/3920075
I changed <add name="Access-Control-Allow-Headers" value="*" /> to <add name="Access-Control-Allow-Headers" value="Content-Type" />.
I changed data: obj, to data: JSON.stringify(obj)

CORS is enabled but still get 405

1 Answers1