vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/wafd/umn/waf_01_0254.html
Li, Qiao e227be9021 WAF Dedicated UMN 01 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Li, Qiao <qiaoli@huawei.com>
Co-committed-by: Li, Qiao <qiaoli@huawei.com>
2022-12-08 11:23:34 +00:00

2.1 KiB
Raw Permalink Blame History

Why Is the Requested Page Unable to Load After JavaScript Anti-Crawler Is Enabled?

After JavaScript anti-crawler is enabled, WAF returns a piece of JavaScript code to the client when the client sends a request. If the client sends a normal request to the website, triggered by the received JavaScript code, the client will automatically send the request to WAF again. WAF then forwards the request to the origin server. This process is called JavaScript verification. Figure 1 shows how JavaScript verification works.

Figure 1 JavaScript anti-crawler detection process
  • To enable the JavaScript anti-crawler protection, the browser on the client must have JavaScript and cookies enabled.
  • If the client does not meet the preceding requirements, only steps 1 and 2 can be performed. In this case, the client request fails to obtain the page.

Check your services. If your website can be accessed by other means except for a browser, disable JavaScript anti-crawler protection.

Parent topic: Anti-Crawler Protection