Results 1 to 2 of 2

Thread: Error show when marking order as shipped Version 9.1

  1. #1
    Join Date
    Dec 2011
    Posts
    1

    Default Error show when marking order as shipped Version 9.1

    Store Version: AspDotNetStorefront Multistore 9.1.0.1/9.1.0.0

    A potentially dangerous Request.Form value was detected from the client (FinalizationData="<root>
    </root>").
    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 (FinalizationData="<root>
    </root>").

    Source Error:

    [No relevant source lines]


    Source File: c:\windows\Microsoft.NET\Framework\v4.0.30319\Temp orary ASP.NET Files\root\9e3e0cc1\9d722a95\App_Web_mnvoy5t4.24.c s Line: 0

    Stack Trace:

    [HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form value was detected from the client (FinalizationData="<root>
    </root>").]
    System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection) +8855748
    System.Web.HttpRequest.ValidateNameValueCollection (NameValueCollection nvc, RequestValidationSource requestCollection) +122
    System.Web.HttpRequest.get_Form() +150
    System.Web.HttpRequest.get_HasForm() +9028559
    System.Web.UI.Page.GetCollectionBasedOnMethod(Bool ean 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(Http Context context) +21
    System.Web.UI.Page.ProcessRequest(HttpContext context) +49
    ASP.admin_orderframe_aspx.ProcessRequest(HttpConte xt context) in c:\windows\Microsoft.NET\Framework\v4.0.30319\Temp orary ASP.NET Files\root\9e3e0cc1\9d722a95\App_Web_mnvoy5t4.24.c s:0
    System.Web.CallHandlerExecutionStep.System.Web.Htt pApplication.IExecutionStep.Execute() +100
    System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean& completedSynchronously) +75

  2. #2
    Join Date
    Sep 2011
    Location
    Lincolnshire, England
    Posts
    2

    Default

    Search for "FinalizationData" in Admin\orderframe.aspx.vb, where the textarea is created for FinalizationData add disabled=""disabled"".

    This will stop the FinalizationData textbox being submitted back to the server.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •