Forum Discussion
Walter_Kacynski
Cirrostratus
CirrostratusASM failed to convert character unicode
Does anyone know how the ASM uft-8 metadata character conversion process works? I have a situation where a user submits unicode U+2019 (http://www.fileformat.info/info/unicode/char/2019/index.htm). However ASM doesn't seem to handle this particular meta character. The only solution is to disable character set checking.
Ashwin_VenkatEmployee
Unicode U+2019 is referred to as 'right single quotation mark': https://www.compart.com/en/unicode/U+2019 and that one percent encodes to %92 per the ASCII table: http://www.ascii-code.com/. This one isn't considered to be unicode, if the application encoding language used by the ASM policy is UTF+8. As a result of this, when ASM gets the percent encoded request and tries to decode %92, it isn't able to do it for this application language. This results in the "Failed to convert character" violation.
Recommendation would be to use a different application language or to continue having the blocking setting disabled for this violation.