Post by @fooflington@infosec.exchange

2026-03-31 13:21 UTC

Latest #firefox #ESR (v149.0) appears to have stopped reporting the HTTP error code when something goes wrong… in this case for a 403. It used to include the HTTP code and some useful words. In this error, it looks like the connection just didn't work rather than we got an error from the server. Is there a way to turn this back on?

Replies (5)

@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!

Open ##2425671
@preya@mastodon.social 2026-04-01 07:51

@fooflington@infosec.exchange Yeah, I've had this for a while, it's really annoying.

Open ##2425673
@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.

Open ##2425674
@mjog@eigenmagic.net 2026-04-01 12:28

@fooflington@infosec.exchange DO NOT QUESTION THE FIREFOX AI MARKETING CEOS

Open ##2425692
@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...

Open ##2425693