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

Potentially Dangerous Request in ASP.NET 4

5 Answers 280 Views

Spell

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

Matthias Otto asked on 20 Mar 2010, 08:36 PM

screenshot.png

Hi,

I am getting a popup with "Error 500: Potentially Dangerous Request" when trying to use RadSpell on multiple controls in ASP.NET 4. The error occurs the moment I click "Check Spell".

Reproduction: Create a fresh ASP.NET 4 project (VB) and add the HTTPRequestHandler for RadScriptManager and RadSpell to the web.config through Telerik's SmartTags. Then add the RadScriptManager and RadSpell to your Default.aspx, create two basic text inputs and try hook up both (i.e. ControlsToCheck="TextBox1,TextBox2")

Web.config (excerpt)

Default.aspx

<%@ Page Title="Home Page" Language="vb" MasterPageFile="~/Site.Master" AutoEventWireup="false"

    CodeBehind="Default.aspx.vb" Inherits="RadSpellTest._Default" %>

<%@ Register Assembly="Telerik.Web.UI" Namespace="Telerik.Web.UI" TagPrefix="telerik" %>

<asp:Content ID="HeaderContent" runat="server" ContentPlaceHolderID="HeadContent">

</asp:Content>

<asp:Content ID="BodyContent" runat="server" ContentPlaceHolderID="MainContent">

    <h2>

        Welcome to ASP.NET!

    </h2>



     <telerik:RadScriptManager ID="RadScriptManager1" runat="server" />

     <input type="text" id="TextBox1" />

     <input type="text" ID="TextBox2" />

     <telerik:RadSpell ID="RadSpell1" Runat="server" ControlsToCheck="TextBox1,TextBox2" IsClientID="True" SupportedLanguages="en-US,English" />

</asp:Content>

Attached you can find a screenshot of the error message.

Note: It does work when TargetFramework of the project is set to 3.5 instead of 4.0 or if RadSpell is given only one ControlToCheck.

Thanks for any help,

Matt

5 Answers, 1 is accepted

answered on 20 Mar 2010, 08:52 PM

Apparently, ASP.NET 4 validates every request that is received. Older versions of ASP.NET only validated requests to ASPX pages.

Telerik-Team, please update your handlers to make them pass ASP.NET 4 request validation.

Workaround: In the meantime, you will have to disable the new request validation by setting <httpRuntime requestValidationMode="2.0" /> in <system.web> in you web.config.

                    <configuration>         
                     
              <system.web>         
                     
                <httpRuntime requestValidationMode="2.0" />         
                ...         
              </system.web>         
              ...         
            </configuration>         
                         

Source: StackOverflow