Question

(Signatures) A potentially dangerous Request.Form value was detected...

Forms

Updated January 28, 2014

asked on January 16, 2014 • Show version history

After upgrading to Forms 9.1 a signature capture piece we implemented in 9 is not being allowed to submit. Are there any workarounds until 9.2 comes out and offers a built in signature capture piece?

This is the error in the activity log:

1/16/2014 4:06:35 PM | Session: jnkjhsi2crjjlezrnd4q1vj4
User: A_User
URL: /Forms/Form/Submit
Message: A potentially dangerous Request.Form value was detected from the client (Field35="...e/svg+xml,<?xml version="1.0" ...").
Stack trace:    at System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection)
   at System.Web.HttpValueCollection.Get(String name)
   at E_Forms.Models.ViewModels.Form.Submit.RetrieveDataFromForm(HttpRequestBase request)
   at E_Forms.Controllers.FormController.Submit()
   at lambda_method(Closure , ControllerBase , Object[] )
   at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<>c__DisplayClass2a.<BeginInvokeAction>b__20()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult)

The field data looks like this:

image/svg+xml,<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="576" height="99"><path fill="none" stroke="#000000" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" d="M 1 72 c 1.51 -0.42 59.71 -12.69 86 -24 c 27.06 -11.65 77.37 -46.08 79 -47 c 0.19 -0.11 -6.64 4.17 -8 7 c -6.46 13.41 -17.12 37.51 -18 47 c -0.26 2.78 10.19 8.4 13 7 c 8.49 -4.24 27.96 -20.62 33 -30 c 2.75 -5.12 -2.65 -25.31 -4 -24 c -4.17 4.07 -35.48 51.39 -38 65 c -0.94 5.06 17.19 17.76 23 16 c 15.71 -4.75 51.29 -42 63 -42 c 7.06 0

(cut short for brevity in this post)

0 0

Answer

APPROVED ANSWER

replied on January 17, 2014 • Show version history

In the Advanced Laserfiche Forms course at the conference, we're demoing a working "wet" signature creating using custom HTML and JavaScript. The user is able to sign the form with a finger or a mouse and once they've accepted their signature it is saved as an image on the form.

The demo business process will be uploaded after the conference, so definitely take a look at that when it's available.

UPDATE: The Advanced Laserfiche Forms powerpoint, business process, and signature instructions are now on the support site. Get them here.

1 0

Replies

replied on January 16, 2014

The thread should be helpful. http://stackoverflow.com/questions/81991/a-potentially-dangerous-request-form-value-was-detected-from-the-client.

I am not sure if it makes sense to you, but you could also try to HTML encode the signature data before you submit.

2 0

You are not allowed to follow up in this post.

Question

Question

(Signatures) A potentially dangerous Request.Form value was detected...

Answer

Replies

Sign in to reply to this post.