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 troupo on Friday August 11, 2023 @09:08AM (#37088269)

The problem is, now I have to do this every time for shitty dumbed down apps.

Prime example: Twitter always responds "oops, something went wrong" even if the backend returns `{ error: "Video aspect ration is not allowed. Try 16:9" }`

[ Parent | on HN ]

Re:Browsers barely care what HTTP status code your web pages... by ryandrake on Friday August 11, 2023 @01:15PM (#37091161)

Those "oopsie-doopsie, website made a poopsie" infantilizing error messages are just awful. Tell the user 1. specifically what went wrong, 2. what, if anything, they can do to correct, and 3. a token (like an error message) that could be useful for tech support or reporting a bug.

People's heads aren't going to explode if you treat them like functioning adults.

[ Parent | on HN ]

Re:Browsers barely care what HTTP status code your web pages... by starttoaster on Saturday August 12, 2023 @12:19AM (#37097015)

You’ve just vastly overestimated the technical capabilities of most Twitter users.

[ Parent | on HN ]

Re:Browsers barely care what HTTP status code your web pages... by dwaite on Saturday August 12, 2023 @08:02PM (#37105300)

The meta conversation here is whether there was a decision to NOT give the user information on how to correct the problem - or if it was a process maturity, developer skill, or limited resources that caused the development to focus on the "happy path" only.

[ Parent | on HN ]