My static site is hosted through Cloudflare and I've found that the service bumps captchas by screenshoting them instead of the actual page. I tried to write a rule to explicitly allow requests from this service to bypass the protection. But I came across the fact that from the systems point of view these requests are practically no different from requests from other bots:
It would be nice to change at least the User-Agent to something that explicitly identifies the service as a screenshot robot, maybe 11tyScreenshoter or something. This would make Cloudflare cool its heels and make it easier to detect and filter all requests with this User-Agent as explicitly allowed by custom rules.
My static site is hosted through Cloudflare and I've found that the service bumps captchas by screenshoting them instead of the actual page. I tried to write a rule to explicitly allow requests from this service to bypass the protection. But I came across the fact that from the systems point of view these requests are practically no different from requests from other bots:
It would be nice to change at least the User-Agent to something that explicitly identifies the service as a screenshot robot, maybe
11tyScreenshoteror something. This would make Cloudflare cool its heels and make it easier to detect and filter all requests with this User-Agent as explicitly allowed by custom rules.