How can I pass custom error information from an ASP.NET MVC3 JsonResult
method to the error
(or success
or complete
, if need be) function of jQuery.ajax()
? Ideally I'd like to be able to:
Here is a basic version of my code:
public JsonResult DoStuff(string argString) { string errorInfo = ""; try { DoOtherStuff(argString); } catch(Exception e) { errorInfo = "Failed to call DoOtherStuff()"; //Edit HTTP Response here to include 'errorInfo' ? throw e; } return Json(true); }
$.ajax({ type: "POST", url: "../MyController/DoStuff", data: {argString: "arg string"}, dataType: "json", traditional: true, success: function(data, statusCode, xhr){ if (data === true) //Success handling else //Error handling here? But error still needs to be thrown on server... }, error: function(xhr, errorType, exception) { //Here 'exception' is 'Internal Server Error' //Haven't had luck editing the Response on the server to pass something here } });
Things I've tried (that didn't work out):
catch
block catch
block xhr
in the jQuery error handlerxhr.getResponseHeader()
, etc. contained the default ASP.NET error page, but none of my informationThe best way to bubble that error from the server side (using php) to the client side is to send a header through the Ajax request somewhere in the 400's (which is always associated with errors). Once the Ajax request receives this it will trigger your error function.
ajax() function returns the XMLHttpRequest object that it creates. Normally jQuery handles the creation of this object internally, but a custom function for manufacturing one can be specified using the xhr option.
Approach: To solve this problem, we will first consider a JSON file named “capitals. json” and try to get this JSON data as a response using AJAX. Then we will create an HTML file “capitals. html” which contains a table which we will use to populate the data we are getting in response.
You could write a custom error filter:
public class JsonExceptionFilterAttribute : FilterAttribute, IExceptionFilter { public void OnException(ExceptionContext filterContext) { if (filterContext.RequestContext.HttpContext.Request.IsAjaxRequest()) { filterContext.HttpContext.Response.StatusCode = 500; filterContext.ExceptionHandled = true; filterContext.Result = new JsonResult { Data = new { // obviously here you could include whatever information you want about the exception // for example if you have some custom exceptions you could test // the type of the actual exception and extract additional data // For the sake of simplicity let's suppose that we want to // send only the exception message to the client errorMessage = filterContext.Exception.Message }, JsonRequestBehavior = JsonRequestBehavior.AllowGet }; } } }
and then register it either as a global filter or only apply to particular controllers/actions that you intend to invoke with AJAX.
And on the client:
$.ajax({ type: "POST", url: "@Url.Action("DoStuff", "My")", data: { argString: "arg string" }, dataType: "json", traditional: true, success: function(data) { //Success handling }, error: function(xhr) { try { // a try/catch is recommended as the error handler // could occur in many events and there might not be // a JSON response from the server var json = $.parseJSON(xhr.responseText); alert(json.errorMessage); } catch(e) { alert('something bad happened'); } } });
Obviously you could be quickly bored to write repetitive error handling code for each AJAX request so it would be better to write it once for all AJAX requests on your page:
$(document).ajaxError(function (evt, xhr) { try { var json = $.parseJSON(xhr.responseText); alert(json.errorMessage); } catch (e) { alert('something bad happened'); } });
and then:
$.ajax({ type: "POST", url: "@Url.Action("DoStuff", "My")", data: { argString: "arg string" }, dataType: "json", traditional: true, success: function(data) { //Success handling } });
Another possibility is to adapt a global exception handler I presented so that inside the ErrorController you check if it was an AJAX request and simply return the exception details as JSON.
The advice above wouldn't work on IIS for remote clients. They will receive a standard error page like 500.htm instead of a response with a message. You have to use customError mode in web.config, or add
<system.webServer> <httpErrors existingResponse="PassThrough" /> </system.webServer>
or
"You can also go into IIS manager --> Error Pages then click on the right on "Edit feature settings..." And set the option to "Detailed errors" then it will be your application that process the error and not IIS."
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With