this post was submitted on 09 Dec 2023
605 points (99.0% liked)

Programmer Humor

32710 readers
185 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 59 points 1 year ago (10 children)

Willing to bet that the backend that they are using doesn't actually give any useful error messages.

[–] [email protected] 14 points 1 year ago (8 children)

Would they surface that to the user anyway? That's something to log, not to tell the client that xyz service failed because of error 123.

[–] PixxlMan 12 points 1 year ago* (last edited 1 year ago) (1 children)

No, please tell the user. They've got their big boy pants on and can handle seeing one or two weird squiggles in the worst case, and might be able to actually diagnose and fix the issue themselves (without having to go through support) in the best case.

[–] [email protected] 12 points 1 year ago

If it’s a backend/service issue, tell the user, but the bare minimum. You shouldn’t disclose too much info about your system to the end user (think of stack traces, error codes unique to some dependency you’re using) as it may give an attacker some valuable information.

load more comments (6 replies)
load more comments (7 replies)