Post #899703
2026-03-31 13:21 UTC
Replies (8)
-
@fooflington@infosec.exchange 2026-04-08 19:57
And it's now fixed! Thankyou @firefoxwebdevs@mastodon.social
-
@neilmadden@infosec.exchange 2026-04-01 07:45
@fooflington@infosec.exchange “there’s a problem with the site” for a 4xx error is really galling!
-
@preya@mastodon.social 2026-04-01 07:51
@fooflington@infosec.exchange Yeah, I've had this for a while, it's really annoying.
-
@tdp_org@mastodon.social 2026-04-01 08:09
@fooflington@infosec.exchange I assume Moz are looking to make error pages less confusing/intimidating for less technical users - which is probably reasonable. What's not reasonable is that this page gives wholly incorrect advice - "try again in a few moments" is not gonna work for a 403 or indeed any 4XX since they're all client/request errors. FWIW/tangentially related, I'd still love an "I'm technical, show me all the details" setting on web browsers/software/OSs.
-
@guenther@chaos.social 2026-04-01 08:19
@fooflington@infosec.exchange the cherry on top is that the wording of different parts of the UI is contradictory. When I visit a page on 127.0.0.1 (via plain http) that returns 404, it says that there's a problem with the website and that Firefox couldn't connect. The security shield icon in the URL bar shows a check mark though, and if i click it, it says there's a connection error and if I click that error, it says that I'm connected securely.
-
@lennybacon@infosec.exchange 2026-04-01 09:14
@fooflington@infosec.exchange @firefoxwebdevs@mastodon.social can probably help. Hopefully.
-
@mjog@eigenmagic.net 2026-04-01 12:28
@fooflington@infosec.exchange DO NOT QUESTION THE FIREFOX AI MARKETING CEOS
-
@kim@fedi.social 2026-04-01 13:02
@fooflington@infosec.exchange Must be a problem with the 'signal' (in the way it's used by non-technical people as a catch-all term for anything network-related sense), I suppose...