Most spam contains links. Implementations are encouraged to detect unwanted links.
The SpamDetectionInFirewall setting in web.xml can instruct the {@link hirondelle.web4j.security.ApplicationFirewall} to use the configured SpamDetector to reject all requests containing at least one parameter that appears to be spam. Such filtering is applied as a hard validation, and will not result in a polished response to the end user.
If that policy is felt to be too aggressive, then the only alternative is to check all items input as text using {@link hirondelle.web4j.model.Check#forSpam()} (usually in a Model Object constructor). Such checks do not need to be applied to numeric or date data, since the regular conversion validations done by {@link RequestParser} for numbers and dates will already detect and reject any spam.
|
|
|
|