Bare byte decoding and French characters

Hi Nathan,

thanks for that solution, it really indicates that this is normal behavior:

If the BIG-IP ASM receives a single-byte sequence when the application language is set
to a multi-byte encoding, such as UTF-8, the character will fail the character decoding process.
The Failed to convert character violation will be triggered [...]

But interesting is the other solution (11491) where it refers to at the end. Is this also available (or could be updated) for version 11.x? I'm wondering because for version 10.x it mentions that these French characters are allowed by default for Rapid Deployments (what we also used when creating the policy). Or has this nothing to do with the above issue?

So would that mean that I have to double check if such "higher" ASCII-character will be used somewhere in the URI or in parameters, and if so that I may not use UTF-8? Or is this also depending how the browser behaves with such characters? I mean e.g. a forum in France, where such characters are included in nearly each POST-request when entering a new comment would be triggered. Isn't there any other method to allow or whitelist such characters?

Thank you!

Ciao Stefan 🙂