Those who frequently browse the website should often encounter a reminder of a real person test. Recently, I received a question asking me how to remove this prompt, so I also studied this “real person detection” in particular. This is a feature of CloudFlare. Basically, everyone sees this prompt when visiting a site. Almost all use CloudFlare. Today I will tell you about this thing in detail!
This “real person detection” is called [Browser Integrity Check] in CloudFlare, and the switch position is in the background of CloudFlare [Security].
To sum up, we know that [Browser Integrity Check] is actually CloudFlare’s protection rule measures to prevent “malicious behavior”, mainly for some automatic programs, malicious crawlers, and user agents. In theory, I generally recommend to enable this option. In fact, strictly speaking, this [Browser Integrity Check] does not affect the browsing experience of front-end visitors very much, because it is generally aimed at first-time visitors, and does not appear every visit, unless the site owner alone Mandatory in the rules.
However, the reality is that many overseas sites seem to require visitors to [Browser Integrity Check], even very frequently. It is actually very simple to solve this problem. CloudFlare itself has given a prompt in the background [Browser Integrity Check] switch position.
You can see that there is a [Privacy Pass Support] switch under [Browser Integrity Check], read the introduction carefully: “Privacy Pass is a browser extension developed by the Privacy Pass team to improve the browsing experience of visitors .enabling Privacy Pass will show fewer CAPTCHAs to visitors.”, Got it? You only need to install an extension called Privacy Pass for your browser. It is available in the official extension library of Chrome and Edge, which can be easily searched and installed. Basically keep the default, no need for too many settings, unless you have special needs:
If you need it, you can try it. Of course, the site owner can also directly disable the Privacy Pass extension support in the CloudFlare background to stop this blocking behavior on the front end. It is very flexible according to your own needs.
