Hacker News new | ask | show | jobs
by geewee 699 days ago
To be fair, I can remember 0 times where as an API consumer I've needed to do different actions depending on whether it was a 401 or a 403 - but I also mainly deal in API->API communication.
2 comments

As an API provider, it is quite important for me to see if my app is spitting out tons of errors 401 or 403.
I have a production API where sending 401 immediately kills your session and you’re logged out. And 403 doesn’t. We have this as a result of race conditions where the front end incorrectly thinks it still has a valid session. But the back end knows better
I like the 401->autokick back to homepage pattern.