← All experiments

EXPERIMENT 03 / TARGETED BOT CONTROL

A quieter check.
A smarter decision.

CloudFront injects AWS’s browser SDK. Targeted Bot Control evaluates signals and behavior on each protected JSON request. A normal visit may need no puzzle at all.

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

Acquire a browser token

The injected SDK runs a background check. The token carries information used by targeted rules.

02

Send one request

Compare AWS SDK handling with a request that deliberately omits credentials. Each click sends one experiment request.

03

Inspect the outcome

Managed rules can permit, challenge, require CAPTCHA, or block. The timeline shows the final HTTP response actually observed.

LIVE BROWSER STATE

Ready the browser. Then test it.

Inspection level
TARGETED
Managed rule actions
Enforced

Waiting for the injected SDK…

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.

READ THE RESPONSE

What did the browser observe?

ResponseWhat it tells you
200 + JSONThis request passed the active rules. It is not a permanent verdict about the visitor.
202 + Challenge headerWAF requested a background browser check. The SDK can handle this during token acquisition.
405 + CAPTCHA headerWAF requested a human puzzle. This page will offer the inline widget and retry after solving.
403The request was denied. Use WAF logs to identify the exact rule and labels.
How do I inspect the real rules and signals?

Open browser DevTools and preserve the Network log. AWS’s fetch wrapper can handle a silent challenge internally, so this timeline may show only the final response. In the AWS WAF console, inspect this web ACL’s requests and Bot Control labels for the exact detection.

CloudFront’s automatic integration adds the background SDK to eligible HTML. It does not add the CAPTCHA widget. This page loads the widget only if WAF requests CAPTCHA. The protected endpoint is /bot-protected/demo.json; the page itself stays public so it can acquire a token first.