CODEWITHSUNDEEP
asp.net-mvcjquerydeploymentiis-7.5
user2067567
user2067567

Reputation: 3803

AJAX Call returning 404(Local) in IIS 7.5 but same works in other IIS

Am having the AJAX calls to my controller in my MVC Application

Controller/FunctionName



$.ajax({
        type: "GET",
        contentType: "application/json; charset=utf-8",
        url: '/Controller/FunctionName',
        .
        .
        .
        )};

Am using MVC 4 and making use of JQUERY Ajax function as shown in the above code. It works totally fine when i run from Visual studio.

I depolyed this to the server machine and as expected it works fine. No issues found in AJAX calls.

Now am trying to deploy this in my local machine IIS which is same as my server version (IIS 7.5) but am getting 404 for all the ajax calls in firebug.

I verified the build and even i pointed to my web folder and am still looking for what went wrong !!

It works in other IIS so It wont be a URL resolving issue is my gues. Am i missing any settings or Any timely idea to fix this would be great.

Thanks

Upvotes: 20

Views: 17287

Answers (4)

Thanh
Thanh

Reputation: 41

Just a complement of Darin's answer that if "the AJAX call is in a separate javascript file where you cannot use server side helpers", use a hidden field to store the url endpoint in the view:

@* file.cshtml *@
@* Method name and Controller, used in scripts/myfile.js *@
@Html.Hidden("URLEndpointName", Url.Action("FunctionName", "Controller"))

which is rendered into HTML as:

<input id="URLEndpointName" name="URLEndpointName" type="hidden" value="/YourApp/Controller/FunctionName">

and read that hidden field in your js:

// myfile.js
$.ajax({
    url: $("#URLEndpointName").val(),
    // Additional code
});

Upvotes: 4

Ejrr1085
Ejrr1085

Reputation: 1071

You can use double dot in the url:

$.ajax({
   url: '../ControllerName/ActionName',
   .......
});

Upvotes: 1

Howard
Howard

Reputation: 1

What I'd found on my setup of IIS7.5 is that the 'Handler Mapping' has a resource named 'OPTIONSVerbHandler' is not set in the right order hence return back as Unknown.

This work for me where my localhost ajax was calling my network server, which has a different name, that it shouldn't give me a CORS issue, but it did and this was my solution.

Open IIS and click on your server name on the left pane. On the right pane double-click 'Handler Mappings' in the middle pane. On the right pane, select 'View Ordered List'. From there find 'OPTIONSVerbHandler' and 'svc-ISAPI-4.0_32bit', move 'OPTIONSVerbHandler' up until it is above 'svc-ISAPI-4.0_32bit'.

Make sure your 'handler' inside your ajax call does not have 'Access-Control-Allow-Origin' in it.

Upvotes: 0

Darin Dimitrov
Darin Dimitrov

Reputation: 1038720

That's normal. You have hardcoded the url to your controller action:

url: '/Controller/FunctionName',

If you deploy your application in a virtual directory in IIS the correct url should be:

url: '/YourAppName/Controller/FunctionName',

That's the reason why you should absolutely never hardcode urls in an ASP.NET MVC application but ALWAYS use url helpers to generate it:

url: '@Url.Action("FunctionName", "Controller")',

and if this AJAX call is in a separate javascript file where you cannot use server side helpers, then you could read this url from some DOM element that you are AJAXifying.

For example let's suppose that you had an anchor:

@Html.ActionLink("click me", "FunctionName", "Controller", null, new { id = "myLink" })

that you AJAXify:

$('#myLink').click(function() {
    $.ajax({
        url: this.href,
        contentType: 'application/json; charset=utf-8',
        type: 'GET',
        .
        .
        .
    )};    
    return false;
});

Notice how we are reading the url from the DOM element which was generated by a helper.

Conclusion and 2 rules of thumb:

  • NEVER EVER hardcode an url in an ASP.NET MVC application
  • ABSOLUTELY ALWAYS use url helpers when dealing with urls in an ASP.NET MVC application

Upvotes: 39

Related Questions