forked from docs/doc-exports
Reviewed-by: Rogal, Marcel <mrogal@noreply.gitea.eco.tsi-dev.otc-service.com> Co-authored-by: Li, Qiao <qiaoli@huawei.com> Co-committed-by: Li, Qiao <qiaoli@huawei.com>
2.4 KiB
2.4 KiB
Why Does WAF Block Normal Requests as Invalid Requests?
Symptom
After a website is connected to WAF, a normal access request is blocked by WAF. On the Events page, the corresponding Event Type reads Invalid request, and the Handle False Alarm button is grayed out, as shown in Figure 1.
Possible Cause
If any of the following cases, WAF blocks the access request as an invalid request:
- When form-data is used for POST or PUT requests, the number of parameters in a form exceeds 8,192.
- The URL contains more than 2,048 parameters.
- The number of headers exceeds 512.
Solution
If you confirm that the blocked request is a normal request, allow it by Configuring Custom Precise Protection Rules.
Parent topic: Checking Whether Normal Requests Are Blocked Mistakenly