From d5ab65ba41f6eb3f2486bb1734a559dac8839917 Mon Sep 17 00:00:00 2001 From: Peter Berg Date: Fri, 30 Jan 2015 16:26:04 -0500 Subject: [PATCH] Update README to warn against use of Negative Captcha with caching I could be wrong about this, but I just spent a bit of time looking through the source code here and trying to debug an issue on my production servers, and the conclusion that I came to was that it was caused by caching. If I'm correct, I figure this could be worth including here to save others from running into the same issue. Big fan of the concept and gem. --- README.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.markdown b/README.markdown index d7483d0..85bff57 100644 --- a/README.markdown +++ b/README.markdown @@ -133,6 +133,10 @@ Modify your form to include the honeypots and other fields. You can probably lea <% end -%> ``` +### Caching / Use in Production + +Note that if you serve cached form markup generated with Negative Captcha and have the :spinner property in NegativeCaptcha.new set to a client-specific value, NegativeCaptcha will be unable to decode any form submission by a client other than the client used to warm the cache. Be sure to re-render all forms generated with Negative Captcha upon each request. + ### Test and enjoy! ## Possible Gotchas and other concerns