There are many approaches here, but we have discovered one that works regardless of which AJAX mechanism you are building upon (MS AJAX, jQuery, XMLHttpRequest, etc.).

The approach we took is to add a tag block to the Login.aspx page. This marker will be used to tell us when we’ve been redirected to the Login.aspx page from an AJAX request sent to IIS. Here is a sample snippet that you could use.

After you’ve added this token to your login page, you can begin checking for the existence of this tag when you receive AJAX responses back from the application server. Here is how we implemented it.

// tell MS AJAX request manager that we have to check for valid login session (Ajax.ActionLink)
Sys.Net.WebRequestManager.add_completedRequest(function (result) {
    IsValidSession(result.get_responseData()); // capture returned ajax response data
});

// attach all ajax completion requests for session review
$('*').ajaxComplete(function (e, xhr, settings) {
    IsValidSession(xhr.responseText);
});

/// Checks for invalid session [JQUERY/MSAJAX]
function IsValidSession(response_data) {
    if (response_data.match(/id="ajaxexpiry"/gi) != null)  // pattern to locate
        window.location.href = "/"; ; // redirect matching to login page
}

The code above is made up of three separate blocks. The first block handles MS AJAX integration. We leverage the WebRequestManager’s completed request handler in the MicrosoftAjax.js library. In the next section we integrate the jQuery AJAX framework by using the ajaxComplete() method handler.

Once we’ve collected the response data from the AJAX requests (MS AJAX or jQuery), we can process the text by matching on the tag pattern (id=”ajaxexpiry”) we created earlier. This is done in the IsValidSession routine called by each AJAX interface above. If we discover a match on our token, we will redirect the user to the login page. In our example, the login page is at the root of the domain, but in your instance, you may need to customize accordingly.

Another possible solution to this issue is to use a periodic polling routine to request content from the server. However, this approach puts additional load on your application server unnecessarily. We chose to do the session checking locally, and check for session expire only when necessary on the client (thus no impact to server resources).

In my case, the FileUpload only works when it is visible when the page is first time loaded (not a postback).  It will not work (Request.Files.Count returns 0) when it is hidden originally and then made visible during later AsyncPostBacks.  Maybe ASP.NET is confused, because I am also changing the submit button’s postback type between full postback and aysnc postback.  The submit button is used by other things, and I only want it to fire a full post back when files need to be uploaded, and in all other cases, I want it to fire async postback and only do partial update on my page.

I spent many hours trying many different solutions I saw on the internet, but none of them worked for me.  However, I found an important hint which led me to the final working solution.  That is the Enctype attribute of the Form.  I learned that the Form.Enctype has to be “multipart/form-data” when files need to be uploaded.  I think this is set automatically for you in normal cases, but it isn’t set up correctly in my case.  So, I manually set it to “multipart/form-data” in OnInit of my user control, and it solves the problem.

First, you need to download the jGrowl extension from here. After including the JavaScript reference to your source, you can begin creating messages by adding the following JavaScript to your page.

$.jGrowl("Customer order successfully submitted!");

jGrowl notifications can be sticky (i.e. you must close them) and they can also accumulate if you want to post several notifications at once. Here’s a quick glimpse of how these notifications can appear with some enhanced styling applied.

jGrowl Sample Notification