Today, collaboration used error 550 with the delete action, when the user does not have permission, which at first looked bad, because, as I know, this error looks like a client (aka 4xx) error for me, not a server (aka 5xx).
When looking at the description, it suggests exactly that it was used correctly. Instead of error 401, which I used to use with some "problems".
Problem with error 401: if user A is logged in and is trying to perform an action that returns 401, he may assume that you should "log in" because you do not have valid credentials to access this HTTP resource. The problem with this approach is that if the user is registered, the server knows that he does not have permission, in this case he looks like more suitable, but it does not quite seem to me that in this case you should use the 550 error script.
Question: What is the correct use (if any) of 550 errors in web applications. I understand that this is used when using FTP and SMTP relays. If any registered user sends an action request that is not allowed, what error should be returned?
Thanks!
source share