Localization and Potentially Dangerous Request.Form Values

D

djmc

Using the asp.net button control (and I assume others), I place the phrase
"Don't Save" in the .Text field. The button displays without any problems,
but upon postback, the server responds with "A potentially dangerous
Request.Form value was detected". I've determined this problem is due to
the single quote in the string.

My main problem occurs when trying to localize our application. In many
foreign languages, the apostrophe is used quite frequently, and it is a
difficult requirement to ask our translators to find phrases without single
quotes. The translator does not know if the key/value of the resource is
destined for static localized text on a page, or if it will be used on a
button or control that will be validated upon postback.

How does one deal with balancing security and localization?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,982
Messages
2,570,189
Members
46,735
Latest member
HikmatRamazanov

Latest Threads

Top