← All experiments

EXPERIMENT 02 / INLINE CAPTCHA

Stay on the page.
Solve at the right moment.

The page is public. Its JSON request is protected. Send that request, inspect WAF’s response, then solve AWS’s puzzle right here.

LIVE SESSION

Your token, right now.

SDK: Checking…Token cookie: Checking…

Background challenge

Checking…

Estimated time remaining

Unknown

Waiting for AWS’s SDK to report whether this session has an active token.

CAPTCHA immunity

Not observed

Immunity time remaining

Unknown

A successful CAPTCHA solve starts this demo’s 60 second immunity window.

Active status comes from AWS’s SDK. Challenge time is an upper limit estimate, because AWS does not expose its expiry timestamp. Automatic refresh can restart the estimate. CAPTCHA has a separate window. WAF validates every protected request.

01

Request

The frontend fetches /inline-protected/demo.json with AWS token handling.

02

Verify

When WAF returns a CAPTCHA response, the page loads AWS’s widget and renders the puzzle below.

03

Retry

After a successful solve, the page retries the same request and displays the returned JSON.

MAKE A REAL REQUEST

Load the protected content.

A background challenge token is not enough for this rule. WAF checks for a recent CAPTCHA solve.

Preparing the experiment…

Request timeline

Only observed events appear here. WAF logs contain the exact matching rule.

  1. No requests yet. Start an experiment to see the sequence.

Protected response

This is populated only when the request returns JSON successfully.

No protected response loaded yet.
Which code belongs to the frontend?

CloudFront inserts challenge.js to acquire background browser tokens. This page separately loads the CAPTCHA jsapi.js from the deployed configuration, calls AwsWafCaptcha.renderCaptcha(), and retries the JSON request in onSuccess. WAF owns token validation.

The configured CAPTCHA API key is an encrypted, domain-scoped client key intended for the browser. Token values are never displayed by this demo.