Read WAF logs
Reference ID lookup, repeated blocks and the exception form.
Open topicCDN.com.tr Help
Put the WAF in log-only mode for the whole site or for the paths you choose, for 7, 14 or 30 days. The WAF rules keep inspecting every request and write the ones they would have blocked to the logs as "would have been blocked", but block none of them. When the period ends, the account goes back to blocking by itself.
Cache, security, WAF, and purge
Put the WAF in log-only mode for the whole site or for the paths you choose, for 7, 14 or 30 days. The WAF rules keep inspecting every request and write the ones they would have blocked to the logs as "would have been blocked", but block none of them. When the period ends, the account goes back to blocking by itself.
Apply log-only mode to the whole site or only to the paths you want to try.
/api/ and =/login.Expected result: The card shows the end date and the days left; the edge servers apply the change within 1-2 minutes.
# API: GET /api/accounts/$ACCOUNT_UUID/waf/mode
# API: PUT /api/accounts/$ACCOUNT_UUID/waf/mode
# {"mode":"detect","scope":"paths","paths":["/api/","=/login"],"days":14}
While the mode is on, the requests the WAF would have blocked are listed under their own filter.
Expected result: You see which rule would stop your real visitors on which path, without anyone being blocked.
Exceptions are permanent: they stay in force after the mode ends.
Expected result: In blocking mode your legitimate requests go through and attack requests are blocked.
# API: GET /api/accounts/$ACCOUNT_UUID/waf/exclusions
# API: PUT /api/accounts/$ACCOUNT_UUID/waf/mode
# {"mode":"block"}
You are adding a new form, checkout step or API to your site and want to see which requests the WAF would stop before any visitor gets blocked.
/api/ covers itself and everything under it; to cover only that exact address, start the line with = (=/login).No. In this mode only the WAF rules stop blocking and log their matches instead. IP, country and ASN blocks, the rate limit and the JavaScript challenge keep blocking. If you apply the mode only to your new feature's paths, the rest of the site stays protected by the WAF as well.
On the Security Events page, set the Show filter to "Log only (would have been blocked)". Each row carries the "Would have been blocked (log only)" badge and shows the time, client IP, method, URI, attack type and rule ID. You can download the report as CSV or XLSX with the same filter.
Note the rule ID and the path from the row and add an exception for that rule and path (with the field, if the rule matched a single field) under WAF exceptions on the same page. The exception stays in force when you go back to blocking, so the same request is not blocked when the mode ends. The detailed steps are in Read WAF logs.
Yes. Choose Blocking on the card and save; the account blocks again within 1-2 minutes.
Yes. GET /api/accounts/{account}/waf/mode returns the current mode, its end date and the days left; PUT to the same address with mode (block or detect), scope (site or paths), paths and days (7, 14 or 30) changes it.