What are the ready-made blocking page templates (Turkish, English, JSON)?

Short answer

In the Ready-made Templates field at the top of the Blocking Page window, there are four ready-made setups: English page, Turkish for visitors who prefer it; Turkish default WAF blocking page; English default WAF blocking page and JSON default blocking page. The first three set the Blocking Page Source field to Content profile and select the built-in WAF blocking page (English) or WAF blocking page (Turkish) profile; all four templates remove the existing Conditional Blocking Pages entries; in their place, the bilingual template writes a single conditional page that shows the WAF blocking page (Turkish) profile to the visitor whose browser prefers Turkish. The JSON template sets the source to Manual content and the type to application/json, and puts a JSON that writes the attack information into the body. No template changes the Blocking Status Code. After the template is confirmed, the window is saved with Edit. Separately from these, there are eight built-in page templates in the Content Pages add form.

Blocking Page Templates

Template	The setting it sets up	Effect on conditional pages
English page, Turkish for visitors who prefer it	Blocking Page Source: Content profile · Blocking Page Profile: WAF Blocking Page (English) · a single conditional page: condition If the client prefers Turkish over English, page WAF Blocking Page (Turkish), status code the current Blocking Status Code	Deletes all the existing entries and writes only this entry in their place
Turkish Default WAF Blocking Page	Blocking Page Source: Content profile · Blocking Page Profile: WAF Blocking Page (Turkish)	Deletes all the existing entries
English Default WAF Blocking Page	Blocking Page Source: Content profile · Blocking Page Profile: WAF Blocking Page (English)	Deletes all the existing entries
JSON Default Blocking Page	Blocking Page Source: Manual content · Blocking Page Content Type: application/json · Blocking Page: {"attackInfo": %WAF_INFO}	Deletes all the existing entries

• When a template is clicked, the Apply "…"? confirmation appears. The text below it is This replaces the current blocking page settings.; if the form has conditional pages, it says This replaces the current blocking page settings, including the N conditional page(s) below. and gives the number of entries to be deleted. The confirmation only fills in the form; the setting is applied when the window is saved with Edit. If the conditional pages are to be kept, Blocking Page Source and the page fields are changed manually instead of using a template.
• The bilingual template uses the built-in condition that reads the browser language preference (Accept-Language) of the visitor; a visitor who does not state a preference sees the English page (Can I show a blocking page based on the visitor's language?).
• The templates that select a profile select the built-in profile itself, not a copy of the page. On the built-in English page, the time of the request is at the top right, the Your Access To This Page Has Been Blocked! heading is in the middle, and the Request ID and IP Address lines are below it (What does a blocked user see?).
• %WAF_INFO in the JSON template is the other spelling of the %WAFINFO Smart Variable and puts the attack details into the response; the fields shown can be restricted (Which Smart Variables can I use on the blocking page (%UID, %SRCIP, %WAFSCORE, %WAFINFO …); is it safe to show attack details?).

Built-in Pages of Content Pages

At the top of the Load Balancer → Profiles → Content Pages add form, there are eight built-in page templates: the (English) and (Turkish) versions of the Waiting room page, WAF Blocking Page, Access Denied Page and Quarantine Page pages (ready page templates). When a template is clicked, the content type and the content are copied into the form; the copy that is given a name and saved with Add is the user's own profile and can be edited. Details: Are there ready-made maintenance / error page templates?

Common Misconceptions

• "The template also sets the status code." The general code is selected separately in the Blocking Status Code field (Why is the 418 status code returned by default on a block; can I change it?).
• "A single-language or JSON template does not touch the conditional pages." All four templates remove the existing conditional pages; only the bilingual template writes its own conditional page in their place. If there are existing conditional pages, the confirmation window shows the number of pages to be deleted.
• "Clicking a template applies the setting immediately." The template only fills in the form; if the window is closed without Edit being clicked, nothing changes.

How it is done in the documentation

• Blocking Page · Ready-Made Templates
• Content Pages · The Built-in Ready Pages
• Content Pages · The Ready Page Templates

Related questions

• Can I show a blocking page based on the visitor's language?
• Can I return a JSON blocking response instead of HTML for API clients?
• Are there ready-made maintenance / error page templates?