Since this seems to be an on-going problem at this time, this topic aims to provide a summary and “current status” regarding CloudFlare and its promise they “aren’t in the business of claiming any browser is more legitimate than another” handling of their Captcha/turnstile pages.
Start of the issue
On Jan 31st, users reported that, similar to an occurrence in 2022, CloudFlare’s captcha/”i’m under attack” mode had started failing and looping instead of passing and letting browser users through. It soon became clear that this time, any UXP browser wasn’t the only being denied access to the sites being “protected” by CloudFlare. Even Firefox ESR 115 was affected.
The community was quick to respond, opening a CloudFlare community thread explaining the problem (which is the only communications channel available to end users, see below) and reporting the issue.
Assuming Mozilla applied corporate pressure for Firefox ESR, CloudFlare changed its captcha scripting soon after which, in turn, exposed a crash issue in UXP by triggering a situation that was not initially accounted for in JavaScript and would not normally
1 Comment
mimasama
Despite a long working relationship between Pale Moon and Cloudflare in the past, the latter refuses to disclose to the browser developers the 2 particular JavaScript functions required by CF's browser check.