Anti spam honey pot |
(12-19-2015, 10:06 PM)skunkbad Wrote: This solution seems bloated. If you really want to have a so called "honeypot field" in your form, all you have to do is add it, then in your form validation add a callback that checks it for any value. If the value is there then die(), redirect(), log_something(), whatever(); Then you would always need to add it manually and remember too use a callback or custom rule. My approach enables this with a simple true / false setting just like csrf protection. Field is auto added and validated so no chance you would forget a step. If you think this is bloated you probebly think the csrf approach is bloated? |
Messages In This Thread |
Anti spam honey pot - by Martin7483 - 09-30-2015, 03:28 AM
RE: Anti spam honey pot - by ignitedcms - 10-01-2015, 10:52 AM
RE: Anti spam honey pot - by Martin7483 - 10-08-2015, 07:48 AM
RE: Anti spam honey pot - by ardavan - 12-19-2015, 08:20 PM
RE: Anti spam honey pot - by skunkbad - 12-19-2015, 10:06 PM
RE: Anti spam honey pot - by Martin7483 - 12-19-2015, 11:26 PM
RE: Anti spam honey pot - by Diederik - 12-20-2015, 08:00 AM
RE: Anti spam honey pot - by includebeer - 12-20-2015, 04:25 PM
RE: Anti spam honey pot - by Martin7483 - 12-22-2015, 04:57 AM
RE: Anti spam honey pot - by ardavan - 02-29-2016, 05:35 AM
RE: Anti spam honey pot - by peterm87 - 03-30-2016, 12:22 PM
RE: Anti spam honey pot - by peterm87 - 03-30-2016, 12:16 PM
RE: Anti spam honey pot - by Martin7483 - 04-07-2016, 07:12 AM
RE: Anti spam honey pot - by Martin7483 - 06-20-2017, 04:58 AM
RE: Anti spam honey pot - by jj.ranran225566 - 07-10-2022, 12:08 AM
|