THREE WAYS TO PROTECT A REQUEST

Meet the gate.
Then test it.

Explore a full-page CAPTCHA, a puzzle inside your page, and targeted bot detection. Every experiment sends real requests through AWS WAF.

Choose an experiment

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 / FULL PAGE

A checkpoint before entry

Navigate to a protected page. AWS supplies the entire CAPTCHA screen, then retries your navigation after a successful solve.

Decision
Always require a recent CAPTCHA solve
Frontend work
A normal link
Inspect the flow
02 / INLINE CAPTCHA

A puzzle within your page

Request protected JSON, see WAF’s response, and solve the puzzle without leaving the page. Watch the request retry.

Decision
Always require a recent CAPTCHA solve
Frontend work
Widget + response handling + retry
Try inline CAPTCHA
03 / TARGETED BOT CONTROL

Let behavior guide the check

Acquire a background browser token, then compare requests with and without it. AWS’s managed rules choose the response.

Decision
Adaptive bot detection
Frontend work
Injected SDK + interactive request controls
Try Bot Control

EXPERIMENT 01

Follow a full-page CAPTCHA request.

01

Probe the endpoint

The probe deliberately omits cookies. WAF should return 405 and x-amzn-waf-action: captcha. The response is logged below.

02

Open the page

A normal navigation displays AWS’s verification screen. Solve its puzzle to reach the dummy protected HTML.

03

Visit again

A valid CAPTCHA solve lasts 60 seconds in this demo. The next request after expiry requires a new solve. Content already loaded remains visible.

Open protected page

Ready. Probe the endpoint or open the protected page.

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.

The pages and controls are public. WAF protects the separate HTML or JSON requests. CAPTCHA checks human interaction; it does not provide user authentication. The background SDK is injected by CloudFront. The inline puzzle’s widget is loaded explicitly by the page.