Bug 781563 - captcha validation is throwing errors even when captcha text is entered correctly
Summary: captcha validation is throwing errors even when captcha text is entered corre...
Keywords:
Status: CLOSED DUPLICATE of bug 765906
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Alex Boone
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-13 18:21 UTC by Nam Duong
Modified: 2015-05-15 01:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-16 13:34:55 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Nam Duong 2012-01-13 18:21:53 UTC 
There are 2 users who sent questions to openshift in re: to captcha throwing validation errors.  They are both using the TITAN promo code.

Seems captcha validation throws the error erroneously as the user validation email is still being sent and the users are able to validate/register.

Urgent cause this causes the user to think the site is broken and the user feels locked out.
Comment 1 Alex Boone 2012-01-13 19:26:26 UTC 
I believe what is happening here is the user is incorrectly solving the CAPTCHA once, at which point an error message is displayed.  The second time, when they solve it correctly, they are obtaining a 500 error (due to bug 781565), which causes the form submission to fail, but does not update the error message, leaving the "Captcha text didn't match" message displayed.

This should be confirmed by the following results:
- Without a promo code, solving the captcha the first, second or Nth time all work
- With a promo code, solving the captcha the first time does not display the captcha error (500 error instead)
Comment 2 Alex Boone 2012-01-16 13:34:55 UTC 

*** This bug has been marked as a duplicate of bug 765906 ***
Note You need to log in before you can comment on or make changes to this bug.