Handling of server-side HTTP 4nn/5nn errors returning a whole HTML document in jQuery's ajax requests
To the point: how would you handle a server-side HTTP 4nn/5nn errors in jQuery's ajax requests? This case concerns a JSP/Servlet webapplication at the server side. Here I am not talking about trivial runtime exceptions such as NullPointerException and so on. Assume that they're all handled perfectly. A good example of such a HTTP 4nn/5nn error is 401 unauthorized (insufficient user rights) and 500 internal server error (database down, I/O error, Errors, etc). Assume that they cannot (or should not) be caught at coding level.
Right now I have just declared an <error-page> in web.xml for those kind of errors. It basically forwards the request to a predefinied JSP/HTML error page wherein the end开发者_如何学Gouser is informed that a serious error has occurred and that the user can contact xx@xx.xx for further assistance. The same page also displays the global details about the error/exception.
It works perfectly in regular HTTP requests, but how would you handle it in XMLHtttp requests using jQuery? What's the best for the user experience? To me, it would be just displaying the entire error page as if it is a normal HTTP request. I've solved it as follows:
function init() {
$.ajaxSetup({
error: handleXhrError
});
}
function handleXhrError(xhr) {
document.open();
document.write(xhr.responseText);
document.close();
}
Although it works perfectly, it feels to me like a hack. Replacing the entire document with the contents of the HTTP error page. But is that also the way you would follow? If not, can you maybe elaborate why not and what way you'd prefer? The only alternative I see is using JS to display some alert/message box to inform the user about the unresolveable error, but the user could dismiss it and continue with the page while that should not be possible.
After all, dealing with errors on asynchronous requests the same way as with synchronous requests is the best for user experience. Only, the
function handleXhrError(xhr) {
document.open();
document.write(xhr.responseText);
document.close();
}
will fail in IE6/7/8 when you've <script> elements which needs to be loaded and initialized as well. IE6/7/8 namely won't do that. In order to get IE to do that, you basically need to keep the current <head> element and only replace its children by $("head").html(newHead). The same should be done for the <body> element.
function handleXhrError(xhr) {
var newDocument = xhr.responseText;
$("head").html(newDocument.substring(newDocument.indexOf("<head>") + 6, newDocument.indexOf("</head>")));
$("body").html(newDocument.substring(newDocument.indexOf("<body>") + 6, newDocument.indexOf("</body>")));
}
Nasty, but it's not possible to do a $(xhr.responseText) when the response text represents a whole HTML document with a head and body. Don't forget to alter the substring index accordingly when you've some attributes on <body> of the error page template (e.g. ID, class, etc).
Use a JQuery dialog, something like this:
function handleXhrError(xhr) {
ele = $("<div></div>").appendTo("body");
ele.html(xhr.responseText);
$(ele).dialog();
}
I should answer the rest of what you asked. I throw and catch specific exceptions where I can, and send special messages to the client. Sometimes I instruct the client to run a function which may redirect the browser or partially refresh part of the page. It just depends on the circumstances. Catching 400/500 will deal with real errors, but you want to also write JS code once to filter all your AJAX requests for custom error flags that you will return from the server, take a look at this page for more: http://www.bennadel.com/blog/1392-Handling-AJAX-Errors-With-jQuery.htm
If necessary, you should also be able to re-direct to one of the pre-defined error pages you set-up with window.location.href = "url-to-error-page";
I think it's better to give a short message instead completely rewriting your page. That way it won't interfere much with the page itself. Google Reader and Gmail do something like this. Reader shows the message and doesn't mark your items read, but you can still read all the loaded posts.
You seem to want to retain a working page/application after you receive an error condition that would result in an unusable state.
I would implement a state history on the client side and revert the page to the last usable state, informing the user via a prominent in-page element what has happened.
The theory behind this is related to transactions. Typically the execution flow is:
- Instruct transaction manager to start a transaction
- Begin transaction
- Capture state
- Return control to calling code
- Begin operations that are part of transaction
- On error: instruct transaction manager to roll back transaction
- Return execution environment to state captured above
- Discard any data no longer needed (e.g. state serialization)
- On success: instruct transaction manager to commmit transaction
- Finalize operations in transaction as needed
- Discard any data no longer needed
I have not done serious study into transaction management in javascript. Since you state that the server-side error makes the client side unusable, perhaps there is some way to implement portions of the transaction on the server-side. It is important that you not leave things half done there more so than on the client-side.
Have you thought about doing a "pre flight check" request to try to capture these issues before the client-side application attempts to do the real work?
加载中,请稍侯......
精彩评论