DNN: 5.2.2
Dynamic Forms: 3.3.40.0

I've setup a form completion event which sends a http post to Salesforce. The first post was successful, but all following requests throw an exception:

AssemblyVersion: 5.2.2
InnerException: The request was aborted: The request was canceled.
Method: System.Net.ConnectStream.CloseInternal
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: The request was aborted: The request was canceled. ---> System.Net.WebException: The request was aborted: The request was canceled. ---> System.IO.IOException: Cannot close stream until all bytes are written. at System.Net.ConnectStream.CloseInternal(Boolean internalCall, Boolean aborting) --- End of inner exception stack trace --- at System.Net.ConnectStream.CloseInternal(Boolean internalCall, Boolean aborting) at System.Net.ConnectStream.System.Net.ICloseEx.CloseEx(CloseExState closeState) at System.Net.ConnectStream.Dispose(Boolean disposing) at System.IO.Stream.Close() at System.IO.StreamWriter.Dispose(Boolean disposing) at System.IO.StreamWriter.Close() at DataSprings.Modules.DynamicForms.DynamicForms.ProcessEvents(Boolean blnRedirectOnly, Boolean blnPaymentGateway, String strPaymentStatus, String strResponseID, Int32 intPaymentUserID) at DataSprings.Modules.DynamicForms.DynamicForms.SubmitForm(Boolean ProcessPaymentNotification, String strResponseID, Boolean blnByPassValidation) at DataSprings.Modules.DynamicForms.DynamicForms.lnkSave_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.LinkButton.OnClick(EventArgs e) at System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

Is this a known error?

Cheers,
Thomas

HI, this is new to me. When you say all follow up request throws an exception, are you referring to other completion events that you have that will not execute after the HTTP posting? -- David

There are only two events configured. The first one sends an email successfully. The second one is the mentioned http post event.

I've changed the port URL to http://authors.aspalliance.com/aldo...#160;which now fails, too.

I'll reduce the post variables all post variables and add the vars step by step see where it breaks.

Cheers,
Thomas

The error is being throw because of the use of an umlaut (mutated vowel Ü) in the textbox.

The user can enter the name of the city. And in the exampel "Hückelhoven" the error occurs.

Cheers,
Thomas

Hmmm... Interesting... We might need to add a feature into the module that allows you to choose an 'Alternate Encoding Method' for http post completion events. I will research this further and look to add this for future versions.

-Chad

Hi,

any news on this topic? Will it make it's way to the feature list?

Cheers,
Thomas

Hi Thomas,

This is still on the list but no direct release date for the enhancement yet... I think part of this is confusing as well because within the silent HTTP Post VB.NET Code there are multiple areas where we can specify an 'encoding' option. Whenever we have implemented this in the past its been a little more clear such as for emails and so forth.

Other options might be to either modify the source and / or if you need the feature added outside of our normal release schedule you can pick up the minimum number of Premium Support hours (6) and we can do this for you. You can find out more about Premium Support if you want to go this route at http://www.datasprings.com/Premium-Support.

Thanks,

Chad

Hi, I found the same problem, or at least it looks very similar when entering "Rodríguez" (it is working if I use "Rodriguez", not the í ). This was fixed? or you have any estimate?

Thanks

Javier

Hi guys,

Sorry the enhancement to allow for alternate encoding did not make the 3.4 release which went out yesterday, this is partly because recently we had made a few changes to the HTTP completion event that were breaking changes related to HTML encoding for the majority of our customers (but did help a few ) so before we wanted to jump back into any changes we wanted to have the code set back the way it was.

A few references as we review this that we can follow up on as they sound similar:
http://social.msdn.microsoft.com/fo...e6dd67edaf

AND
http://social.msdn.microsoft.com/forums/en-US/vblanguage/thread/40a35628-e536-46e0-8fe1-432c8af2c369

If either of you are on the 3.4 release already I would be happy to send you over a patch you can test that would include some changes made for specifying the encoding, right now it looks like no encoding is specified so one thing we can try is to specify UTF8... Some of the other threads are more complicated though so I will need to test this further.

Thanks,

-Chad

... I'm having a similar problem...
Wouldn't url-encoding be a good solution?

UrlEncode(Hückelhoven) = H%C3%BCckelhoven ...

Hi guys...

Yes, the problem with this was that in the past we did add URL Encoding and it ended up causing a major problem and the HTTP Post wasn't working at all.

The GREAT news is that we modified this and now tested this further to only URL Encode the specific responses for HTTP Posts and a quick test shows this is successful! You can test this for yourself here (enter a valid email on this page)

https://www.datasprings.com/Products/DNN-Modules/Dynamic-Forms/Dynamic-Forms-Demo-33-Silent-Post-Demonstration/tabid/1051/language/en-US/Default.aspx

You can try these characters as a test:
á â ä Ŏ Ѐ ē é ê

It appears to work now. So, we have added this to the most recent patch for the 3.4 release which we plan to post next week. This should be 3.4.20, if someone needs a patch sooner for 3.4 please open a support ticket and provide me with your invoice ID.

We don't typically add or update patches for previous versions however we can make an exception in this case. If you are running into this problem and are on 3.1 or 3.3 and don't plan to upgrade (probably won't go back much further then that) let me know and we can setup a patch for you.

Thanks,

Chad

... Nice! Just one more little thing: I filled the form with last name D'Angiò (a quite common last name here in Italy) but received D''Angiò in the confirmation email. It looks like sql injection prevention, I'm hoping that does not happen on the sender form side: it would be bad!

Hi. Yep, it was and doesn't need to be since this isn't a SQL Event. I have updated the code and this will also make it in the 3.4.20 patch for the 3.4 release. Thanks for bringing this to our attention!

-Chad

Hi Chad
will this patch also correct my problem with paypal??
My PayPal paramerts list looks the following:
&item_name="Membership Fanclub"¤cy_code=CHF&amount=49&no_shipping=1&first_name=$(FName)&last_name=$(LName)&email=$(Email)

The bad news: All names with äöü etc. in it will result in "Completed / web_accept(INVALID)" completion because the user is registered at PayPal with äöü but the name in $(LName) or ä(Fname) ist incorrectly submitted to PayPal.

So, for me this patch is essential. By the way: does this patch also inlcude a correctiion for the DNN 5.5 "enter key" problem?

Best regards

Thomas

Hi Thomas - yes, we just corrected this today as well so it will be avaliable when the full patch is released (just pending some items related to file/image uploads before release).

We do not have any patches yet avaliable for the new issue that comes up with 5.5 and the enter key, that is something we are still researching.

Thanks,

Chad