- From: Chuck Houpt <chuck@habilis.net>
- Date: Mon, 12 Aug 2024 08:32:25 -0400
- To: "James R. Haigh (+ML.W3.Validator subaddress)" <JRHaigh+ML.W3.Validator@Runbox.com>
- Cc: www-validator@w3.org
> What needs to be done to fix this problem? What is the Validator now using JavaScript for? And how can we make this usage of JavaScript /optional/ again? I'm going to guess that the issue isn't the Validator itself, but its web-host/CDN Cloudflare. A few years back, the Validator switched to using Cloudflare to protect it from DDoS attacks and over-zealous checker scripts. When Cloudflare thinks there's "too much" traffic from one source, it will put up a CAPTCHA challenge page. Unfortunately, the challenge page usually requires Javascript as well as other popular-browser features. Thus text-browsers often can't complete the challenge. I'm currently able to use the Validator with a text-browser from a pedestrian consumer IP address. I image I'd be blocked by a challenge page if I accessed it from a high-traffic network, like a VPN, datacenter, etc. - Chuck
Received on Monday, 12 August 2024 12:32:41 UTC