iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
Hello,
I tried using the html editor and in particular using the font or bold function, I would get this error the following error. Please help!
Server Error in '/WebSite5' Application. A potentially dangerous Request.Form value was detected from the client (txtHtmlEditor="<FONT color=#99ff00>..."). Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. To allow pages to override application request validation settings, set the requestValidationMode attribute in the httpRuntime configuration section to requestValidationMode="2.0". Example: <httpRuntime requestValidationMode="2.0" />. After setting this value, you can then disable request validation by setting validateRequest="false" in the Page directive or in the <pages> configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case. For more information, see http://go.microsoft.com/fwlink/?LinkId=153133. Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.Form value was detected from the client (txtHtmlEditor="<FONT color=#99ff00>...").Source Error: The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:1. Add a "Debug=true" directive at the top of the file that generated the error. Example: <%@ Page Language="C#" Debug="true" %>or:2) Add the following section to the configuration file of your application:<configuration> <system.web> <compilation debug="true"/> </system.web></configuration>Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. Stack Trace: [HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form value was detected from the client (txtHtmlEditor="<FONT color=#99ff00>...").] System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection) +8812804 System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, RequestValidationSource requestCollection) +122 System.Web.HttpRequest.get_Form() +150 System.Web.HttpRequest.get_HasForm() +8985375 System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +97 System.Web.UI.Page.DeterminePostBackMode() +69 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +8431 System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +253 System.Web.UI.Page.ProcessRequest() +78 System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21 System.Web.UI.Page.ProcessRequest(HttpContext context) +49 ASP.logbookentries_aspx.ProcessRequest(HttpContext context) +37 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +100 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.225
Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. To allow pages to override application request validation settings, set the requestValidationMode attribute in the httpRuntime configuration section to requestValidationMode="2.0". Example: <httpRuntime requestValidationMode="2.0" />. After setting this value, you can then disable request validation by setting validateRequest="false" in the Page directive or in the <pages> configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case. For more information, see http://go.microsoft.com/fwlink/?LinkId=153133. Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.Form value was detected from the client (txtHtmlEditor="<FONT color=#99ff00>...").Source Error: The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:1. Add a "Debug=true" directive at the top of the file that generated the error. Example: <%@ Page Language="C#" Debug="true" %>or:2) Add the following section to the configuration file of your application:<configuration> <system.web> <compilation debug="true"/> </system.web></configuration>Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. Stack Trace: [HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form value was detected from the client (txtHtmlEditor="<FONT color=#99ff00>...").] System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection) +8812804 System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, RequestValidationSource requestCollection) +122 System.Web.HttpRequest.get_Form() +150 System.Web.HttpRequest.get_HasForm() +8985375 System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +97 System.Web.UI.Page.DeterminePostBackMode() +69 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +8431 System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +253 System.Web.UI.Page.ProcessRequest() +78 System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21 System.Web.UI.Page.ProcessRequest(HttpContext context) +49 ASP.logbookentries_aspx.ProcessRequest(HttpContext context) +37 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +100 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.225
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:1. Add a "Debug=true" directive at the top of the file that generated the error. Example: <%@ Page Language="C#" Debug="true" %>or:2) Add the following section to the configuration file of your application:<configuration> <system.web> <compilation debug="true"/> </system.web></configuration>Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
[HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form value was detected from the client (txtHtmlEditor="<FONT color=#99ff00>...").] System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection) +8812804 System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, RequestValidationSource requestCollection) +122 System.Web.HttpRequest.get_Form() +150 System.Web.HttpRequest.get_HasForm() +8985375 System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +97 System.Web.UI.Page.DeterminePostBackMode() +69 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +8431 System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +253 System.Web.UI.Page.ProcessRequest() +78 System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21 System.Web.UI.Page.ProcessRequest(HttpContext context) +49 ASP.logbookentries_aspx.ProcessRequest(HttpContext context) +37 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +100 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.225
I tried to reproduce the problem in my local test by viewing the CustomEditorTypes.aspx sample file that available in WebGridSamples project in IE browser; make changes to the cell of “Notes” column using the font or bold function; save the changes by clicking the “Update” button. Unfortunately, my efforts were not successful – everything worked smoothly and the HtmlEditor was accessed without any issues.
For your information, I’m using WebGrid 7 build 431; WebUI.NET Framework 3 build 772; and IE 8 as the browser. Please let us know the build version of your WebGrid; WebUI.NET Framework 3; and the browser version.
Hi Yudi,
I have webgrid 7.0.7200 and IE8. Where can I find version of my webui.net framework?
thanks,
Steve
The steps below show how to find the build version of WebGrid 7 and WebUI.NET Framework 3.
Hope this helps.
here is my build version webgrid 7.0.7200.429 and webui.net framework 3.0.5000.770. i'm using IE8.
I’d like to suggest you to apply the latest hotfix of WebGrid 7 (build 431) and WebUI.NET Framework 3 (build 772). You can use the Intersoft Update Manager application to check for the latest available update and automatically install them as easy as a few clicks away.
For your information, I’m using WebGrid 7 build 431 and WebUI.NET Framework 3 build 772 and test the reported issue under IE 8 browser as well. Hope that applying the hotfix would address the issue properly otherwise there are another factor that we should check regarding this problem.
Look forward to hearing back from you.
Yudi,
I tried to update my webgrid 7, but I get this error that it has been blocked. Please see screen shot.
Should you find any difficulties when using the Intersoft Update Manager application, alternately you can try to apply the latest hotfix manually. First, you will need obtaining the hotfix file from “My Components” section of your TDN account. Next, please carefully follow the step-by-step shown in http://www.intersoftpt.com/Support/WebUIStudio/Tutorial/Text/Apply-ASPNET-product-hotfix-manually/ in order to apply the hotfix manually.
This should helps.
I don't have a tdn account. where can i register for one? thanks.
The TDN can be accessed in http://dev2.intersoftpt.com/. If you don’t have the credential (user name and password) to login into the TDN, please try to contact the person who’s in charge when purchase Intersoft control.
I'm still getting the same error after applying the hotfix for webgrid. Please see screen shot. thanks.
*Edited: remove attachment because it contains some confidentials information (by Intersoft Support)
I’m willing to advise you further but in order to do so I would need you to elaborate on your specific scenario and possibly provide a running simple sample and a step-by-step guide that I can use to observe the problematic behavior.
You may modify the CustomEditorTypes.aspx sample file which is available within WebGridSamples project and have the modified sample attached to be investigated further.
Hi Steve,
You could try disabling request validation in ASP.NET if that is an option for you. See this link for more information.
http://www.asp.net/learn/whitepapers/request-validation
I agree with the post from Questica Support.
You might also want to check the requestValidationMode in your web.config file. For more information, please check this link http://jefferytay.wordpress.com/2010/04/15/asp-net-4-breaking-changes-1-requestvalidationmode-cause-validaterequestfalse-to-fail/.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname