| ▲ | sli 3 hours ago |
| Every single website on the internet just says "whoopsie doodle, me made an oopsie" instead of just telling me what the problem is. This so-called mistake is so widespread that it has been the standard for at least a decade. I agree it's a mistake, but I don't believe that it's viewed that way by anyone making the decision to do it. |
|
| ▲ | oldestofsports 3 hours ago | parent [-] |
| You dont expose error details to the user for security reasons, even though it does indeed make the user experience worse. |
| |
| ▲ | falcor84 2 hours ago | parent [-] | | I understand not exposing a full stack trace, but I don't see any excuse to not even expose a googleable error code. If me having an error code makes your product insecure, then you have a much bigger problem. | | |
| ▲ | teaearlgraycold 2 hours ago | parent [-] | | I show the stack trace on AGPL projects. Why hide what they can already see for themselves? | | |
| ▲ | falcor84 2 hours ago | parent [-] | | The reason I see is that it might expose the value of secret keys or other sensitive variables. But if you are certain it won't happen, then yes |
|
|
|