I keep telling you! Chrome can sometimes hide an HTTP 500 ClassNotFound error!!
-
-
Maybe we should just all use a web server that already does that, like IIS.
-
That the browser shouldn't break stuff without consulting me. I want my users to report that error they saw to me so I can go into the logs and see what was wrong. But an error that says "Oh, there was an error! Sorry! Won't tell you what it is!" isn't very helpful.
That also does nothing to improve UX over a simple page that literally says the word "Error." Except one is prettier. And I'm pretty sure my users
- Understand the meaning of the word "error"
- Don't understand HTTP status codes
- Won't cry if the goddamn motherfucking error page isn't pretty with clickable buttons, since that does literally, completely, totally, and entirely nothing to solve the problem.
-
504 vs 500 vs 502 vs 510 doesn't actually matter if you don't control the server.
Well, 504 might go away after a refresh, 500 means it likely won't work until a team of highly trained monkeys gets to it.
Nobody knows what "Sorry!" means other than something bad happened.
Well, here's a 404 from my work portal:
Here's one from IE6:
And one from the newer IE:
I'll let you figure out which one is more informative to someone who stumbles upon it.
-
Defend THAT.
There's no defense at all. You should've included a humorous quote from a book or something.
-
the browser shouldn't break stuff without consulting me.
So basically, you can't test, don't understand usability, and don't monitor prod for errors... and it's Chrome's problem?
I found TR
-
But an error that says "Oh, there was an error! Sorry! Won't tell you what it is!" isn't very helpful.
Yeah, except that's not what happens.
And either way, your logs give you the exact fucking info you need. All you need from the user is to tell you to look into the logs, and if you're getting 500s, then you shouldn't even need that.
-
Oh yeah, let's tear this up:
- retyping the address:
- That doesn't solve a 404. What? - go back
- That's what the user will most likely do anyway.
- go back, except less helpful
- Already covered.
- retyping the address:
-
Okay, but now it's my server. And I don't want friendly errors, EVER. I love bad UX. I hate users, and I want all of my users to die and my company to fail. Now what?
I believe the only possible answer is stop programming forever, which I already posted near the top of the thread.
-
Yep!
-
But I'm my only user, and I don't want to delve into the logs until I know what the fuck I'm looking for.
-
I want my users to report that error they saw to me
99.999999999999999999999999999999999999% of users will just go "" and go to a different site; they won't hang around long enough to even notice there's an e-mail link, let alone click on it.
-
I believe I told you to go skewer yourself on the space needle to help cleanse the gene pool. How's progress on that?
-
So then:
No UX improvement either way.
Oh.
-
-
retyping the address:That doesn't solve a 404. What?
If you typed the address in from like a magazine or something, then yes it might.
But I'm my only user
Then I have no idea why you have a website at all. Some mental masturbation thing?
-
No, more like physical. But close.
-
Okay, I have decided everyone in this thread that disagrees with me has never programmed once in their entire lifetime, and is dumb. Muted.
-
99.999999999999999999999999999999999999% of users will just go "
" and go to a different site; they won't hang around long enough to even notice there's an e-mail link, let alone click on it.If he had an email link and instructions on what to email, he'd probably push the page over 512 bytes and this would all be a non-issue.
Maybe that's why Chrome implemented it, to filter out the laziest of the lazy.
-
It costs like $35 to go up the Space Needle and I don't have a debit card.
-
You still haven't addressed @ChrisH's "maintenance notification" pages.
-
Correct.
-
It costs like $35 to go up the Space Needle and I don't have a debit card.
Surely there's a bridge nearby that you could set up shop under.
-
Because it's a valid example of where your shitty friendly error pages are wrong?
-
For example, they could (gasp!) TALK TO the developers of Chrome and/or IE and find out the criteria for a good error message, then implement one. Or alternatively, try to convince those developers that their own error messages are sufficient and disable the feature.
Talking to people!? But I R open sourrcezzz! I live in BASEMENT and write WEB SERVER!!! PEOPLE SCARE ME GASP!!!
It's not like Microsoft itself does a much better job at it. This is the default error message produced by IIS 8.5:
This is Apache's:
Both indicate that something could not be found, Microsoft's page just looks a bit more pretty.
-
401 (you dun goofed up the password), 403 (get yourself a higher clearance level), 404/410 (you either typoed the URL or we took this down, in either case don't keep trying), 429 (please chill the fuck out)...
Just so you know, I am TOTALLY stealing this and passing it off as my own cleverness now.
-
I totally didn't push the like button because of the space between the words "Love" and "You".
-
-
But I'm my only user,
In that case, turn it off on your own client yourself. Don't shit it up for the rest of the world.
-
I want my users to report that error they saw to me so I can go into the logs and see what was wrong.
Imagine if there was a way of you getting a report of which error they got, without them having to do it, regardless of what error the user gets. JUST IMAGINE!
Oh, wait...
-
Microsoft's also attempts (and note I'm not saying it's PERFECT GODLY GOODNESS or anything) to explain why the URL wasn't found.
But neither of them go into "what can you do about it", which the default IE one does. Even if its suggestions aren't perfect.
-
Imagine if there was a way of you getting a report of which error they got, without them having to do it, regardless of what error the user gets. JUST IMAGINE!
As far as my company's web app is concerned I prefer the browser not get friendly errors mainly because most of the clients are not savvy enough to find the log file with the error, which means I have to GoToMeeting with them and find it for them, and that takes up time I don't have.
-
You're right, Blakey. The error messages that web servers return by default could be much more user friendly than they right now.
However, any decent website has its own error page which is generally more useful: some offer a 'did you mean?' page with search results, others present a list of categories, you'll find some funny images, and so on.
Except if you're a Discodev, then you simply shift the blame to the visitor and overload them with stuff like /latest.json (whatever that might be).
-
Both indicate that something could not be found, Microsoft's page just looks a bit more pretty.
Sure, if you know what 404, URL and server mean. Otherwise it's "thing not found. Try some things" vs "thing not found thing on the thing is thing".
-
Our local firetruck is #404. When we see it driving around, we yell, "Firetruck 404, firetruck not found!"
-
Use the "Custom ASP Errors" feature in IIS 5.0 to pad the response that the server sends with enough characters to override the friendly error messages.
What the fuck is wrong with Microsoft. WHY WOULD YOU DO THAT!
-
I can't speak for Microsoft, but some companies like to add a bit of style to their error pages
-
If GitHub does it, it must be a hipster thing that no real developer would ever implement on a project.
<inb4 whoosh
-
-
Like Markdown?
-
Our local firetruck is #404. When we see it driving around, we yell, "Firetruck 404, firetruck not found!"
Major freeway close to me:
-
Yes, like Markdown.
-
Both indicate that something could not be found, Microsoft's page just looks a bit more pretty.
Meh. HomeStar Runner got it best:
http://www.homestarrunner.com/sbemail2000.html
-
