Matthew Slowe

@[email protected]
256 Followers
356 Following
264 Posts

πš†πšŠπš”πšŽπš„πš™: πš•πšπš› πš›πŸΆ, 𝟢𝚑𝚌𝟢𝚏𝚏𝚎𝚎; πš‹πš• πšπš›πš’πš—πš”; πš–πš˜πšŸ πš™πšŒ,πš•πš›; /* πš…πš’πšŽπš πšœ πšŠπš›πšŽ πš–πš’πš—πšŽ πš—πš˜πš πš–πš’ πšŽπš–πš™πš•πš˜πš’πšŽπš›'𝚜. */


Working in IT to help HE & FE (and other public sector) organisations work better together.


Somewhere in the vicinity of the far South East of #England
 and occasionally in the farther reaches of #Scotland

#photography #kent #highlands #linux #federation #eduroam #shibboleth #saml #itsecurity #highereducation #academia

And it pains me to need to say that I do not consent to any third-party Mastodon or other fediverse instance's Terms of Service, as I am not a user of their service. All posts are my own, and permission to propagate them is always revocable.

Homepagehttps://mafoo.org.uk/
PGP/GPG fingerprint8DFB 9F42 93A2 44C0 24AD 1F4B 6BE0 CF7D 0460 0314
Pixabayhttps://pixabay.com/users/fooflington-13730829/
ORCiDhttps://orcid.org/0000-0003-0219-5908
Show threadMatthew Slowe16h ago

@kim yeah, but the wording is, therefore, too specific ;-) Thankfully, Firefox have picked it up and are in the process of fixing!

https://mastodon.social/@firefoxwebdevs/116328865917464238

Matthew Slowe19h ago
Show threadFirefox for Web Developers19h ago

@lennybacon @fooflington https://bugzilla.mozilla.org/show_bug.cgi?id=2023800#c14 - the fix is in the process of being uplifted to 149.

Thanks for pinging me on this! But it looks like a fix will land in 149 (and 150) soon.

2023800 - New certificate error pages contain misleading information on http errors

RESOLVED (jbrown) in Firefox - Security. Last updated 2026-04-01.

Show threadMatthew Slowe19h ago

@noratrieb while most of what you have said is true, if the messaging is to remain, it needs some nuance adding about what the cause of the error actually is as it's currently factually wrong.

I disagree that the client (the User Agent, in this case the browser) is "part of the website".

Matthew Slowe19h ago
Show threadFirefox for Web Developers19h ago
@lennybacon @fooflington looking into it. It's fixed in Nightly.
Show threadMatthew Slowe19h ago
@firefoxwebdevs Brilliant, thankyou
Show threadMatthew Slowe19h ago

@noratrieb @tdp_org except that's not what 4xx errors are…

RFC 2616 defines 4xx errors as "Client errors", not "Server errors" (which are the 5xx set):

The 4xx class of status code is intended for cases in which the client seems to have erred

The problem is with the client. Resubmitting the same request is not expected to change the result.

https://datatracker.ietf.org/doc/html/rfc2616#section-10.4

RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1

HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1", and is an update to RFC 2068. [STANDARDS-TRACK]

IETF Datatracker
Show threadMatthew Slowe20h ago
@guenther oh, joy!
Matthew Slowe20h ago
Show threadNeil Craig20h ago

@fooflington 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.

Show threadMatthew Slowe21h ago

@neilmadden yes! It took me a moment to realise it wasn't telling me the whole truth…!

"Something went wrong" would have been better words… but I still want to know what's going on underneath, even if it's on a "Show more..." button.

Show threadMatthew Slowe21h ago
@Edent it's migrated down under