Hi friends,
I have set parameter matching in UTF8 encoding on modsecurity, but there is a
web application which using iso-8859-1 for its encoding, and the thing is
modsecurity will detect every parameter encoded in iso-8859-1 in the post and
get parameters as an attack, that is natural behavior but I wonder how we can
support other encoding such as iso-8859-1, also there are some functions which
I think are ambiguous, like t:urlDecodeUni, I couldn't detect any
transformation by this function, also SecUnicodeCodePage and SecUnicodeMapFile,
the thing is it is not clear what exactly mapping do,
I will be so thankful if you can guide me, do you think I have to change in the
developing level to support other encodings?
Thanks a lot,
All the best
~Iman
_______________________________________________
Owasp-modsecurity-core-rule-set mailing list
Owasp-modsecurity-core-rule-set@lists.owasp.org
https://lists.owasp.org/mailman/listinfo/owasp-modsecurity-core-rule-set
