Enabling Break Protection to Protect Origin Servers

Prerequisites

• You have added the website to WAF.
• You have upgraded the dedicated WAF instance to the latest version. For details, see Upgrading a Dedicated WAF Instance.

Constraints

• You have selected Dedicated mode for your website deployment.
• Before enabling Break Protection, make sure you have updated dedicated WAF instances to the latest version,, or your services might be affected.
• Connection Protection is available in some regions. For details, see Functions.

Enabling Break Protection

1. Log in to the management console.
2. Click in the upper left corner of the management console and select a region or project.
3. Click in the upper left corner and choose Web Application Firewall under Security & Compliance.
4. In the navigation pane, choose Website Settings.
5. In the Domain Name column, click the website domain name to go to the basic information page.
6. In the Break Protection area, click the status icon to toggle it on.
   Figure 1 Break Protection
   

7. Click next to each parameter, edit Breakdown Protection and Connection Protection parameters to meet your requirements, and click to save settings. Table 1 describes these parameters.

   Table 1 Connection Protection parameters

   Parameter		Description	Example Value
   Breakdown Protection	502/504 Error Threshold	30s 502/504 Error Threshold	1000
   	502/504 Error Percentage (%)	A breakdown is triggered when the 502/504 error threshold and percentage threshold have been reached.	90
   	Initial Downtime (s)	Protection period upon the first breakdown. During this period, WAF stops forwarding client requests.	180
   	Multiplier for Consecutive Breakdowns	The maximum multiplier you can use for consecutive breakdowns. The number of breakdowns are counted from 0 every time the accumulated breakdown protection duration reaches 3,600s. For example, assume that Initial Downtime (s) is set to 180s and Multiplier for Consecutive Breakdowns is set to 3. If the breakdown is triggered for the second time, that is, less than 3, the protection duration is 360s (180s x 2). If the breakdown is triggered for the third or fourth time, that is, greater than or equal to 3, the protection duration is 540s (180s x 3). The breakdowns are counted from 0 when the total downtime duration exceeds one hour (3,600s).	3
   Connection Protection	Pending URL Request Threshold	Connection Protection is triggered when the number of read URL requests reaches the threshold you configure.	6,000
   	Duration (s)	Protection duration. During this period, WAF stops forwarding client requests.	60

   

   Use Figure 1 as an example:

   • Breakdown Protection: When the number of 502/504 errors returned by the protected website exceeds 1,000 and accounts for 90% or more of the total access requests of the website for the first time, the first breakdown protection is triggered. During the first breakdown protection, WAF stops forwarding client requests for 180s (that is, blocks visitors access to the website for 180s). If a second consecutive breakdown protection is triggered, WAF stops forwarding client requests for 360s (180 x 2). If a third or more consecutive breakdowns are triggered, WAF stops forwarding client requests for 540s (180s x 3). The breakdowns are counted from 0 when the total downtime duration exceeds one hour (3,600s).
   • Connection Protection: When the number of read URL requests in the waiting queue exceeds 6,000, WAF stops forwarding client requests for 60 seconds and returns the maintenance page of the website to visitors.