Quoted post unavailable.
Because it works super great at throttling malicious traffic and solves a hard problem real site admins have.
Firefox appears to be flagged as suspicious by Cloudflare
61–70 of 191 posts
Re: Firefox appears to be flagged as suspicious by Cloudflare
#62Earlier quoted context omitted.
Really? I'm a firefox user too and whilst I occasionally bump into some situation as you describe where I need to hop onto Chrome, I genuinely can't remember the last time this happened. Nope, actually - sometime last year, with some poorly-coded gig ticket purchase thing, if I remember right. I was able to check the code and amend some stupid niggle in WebDev tools to get around it. Not saying I should have to accep…
Often, just changing the user agent string so that Firefox appears to be Chrome will let those sites work. I.e. they work fine in Firefox, but are restricted by user agent string checks to reject that browser and/or OS. There are several plugins for Firefox that make this easy.
I've used Firefox and Mozilla for what, 20 years? And I've never bumped into a situation like this. Some very clearly shit internal IT systems had pathetic IE requirements, but never one that said sorry go get chrome
Re: Firefox appears to be flagged as suspicious by Cloudflare
#63I mean, with that market share, popularity among open source fans... it's an easy group to target and filter oddballs. I'm a Firefox user and I'm used to this treatment at every step of the way, no matter if it's about software, airports, opening a bank account so I can receive a salary, etc. Fundamental things everyone wants to do are being made hard to do the right way. It's always anti privacy, anti self repair, a…
Really? I'm a firefox user too and whilst I occasionally bump into some situation as you describe where I need to hop onto Chrome, I genuinely can't remember the last time this happened. Nope, actually - sometime last year, with some poorly-coded gig ticket purchase thing, if I remember right. I was able to check the code and amend some stupid niggle in WebDev tools to get around it. Not saying I should have to accep…
Same, firefox works as it should for me.
Re: Firefox appears to be flagged as suspicious by Cloudflare
#64Tried it, didn't stop me viewing the page, no delay either
Re: Firefox appears to be flagged as suspicious by Cloudflare
#65Re: Firefox appears to be flagged as suspicious by Cloudflare
#66Maybe it's your IP. I tried it in Firefox and Edge. No problem
Re: Firefox appears to be flagged as suspicious by Cloudflare
#67Can confirm that I got that exact challenge only on Firefox at least a week ago, although only on one site. Still getting it now.
Re: Firefox appears to be flagged as suspicious by Cloudflare
#68I use Firefox Focus on my phone (opens links from apps in a private session - generally a great idea!) and always get this 5 second delay (which is often actually 10 or more seconds). I never considered that it's a Firefox-only thing!
Re: Firefox appears to be flagged as suspicious by Cloudflare
#69Earlier quoted context omitted.
Really? I'm a firefox user too and whilst I occasionally bump into some situation as you describe where I need to hop onto Chrome, I genuinely can't remember the last time this happened. Nope, actually - sometime last year, with some poorly-coded gig ticket purchase thing, if I remember right. I was able to check the code and amend some stupid niggle in WebDev tools to get around it. Not saying I should have to accep…
Often, just changing the user agent string so that Firefox appears to be Chrome will let those sites work. I.e. they work fine in Firefox, but are restricted by user agent string checks to reject that browser and/or OS. There are several plugins for Firefox that make this easy.
I wonder if those plugins are causing Firefox's marketshare to appear worse than it actually is.
Re: Firefox appears to be flagged as suspicious by Cloudflare
#70Earlier quoted context omitted.
> If they don't, the website is broken. The Internet is a network with social effects. Whether "this didn't work" means "the website is broken" or "the browser is broken" has always been more about end-user experience and the wisdom of crowds than a more concrete definition. A website broken only on Firefox works for 96.5% of users. I have personally had to make the hard judgment call (as a fan of Firefox!) to not sp…
That's too bad. If you didn't make that call it would probably have larger market share. What you've done actually feeds in to the problem.
But that's the issue. It's not my problem. My problem is maximizing the user experience for most of my users, and that involves squashing usability bugs common to all browsers and adding features that have been requested, not keeping up with the Gecko quirks-du-jour.
(Speaking of "quirks-du-jour", the problem eventually "solved itself." The next major iteration of Firefox fixed a rendering regression and resolved the bug. We "solved" the problem spending zero eng-hours on it; you can't beat that for efficiency. But that's the challenge Mozilla faces as an also-ran: burden's on them to keep up with the competition and make their rendering agent on-par with other agents for both performance and strangeness, because they lack the market clout to make developers bend to their flaws and oddities. No matter who the front runner is, there are always flaws and oddities.)