In the past, there were some problems due to over-eager WAF rules, so
this might be a false positive of that kind. It's hard to figure out
what exactly it might be, and unfortunately code samples are very
close to the stuff that a WAF wants to filter out. If you look at the
content and can guess what might be in a filter, it helps to sprinkle
a misspelling in there, or a space.
If I remember correctly, I had to "damage" code once and
write "get Property()" (see the extra space?)
And indeed, I still have to do that...
