The error message:
Sys.WebForms.PageRequestManagerParserErrorExeption: 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''.
We have experienced this error with only the latest Ajax control. I have read the following blog post (http://blogs.telerik.com/blogs/07-06-24/Firewalls_breaking_ASP_NET_AJAX.aspx) about this issue, but we use SonicWall not Watchguard. Is there anything we can do to the Firewall to stop this?
Sys.WebForms.PageRequestManagerParserErrorExeption: 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''.
We have experienced this error with only the latest Ajax control. I have read the following blog post (http://blogs.telerik.com/blogs/07-06-24/Firewalls_breaking_ASP_NET_AJAX.aspx) about this issue, but we use SonicWall not Watchguard. Is there anything we can do to the Firewall to stop this?
1 Answer, 1 is accepted
0
Hello Mr,
I suppose that SonicWall uses similar mechanism to remove the unknown headers and strips the X-MicrosoftAjax Delta=true value which produces the error. You will need to find a way to prevent this behavior in order to address the issue at hand.
Best regards,
Sebastian
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
I suppose that SonicWall uses similar mechanism to remove the unknown headers and strips the X-MicrosoftAjax Delta=true value which produces the error. You will need to find a way to prevent this behavior in order to address the issue at hand.
Best regards,
Sebastian
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.