Forum Discussion

tminfw2's avatar
tminfw2
Icon for Nimbostratus rankNimbostratus
Jan 29, 2015

Bare byte decoding and French characters

Currently, our ASM policies are configured with bare byte decoding check activated. However, this poses problems, as some of our legitimate French pages are flagged with this error. Specifically, it ...
ASM Advanced WAF
management
security
Stefan_Klotz's avatar
Stefan_Klotz
Icon for Cumulonimbus rankCumulonimbus
Oct 29, 2015

Hi all,

 

we have a similar issue here as well, so I decided to use this thread instead of opening a new one.

 

We are using a UTF-8 policy on 11.4.1 HF8 and the violation "Failed to convert character" is triggered due to French characters (like é) on a parameter value. We tried already "Ignore Value" for this parameter as well as disable "Check characters on this parameter value", but the violation will still be triggered. In the lab we found out that the list of Character Sets includes these French characters if you are using Western European instead of UTF-8. Is this the reason why the F5 can't read such characters correctly, because I always thought that UTF-8 is a universal language to avoid such issues? Also in the learning suggestion section it's not possible to learn this violation/make an exception for it. So right now we disabled blocking for this violation type at all.

 

But isn't there a much better and granular option to solve this issue?

 

Thank you!

 

Ciao Stefan :)