How to Fix No 'Access-Control-Allow-Origin' header is present on the requested resource

Question

I know the question has been asked many time but i still didn't find the solution.
Am having a cross domain error when i tried to communicate with my API from the client. I don't know if there's something am missing here.

XMLHttpRequest cannot load http://localhost:28184/Customer/AddCustomer.

No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin http://localhost:28189 is therefore not allowed access. The response had HTTP status code 404.

Ajax call:

 function AddCompany()
 {
   var companyModel = {
      ----------
 }

$.support.cors = true;
$.ajax({    
    url: BaseUrl + "Customer/AddCustomer",
    type: "POST",
    withCredentials: false,    
    dataType: "Jason",
    cach: false,
    async: true,
    crossDomain: true,
    data: companyModel,
    success: function(data){
       alert("Company has been successfully registered");
    }       
 });
}

API controller:

using System.Threading.Tasks;
using System.Web.Http;
using System.Web.Http.Cors;
using Fleet_API.Models;

namespace Fleet_API.Controllers
{
[EnableCors(origins: "*", headers: "*", methods: "*")]
[RoutePrefix("Api/Customer")]
public class CustomerController : ApiController
{
    [Route("AddCustomer")]
    [HttpPost]
    public async Task<bool>AddCompany(CustomerModel model)
    {
         ------------------------
    }
}
}

Hosts file from windows

   # localhost name resolution is handled within DNS itself.
   #    127.0.0.1       localhost
   #    ::1             localhost

@JaromandaX i don't understand what you please. can you please rephrase your solution — mavhungu khodani, Sep 16 '16 at 08:29
check what headers are coming for the request - I can't make it any simpler for a web developer — Jaromanda X, Sep 16 '16 at 08:29
`No it is not the same` - good, because if it were, then CORS wouldn't be required - check your developer tools network tab, see what repsonse headers come in for the `Customer/AddCustomer` request - verify you are actually getting the CORS headers as required — Jaromanda X, Sep 16 '16 at 08:31
Can you please give me a direction on were to find it. I guess you refering to Ctrl + Fn + F12 which is console. — mavhungu khodani, Sep 16 '16 at 08:35
Refer to [this](http://www.asp.net/web-api/overview/security/enabling-cross-origin-requests-in-web-api#allowed-origins) — Mihir, Sep 16 '16 at 08:35
Developer Tools are tools for web developers to help them develop for the interweb - hope that helps — Jaromanda X, Sep 16 '16 at 08:37
I will go through the document and hopefully i will get the solution as i have been stuck for two days now — mavhungu khodani, Sep 16 '16 at 08:38
@Mihir After reading the document you sent. I can simply confirm that i have done everything. the same way as the tutorial. Please help — mavhungu khodani, Sep 16 '16 at 08:53
@JaromandaX can you please give me another suggestion i have tried but still it doesn't hit the API — mavhungu khodani, Sep 16 '16 at 08:54
`dataType: "Jason"` is that a typo just here, or is that your actual code? should be `json` — Jaromanda X, Sep 16 '16 at 09:00
For now i can say no because it is not heating the API. how do i give it instructions? — mavhungu khodani, Sep 16 '16 at 09:01
Let me change the spelling and see if it will make the difference — mavhungu khodani, Sep 16 '16 at 09:01
@JaromandaX i have changed Jason to jason and still i doesn't work. Please help am really behind because of this error. maybe other possible solution — mavhungu khodani, Sep 16 '16 at 09:09
`For now i can say no because it is not heating the API` - then what is giving you the CORS error??? — Jaromanda X, Sep 16 '16 at 09:12
for fun try `method: "POST"` instead of `type: "POST"` and `cache: false,` instead of `cach: false` (notice the e in cache) and comment out/remove the `crossDomain: true,` altogether — Jaromanda X, Sep 16 '16 at 09:14
getting this error : XMLHttpRequest cannot load http://localhost:28184/Customer/AddCustomer. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:28189' is therefore not allowed access. The response had HTTP status code 404. — mavhungu khodani, Sep 16 '16 at 09:16
I don't know .NET that well ... but ... `RoutePrefix("Api/Customer")` ... `[Route("AddCustomer")]` ... you call using `/Customer/AddCustomer` with no hint of `Api` in the path - again, I don't know the .NET very well, but it looks awfully suspicious — Jaromanda X, Sep 16 '16 at 09:28
Just read up on it, and, I think you'll need to call that using `/Api/Customer/AddCustomer` rather than just `/Customer/ApiCustomer` — Jaromanda X, Sep 16 '16 at 09:32
I have other pages working fine without any problem. this is my first time being stuck in like this. — mavhungu khodani, Sep 16 '16 at 09:34
are u using chrome ? see this http://stackoverflow.com/questions/28547288/no-access-control-allow-origin-header-is-present-on-the-requested-resource-err — FakeisMe, Sep 16 '16 at 10:30
@FakeisMe I disagree with you because i have application i have developed previously and i have use json as a datatype not p. — mavhungu khodani, Sep 17 '16 at 12:29

How to Fix No 'Access-Control-Allow-Origin' header is present on the requested resource

0 Answers0