We currently have a few pages that use RadAjaxManagers on them in a project that uses the ASP.NET membership authentication system.
This system has been working fine, however when a user is logged in and either is disabled (user.IsApproved = False / put into Disabled User role) or is removed from the role needed to access the page they are on, the membership then redirects them to an error page. When this happens the user triggers an Ajax request the following error pops up.
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.21022; .NET CLR 3.5.30729; MDDR; .NET CLR 3.0.30729; .NET CLR 1.1.4322)
Timestamp: Fri, 4 Dec 2009 19:17:48 UTC
Message: Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled.
Details: Error parsing near '
<!DOCTYPE html P'.
Line: 6
Char: 62099
Code: 0
How can we get the authentication and role system built into ASP.Net 2.0 to play nicely with the RadAjaxManager and properly handle the situations described above? The system currently works fine as long as teh RadAjaxManager is not involved.
We do have the following in the web.config, btu still get the error:
<location path="WebResource.axd"> |
<system.web> |
<authorization> |
<allow users="*"/> |
</authorization> |
</system.web> |
</location> |
<location path="Telerik.Web.UI.WebResource.axd"> |
<system.web> |
<authorization> |
<allow users="*"/> |
</authorization> |
</system.web> |
</location> |
<location path="ScriptResource.axd"> |
<system.web> |
<authorization> |
<allow users="*"/> |
</authorization> |
</system.web> |
</location> |