[NFBCS] Website and browser question

[Brian Shell]

I thought the opposite was true where Firefox is the only major browser 
that is not Chromium-based.  This sounds like name resolution or maybe 
it is resolving and the connection is getting blocked elsewhere.  If the 
error mentions anything like name or can't find or resolve then it's 
DNS.  If it mentions a time out or connection refused, then something 
has blocked the traffic.  Firefox has DNS-over-HTTPS enabled by default 
which could make it resolve differently.  I think they forward to 
Cloudflare to determine if the website is safe.  It could also be 
security protection on your machine blocking the site although I'd 
expect it to trigger on Chrome too.  Maybe it's Firefox address bar 
automatic search feature trying to "help" by sending to a search engine 
which you can prevent by including the https:// in front of the website 
address.

On 2/18/2026 8:46 AM, Tracy Carcione via NFBCS wrote:
>
> If I go to knitpicks.com using Firefox, it loads just fine, but, if I 
> go to the same site using Chrome, it gives me a network error and 
> tells me to check the spelling. And, if I put knitpicks into Google 
> search and click on an ad, I get a network error again.
>
> Why?  I thought Chrome and Firefox use the same underlying engine, so 
> why do I get such different results?
>
> Just curious.
>
> Tracy
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/shellbr%40runbox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260218/33eee1f4/attachment.htm>