CAPTCHA verification

Status: completion un-verified. The custom page and trusted connection were observed, but a Google quota warning and an expired challenge prevented live human completion. The configuration below describes intended behavior.

A human-verification challenge asks visitors to complete a task before reaching the application, unlike the automatic JavaScript challenge. CAPTCHA stands for “Completely Automated Public Turing test to tell Computers and Humans Apart.” Use the custom page to explain what to do.

Visitor message: Please complete the verification to continue.

The load balancer’s captcha_challenge.custom_page supplies the wording; cookie_expiry is 300 seconds in this example. Keep the CAPTCHA controls usable when customizing the page. A returning visitor with an accepted cookie may not see the challenge again.

This setting is not restricted to /challenge; that path is only a test URL. To challenge selected paths, see conditional challenges.

CAPTCHA challenge source

{
  "spec": {
    "captcha_challenge": {
      "cookie_expiry": 300,
      "custom_page": "string:///PHA+UGxlYXNlIGNvbXBsZXRlIHRoZSB2ZXJpZmljYXRpb24gdG8gY29udGludWUuPC9wPg=="
    }
  }
}

Decoded preview (escaped):

<p>Please complete the verification to continue.</p>

Expected result (un-verified): In a fresh browser session, the visitor sees the message, completes a usable CAPTCHA, and reaches the application. With an accepted cookie, a repeat request normally reaches the application without another challenge. Clear the cookie to test the first visit again.