Within our project we are using HTTP statuses to tell the client the state of their authentication. So when user is not logged in, the service will tell him 401. What is undesired is the fact that these will be logged in Google Chrome console looking like "There has been an error" whereas it is just "you are not logged in".
We also use other HTTP statuses like "Conflict", "Gone" and so – all of them raising errors in console. What would be the best practice in such case?
