This content has been marked as final. Show 3 replies
The example you gave works fine on my machine. Are you viewing the source code to see what the real response is? IE will translate a & in the HTML into "&" on screen.
I should also mention that we do a fair amount with WDDX (passing it in hidden form fields, etc) and we haven't noticed a problem with character entities.
Thanks for your reply. You are right, I didn't check my example carefully. That works correctly. But I can confirm that my actual problem was accurate. If the request contains data with &,<,>,'," chars, something like the attached code works only if the original request does not already exist. If the user is required to use the generated confirmation form, the cfwddx tag throws an error because submitting the form decodes the character entities before the cfwddx call. I look at the source and the value of the hidden field contains &, but if I print the wddxString out before the cfwddx call, it contains & in the source when the confirmation is submitted. If "fixed" it by using URLEncodedFormat() and URLDecode() on the wddxString.