This is a migrated thread and some comments may be shown as answers.

System.Web.HttpException: Response is not available in this context

8 Answers 1194 Views

Ajax

This is a migrated thread and some comments may be shown as answers.

CSurieux asked on 02 Sep 2009, 04:37 PM

Hello,

I get this after an exception in an ajax callback (using RadAjaxManager) when I try to redirect to an error page using
Ajax redirect.
My code

    
                        if ( IsInAsyncPostBack && ( AjaxManager != null ) )  
        
                        {  
        
                            if ( url.StartsWith("~/") )  
        
                                url     =   ResolveClientUrl(url);  
        
                            AjaxManager.Redirect(url);  
        
                        }  
        
                        else  
        
                            Response.Redirect(url,endResponse);

May be ajaxmanager should not get Page.Response but HttpContext.Current.Response ?

May be the idea of redirecting using ajax during a call back is bad ?
In this case how to incorporate ajax in my general errors manager which redirects to a standard error page.

Thanks for help
CS

8 Answers, 1 is accepted

answered on 08 Sep 2009, 10:41 AM

Hello Mira,

In my error scenario, all exceptions are trapped as soon as possible and transformed in a generic app exeption depending on context, then these exceptions are catched by the general app error handler in Global.asax, here after some analysis the response is redirected to different error pages.

When the error occurs in a postback, no pb everything works.
When error occurs during an ajax callback, I was expecting to be able to redirect from clientside using ajaxmanager redirect, but it appears that code in ajaxmanager uses the Page property to access Response.
This doesn't work because Page.Response is no more accessible (I get an exception and see from the exception stack it occurs in ajaxmanager trying to access Page.Response), it should use HttpContext.Response because it seems to be available even when Page.response is no more accessible.

Regards
CS