If all the corporations can just stop trying to be cute in their error messages, that would be great. This is literally worse than “ERROR: Unknown Error” because this goes out of its way to taunt you while still giving you no actionable information.
Depends if this cure message is a psuedonym for the real message. Kind of you have a different quip for each one, then reporting it the Devs will know what the issue is but any bad actors won’t be able to try and discern cause and effect from any exploits they are trying (or at least make it harder)
If all the corporations can just stop trying to be cute in their error messages, that would be great. This is literally worse than “ERROR: Unknown Error” because this goes out of its way to taunt you while still giving you no actionable information.
I will say that at least it has an error code. So you can actually look it up
I see nothing wrong with it
How can the client know the back end issue
And
What’s the point of giving it to the end user
Any fix would be the user contacting the company and the error code is there. Follow ups would be a traceroute
Depends if this cure message is a psuedonym for the real message. Kind of you have a different quip for each one, then reporting it the Devs will know what the issue is but any bad actors won’t be able to try and discern cause and effect from any exploits they are trying (or at least make it harder)
security through obscurity is not security.
Didn’t say it was the best practice, but it is a practice