Validating CAPTCHA challenge secret

From ePrize Developers Wiki

(Difference between revisions)
Jump to: navigation, search
Current revision (13:57, 30 June 2011) (edit) (undo)
 
(One intermediate revision not shown.)
Line 5: Line 5:
== Headers ==
== Headers ==
-
Both headers must be added to the create profile request for the challenge to be correctly validated.
+
Both headers must be added to the create profile request for the challenge to be correctly validated. The {secret} is the text embedded in the image fetched via [[Fetch_CAPTCHA_challenge|fetch CAPTCHA challenge]].
-
Request header representation:
+
Request header representation (use only the relative captcha location as noted here):
<pre>X-CAPTCHA-Challenge: /v1/{apikey}/captcha/{challenge-id}
<pre>X-CAPTCHA-Challenge: /v1/{apikey}/captcha/{challenge-id}

Current revision

This is not a resource itself, but validation of a CAPTCHA challenge takes place as a side-effect of creating a profile if the API key is marked as requiring CAPTCHA validation. For these API keys, the client must send CAPTCHA challenge/response information in the request headers of the API call.

For full information please see create profile.

Headers

Both headers must be added to the create profile request for the challenge to be correctly validated. The {secret} is the text embedded in the image fetched via fetch CAPTCHA challenge.

Request header representation (use only the relative captcha location as noted here):

X-CAPTCHA-Challenge: /v1/{apikey}/captcha/{challenge-id}
X-CAPTCHA-Response: {secret}



Personal tools