Browsers barely care what HTTP status code your web pages are served with

Re:Browsers barely care what HTTP status code your web pages... by CapsAdmin on Friday August 11, 2023 @02:21PM (#37092019)

Yeah this problem is a little more complicated than what I mentioned. By all means map known errors, but does the fallback really need to be "something went wrong?"

It was a bit of a rhetorical statement (or at least in my mind it was). Like how about "Something went wrong (see details)" or something to that effect?

In my work experience some people are really dogmatic about the idea of not showing any sort of error messages to users whatsoever.

[ Parent | on HN ]

Re:Browsers barely care what HTTP status code your web pages... by delecti on Friday August 11, 2023 @05:17PM (#37094153)

In my work experience, users will complain about any sort of message. We recently got a request to change a message of "OK" to something more detailed. What more do you want than a message telling you that the thing you were trying to do succeeded?

So I'm very sympathetic to people arguing against showing error messages.

[ Parent | on HN ]