It’s like a health check. When you hit /api/health/ it probably doesn’t report all the details like number of users created today, count of files in the S3 bucket, whatever. It checks that shit’s basically working, it heard your request, and now everything is 200 OK.
(No, you can’t return a 204 no content in this metaphor because that’s not what the client is expecting. If they don’t get a 200 back, they’re going to think something is wrong and investigate.)
I’m just assuming some of you are like backend developers and this metaphor will make sense to you.
It’s like a health check. When you hit /api/health/ it probably doesn’t report all the details like number of users created today, count of files in the S3 bucket, whatever. It checks that shit’s basically working, it heard your request, and now everything is 200 OK.
(No, you can’t return a 204 no content in this metaphor because that’s not what the client is expecting. If they don’t get a 200 back, they’re going to think something is wrong and investigate.)
I’m just assuming some of you are like backend developers and this metaphor will make sense to you.
How do I return a 403 to the person asking
I prefer the 418 response
“I am not allowed to tell you”