[CLOSED] Globally Stop Execution of Direct Methods when Session is Expired

[logicspeak]

I know we need to use the Ext.net.X.Redirect when session is expired during a ajax request, but even after we call this method the execution of the direct method still occurs. This can cause an error when we are accessing Session during the direct method call. I am wondering if we can globally stop the execution of the ajax request to prevent this from happening. We could check for the Session variable being null in the direct method, but we would rather not have to go back and add this check to hundreds of existing direct methods.

Thanks!

[Daniil]

Hi,

Vladimir suggests to try with Global.asax by the following way:

Example

protected void Application_PostAcquireRequestState(object sender, EventArgs e)
{
    HttpApplication app = (HttpApplication)sender;
    HttpRequest request = app.Context.Request;

    if (X.IsAjaxRequest && app.Session.IsNewSession)
    {
        app.Context.Response.Clear();
        app.Context.Response.ClearContent();
        app.Context.Response.ClearHeaders();
        app.Context.Response.StatusCode = 200;
        app.Context.Response.ContentType = "application/json";
        app.Context.Response.Charset = "utf-8";
        app.Context.Response.Cache.SetNoServerCaching();
        app.Context.Response.Cache.SetMaxAge(TimeSpan.Zero);

        app.Context.Response.Write(string.Format("{{script:\"window.location='login.aspx';\"}}"));
        app.CompleteRequest();
    }
}

[logicspeak]

Thanks guys. This works well in most situations. However, it does appear that sometimes when clicking on a TabPanel that loads another page in an iframe, the page in the iframe continues to execute. So an exception is thrown. The exception does not prevent the redirect though, so not a huge issue. I guess it could cause confusion for exception logging purposes.

I thought I'd mention it to see if you guys have any ideas?

Thanks!

[logicspeak]

Correction:
The issue comes from clicking on a Panel in a TabPanel collection.

Here are some properties we set when creating the panel:

int userFormId = 1;
Ext.Net.Panel tab = new Ext.Net.Panel();
tab.Closable = true;
tab.Border = false;
tab.Title = "My Panel";
tab.TabTip = "This is my panel";
tab.AutoLoad.Url = "PathToWebContentPage.aspx";
tab.AutoLoad.Mode = Ext.Net.LoadMode.IFrame;
tab.AutoLoad.MaskMsg = "Loading...";
tab.AutoLoad.ShowMask = true;
tab.ID = string.Format("tab_{0}", userFormId);
tab.Listeners.Close.Handler = string.Format("Ext.net.DirectMethods.CloseForm('{0}')", userFormId);
tab.Listeners.Activate.Handler = string.Format("Ext.net.DirectMethods.ActivateTab('{0}')", userFormId);
tab.Icon = Ext.Net.Icon.Page;
tab.CustomConfig.Add(new ConfigItem("userFormId", userFormId.ToString()));
 
//The TabPanel
TabPanel1.Items.Add(tab);

The exception occurs during the page load of the page in the iframe and not during the Activate handler call. So it appears that the direct method execution was stopped as we wanted, but the iframe autoloading is not stopped.

Thanks!

[Daniil]

Well, there is no direct relation between iframe and AJAX.

You should be able to pass a respective parameter within an url and analyze it in Global.asax.

You should return 302 status code in a case with an iframe.

As well Response.Redirect might work (not 100% sure). Though redirection will occur within an iframe.

Probably, you will need to redirect a parent page. Then you should return a page, i.e. a correct HTML page with:

parent.window.location = "url";

script.

Don't forget to set up "text/html" ContentType.