Firefox error pages became unusable.
`authenticity of the received data could not be verified` my ass.
Server is down, no data sent. But, hey, neither `connection refused` nor`connection reset`, but `authenticity ... could not be verified`. Authenticity of what, exactly? Closed socket? orz.
That error message is not just useless it’s also misleading.
If I try to turn this vague wording into a technical explanation what I am getting is that an HTTP response has been received, but the authenticity of that response cannot be confirmed due to a TLS certificate error.
And that’s simply not how HTTPS works.
If a customer ever sent us a screenshot like that they would be told to use another browser. Unfortunately error messages in Chrome are also getting worse.
I was certainly not trying to diagnose what the error message means. I can see what the error message implies, and what it implies is incorrect. So as far as that error message goes, the problem could be anything.
Getting a useless error message telling you to contact the administrator is even worse when you are the administrator.
But my main point is that a browser needs to give a meaningful error message regardless of the technical level of the user. Because a user who doesn’t have the technical knowledge themselves can still take a screenshot and send it to somebody who does.
anparker
kasperd