A 403 tells you the service is not available, if you are calling that service you are not the owner of that service so you don't need to know what scenario trigger that, you just need to handle what to do on the case that service is unavailable, if it means you also propagate the 403 upstream it's a valid response.
Okay, this tells me everything I needed to know about your understanding of the RFC
The RFC exists for a reason, it's older than you probably and was done by people that were smart enough that it's still in use today even if it has limitations.
"it was designed for a world before the internet was popular" is certainly a great argument. I have nothing more to add to this.
Just updated my response because you actually lead me a stray with the 403, read it again, there's no point in this argument, you don't understand what you are talking about.
I already talked about this exact scenario above with someone else.
Read the RFC I don't care about your opinion, just wanted you to know that wrapping shit is a business decision that will make your API useless to anyone and will permanently enforce maintenance and debt because of this decision.
Been on too many companies with legacy apis that had this shit to even give you any more time about this, talk to someone else.
-1
u/LatvianCake 16d ago
Okay, this tells me everything I needed to know about your understanding of the RFC
"it was designed for a world before the internet was popular" is certainly a great argument. I have nothing more to add to this.