When the kaptcha is generated, the generated key is stored in the session for verification. I'm guessing the session is lost between initial display and verification. From memory your jsessionid is a cookie value. Are you switching domains or something?
I'd inspect the request headers and make sure the jsessionid cookie header is consistent between kaptcha view and verification. On 18 Nov 2014 21:02, "George Christman" <gchrist...@cardaddy.com> wrote: > Hmm, I don't use sticky sessions, but why do you think this would be > happening all of a sudden? btw lance, how does this work, is it suppose to > store some type of cookie? > > On Tue, Nov 18, 2014 at 1:25 PM, Lance Java <lance.j...@googlemail.com> > wrote: > > > I'm guessing this is a session issue. Perhaps a session cookie issue? Or > > clustering / session replication issue? > > On 18 Nov 2014 14:06, "George Christman" <gchrist...@cardaddy.com> > wrote: > > > > > Yesterday I appeared to be having a lot of failures with kaptcha. > > Sometimes > > > the image would appear and sometimes it wouldn't. When it did appear, > it > > > would always fail saying the text didn't match even though it did. I > > ended > > > up just removing it until I could figure out the cause of it's failure. > > It > > > appears to have worked perfectly up until yesterday and the only thing > I > > > can think of is I upgraded Guava to a newer version, but other than > that > > I > > > don't see where I made any changes. I followed the source back to > > > com.google.code.kaptcha, but that was as far as I was able to get. Does > > > someone know what might be causing kaptcha to fail like this? > > > > > > > > > -- > George Christman > CEO > www.CarDaddy.com > P.O. Box 735 > Johnstown, New York >
